[gentoo-user] [OT] Problems with libvirt / qemu

[gentoo-user] [OT] Problems with libvirt / qemu

[Dan Johansson]

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:
<domain type='kvm'>
  <name>wilmer</name>
  <uuid>a421968d-0573-1356-8cb7-32caff525a03</uuid>
  <memory>2097152</memory>
  <currentMemory>2097152</currentMemory>
  <vcpu>2</vcpu>
  <os>
    <type arch='x86_64' machine='pc-0.12'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <source file='/var/lib/kvm/Wilmer/Wilmer.qcow2'/>
      <target dev='hda' bus='ide'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='ethernet'>
      <mac address='de:ed:be:ef:01:03'/>
      <script path='no'/>
      <target dev='qtap13'/>
      <model type='rtl8139'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </interface>
    <interface type='ethernet'>
      <mac address='de:ed:be:ef:03:03'/>
      <script path='no'/>
      <target dev='qtap33'/>
      <model type='rtl8139'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='5903' autoport='no' listen=''/>
    <video>
      <model type='cirrus' vram='9216' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
  </devices>
</domain>


Anyone seeing something obvious that I have missed?

 Regards,
-- 
Dan Johansson, <http://www.dmj.nu>
***************************************************
This message is printed on 100% recycled electrons!
***************************************************

[gentoo-user] Re: [OT] Problems with libvirt / qemu

[walt]

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.

Fingers crossed :)

Re: [gentoo-user] Re: [OT] Problems with libvirt / qemu

[Dan Johansson]

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!
***************************************************

Re: [gentoo-user] [OT] Problems with libvirt / qemu

[Ward Poelmans]

On Sun, Oct 10, 2010 at 16:05, Dan Johansson <Dan.Johansson@dmj.nu> wrote:

>    <disk type='file' device='disk'>
>      <source file='/var/lib/kvm/Wilmer/Wilmer.qcow2'/>
>      <target dev='hda' bus='ide'/>
>      <address type='drive' controller='0' bus='0' unit='0'/>
>    </disk>

On my system, this section looks like:
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='image.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04'
function='0x0'/>
    </disk>

Try adding "<driver name='qemu' type='qcow2'/>" to yours?

Ward

Re: [gentoo-user] [OT] Problems with libvirt / qemu

[Dan Johansson]

On Monday 11 October 2010 19.02:10 Ward Poelmans wrote:
> On Sun, Oct 10, 2010 at 16:05, Dan Johansson <Dan.Johansson@dmj.nu> wrote:
> 
> >    <disk type='file' device='disk'>
> >      <source file='/var/lib/kvm/Wilmer/Wilmer.qcow2'/>
> >      <target dev='hda' bus='ide'/>
> >      <address type='drive' controller='0' bus='0' unit='0'/>
> >    </disk>
> 
> On my system, this section looks like:
>     <disk type='file' device='disk'>
>       <driver name='qemu' type='qcow2'/>
>       <source file='image.qcow2'/>
>       <target dev='vda' bus='virtio'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x04'
> function='0x0'/>
>     </disk>
> 
> Try adding "<driver name='qemu' type='qcow2'/>" to yours?
> 
Thanks, that did the trick!

Regards,
-- 
Dan Johansson, <http://www.dmj.nu>
***************************************************
This message is printed on 100% recycled electrons!
***************************************************