1 |
On 10/10/2010 07:05 AM, Dan Johansson wrote: |
2 |
> I know this is of topic, but this is one of the few lists where you mostly get a competent answer. |
3 |
> |
4 |
> I have a small problem with libvirt / qemu. I have created a guest (also gentoo) on a gentoo hosts and when I start it from the command-line the guests starts OK, but when I start the guest through libvirt with "virsh start" I get "Booting from Hard Disk... |
5 |
> Boot failed: not a bootable disk |
6 |
> No bootable device" |
7 |
> |
8 |
> This is the command-line I use to start the guest (which works) |
9 |
> "cd /var/lib/kvm/Wilmer; /usr/bin/qemu-system-x86_64 --enable-kvm \ |
10 |
> -net nic,vlan=1,model=rtl8139,macaddr=DE:ED:BE:EF:01:03 -net tap,vlan=1,ifname=qtap13,script=no,downscript=no \ |
11 |
> -net nic,vlan=3,model=rtl8139,macaddr=DE:ED:BE:EF:03:03 -net tap,vlan=3,ifname=qtap33,script=no,downscript=no \ |
12 |
> -m 2048 -k de-ch -vnc :3 -daemonize \ |
13 |
> Wilmer.qcow2" |
14 |
> |
15 |
> |
16 |
> The libvirt XML-file was created using "virsh domxml-from-native qemu-argv" and this is the result of that conversion: |
17 |
|
18 |
> <boot dev='hd'/> |
19 |
|
20 |
You obviously know more about libvirt than I do, but I'm wondering about |
21 |
that 'hd'. qemu knows enough to interpret Wilmer.qcow2 as the boot disk, |
22 |
but maybe libvirt isn't that smart. |
23 |
|
24 |
I'd maybe try using an explicit '-hda Wilmer.qcow2' in your original script |
25 |
so virsh doesn't need to assume anything while converting it. |
26 |
|
27 |
Fingers crossed :) |