OpenNebula

We are using One 1.4 with KVM

When we were using Libvirt 0.7.5, here is how the Disk definition in VM template, deployment.0 and actual libvirt generated XML were looking.

VM Template:

DISK=[
clone=no,
source=/sharedstorage/path/images/UbuntuABC0,
target=hda,
type=disk
]

deployment.0 :

<disk type='file' device='disk'>
                        <source file='/mnt/stor/one/5/images/disk.0'/>
                        <target dev='hda'/>
                </disk>

libvirt generated XML:
<disk type='file' device='disk'>
<source file='/mnt/stor/one/5/images/disk.0'/>
<target dev='hda' bus='ide'/>
<state/>
</disk>

However when we were using libvirt 0.8.3 the libvirt generated XML looks different.

libvirt generated XML:
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/mnt/stor/one/5/images/disk.0'/>
<target dev='hda' bus='ide'/>
<alias name='ide0-0-0'/>
<address type='drive' controller='0' bus='0' unit='0'/>
</disk>

If you see it adds the driver tag with type as "raw". Because of this, if we have a qcow2 disk file of 20GB virtual size, the actual disk space inside the VM is showing up as some other value (the physical size of the qcow2 image).

Is it possible to pass the driver tag from onevm template? If we have to add that tag and have the driver type as "qcow2", changing LibvirtDriver.cc will take care of it?

Ranga