Installation guide

Symp t o m

After building a guest virtual machine from an existing disk image, the guest booting stalls

with the error message No bo o t d evi ce. However, the guest virtual machine can start

successfully using the Q EMU command directly.

In vest ig at io n

The disk's bus type is not specified in the command for importing the existing disk image:

# virt-install \

--connect qemu:///system \

--ram 2048 -n rhel_64 \

--os-type=linux --os-variant=rhel5 \

--disk path=/root/RHEL-Server-5.8-64-

virtio.qcow2,device=disk,format=qcow2 \

--vcpus=2 --graphics spice --noautoconsole --import

However, the command line used to boot up the guest virtual machine using Q EMU directly

shows that it uses vi rti o for its bus type:

# ps -ef | grep qemu

/usr/libexec/qemu-kvm -monitor stdio -drive file=/root/RHEL-

Server-5.8-32-

virtio.qcow2,index=0,i f= vi rti o ,media=disk,cache=none,format=qcow2

-net nic,vlan=0,model=rtl8139,macaddr=00:30:91:aa:04:74 -net

tap,vlan=0,script=/etc/qemu-ifup,downscript=no -m 2048 -smp

2,cores=1,threads=1,sockets=2 -cpu qemu64,+sse2 -soundhw ac97 -

rtc-td-hack -M rhel5.6.0 -usbdevice tablet -vnc :10 -boot c -no-

kvm-pit-reinjection

Note the bus= in the guest's XML generated by lib virt for the imported guest:

<os>

</os>

<acpi/>

<apic/>

<pae/>

</features>

</clock>

<on_poweroff>destroy</on_poweroff>

<on_reboot>restart</on_reboot>

<on_crash>restart</on_crash>

Common libvirt errors and t roublesh oot ing

135