Hi, I just noticed that once I upgrade to libvirt-0.9.6-1 from the virt-preview repo on my Fedora 15 machine I can no longer boot guests that use virtio disks. I only get "Boot failed: could not read the boot disk". Removing the disk and re-adding it as IDE drive allows KVM to boot from the disk (although the full boot obviously fails due to the hda/vda naming difference but that's expected).
After downgrading to libvirt-0.8.8-7 again the problem goes away and the guest boot fine from virtio disks.
Is this a known problem? Do I have to configure something differently to make this work as it should?
Regards, Dennis
Hey Dennis,
On Tue, Sep 27, 2011 at 16:20, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
Hi, I just noticed that once I upgrade to libvirt-0.9.6-1 from the virt-preview repo on my Fedora 15 machine I can no longer boot guests that use virtio disks. I only get "Boot failed: could not read the boot disk". Removing the disk and re-adding it as IDE drive allows KVM to boot from the disk (although the full boot obviously fails due to the hda/vda naming difference but that's expected).
After downgrading to libvirt-0.8.8-7 again the problem goes away and the guest boot fine from virtio disks.
Is this a known problem? Do I have to configure something differently to make this work as it should?
What version of Seabios are you using? I believe support for direct booting from virtio disks was added only recently.
Kind regards,
Ruben
On 09/28/2011 01:23 PM, Ruben Kerkhof wrote:
Hey Dennis,
On Tue, Sep 27, 2011 at 16:20, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
Hi, I just noticed that once I upgrade to libvirt-0.9.6-1 from the virt-preview repo on my Fedora 15 machine I can no longer boot guests that use virtio disks. I only get "Boot failed: could not read the boot disk". Removing the disk and re-adding it as IDE drive allows KVM to boot from the disk (although the full boot obviously fails due to the hda/vda naming difference but that's expected).
After downgrading to libvirt-0.8.8-7 again the problem goes away and the guest boot fine from virtio disks.
Is this a known problem? Do I have to configure something differently to make this work as it should?
What version of Seabios are you using? I believe support for direct booting from virtio disks was added only recently.
That can't be right. I've been using only virtio disks for years now and never had any problem booting from them. Also as I mentioned above it is upgrading/downgrading libvirt that creates/fixes the issue. I don't touch the installed seabios package at all.
Regards, Dennis
On Wed, Sep 28, 2011 at 16:12, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
On 09/28/2011 01:23 PM, Ruben Kerkhof wrote:
Hey Dennis,
On Tue, Sep 27, 2011 at 16:20, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
Hi, I just noticed that once I upgrade to libvirt-0.9.6-1 from the virt-preview repo on my Fedora 15 machine I can no longer boot guests that use virtio disks. I only get "Boot failed: could not read the boot disk". Removing the disk and re-adding it as IDE drive allows KVM to boot from the disk (although the full boot obviously fails due to the hda/vda naming difference but that's expected).
After downgrading to libvirt-0.8.8-7 again the problem goes away and the guest boot fine from virtio disks.
Is this a known problem? Do I have to configure something differently to make this work as it should?
What version of Seabios are you using? I believe support for direct booting from virtio disks was added only recently.
That can't be right. I've been using only virtio disks for years now and never had any problem booting from them. Also as I mentioned above it is upgrading/downgrading libvirt that creates/fixes the issue. I don't touch the installed seabios package at all.
Regards, Dennis
Somewhere around 0.9.4 libvirt switched to use a different method to indicate from which device to boot. See http://libvirt.org/git/?p=libvirt.git;a=commit;h=c3068d4d2381146ed46051ad636...
I think this causes Seabios to skip using extboot.bin for booting and to try to directly boot from a disk. If your Seabios version is too old, it won't support booting from virtio disks directly.
Does adding <bootmenu enable='yes'/> to your xml help? If I'm right this will cause Seabios to fall back to using extboot.bin
This is all just a wild guess, but I'm having the same issue with scsi disks.
Regards,
Ruben
On Wed, 2011-09-28 at 16:39 +0200, Ruben Kerkhof wrote:
On Wed, Sep 28, 2011 at 16:12, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
On 09/28/2011 01:23 PM, Ruben Kerkhof wrote:
Hey Dennis,
On Tue, Sep 27, 2011 at 16:20, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
Hi, I just noticed that once I upgrade to libvirt-0.9.6-1 from the virt-preview repo on my Fedora 15 machine I can no longer boot guests that use virtio disks. I only get "Boot failed: could not read the boot disk". Removing the disk and re-adding it as IDE drive allows KVM to boot from the disk (although the full boot obviously fails due to the hda/vda naming difference but that's expected).
After downgrading to libvirt-0.8.8-7 again the problem goes away and the guest boot fine from virtio disks.
Is this a known problem? Do I have to configure something differently to make this work as it should?
What version of Seabios are you using? I believe support for direct booting from virtio disks was added only recently.
That can't be right. I've been using only virtio disks for years now and never had any problem booting from them. Also as I mentioned above it is upgrading/downgrading libvirt that creates/fixes the issue. I don't touch the installed seabios package at all.
Regards, Dennis
Somewhere around 0.9.4 libvirt switched to use a different method to indicate from which device to boot. See http://libvirt.org/git/?p=libvirt.git;a=commit;h=c3068d4d2381146ed46051ad636...
I think this causes Seabios to skip using extboot.bin for booting and to try to directly boot from a disk. If your Seabios version is too old, it won't support booting from virtio disks directly.
Does adding <bootmenu enable='yes'/> to your xml help? If I'm right this will cause Seabios to fall back to using extboot.bin
This is all just a wild guess, but I'm having the same issue with scsi disks.
If you are using virt-preview, it is best to use all of virt-preview, and not just cherry pick packages. The version of seabios in virt-preview is seabios-0.6.2-2 which matches what is currently in F16.
Justin
Hi All,
Maybe it is a combination of libvirt and qemu. I had an similar issue as i made the update on F14. I installed the libvirt packages for F14 from ftp://libvirt.org/libvirt/ and i could no boot the vm's as well. I traced this done to the generated qemu command for the disk. For drives using virtio this disk (if=none) arguments were not generated as expected.
e.g.
-drive
file=/var/lib/libvirt/images/winxp.img,if=none,id=drive-ide0-0-0,format=raw,cache=writeback
in previous version it generated the argument as "..,if=virtio,..". I tested this by manually executing the command-line.
i solved this issue by updating qemu to version 0.15 which apparently does not need "if=virtio" and can life with "if=none". -- Regards Soeren
On 09/28/2011 04:39 PM, Ruben Kerkhof wrote:
On Wed, Sep 28, 2011 at 16:12, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
On 09/28/2011 01:23 PM, Ruben Kerkhof wrote:
Hey Dennis,
On Tue, Sep 27, 2011 at 16:20, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
Hi, I just noticed that once I upgrade to libvirt-0.9.6-1 from the virt-preview repo on my Fedora 15 machine I can no longer boot guests that use virtio disks. I only get "Boot failed: could not read the boot disk". Removing the disk and re-adding it as IDE drive allows KVM to boot from the disk (although the full boot obviously fails due to the hda/vda naming difference but that's expected).
After downgrading to libvirt-0.8.8-7 again the problem goes away and the guest boot fine from virtio disks.
Is this a known problem? Do I have to configure something differently to make this work as it should?
What version of Seabios are you using? I believe support for direct booting from virtio disks was added only recently.
That can't be right. I've been using only virtio disks for years now and never had any problem booting from them. Also as I mentioned above it is upgrading/downgrading libvirt that creates/fixes the issue. I don't touch the installed seabios package at all.
Regards, Dennis
Somewhere around 0.9.4 libvirt switched to use a different method to indicate from which device to boot. See http://libvirt.org/git/?p=libvirt.git;a=commit;h=c3068d4d2381146ed46051ad636...
I think this causes Seabios to skip using extboot.bin for booting and to try to directly boot from a disk. If your Seabios version is too old, it won't support booting from virtio disks directly.
Does adding<bootmenu enable='yes'/> to your xml help? If I'm right this will cause Seabios to fall back to using extboot.bin
This is all just a wild guess, but I'm having the same issue with scsi disks.
Regards,
Ruben _______________________________________________ virt mailing list virt@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/virt
On 09/28/2011 04:39 PM, Ruben Kerkhof wrote:
On Wed, Sep 28, 2011 at 16:12, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
On 09/28/2011 01:23 PM, Ruben Kerkhof wrote:
Hey Dennis,
On Tue, Sep 27, 2011 at 16:20, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
Hi, I just noticed that once I upgrade to libvirt-0.9.6-1 from the virt-preview repo on my Fedora 15 machine I can no longer boot guests that use virtio disks. I only get "Boot failed: could not read the boot disk". Removing the disk and re-adding it as IDE drive allows KVM to boot from the disk (although the full boot obviously fails due to the hda/vda naming difference but that's expected).
After downgrading to libvirt-0.8.8-7 again the problem goes away and the guest boot fine from virtio disks.
Is this a known problem? Do I have to configure something differently to make this work as it should?
What version of Seabios are you using? I believe support for direct booting from virtio disks was added only recently.
That can't be right. I've been using only virtio disks for years now and never had any problem booting from them. Also as I mentioned above it is upgrading/downgrading libvirt that creates/fixes the issue. I don't touch the installed seabios package at all.
Regards, Dennis
Somewhere around 0.9.4 libvirt switched to use a different method to indicate from which device to boot. See http://libvirt.org/git/?p=libvirt.git;a=commit;h=c3068d4d2381146ed46051ad636...
I think this causes Seabios to skip using extboot.bin for booting and to try to directly boot from a disk. If your Seabios version is too old, it won't support booting from virtio disks directly.
Does adding<bootmenu enable='yes'/> to your xml help? If I'm right this will cause Seabios to fall back to using extboot.bin
This is all just a wild guess, but I'm having the same issue with scsi disks.
I just checked my yum history and indeed while I updated almost all packages from virt-preview seabios-bin was not among them. After pulling that in as well the problem went away.
The libvirt package should probably be updated to require seabios-bin >= 0.6.2.
Regards, Dennis
[adding libvirt list]
On 09/28/2011 09:24 AM, Dennis Jacobfeuerborn wrote:
I just noticed that once I upgrade to libvirt-0.9.6-1 from the virt-preview repo on my Fedora 15 machine I can no longer boot guests that use virtio disks. I only get "Boot failed: could not read the boot disk". Removing the disk and re-adding it as IDE drive allows KVM to boot from the disk (although the full boot obviously fails due to the hda/vda naming difference but that's expected).
After downgrading to libvirt-0.8.8-7 again the problem goes away and the guest boot fine from virtio disks.
Somewhere around 0.9.4 libvirt switched to use a different method to indicate from which device to boot. See http://libvirt.org/git/?p=libvirt.git;a=commit;h=c3068d4d2381146ed46051ad636...
I think this causes Seabios to skip using extboot.bin for booting and to try to directly boot from a disk. If your Seabios version is too old, it won't support booting from virtio disks directly.
The libvirt package should probably be updated to require seabios-bin>= 0.6.2.
Yes, that probably needs to happen to libvirt.spec when built for F16 (and thus imported into F15 via virt-preview). I'll tackle that, since I've been making a couple other spec file patches lately.
On Wed, Sep 28, 2011 at 11:41:11AM -0600, Eric Blake wrote:
[adding libvirt list]
On 09/28/2011 09:24 AM, Dennis Jacobfeuerborn wrote:
I just noticed that once I upgrade to libvirt-0.9.6-1 from the virt-preview repo on my Fedora 15 machine I can no longer boot guests that use virtio disks. I only get "Boot failed: could not read the boot disk". Removing the disk and re-adding it as IDE drive allows KVM to boot from the disk (although the full boot obviously fails due to the hda/vda naming difference but that's expected).
After downgrading to libvirt-0.8.8-7 again the problem goes away and the guest boot fine from virtio disks.
Somewhere around 0.9.4 libvirt switched to use a different method to indicate from which device to boot. See http://libvirt.org/git/?p=libvirt.git;a=commit;h=c3068d4d2381146ed46051ad636...
I think this causes Seabios to skip using extboot.bin for booting and to try to directly boot from a disk. If your Seabios version is too old, it won't support booting from virtio disks directly.
The libvirt package should probably be updated to require seabios-bin>= 0.6.2.
Yes, that probably needs to happen to libvirt.spec when built for F16 (and thus imported into F15 via virt-preview). I'll tackle that, since I've been making a couple other spec file patches lately.
It is not a libvirt requirement really. It is QEMU that is advertising it supports the per-device boot ordering feature. libvirt queries this and then tries to use it. QEMU should have required the new Seabios if it intends to advertise this feature.
Daniel
On 09/28/2011 11:43 AM, Daniel P. Berrange wrote:
The libvirt package should probably be updated to require seabios-bin>= 0.6.2.
Yes, that probably needs to happen to libvirt.spec when built for F16 (and thus imported into F15 via virt-preview). I'll tackle that, since I've been making a couple other spec file patches lately.
It is not a libvirt requirement really. It is QEMU that is advertising it supports the per-device boot ordering feature. libvirt queries this and then tries to use it. QEMU should have required the new Seabios if it intends to advertise this feature.
Ah, then the problem is qemu's spec file. On F16, I see this from 'yum deplist qemu-system-x86':
dependency: seabios-bin provider: seabios-bin.noarch 0.6.2-2.fc16
So it is not requiring a minimal version, and when backporting qemu to F15 via virt-preview, no seabios-bin upgrade is being pulled in. I've created https://bugzilla.redhat.com/show_bug.cgi?id=741992 against qemu.
On 09/28/2011 07:56 PM, Eric Blake wrote:
On 09/28/2011 11:43 AM, Daniel P. Berrange wrote:
The libvirt package should probably be updated to require seabios-bin>= 0.6.2.
Yes, that probably needs to happen to libvirt.spec when built for F16 (and thus imported into F15 via virt-preview). I'll tackle that, since I've been making a couple other spec file patches lately.
It is not a libvirt requirement really. It is QEMU that is advertising it supports the per-device boot ordering feature. libvirt queries this and then tries to use it. QEMU should have required the new Seabios if it intends to advertise this feature.
Ah, then the problem is qemu's spec file. On F16, I see this from 'yum deplist qemu-system-x86':
dependency: seabios-bin provider: seabios-bin.noarch 0.6.2-2.fc16
So it is not requiring a minimal version, and when backporting qemu to F15 via virt-preview, no seabios-bin upgrade is being pulled in. I've created https://bugzilla.redhat.com/show_bug.cgi?id=741992 against qemu.
I'm not sure if that is correct. It is purely the libvirt update that breaks things:
1. qemu 0.14.0, libvirt 0.8.8, seabios-bin 0.6.0 => virtio boots fine
2. update libvirt to 0.9.6 => virtio boot breaks
3. update seabios-bin to 0.6.2 => virtio works again
Since I didn't update qemu at all any changes to its dependencies do not help in this situation.
Regards, Dennis
On Wed, Sep 28, 2011 at 08:16:23PM +0200, Dennis Jacobfeuerborn wrote:
On 09/28/2011 07:56 PM, Eric Blake wrote:
On 09/28/2011 11:43 AM, Daniel P. Berrange wrote:
The libvirt package should probably be updated to require seabios-bin>= 0.6.2.
Yes, that probably needs to happen to libvirt.spec when built for F16 (and thus imported into F15 via virt-preview). I'll tackle that, since I've been making a couple other spec file patches lately.
It is not a libvirt requirement really. It is QEMU that is advertising it supports the per-device boot ordering feature. libvirt queries this and then tries to use it. QEMU should have required the new Seabios if it intends to advertise this feature.
Ah, then the problem is qemu's spec file. On F16, I see this from 'yum deplist qemu-system-x86':
dependency: seabios-bin provider: seabios-bin.noarch 0.6.2-2.fc16
So it is not requiring a minimal version, and when backporting qemu to F15 via virt-preview, no seabios-bin upgrade is being pulled in. I've created https://bugzilla.redhat.com/show_bug.cgi?id=741992 against qemu.
I'm not sure if that is correct. It is purely the libvirt update that breaks things:
qemu 0.14.0, libvirt 0.8.8, seabios-bin 0.6.0 => virtio boots fine
update libvirt to 0.9.6 => virtio boot breaks
update seabios-bin to 0.6.2 => virtio works again
Since I didn't update qemu at all any changes to its dependencies do not help in this situation.
The QEMU in F15 was already broken, we just didn't know about it until we tried the new libvirt. F15 should have a seabios 0.6.1 at least, but for a long time we couldn't biuld it because of a binutils bug...
Daniel
On Wed, 2011-09-28 at 11:56 -0600, Eric Blake wrote:
On 09/28/2011 11:43 AM, Daniel P. Berrange wrote:
The libvirt package should probably be updated to require seabios-bin>= 0.6.2.
Yes, that probably needs to happen to libvirt.spec when built for F16 (and thus imported into F15 via virt-preview). I'll tackle that, since I've been making a couple other spec file patches lately.
It is not a libvirt requirement really. It is QEMU that is advertising it supports the per-device boot ordering feature. libvirt queries this and then tries to use it. QEMU should have required the new Seabios if it intends to advertise this feature.
Ah, then the problem is qemu's spec file. On F16, I see this from 'yum deplist qemu-system-x86':
dependency: seabios-bin provider: seabios-bin.noarch 0.6.2-2.fc16
So it is not requiring a minimal version, and when backporting qemu to F15 via virt-preview, no seabios-bin upgrade is being pulled in. I've created https://bugzilla.redhat.com/show_bug.cgi?id=741992 against qemu.
Well, there was no older seabios shipping with F16, so it made sense. As for virt-preview, seabios updates were also available there long before the qemu which required them. Enabling virt-preview and doing a yum update would have installed the new seabios as well. I just don't think that virt-preview can ever be trusted to pick and choose specific packages, you either want the F15 virt stack as it is, or the F16 (virt-preview) virt stack.
Justin
-
Daniel P. Berrange -
Dennis Jacobfeuerborn -
Eric Blake -
Justin Forbes -
Ruben Kerkhof -
Soeren Grunewald