Re: [libvirt] Libvir on Hardy: file a bug or not?
On Tue, Jul 29, 2008 at 08:53:03AM +0300, Mihamina Rakotomandimby (R12y) wrote: Hi, I am using Ubuntu Hardy up to date. I get: virsh # start xp libvir: QEMU error : QEMU quit during console startup qemu: unknowm parameter 'boot' in 'file=/home/mihamina/xp.img,if=ide,boot=on' error: Failed to start domain xp If I change the domain type with qemu, I have no error (and the virtual machine starts without any problem. The Ubuntu libvirt had a early version of the patch for supporting the 'boot=on' parameter - I believe they always use it for any VM with a domain type of 'kvm'. Since you are using regular QEMU it is correct that you need to change the domain type to type=qemu anyway. This is my installed things: $ dpkg -l | awk '/(virt|qemu|kvm)/{print $2,$3}' kvm 1:62+dfsg-0ubuntu8 libvirt-bin 0.4.0-2ubuntu8 libvirt0 0.4.0-2ubuntu8 python-libvirt 0.4.0-2ubuntu8 python-virtinst 0.300.2-0ubuntu6 python-virtkey 0.50ubuntu0.1 qemu 0.9.1-1ubuntu1 virt-manager 0.5.3-0ubuntu10 virt-viewer 0.0.2-1ubuntu1 Is it an upstream bug or a distribution bug? I believe it is a disto bug - the upstream code for this should be auto-detecting whether 'boot=on' is supported automatically now. Who is supposed to be noticed? The packager or the upstream (where please)? Generally speaking, if you are yusing the libvir packages built by your OS distributor,then use their bug tracking system. They will forward bugs to upstream libvirt as required, or fix OS specific bugs directly. http://libvirt.org/bugs.html 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 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Libvir on Hardy: file a bug or not?
Daniel P. Berrange wrote: The Ubuntu libvirt had a early version of the patch for supporting the 'boot=on' parameter - I believe they always use it for any VM with a domain type of 'kvm'. Since you are using regular QEMU it is correct that you need to change the domain type to type=qemu anyway. My problem if I use qemu as domain type is the guest is slow enough to make me think it doesnt use the kvm. In the beginning, and in Ubuntu documentation, the domain type is qemu as default. So, the question that might solve the problems: How can assume it's realy using kvm (and not just qemu)? Note: when I launch the guest via the kvm command [1], it's faster. [1] e.g.: $ kvm -m 512 -hda foo.img -cdrom bar.iso -boot d -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Libvir on Hardy: file a bug or not?
Quoting Mihamina Rakotomandimby (R12y) [EMAIL PROTECTED]: I cannot help you with your problem but in case you want to try the latest and greatest libvirt, there are 0.4.4 packages available in my PPA: http://launchpad.net/~pgquiles/+archive (UNOFFICIAL AND UNSUPPORTED) Hi, I am using Ubuntu Hardy up to date. When defining a domain with: domain type='kvm' id='1' namexp/name uuiddd4618e5-1c48-a481-0671-d75f38f59037/uuid memory524288/memory currentMemory524288/currentMemory vcpu1/vcpu os type arch='x86_64' machine='pc'hvm/type boot dev='hd'/ /os clock offset='localtime'/ on_poweroffdestroy/on_poweroff on_rebootdestroy/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/qemu-system-x86_64/emulator disk type='file' device='cdrom' source file='/home/mihamina/xpjohnny.iso'/ target dev='hdc' bus='ide'/ readonly/ /disk disk type='file' device='disk' source file='/home/mihamina/xp.img'/ target dev='hda' bus='ide'/ /disk interface type='bridge' mac address='00:16:3e:1e:b2:22'/ source bridge='br0'/ target dev='vnet1'/ /interface input type='tablet' bus='usb'/ input type='mouse' bus='ps2'/ graphics type='vnc' port='5900' listen='127.0.0.1'/ /devices /domain I get: virsh # start xp libvir: QEMU error : QEMU quit during console startup qemu: unknowm parameter 'boot' in 'file=/home/mihamina/xp.img,if=ide,boot=on' error: Failed to start domain xp If I change the domain type with qemu, I have no error (and the virtual machine starts without any problem. This is my installed things: $ dpkg -l | awk '/(virt|qemu|kvm)/{print $2,$3}' kvm 1:62+dfsg-0ubuntu8 libvirt-bin 0.4.0-2ubuntu8 libvirt0 0.4.0-2ubuntu8 python-libvirt 0.4.0-2ubuntu8 python-virtinst 0.300.2-0ubuntu6 python-virtkey 0.50ubuntu0.1 qemu 0.9.1-1ubuntu1 virt-manager 0.5.3-0ubuntu10 virt-viewer 0.0.2-1ubuntu1 Is it an upstream bug or a distribution bug? Who is supposed to be noticed? The packager or the upstream (where please)? PS: I wrote because I saw http://www.mail-archive.com/libvir-list@redhat.com/msg06109.html -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Libvir on Hardy: file a bug or not?
Pau Garcia i Quiles wrote: I cannot help you with your problem but in case you want to try the latest and greatest libvirt, there are 0.4.4 packages available in my PPA: http://launchpad.net/~pgquiles/+archive (UNOFFICIAL AND UNSUPPORTED) They doesnt solve the problem. Thank you, anyway. -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] Libvir on Hardy: file a bug or not?
Hi, I am using Ubuntu Hardy up to date. When defining a domain with: domain type='kvm' id='1' namexp/name uuiddd4618e5-1c48-a481-0671-d75f38f59037/uuid memory524288/memory currentMemory524288/currentMemory vcpu1/vcpu os type arch='x86_64' machine='pc'hvm/type boot dev='hd'/ /os clock offset='localtime'/ on_poweroffdestroy/on_poweroff on_rebootdestroy/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/qemu-system-x86_64/emulator disk type='file' device='cdrom' source file='/home/mihamina/xpjohnny.iso'/ target dev='hdc' bus='ide'/ readonly/ /disk disk type='file' device='disk' source file='/home/mihamina/xp.img'/ target dev='hda' bus='ide'/ /disk interface type='bridge' mac address='00:16:3e:1e:b2:22'/ source bridge='br0'/ target dev='vnet1'/ /interface input type='tablet' bus='usb'/ input type='mouse' bus='ps2'/ graphics type='vnc' port='5900' listen='127.0.0.1'/ /devices /domain I get: virsh # start xp libvir: QEMU error : QEMU quit during console startup qemu: unknowm parameter 'boot' in 'file=/home/mihamina/xp.img,if=ide,boot=on' error: Failed to start domain xp If I change the domain type with qemu, I have no error (and the virtual machine starts without any problem. This is my installed things: $ dpkg -l | awk '/(virt|qemu|kvm)/{print $2,$3}' kvm 1:62+dfsg-0ubuntu8 libvirt-bin 0.4.0-2ubuntu8 libvirt0 0.4.0-2ubuntu8 python-libvirt 0.4.0-2ubuntu8 python-virtinst 0.300.2-0ubuntu6 python-virtkey 0.50ubuntu0.1 qemu 0.9.1-1ubuntu1 virt-manager 0.5.3-0ubuntu10 virt-viewer 0.0.2-1ubuntu1 Is it an upstream bug or a distribution bug? Who is supposed to be noticed? The packager or the upstream (where please)? PS: I wrote because I saw http://www.mail-archive.com/libvir-list@redhat.com/msg06109.html -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list