Hello,
I am trying to create a VM from a image, and it fails with the following error
message :
[DiM][I]: New VM state is ACTIVE.
[LCM][I]: New VM state is PROLOG.
[TM][W]: No size or format in FS, skipping
[TM][I]: Command execution fail: /var/lib/one/remotes/tm/vmfs/clone
Hi,
Could you check that
/vmfs/volumes/101/ab77b4b5184b6c9b5bf08b3001d71fd3/disk.vmdk exists
in the ESX host?
Regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G |
It does not exist, the whole volume /vmfs/volumes/101/ seems to be empty.
Thanks,
Cosmin___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Actually, it kind of worked, i have no idea how that image dissapeared, but
still showed up as available. But now it throws another error :
oneadmin@OpenNebula:/home/oneadmin$ cat /var/log/one/9.log
Thu Oct 24 09:39:20 2013 [DiM][I]: New VM state is ACTIVE.
Thu Oct 24 09:39:20 2013 [LCM][I]:
This is the VM path , with the files contained.
~ # ls /vmfs/volumes/100/9
disk.0 disk.2 disk.2.iso
This is the template :
oneadmin@OpenNebula:/home/oneadmin$ onetemplate show 2
TEMPLATE 2 INFORMATION
ID : 2
NAME : test_template
USER : oneadmin
GROUP
Hi,
Ok, I think the problem is in the volatile disk that you are defining in the VM.
DISK=[
SIZE=5120,
TYPE=fs ]
which doesn't have the FORMAT attribute, hence the following log message:
Thu Oct 24 09:39:20 2013 [TM][W]: No size or format in FS, skipping
Please try again with the
Glad it worked. I've changed the documentation [1] to reflect that
FORMAT is mandatory.Any feedback on this to make the documentation
clearer is welcomed.
Reards,
-T
[1]
http://opennebula.org/documentation:rel4.2:evmwareg?#datablocks_volatile_disks
--
OpenNebula - Flexible Enterprise Cloud
I already tried without the second disk and it worked. With your option it also
worked with a new disk.
Thanks a lot, i really apreciate all the help,
Cosmin
On Thursday, October 24, 2013 5:17 PM, Tino Vazquez cvazq...@c12g.com wrote:
Hi,
Ok, I think the problem is in the volatile disk
