[one-users] Defining disk driver type in Libvirt XML

[Javier Fontan]

Hello,

We do not support that feature in 1.4 or 2.0 but maybe it is a good
thing to add. Can you open an issue in http://dev.opennebula.org so we
do not forget about it and can discuss the possibility to add that?
For sure it won't be added to release 2.0 as it is feature freeze
right now but we can have that into account for next releases.

Ways to solve that is to do as you say and modify deployment file
generation in LibvirtDriver.cc. Another way is to use RAW parameter in
your template to define the disk. The problem with this last way of
doing that is that transfer manager wont know about the disk and it
wont be cloned.

Bye

On Mon, Sep 20, 2010 at 6:53 PM, Rangababu Chakravarthula
<rbabu at hexagrid.com> wrote:
> 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 (1.4). If not, has
> this been addressed in 2.0? If we have to add that tag and have the driver
> type as "qcow2", changing LibvirtDriver.cc will take care of it?
>
> Ranga
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>



-- 
Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org