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@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list