Bug 761297 - virt-manager fails to boot disk image that qemu can
Summary: virt-manager fails to boot disk image that qemu can
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-08 00:33 UTC by Scott Tsai
Modified: 2011-12-08 00:35 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-08 00:35:32 UTC
Type: ---


Attachments (Terms of Use)
libvirt VM XML file (1.67 KB, text/xml)
2011-12-08 00:33 UTC, Scott Tsai
no flags Details

Description Scott Tsai 2011-12-08 00:33:31 UTC
Created attachment 542294 [details]
libvirt VM XML file

Description of problem:
With the VirtualBox disk image distributed by the OpenRISC project, booting through qemu-kvm from the CLI works but after importing into virt-manager, booting fails with: 

I can boot the VirtualBox image prepared by the OpenRISC project using qemu

With this VirtualBox image prepared by the OpenRISC project:

I can boot it with:



Version-Release number of selected component (if applicable):
virt-manager-0.9.0-7.fc16.noarch
libvirt-0.9.6-2.fc16.x86_64
qemu-0.15.1-3.fc16.x86_64

How reproducible:
always

Steps to Reproduce:
1. Download and extract ftp://ocuser:ocuser@openrisc.opencores.org/virtualbox-image/OpenRISC_Ubuntu_2011-11-28.vdi.bz2 (1.1 GB)
2. Using qemu-kvm directly works:
qemu-kvm -drive file=OpenRISC_Ubuntu_2011-11-28.vdi,id=drive-virtio-disk0,if=virtio
3. Create new VM in virt-manager while specifying the image
New VM -> Import existing disk image -> specify .vdi path, specify OS type and version as Linux, Ubuntu 11.10 reflecting what's actually inside the image
4. The VM fails to boot with:
Booting from Hard Disk...
"Boot failed: not a bootable disk"

Additional info:
libvirt VM XML file attached.

Using ps(1), I see that virt-manager is launching qemu-kvm with:

usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name openrisc-ubuntu-11.10 -uuid 537a8538-c6f6-ad88-0c7b-5be4df8bdbec -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/openrisc-ubuntu-11.10.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -drive file=/home/scottt/work/openrisc/OpenRISC_Ubuntu_2011-11-28.vdi,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:3d:f3:13,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6

Comment 1 Scott Tsai 2011-12-08 00:35:32 UTC
My apologies. I accidentally submitted the bug while still editing the description. I'll close this one and try again.


Note You need to log in before you can comment on or make changes to this bug.