Bug#575628: pxe not working with libvirt 0.7.7 + qemu-kvm 0.12
This issue has been fixed in upstream with a patch here: http://lists.gnu.org/archive/html/qemu-devel/2010-04/msg00377.html I rebuild qemu-kvm package with the patch and PXE boot works again for me.
Bug#575628: pxe not working with libvirt 0.7.7 + qemu-kvm 0.12
28.04.2010 11:00, Konstantin Stepanyuk wrote: This issue has been fixed in upstream with a patch here: http://lists.gnu.org/archive/html/qemu-devel/2010-04/msg00377.html http://git.debian.org/?p=collab-maint/qemu-kvm.git;a=commit;h=8737e37ee07e1ac66db44a4d0908356ebd6b48b3 I applied that patch about 3 weeks ago to my local git tree did not push it at that time. Note the bug is tagged pending upload for this reason. I rebuild qemu-kvm package with the patch and PXE boot works again for me. Actually it's time to upload new release I think, amount of fixes grows at http://git.debian.org/?p=collab-maint/qemu-kvm.git . I were waiting for new upstream stable release that incorporates all this and more, but apparently that's just too long a delay. Thanks! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575628: [Pkg-libvirt-maintainers] Bug#575628: pxe not working with libvirt 0.7.7 + qemu-kvm 0.12
On Sat, Mar 27, 2010 at 02:15:45PM -0500, Brian Kroth wrote: Package: libvirt-bin, qemu-kvm Severity: important Attempts to PXE boot with these two versions give the following error message: # virsh start faitest32 error: Failed to start domain faitest32 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/1 Cannot boot from non-existent NIC From /var/log/libvirt/qemu/faitest32.log: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/local.hd/users/bpkroth USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name faitest32 -uuid 2b09b863-c3ca-a819-8580-4763a3fdd61d -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/faitest32.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot dnc -drive if=none,media=cdrom,id=drive-ide0-1-0,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/home/vms/images/faitest32/faitest32.img,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/home/vms/images/faitest32/faitest32-2.img,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1 -device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:a1:90:92,bus=pci.0,addr=0x4 -net tap,fd=56,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 0.0.0.0:0,password,tls,x509=/etc/pki/libvirt-vnc -k en-us -vga vmware -device i6300esb,id=watchdog0,bus=pci.0,addr=0x7 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 char device redirected to /dev/pts/1 Cannot boot from non-existent NIC Could you try to add execute this by hand and find the offending option? -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575628: [Pkg-libvirt-maintainers] Bug#575628: pxe not working with libvirt 0.7.7 + qemu-kvm 0.12
Guido Günther a...@sigxcpu.org 2010-03-28 14:53: On Sat, Mar 27, 2010 at 02:15:45PM -0500, Brian Kroth wrote: Package: libvirt-bin, qemu-kvm Severity: important Attempts to PXE boot with these two versions give the following error message: # virsh start faitest32 error: Failed to start domain faitest32 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/1 Cannot boot from non-existent NIC From /var/log/libvirt/qemu/faitest32.log: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/local.hd/users/bpkroth USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name faitest32 -uuid 2b09b863-c3ca-a819-8580-4763a3fdd61d -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/faitest32.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot dnc -drive if=none,media=cdrom,id=drive-ide0-1-0,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/home/vms/images/faitest32/faitest32.img,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/home/vms/images/faitest32/faitest32-2.img,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1 -device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:a1:90:92,bus=pci.0,addr=0x4 -net tap,fd=56,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 0.0.0.0:0,password,tls,x509=/etc/pki/libvirt-vnc -k en-us -vga vmware -device i6300esb,id=watchdog0,bus=pci.0,addr=0x7 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 char device redirected to /dev/pts/1 Cannot boot from non-existent NIC Could you try to add execute this by hand and find the offending option? -- Guido Yeah, I did that. It's as the other bug I linked said. Basically, libvirt changed the way it arranges the command lines from the XML so that what was this in =0.7.5: -net nic,macaddr=52:54:00:a1:90:92,vlan=0,model=virtio,name=virtio.0 -net tap,fd=22,vlan=0,name=tap.0 became this in 0.7.7 (possibly also 0.7.6): -device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:a1:90:92,bus=pci.0,addr=0x4 -net tap,fd=23,vlan=0,name=hostnet0 The problem appears to be that qemu 0.12.3 (possibly for earlier versions as well) doesn't parse the -device virtio-net... option as being a NIC, so it fails to boot from it. I have tried this with other NIC models as well and they all result in the same problem - if the NIC definition is given as a -device instead of a -net nic, then qemu refuses to boot from it. Luckily I had a previous version of libvirt and company lying around on a mirror server at work so I was able to revert that and get back to my PXE booting. I couldn't find previous versions (0.11.1+dfsg-1 is where I was) for the qemu-kvm package to see if this still happened there. I'll also note that libvirt 0.7.7 rearranges the XML so that the address... blocks always appear, so I don't think it's possible to convince it to go back to using the -net nic style of arguments. Brian signature.asc Description: Digital signature
Bug#575628: [Pkg-libvirt-maintainers] Bug#575628: pxe not working with libvirt 0.7.7 + qemu-kvm 0.12
Brian Kroth wrote: Guido Günther a...@sigxcpu.org 2010-03-28 14:53: [] Could you try to add execute this by hand and find the offending option? -- Guido Yeah, I did that. It's as the other bug I linked said. Basically, libvirt changed the way it arranges the command lines from the XML so that what was this in =0.7.5: -net nic,macaddr=52:54:00:a1:90:92,vlan=0,model=virtio,name=virtio.0 -net tap,fd=22,vlan=0,name=tap.0 became this in 0.7.7 (possibly also 0.7.6): -device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:a1:90:92,bus=pci.0,addr=0x4 -net tap,fd=23,vlan=0,name=hostnet0 The problem appears to be that qemu 0.12.3 (possibly for earlier versions as well) doesn't parse the -device virtio-net... option as being a NIC, so it fails to boot from it. I have tried this with other NIC models as well and they all result in the same problem - if the NIC definition is given as a -device instead of a -net nic, then qemu refuses to boot from it. Very good findings. It appears to be a kvm bug after all, -- I don't see a way to tell it to boot from network with -device..-net pair, only with -net..-net pair. Confirmed. I'll check this in more detail. Thanks! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575628: pxe not working with libvirt 0.7.7 + qemu-kvm 0.12
Package: libvirt-bin, qemu-kvm Severity: important Attempts to PXE boot with these two versions give the following error message: # virsh start faitest32 error: Failed to start domain faitest32 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/1 Cannot boot from non-existent NIC From /var/log/libvirt/qemu/faitest32.log: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/local.hd/users/bpkroth USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name faitest32 -uuid 2b09b863-c3ca-a819-8580-4763a3fdd61d -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/faitest32.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot dnc -drive if=none,media=cdrom,id=drive-ide0-1-0,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/home/vms/images/faitest32/faitest32.img,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/home/vms/images/faitest32/faitest32-2.img,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1 -device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:a1:90:92,bus=pci.0,addr=0x4 -net tap,fd=56,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 0.0.0.0:0,password,tls,x509=/etc/pki/libvirt-vnc -k en-us -vga vmware -device i6300esb,id=watchdog0,bus=pci.0,addr=0x7 -watchdog-action reset -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 char device redirected to /dev/pts/1 Cannot boot from non-existent NIC # virsh dumpxml faitest32 domain type='kvm' namefaitest32/name uuid2b09b863-c3ca-a819-8580-4763a3fdd61d/uuid memory524288/memory currentMemory524288/currentMemory vcpu1/vcpu os type arch='i686' machine='pc-0.12'hvm/type boot dev='cdrom'/ boot dev='network'/ boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='cdrom' driver name='qemu' type='raw'/ target dev='hdc' bus='ide'/ readonly/ address type='drive' controller='0' bus='1' unit='0'/ /disk disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/home/vms/images/faitest32/faitest32.img'/ target dev='vda' bus='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x05' function='0x0'/ /disk disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/home/vms/images/faitest32/faitest32-2.img'/ target dev='vdb' bus='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x06' function='0x0'/ /disk controller type='ide' index='0' address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='52:54:00:a1:90:92'/ source bridge='br2'/ model type='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /interface serial type='pty' target port='0'/ /serial console type='pty' target port='0'/ /console input type='mouse' bus='ps2'/ graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' keymap='en-us'/ video model type='vmvga' vram='9216' heads='1'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video watchdog model='i6300esb' action='reset' address type='pci' domain='0x' bus='0x00' slot='0x07' function='0x0'/ /watchdog /devices /domain This is similar to the following report: http://www.mail-archive.com/libvir-l...@redhat.com/msg21531.html # dpkg -l | egrep -i 'qemu-kvm|libvirt-bin' ii libvirt-bin 0.7.7-1 the programs for the libvirt library ii qemu-kvm0.12.3+dfsg-4 Full virtualization on x86 hardware Let me know if you need any other info. Thanks, Brian signature.asc Description: Digital signature
