On Sunday 10 October 2010 20.08:26 walt wrote: > On 10/10/2010 07:05 AM, Dan Johansson wrote: > > I know this is of topic, but this is one of the few lists where you mostly > > get a competent answer. > > > > 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... > > Boot failed: not a bootable disk > > No bootable device" > > > > This is the command-line I use to start the guest (which works) > > "cd /var/lib/kvm/Wilmer; /usr/bin/qemu-system-x86_64 --enable-kvm \ > > -net nic,vlan=1,model=rtl8139,macaddr=DE:ED:BE:EF:01:03 -net > > tap,vlan=1,ifname=qtap13,script=no,downscript=no \ > > -net nic,vlan=3,model=rtl8139,macaddr=DE:ED:BE:EF:03:03 -net > > tap,vlan=3,ifname=qtap33,script=no,downscript=no \ > > -m 2048 -k de-ch -vnc :3 -daemonize \ > > Wilmer.qcow2" > > > > > > The libvirt XML-file was created using "virsh domxml-from-native qemu-argv" > > and this is the result of that conversion: > > > <boot dev='hd'/> > > You obviously know more about libvirt than I do, but I'm wondering about > that 'hd'. qemu knows enough to interpret Wilmer.qcow2 as the boot disk, > but maybe libvirt isn't that smart. > > I'd maybe try using an explicit '-hda Wilmer.qcow2' in your original script > so virsh doesn't need to assume anything while converting it.
Good point - but that did not help, still the same. :-( -- Dan Johansson, <http://www.dmj.nu> *************************************************** This message is printed on 100% recycled electrons! ***************************************************
