qemu-kvm-0.12 bug?
Hi,
I've switched from -0.11.0 to -0.12 and from 2.6.31.6 to 2.6.32.2 to try the new virtio-memory-API introduced in latest libvirt from git. I can start VMs f.e. by kvm -cdrom $someiso --enable-kvm but my domain configs to not work anymore.
Domain config: http://pastebin.com/f66324669
Qemu log when doing "virsh start wp01":
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M
pc-0.11 -enable-kvm -m 1000 -smp 1 -name wp01 -uuid
4c34e9aa-2bcd-fa8e-bc98-4417c1cb779a -chardev socket,id=monitor,path=/usr/local/var/lib/libvirt/qemu/wp01.monitor,server,nowait -monitor chardev:monitor -boot
c -kernel /boot/vmlinuz-2.6.32.2 -initrd /boot/initrd.img-2.6.32.2 -append
root=/dev/vdb noresume2 -drive file=/dev/disk/by-path/ip-10.0.1.1:3260-iscsi-iqn.2009-09.local:store.wp01-swap-lun-0,if=virtio,index=0,boot=on -drive file=/dev/disk/by-path/ip-10.0.1.1:3260-iscsi-iqn.2009-09.local:store.wp01-disk-lun-0,if=virtio,index=1 -net nic,macaddr=00:16:3e:00:01:01,vlan=0,model=virtio,name=virtio.0 -net
tap,fd=18,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial
chardev:serial0 -parallel none -usb -vnc 0.0.0.0:0 -k de -vga cirrus
char device redirected to /dev/pts/3
Option 'ipv4': Use 'on' or 'off'
Failed to parse "yes" for "dummy.ipv4"
rom: requested regions overlap (rom vapic.bin. free=0x0000000000000600,
addr=0x0000000000000000)
rom loading failed
Is this a bug or am I missing something?
Thanks, kr
tom
Quoted 6 lines · On Tuesday 22 December 2009 13:02:28 Thomas Treutner wrote:
Hi,
I've switched from -0.11.0 to -0.12 and from 2.6.31.6 to 2.6.32.2 to try the new virtio-memory-API introduced in latest libvirt from git. I can start VMs f.e. by kvm -cdrom $someiso --enable-kvm but my domain configs to not work anymore.
Just found the other bug report about this....
Quoted 9 lines · On Tuesday 22 December 2009 13:25:30 Thomas Treutner wrote:
Quoted 6 lines · On Tuesday 22 December 2009 13:02:28 Thomas Treutner wrote:
Hi,
I've switched from -0.11.0 to -0.12 and from 2.6.31.6 to 2.6.32.2 to try the new virtio-memory-API introduced in latest libvirt from git. I can start VMs f.e. by kvm -cdrom $someiso --enable-kvm but my domain configs to not work anymore.
Just found the other bug report about this....
Which solves this problem, but introduces the next. My VMs are stuck at boot, after "SeaBIOS...gPXE" nothing happens.
Domain config: http://pastebin.com/f66324669
I had to do ./configure --disable-xen due to some other bug at compilation, could that be related?
thx,kr
tom
Quoted 9 lines
Quoted 6 lines
Quoted 4 lines
I've switched from -0.11.0 to -0.12 and from 2.6.31.6 to 2.6.32.2 to try the new virtio-memory-API introduced in latest libvirt from git. I can start VMs f.e. by kvm -cdrom $someiso --enable-kvm but my domain configs to not work anymore.
Just found the other bug report about this....
Which solves this problem, but introduces the next. My VMs are stuck at boot, after "SeaBIOS...gPXE" nothing happens.
Similar problem here with 0.12.1.1.
I prefer to start my linux guests with -kernel, -append and -initrd. With this options qemu-kvm stuck at boot.
Windows 2k8 or CDROM images work flawless.
0.12.0-rc2 didn't show this bug.
Bernhard
Quoted 10 lines · Bernhard Held
Quoted 10 lines
Quoted 7 lines
Quoted 5 lines
I've switched from -0.11.0 to -0.12 and from 2.6.31.6 to 2.6.32.2 to try the new virtio-memory-API introduced in latest libvirt from git. I can start VMs f.e. by kvm -cdrom $someiso --enable-kvm but my domain configs to not work anymore.
Just found the other bug report about this....
Which solves this problem, but introduces the next. My VMs are stuck at boot, after "SeaBIOS...gPXE" nothing happens.
Quoted 10 lines
Similar problem here with 0.12.1.1.
I prefer to start my linux guests with -kernel, -append and -initrd. With this options qemu-kvm stuck at boot.
Windows 2k8 or CDROM images work flawless.
0.12.0-rc2 didn't show this bug.
I just posted a fix for this. It will be included with 0.12.1.2 or 0.12.2.
Signature · 1 line
error compiling committee.c: too many arguments to function
Quoted 6 lines · On Thursday 24 December 2009 15:26:59 Avi Kivity wrote:
Quoted 5 lines · Bernhard Held
Quoted 2 lines
Which solves this problem, but introduces the next. My VMs are stuck at boot, after "SeaBIOS...gPXE" nothing happens.
Similar problem here with 0.12.1.1.
Quoted 8 lines
Quoted 6 lines
I prefer to start my linux guests with -kernel, -append and -initrd. With this options qemu-kvm stuck at boot.
Windows 2k8 or CDROM images work flawless.
0.12.0-rc2 didn't show this bug.
I just posted a fix for this. It will be included with 0.12.1.2 or 0.12.2.
Yep, fixed the bug for me. thx!
kr,t
Quoted 10 lines · On Thursday 24 December 2009 18:01:58 Thomas Treutner wrote:
Quoted 9 lines · On Thursday 24 December 2009 15:26:59 Avi Kivity wrote:
Quoted 8 lines · Bernhard Held
Quoted 2 lines
Which solves this problem, but introduces the next. My VMs are stuck at boot, after "SeaBIOS...gPXE" nothing happens.
Similar problem here with 0.12.1.1.
I prefer to start my linux guests with -kernel, -append and -initrd. With this options qemu-kvm stuck at boot.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
Windows 2k8 or CDROM images work flawless.
0.12.0-rc2 didn't show this bug.
I just posted a fix for this. It will be included with 0.12.1.2 or 0.12.2.
Yep, fixed the bug for me. thx!
...and made the next bug visible - I can't set the assigned memory by
$ virsh setmem domain kbyte
With -0.11, it works flawlessly. I tried 2.6.31.6, 2.6.32-rc5 and 2.6.32.2, it makes no difference.
Is it a bug in KVM or are there some recent changes in KVM which aren't reflected by libvirt?
kr,tom
Quoted 10 lines · Thomas Treutner
...and made the next bug visible - I can't set the assigned memory by
$ virsh setmem domain kbyteWith -0.11, it works flawlessly. I tried 2.6.31.6, 2.6.32-rc5 and 2.6.32.2, it makes no difference.
What's this, the balloon driver?
Signature · 1 line
error compiling committee.c: too many arguments to function
Quoted 9 lines · On Tuesday 29 December 2009 11:36:03 Avi Kivity wrote:
Quoted 6 lines · Thomas Treutner
...and made the next bug visible - I can't set the assigned memory by
$ virsh setmem domain kbyteWith -0.11, it works flawlessly. I tried 2.6.31.6, 2.6.32-rc5 and 2.6.32.2, it makes no difference.
What's this, the balloon driver?
Yep, virtio_balloon is of course loaded.
kr,t
Quoted 6 lines · Thomas Treutner
Quoted 4 lines · On Tuesday 29 December 2009 11:36:03 Avi Kivity wrote:
Quoted 2 lines · Thomas Treutner
...and made the next bug visible - I can't set the assigned memory by
Quoted 11 lines
Quoted 7 lines
Quoted 5 lines
$ virsh setmem domain kbyteWith -0.11, it works flawlessly. I tried 2.6.31.6, 2.6.32-rc5 and 2.6.32.2, it makes no difference.
What's this, the balloon driver?
Yep,
virtio_balloonis of course loaded.
Hm, I get "The balloon device has not been activated by the guest" in the qemu monitor.
Signature · 1 line
error compiling committee.c: too many arguments to function
Quoted 14 lines · On Tue, 29 Dec 2009 13:10:36 +0200 Avi Kivity <[email protected]> wrote:
Quoted 13 lines · Thomas Treutner
Quoted 11 lines · On Tuesday 29 December 2009 11:36:03 Avi Kivity wrote:
Quoted 7 lines · Thomas Treutner
...and made the next bug visible - I can't set the assigned memory by
$ virsh setmem domain kbyteWith -0.11, it works flawlessly. I tried 2.6.31.6, 2.6.32-rc5 and 2.6.32.2, it makes no difference.
What's this, the balloon driver?
Quoted 7 lines
Quoted 4 lines
Yep,
virtio_balloonis of course loaded.Hm, I get "The balloon device has not been activated by the guest" in the qemu monitor.
Is the "-balloon virtio" parameter passed on the command-line?
Quoted 5 lines · On Tuesday 29 December 2009 12:48:39 Luiz Capitulino wrote:
Quoted 2 lines · On Tue, 29 Dec 2009 13:10:36 +0200 Avi Kivity <[email protected]> wrote:
Hm, I get "The balloon device has not been activated by the guest" in the qemu monitor.
Is the "-balloon virtio" parameter passed on the command-line?
# grep balloon /usr/local/var/log/libvirt/qemu/* | wc -l 0
These logs include some history - so the parameter isn't used by libvirt even when ballooning works?
kr,t
Quoted 5 lines · On Tue, 29 Dec 2009 13:08:26 +0100 Thomas Treutner <[email protected]> wrote:
Quoted 4 lines · On Tuesday 29 December 2009 12:48:39 Luiz Capitulino wrote:
Quoted 2 lines · On Tue, 29 Dec 2009 13:10:36 +0200 Avi Kivity <[email protected]> wrote:
Hm, I get "The balloon device has not been activated by the guest" in the qemu monitor.
Quoted 7 lines
Quoted 1 line
Is the "-balloon virtio" parameter passed on the command-line?
# grep balloon /usr/local/var/log/libvirt/qemu/* | wc -l 0These logs include some history - so the parameter isn't used by libvirt even when ballooning works?
This parameter is new in qemu-0.12.
Quoted 9 lines · On Tuesday 29 December 2009 13:24:36 Luiz Capitulino wrote:
Quoted 7 lines
Quoted 1 line
Is the "-balloon virtio" parameter passed on the command-line?
# grep balloon /usr/local/var/log/libvirt/qemu/* | wc -l 0These logs include some history - so the parameter isn't used by libvirt even when ballooning works?
This parameter is new in qemu-0.12.
Ah, thx! I informed the libvirt guys.
kr,t
Quoted 6 lines · Luiz Capitulino
Quoted 4 lines
Hm, I get "The balloon device has not been activated by the guest" in the qemu monitor.
Is the "-balloon virtio" parameter passed on the command-line?
With this parameter, everything works.
Signature · 1 line
error compiling committee.c: too many arguments to function
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Which solves this problem, but introduces the next. My VMs are stuck at boot,
after "SeaBIOS...gPXE" nothing happens.Similar problem here with 0.12.1.1.
I prefer to start my linux guests with -kernel, -append and -initrd. With this options qemu-kvm stuck at boot.
Quoted 6 lines
Quoted 4 lines
Windows 2k8 or CDROM images work flawless.
0.12.0-rc2 didn't show this bug.
I just posted a fix for this. It will be included with 0.12.1.2 or 0.12.2.
Now everything works for me.
Thanks for the quick patch!
Bernhard