Right, that might be a bit confusing.

FS Format (FSTYPE in the code) is used to generate and format the new
datablock. Take a look at this:
https://github.com/OpenNebula/one/blob/master/src/mad/sh/scripts_common.sh#L284

Qcow2 is a bit of an exception: all the other datablocks are created with
'dd', but qcow2 is created with 'qemu-img'.

The Driver is passed directly to the hypervisor to indicate what format the
image is. That is, the driver ends up being an argument in the final
qemu-kvm command's disk section.

cheers,
Jaime

On Wed, Nov 26, 2014 at 5:02 PM, Madko <[email protected]> wrote:

> I will try that. Do you now what is the distinction between FS Format and
> Driver ? FS Format is the actual format on the datastore passed to qemu-img
> create? And driver is the part that goes in the domain xml?
>
>
> 2014-11-26 16:06 GMT+01:00 Jaime Melis <[email protected]>:
>
>> You would need:
>> - FS format: qcow2
>> - Driver: qcow2
>> - Device prefix: vd
>>
>> On Wed, Nov 26, 2014 at 3:35 PM, Madko <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> When I add a new disk to a running instance, I type raw (or anything
>>> else) in the FS format, qcow2 in the driver field and choose vd as device
>>> prefix.
>>>
>>> I then have an error that the disk.2 is not a qcow2 format. Qemu-img
>>> shows that in fact it's a raw format image that have been created. So I
>>> retry with a raw format and then it works. So how do we attach a disk in
>>> qcow2 format?
>>>
>>> Moreover, if I choose read only, I still can write/format this disk in
>>> the VM. Is it normal?
>>>
>>>
>>> best regards,
>>>
>>> --
>>> Edouard Bourguignon
>>>
>>> _______________________________________________
>>> Users mailing list
>>> [email protected]
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>
>>
>> --
>> OpenNebula - Flexible Enterprise Cloud Made Simple
>> --
>> Jaime Melis
>> Senior Infrastructure Architect at OpenNebula Systems (formerly C12G Labs)
>> [email protected] | @OpenNebula
>> --
>> Confidentiality Warning: The information contained in this e-mail and any
>> accompanying documents, unless otherwise expressly indicated, is
>> confidential and privileged, and is intended solely for the person and/or
>> entity to whom it is addressed (i.e. those identified in the "To" and "cc"
>> box). They are the property of OpenNebula.Systems S.L.. Unauthorized
>> distribution, review, use, disclosure, or copying of this communication, or
>> any part thereof, is strictly prohibited and may be unlawful. If you have
>> received this e-mail in error, please notify us immediately by e-mail at
>> [email protected] and delete the e-mail and attachments and any
>> copy from your system. OpenNebula's thanks you for your cooperation.
>>
>
>
>
> --
> Edouard Bourguignon
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>


-- 
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Jaime Melis
Senior Infrastructure Architect at OpenNebula Systems (formerly C12G Labs)
[email protected] | @OpenNebula
--
Confidentiality Warning: The information contained in this e-mail and any
accompanying documents, unless otherwise expressly indicated, is
confidential and privileged, and is intended solely for the person and/or
entity to whom it is addressed (i.e. those identified in the "To" and "cc"
box). They are the property of OpenNebula.Systems S.L.. Unauthorized
distribution, review, use, disclosure, or copying of this communication, or
any part thereof, is strictly prohibited and may be unlawful. If you have
received this e-mail in error, please notify us immediately by e-mail at
[email protected] and delete the e-mail and attachments and any copy
from your system. OpenNebula's thanks you for your cooperation.
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Reply via email to