[libvirt] libvirt generates bad kvm command line
Hi folks, using this command sequence <code> export VIRSH_DEFAULT_CONNECT_URI=qemu:///system name=Testing kvmdir=/export/hdunkel/kvm hda=$kvmdir/$name/hda.qcow2 iso=/export/isos/debian-testing-amd64-netinst.iso mkdir -p $kvmdir/$name qemu-img create -f qcow2 $hda 32G virt-install --connect ${VIRSH_DEFAULT_CONNECT_URI} \ -n $name -r 1024 -vcpus=1 -f $hda -c $iso \ --network=bridge:br0 --vnc --accelerate -v \ --os-type=linux --os-variant=debianSqueeze </code> I get the famous "cdrom boot failure code 0003" error. The log file shows that libvirt generated this kvm command line: <code> 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 -m 1024 -smp 1 -name Testing \ -uuid 3a6b6b3f-84e6-6a21-a51a-2c61cf3914e2 \ -monitor unix:/var/lib/libvirt/qemu/Testing.monitor,server,nowait \ -no-reboot -boot d \ -drive file=/export/hdunkel/kvm/Testing/hda.qcow2,if=virtio,index=0 -drive file=/export/isos/debian-testing-amd64-netinst.iso,if=virtio,media=cdrom,index=1 \ -net nic,macaddr=52:54:00:3e:0b:26,vlan=0,model=virtio,name=virtio.0 \ -net tap,fd=18,vlan=0,name=tap.0 -serial pty -parallel none \ -usb -usbdevice tablet -vnc 127.0.0.1:0 -k en-us -vga cirrus </code> If I try this on the command line, then there is the same 0003 error. If I omit the if=virtio for the cdrom drive, then it boots the cd without 0003. Can you reproduce this? Is this a problem with libvirt or with the kvm module? Kernel is 2.6.31.5, i.e. kvm 0.88. libvirt is 0.7.2 Any helpful comments would be highly appreciated. Harri
Harald Dunkel wrote:
If I try this on the command line, then there is the same 0003 error.
If I omit the if=virtio for the cdrom drive, then it boots the cd without 0003.
Yeah, the "if=virtio" on the cdrom line is bogus.
Can you reproduce this? Is this a problem with libvirt or with the kvm module?
Neither. I believe this was a bug with virt-install that has been since fixed. Cole, do you have a link to the fix? -- Chris Lalancette
On 11/02/2009 10:54 AM, Chris Lalancette wrote:
Harald Dunkel wrote:
If I try this on the command line, then there is the same 0003 error.
If I omit the if=virtio for the cdrom drive, then it boots the cd without 0003.
Yeah, the "if=virtio" on the cdrom line is bogus.
Can you reproduce this? Is this a problem with libvirt or with the kvm module?
Neither. I believe this was a bug with virt-install that has been since fixed. Cole, do you have a link to the fix?
Yeah, the commit is here (the last hunk is the important one): http://hg.fedorahosted.org/hg/python-virtinst/rev/252ff7bc5ff9 Relevant fedora packages should have the fix. - Cole
Cole Robinson wrote:
Yeah, the commit is here (the last hunk is the important one):
http://hg.fedorahosted.org/hg/python-virtinst/rev/252ff7bc5ff9
Relevant fedora packages should have the fix.
Maybe you could do the community outside of the Fedora universe a favor and update the source package on http://virt-manager.et.redhat.com/download.html ? Many thanx Harri
Harald Dunkel wrote:
Maybe you could do the community outside of the Fedora universe a favor and update the source package on http://virt-manager.et.redhat.com/download.html ?
Sorry about these harsh words, but I was really pissed about this. It took me an awful lot of time to figure out what is going wrong in libvirt and its GUIs. You have a fix for this fatal problem for more than 6 weeks, and yet the "stable" version on your web page was not updated. This is very frustrating and disappointing about the whole libvirt project. Regards Harri
On Tue, Nov 03, 2009 at 12:27:38PM +0100, Harald Dunkel wrote:
Harald Dunkel wrote:
Maybe you could do the community outside of the Fedora universe a favor and update the source package on http://virt-manager.et.redhat.com/download.html ?
Sorry about these harsh words, but I was really pissed about this. It took me an awful lot of time to figure out what is going wrong in libvirt and its GUIs. You have a fix for this fatal problem for more than 6 weeks, and yet the "stable" version on your web page was not updated. This is very frustrating and disappointing about the whole libvirt project.
Pardon ? I'm pushing libvirt release about every month sometime more often ... You're mixing issues IMHO ! Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/
Daniel Veillard wrote:
Pardon ? I'm pushing libvirt release about every month sometime more often ... You're mixing issues IMHO !
Sorry, but I was talking about virtinst and the other GUIs. http://virt-manager.et.redhat.com/download.html shows just the releases from end of July (and older). My assumption (by now) was that the virt-manager GUIs and libvirt are coming from the same team. I apologize for this misunderstanding. Regards Harri
On 11/03/2009 05:38 AM, Harald Dunkel wrote:
Cole Robinson wrote:
Yeah, the commit is here (the last hunk is the important one):
http://hg.fedorahosted.org/hg/python-virtinst/rev/252ff7bc5ff9
Relevant fedora packages should have the fix.
Maybe you could do the community outside of the Fedora universe a favor and update the source package on http://virt-manager.et.redhat.com/download.html ?
I'm cutting new releases by the end of next week. If you are updating your packages manually, I'd recommend just using a source checkout until a new release is available: http://virt-manager.org/scmrepo.html If you are getting your packages from another distro, open a bug with them and point to the commit I posted above. - Cole
participants (4)
-
Chris Lalancette -
Cole Robinson -
Daniel Veillard -
Harald Dunkel