fix(drivers): boot port must always use network-type interface

LibvirtPoolDriver.create_machine() applied the hypervisor's own
network_type (bridge/network) to the initial boot-network port. The
boot network is always a plain libvirt virtual network regardless of
the hypervisor's main network type, so on a bridge-type hypervisor
libvirt tried to treat the boot network's name as a literal host
bridge device name and rejected it as too long for IFNAMSIZ.

attach_port(), used for the real port attached later, is unaffected
and continues to honor network_type.

Author: VasilyStepanov

exordos_core/compute/pool/drivers/libvirt.py

@@ -1269,9 +1269,13 @@ def create_machine(
                 mac=port.mac,
                 rom=self._spec.iface_rom_file,
                 mtu=self._spec.iface_mtu,
-                # TODO(akremenetsky): This parameter should be taken from
-                # the network
-                iface_type=self._spec.network_type,
+                # The port a machine is created with is always the transient
+                # boot network (see pool.py's MetaMachine.dump_to_dp), which
+                # is always a plain libvirt virtual network - never the
+                # hypervisor's own (possibly bridge-type) main network. The
+                # real port replaces it later via attach_port(), which does
+                # use self._spec.network_type.
+                iface_type="network",
                 source=port.source,
             )