OpenNebula

Looking at code, I could find a similar bug for vmfs, vmdk and lvm.
iscsi is ok.

Hi,

I was trying to attach an unformatted datablock image to a windows vm. I used save_as as file system for that purpose in sunstone webif. It looks like it is not the right way to do it. Can you tell me how to create such unformatted image properly ?

Thanks,

Laurent

Laurent Grawet wrote:

Hi,

I was trying to attach an unformatted datablock image to a windows vm. I used save_as as file system for that purpose in sunstone webif. It looks like it is not the right way to do it. Can you tell me how to create such unformatted image properly ?

There are several options depending on your final goal

1. The unformatted datablock will be used as an scracth disk and you will not need to keep its contents. Use a volatile disk in the template definition, just add
   DISK = [ TYPE = fs,
   SIZE = 4096,
   FORMAT = raw ]

1. You may want to keep the image. Then create an empty datablock as a regular image and then add it as any other disk. Use the following file for oneimage create

NAME = "windisk"
TYPE = DATABLOCK
SIZE = 4096
FSTYPE = vfat

then use it as

DISK = [ IMAGE = "windisk" ]

1. You can always hotplug either a volatile disk or datablock if you forgot to add it to the initial VM.

Thanks,

Laurent

Hi Ruben,

"FORMAT = raw" is exactly what I need but for persistent image. Looking at code, I see datastore/fs/mkfs is calling mkfs_command in scripts_common.sh, which implements raw type, so I can use FSTYPE="raw" for persistent image.

Formating with file system makes no really sense in my case, because I will use this image with windows guest. So I will have to create partition table with at least one partition from inside the guest first, then format it with ntfs.

I couldn't find any mention of FSTYPE="raw" in documentation. It is worth document it in
http://opennebula.org/documentation:rel3.8:img_template
http://opennebula.org/documentation:rel3.8:img_guide

I first tried FSTYPE="" (leaving this field empty in sunstone) and, of course, image creation action failed because linux mkfs command with empty fstype arg failed. It has side effects with some ds drivers because you have to manually do the cleanup on storage afterwards. OpenNebula won't do it with image in error state.

It would be good to do this check in mkfs_command function.

Something like :

        "raw" | "" )
            echo "" 
            return 0
            ;;

Cheers,

Laurent

Thanks, that's perfect !
(just a small typo in the doc: "Use raw to not to...")

Regards,

Laurent