Red Hat Bugzilla – Bug 512358
Unable to boot using qemu-kvm and gPXE from virt-preview repository
Last modified: 2009-09-29 11:18:13 EDT
Description of problem:
Unable to boot from PXE using new qemu packages from virt-preview repository (
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. enable repository described here: http://markmc.fedorapeople.org/virt-preview
2. yum update
3. run: qemu-kvm -net nic,model=virtio -boot n -net tap,ifname=tap0
You need fully functional PXE booting on your network. If you don't have it, I can retest new kernel.
Press Ctrl-B to configure gPXE (PCI 00:00.0)...
then this virtual computer is running at 100% CPU, I can't type, ctrl-B does nothing, ... I can't only kill it.
Boot from PXE.
markmc suggested some urls:
I have backports of those patches to a F11 kernel. It is the same patches that are included in the RHEL5 tree.
I'm attaching them to the BZ, so they can be picked up.
F12 won't need them.
Created attachment 354155 [details]
First patch. Allow us to manipulate interrupt shadow bit in emulated instructions
Created attachment 354157 [details]
use the previous infrastructure to set interrupt shadow after emulated instructions.
workaround is to use etherboot ROMs, you need to fix /usr/share/qemu/pxe* symlinks
This completely blocks booting VMs with KVM on f11 hosts. It would be very nice if we could get it fixed. The only workaround is to rip out gpxe, install etherboot, and fudge symlinks... which is ugly.
*** Bug 494469 has been marked as a duplicate of this bug. ***
Looks like this is fixed in 2.6.30 upstream which should be pushed to Fedora 11 at some point. CVS for F-11 is already at 2.6.30, so there isn't really any way to easily push this patch before 2.6.30 is released.
188.8.131.52 is out, but problem still persist.
[ondrejj@work ~]$ rpm -q kernel-PAE qemu-kvm
[ondrejj@work ~]$ uname -a
Linux work.salstar.sk 184.108.40.206-43.fc11.i686.PAE #1 SMP Thu Aug 27 21:34:36 EDT 2009 i686 i686 i386 GNU/Linux
Thanks for testing Jan. It appears these patches only went into 220.127.116.11
18.104.22.168-64.fc11 is now available for F-11 updates. Please reopen this bug if there are further problems found.