Description of problem: When trying to install on a freshly F20 dom0 a guest without the --network option I get errors arising from the fact that NAT does not seem to be automatically enabled. Version-Release number of selected component (if applicable): [root@tst035 ~]# rpm -qa | grep libvirt libvirt-daemon-driver-network-1.1.3.1-2.fc20.x86_64 libvirt-daemon-config-network-1.1.3.1-2.fc20.x86_64 libvirt-daemon-config-nwfilter-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-nwfilter-1.1.3.1-2.fc20.x86_64 libvirt-glib-0.1.7-2.fc20.x86_64 libvirt-daemon-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-qemu-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-libxl-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-uml-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-secret-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-storage-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-vbox-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-nodedev-1.1.3.1-2.fc20.x86_64 libvirt-client-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-lxc-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-interface-1.1.3.1-2.fc20.x86_64 libvirt-daemon-driver-xen-1.1.3.1-2.fc20.x86_64 libvirt-python-1.1.3.1-2.fc20.x86_64 libvirt-1.1.3.1-2.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. virt-install --name F20-64 --ram 768 --file=/dev/sdb --location=http://192.168.102.1/tftpboot/lab/tst031/f20 2. 3. Actual results: [root@tst035 log]# virt-install --name F20-64 --ram 768 --file=/dev/sdb --location=http://192.168.102.1/tftpboot/lab/tst031/f20 Starting install... Retrieving file .treeinfo... | 2.2 kB 00:00:00 !!! Retrieving file vmlinuz... | 9.8 MB 00:00:00 !!! Retrieving file initrd.img... | 65 MB 00:00:00 !!! ERROR End of file while reading data: Input/output error Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect xen:/// start F20-64 otherwise, please restart your installation. Expected results: [root@tst035 log]# virt-install --name F20-64 --ram 768 --file=/dev/sdb --location=http://192.168.102.1/tftpboot/lab/tst031/f20 Starting install... Retrieving file .treeinfo... | 2.2 kB 00:00:00 !!! Retrieving file vmlinuz... | 9.8 MB 00:00:00 !!! Retrieving file initrd.img... | 65 MB 00:00:00 !!! Additional info: libvirtd when run in debug mode shows: libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virDomainCreateXML:2016 : conn=0x7f11cc000a80, xmlDesc=<domain type="xen"> libvirtd: <name>F20-64</name> libvirtd: <uuid>00c86a18-6290-4650-bad5-13525b16dc17</uuid> libvirtd: <memory>786432</memory> libvirtd: <currentMemory>786432</currentMemory> libvirtd: <vcpu>1</vcpu> libvirtd: <os> libvirtd: <type arch="x86_64">linux</type> libvirtd: <kernel>/var/lib/xen/virtinst-vmlinuz.CktfGE</kernel> libvirtd: <initrd>/var/lib/xen/virtinst-initrd.img.05pRsP</initrd> libvirtd: <cmdline>method=http://192.168.102.1/tftpboot/lab/tst031/f20</cmdline> libvirtd: </os> libvirtd: <on_poweroff>destroy</on_poweroff> libvirtd: <on_reboot>destroy</on_reboot> libvirtd: <on_crash>destroy</on_crash> libvirtd: <devices> libvirtd: <disk type="block" device="disk"> libvirtd: <source dev="/dev/sdb"/> libvirtd: <target dev="xvda" bus="xen"/> libvirtd: </disk> libvirtd: <interface type="network"> libvirtd: <source network="default"/> libvirtd: <mac address="00:16:3e:ed:39:15"/> libvirtd: </interface> libvirtd: <input type="mouse" bus="xen"/> libvirtd: <graphics type="vnc" port="-1" keymap="en-us"/> libvirtd: <video> libvirtd: <model type="cirrus"/> libvirtd: </video> libvirtd: </devices> libvirtd: </domain> libvirtd: , flags=0 libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virObjectRef:293 : OBJECT_REF: obj=0x7f11d4178aa0 libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virObjectRef:293 : OBJECT_REF: obj=0x7f11f7094fc0 libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virAccessManagerCheckDomain:231 : manager=0x7f11f7094fc0(name=stack) driver=xenlight domain=0x7f11c4008400 perm=2 libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virAccessManagerCheckDomain:231 : manager=0x7f11f70963e0(name=none) driver=xenlight domain=0x7f11c4008400 perm=2 libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virAccessManagerCheckDomain:231 : manager=0x7f11f7094fc0(name=stack) driver=xenlight domain=0x7f11c4008400 perm=4 libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virAccessManagerCheckDomain:231 : manager=0x7f11f70963e0(name=none) driver=xenlight domain=0x7f11c4008400 perm=4 libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x7f11f7094fc0 libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virObjectNew:199 : OBJECT_NEW: obj=0x7f11c4002ba0 classname=virDomainObj libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virObjectNew:199 : OBJECT_NEW: obj=0x7f11c4004fe0 classname=libxlDomainObjPrivate libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virDomainObjNew:2063 : obj=0x7f11c4002ba0 libvirtd: 2013-12-06 17:43:58.970+0000: 2186: debug : virObjectRef:293 : OBJECT_REF: obj=0x7f11d4178aa0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virObjectRef:293 : OBJECT_REF: obj=0x7f11d4178aa0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x7f11d4178aa0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: error : libxlMakeNic:889 : internal error: libxenlight does not support network device type network libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x7f11d4178aa0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virObjectRef:293 : OBJECT_REF: obj=0x7f11c4002ba0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x7f11c4002ba0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x7f11c4002ba0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x7f11c4002ba0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virDomainObjDispose:2029 : obj=0x7f11c4002ba0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x7f11c4004fe0 libvirtd: 2013-12-06 17:43:58.971+0000: 2186: debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x7f11c4004fe0 libvirtd: ====== end of log =====
When I try to do this using virt-manager I get this: Unable to complete install: 'End of file while reading data: Input/output error' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1959, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 389, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 454, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: End of file while reading data: Input/output error The libvirtd message is the same: libxlMakeNic:889 : internal error: libxenlight does not support network device type network
Currently, the libxl driver only supports interface types 'bridge' and 'ethernet'. From libxlMakeNic() in src/libxl/libxl_conf.c switch (l_nic->type) { case VIR_DOMAIN_NET_TYPE_BRIDGE: if (VIR_STRDUP(x_nic->bridge, l_nic->data.bridge.brname) < 0) return -1; /* fallthrough */ case VIR_DOMAIN_NET_TYPE_ETHERNET: if (VIR_STRDUP(x_nic->script, l_nic->script) < 0) return -1; break; default: virReportError(VIR_ERR_INTERNAL_ERROR, _("libxenlight does not support network device type %s"), virDomainNetTypeToString(l_nic->type)); return -1; }
This is fixed in F21.