Bug 663087 - regression: can not boot any image in F14 qemu-kvm on i386
Summary: regression: can not boot any image in F14 qemu-kvm on i386
Keywords:
Status: CLOSED DUPLICATE of bug 649333
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 14
Hardware: i686
OS: All
low
medium
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-14 16:36 UTC by Ales Kozumplik
Modified: 2014-09-30 23:39 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-15 12:56:11 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ales Kozumplik 2010-12-14 16:36:54 UTC 
Steps to reproduce:
1) create a VM in virt-manager in F14, host machine is i386
2) select boot from network (PXE) (but I also tested this with a boot.iso, with the same result)
3) start the machine, select an entry from the list

The machine hangs, with the following on the screen:
http://akozumpl.fedorapeople.org/eddfail.png

top reveals qemu-kvm process takes nearly 100% cpu.
Comment 1 Ales Kozumplik 2010-12-14 16:39:07 UTC 
Just to make it easier to search for this bug: the message on the screen says:

Probing EDD (edd=off to disable).. OK
Comment 2 Daniel Berrangé 2010-12-14 16:47:32 UTC 
Please provide the virt-manager log file from $HOME/.virt-manager/virt-manager.log, guest XML (virsh dumpxml $GUESTNAME)  and the full QEMU command line from /var/log/libvirt/qemu/$GUESTNAME.log
Comment 3 Jan ONDREJ 2010-12-14 19:45:08 UTC 
Do you have latest Fedora 14 stable kernel on host?

I think this is duplicate of 649333, maybe 575330 too.

If you can't reproduce it with latest stable kernel, close it as duplicate of 649333.
Comment 4 Ales Kozumplik 2010-12-15 12:56:11 UTC 
Jan,

many thanks, the latest kernel fixed this for me.

Ales

*** This bug has been marked as a duplicate of bug 649333 ***
Note You need to log in before you can comment on or make changes to this bug.