[libvirt] libvirt 0.7.5 vs qemu 0.12.1 imcompatability?
The update from qemu 0.11.0 to qemu 0.12.1 in the virt-preview repository seems to have broken things. Starting a VM now just gives me a blank screen and a log which says: Option 'ipv4': Use 'on' or 'off' Failed to parse "yes" for "dummy.ipv4" I assume libvirt is sending a it a command on the monitor interface that it no longer understands... Tom -- Tom Hughes (tom@compton.nu) http://www.compton.nu/
On Wed, Jan 06, 2010 at 03:38:29PM +0000, Tom Hughes wrote:
The update from qemu 0.11.0 to qemu 0.12.1 in the virt-preview repository seems to have broken things. Starting a VM now just gives me a blank screen and a log which says:
Option 'ipv4': Use 'on' or 'off' Failed to parse "yes" for "dummy.ipv4"
I assume libvirt is sending a it a command on the monitor interface that it no longer understands...
That warning message should be harmless - all my VMs show that and they work ok. It is not actually something libirt sets - its a internal QEMU default setting which is wrong Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
On 06/01/10 15:53, Daniel P. Berrange wrote:
On Wed, Jan 06, 2010 at 03:38:29PM +0000, Tom Hughes wrote:
The update from qemu 0.11.0 to qemu 0.12.1 in the virt-preview repository seems to have broken things. Starting a VM now just gives me a blank screen and a log which says:
Option 'ipv4': Use 'on' or 'off' Failed to parse "yes" for "dummy.ipv4"
I assume libvirt is sending a it a command on the monitor interface that it no longer understands...
That warning message should be harmless - all my VMs show that and they work ok. It is not actually something libirt sets - its a internal QEMU default setting which is wrong
Hmm... Well something is wrong because I just get a black screen. I don't even get the BIOS messages since I updated this morning. Downgrading back to the fedora-updates version of qemu makes it work again. BTW the trigger for that warning seems to be that I have listen='0.0.0.0' set on the vnc adaptor to allow connections from remote machines, which causes libvirt to build a qemu command line with "-vnc 0.0.0.0:0". Tom -- Tom Hughes (tom@compton.nu) http://www.compton.nu/
On Wednesday 06 January 2010 17:11:17 Tom Hughes wrote:
On 06/01/10 15:53, Daniel P. Berrange wrote:
On Wed, Jan 06, 2010 at 03:38:29PM +0000, Tom Hughes wrote:
The update from qemu 0.11.0 to qemu 0.12.1 in the virt-preview repository seems to have broken things. Starting a VM now just gives me a blank screen and a log which says:
Option 'ipv4': Use 'on' or 'off' Failed to parse "yes" for "dummy.ipv4"
I assume libvirt is sending a it a command on the monitor interface that it no longer understands...
That warning message should be harmless - all my VMs show that and they work ok. It is not actually something libirt sets - its a internal QEMU default setting which is wrong
Hmm... Well something is wrong because I just get a black screen. I don't even get the BIOS messages since I updated this morning.
If you start your VM with -kernel $image, there's a bug in qemu-0.12.1(.1?), which is fixed in 0.12.1.2.
Downgrading back to the fedora-updates version of qemu makes it work again.
BTW the trigger for that warning seems to be that I have listen='0.0.0.0' set on the vnc adaptor to allow connections from remote machines, which causes libvirt to build a qemu command line with "-vnc 0.0.0.0:0".
Tom
On 06/01/10 17:32, Thomas Treutner wrote:
On Wednesday 06 January 2010 17:11:17 Tom Hughes wrote:
Hmm... Well something is wrong because I just get a black screen. I don't even get the BIOS messages since I updated this morning.
If you start your VM with -kernel $image, there's a bug in qemu-0.12.1(.1?), which is fixed in 0.12.1.2.
It's a windows VM, so no. The qemu command libvirt is using is: /usr/bin/qemu-kvm -S -M pc-0.11 -enable-kvm -m 1024 -smp 2 -name windows_xp_64 -uuid bb4c089d-1a5e-b349-07fe-4098efdf5fe0 -monitor unix:/var/lib/libvirt/qemu/windows_xp_64.monitor,server,nowait -localtime -boot c -drive file=/var/lib/libvirt/images/windows_xp_64.img,if=virtio,index=0,boot=on -drive if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:12:4a:56,vlan=0,model=virtio,name=virtio.0 -net tap,fd=27,vlan=0,name=tap.0 -serial pty -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:0 -k en-gb -vga std -soundhw es1370 That said, I've tried stripping most of that out and still get nothing so I think something more fundamental is wrong. Tom -- Tom Hughes (tom@compton.nu) http://www.compton.nu/
Hi Tom, I've had similar trouble with old bios images. Once I replaced them with those built with qemu-kvm, things started working... regards nik On Wed, Jan 06, 2010 at 05:34:57PM +0000, Tom Hughes wrote:
On 06/01/10 17:32, Thomas Treutner wrote:
On Wednesday 06 January 2010 17:11:17 Tom Hughes wrote:
Hmm... Well something is wrong because I just get a black screen. I don't even get the BIOS messages since I updated this morning.
If you start your VM with -kernel $image, there's a bug in qemu-0.12.1(.1?), which is fixed in 0.12.1.2.
It's a windows VM, so no. The qemu command libvirt is using is:
/usr/bin/qemu-kvm -S -M pc-0.11 -enable-kvm -m 1024 -smp 2 -name windows_xp_64 -uuid bb4c089d-1a5e-b349-07fe-4098efdf5fe0 -monitor unix:/var/lib/libvirt/qemu/windows_xp_64.monitor,server,nowait -localtime -boot c -drive file=/var/lib/libvirt/images/windows_xp_64.img,if=virtio,index=0,boot=on -drive if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:12:4a:56,vlan=0,model=virtio,name=virtio.0 -net tap,fd=27,vlan=0,name=tap.0 -serial pty -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:0 -k en-gb -vga std -soundhw es1370
That said, I've tried stripping most of that out and still get nothing so I think something more fundamental is wrong.
Tom
-- Tom Hughes (tom@compton.nu) http://www.compton.nu/
-- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
-- ------------------------------------- Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis@linuxbox.cz -------------------------------------
On 06/01/10 18:56, Nikola Ciprich wrote:
I've had similar trouble with old bios images. Once I replaced them with those built with qemu-kvm, things started working...
I've using the packages from virt-preview so I've got whatever BIOS images are being packaged. I've experimented some more now and even a simple: qemu-kvm -enable-kvm just gives me nothing whereas the older version brings up the BIOS screen. Actually looking at it, the BIOS is a separate package which doesn't exist in the virt-preview repository so I'm still using the normal Fedora one. Maybe that's the problem? What's the best channel for reporting issues with the virt-preview packages? Tom -- Tom Hughes (tom@compton.nu) http://www.compton.nu/
On Thu, Jan 07, 2010 at 10:08:33AM +0000, Tom Hughes wrote:
On 06/01/10 18:56, Nikola Ciprich wrote:
I've had similar trouble with old bios images. Once I replaced them with those built with qemu-kvm, things started working...
I've using the packages from virt-preview so I've got whatever BIOS images are being packaged. I've experimented some more now and even a simple:
qemu-kvm -enable-kvm
just gives me nothing whereas the older version brings up the BIOS screen.
Actually looking at it, the BIOS is a separate package which doesn't exist in the virt-preview repository so I'm still using the normal Fedora one. Maybe that's the problem?
Yes, the KVM from rawhide is not compatible with the BIOS from F12, so this sounds like a bug in virt-preview
What's the best channel for reporting issues with the virt-preview packages?
The fedora-virt mailing list Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
participants (4)
-
Daniel P. Berrange -
Nikola Ciprich -
Thomas Treutner -
Tom Hughes