[one-users] Vmware vm deployment error

[Tino Vazquez]

Hi Nuno,

This may be related to the image registration problem. Let's solve that first.

Best.

-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple

--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G | es.linkedin.com/in/tinova

--
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 C12G Labs 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 abuse at c12g.com and delete the e-mail and
attachments and any copy from your system. C12G thanks you for your
cooperation.


On 8 April 2014 11:33, Nuno Serro <nserro at reitoria.ulisboa.pt> wrote:
> Hello,
>
> We are using opennebula (4.4.1). When instantiating a new VM in ESXi (5.5.0)
> the deployment fails with the following error (full log attached):
>
> Tue Apr 8 09:50:26 2014 [VMM][I]: error: internal error Could not start
> domain: FileNotFound - File
> /vmfs/volumes/4ca0eadf-b14a6199-7a7d-1cc1de6b4f22/461/disk.0/disk.vmdk was
> not found
>
> The problem is that vmdk does not exist with the name referenced in the
> deployment file. The vmdk image is correctly linked from the image datastore
> to the system datastore, but the name is different:
>
> ID 114 - systemDS
> ID 112 - imageDS
>
> ~ # ls -lR /vmfs/volumes/114/461/
> /vmfs/volumes/114/461/:
> total 1152
> drwxr-xr-x    1 root     root          1120 Apr  8 09:19 disk.0
> -rw-r--r--    1 root     root        376832 Apr  8 08:50 disk.1
> lrwxrwxrwx    1 root     root            28 Apr  8 08:50 disk.1.iso ->
> /vmfs/volumes/114/461/disk.1
>
> /vmfs/volumes/114/461/disk.0:
> total 320
> lrwxrwxrwx    1 root     root            83 Apr  8 08:50
> 3040f8c5a4048d3f43a874efbfd1d07b ->
> /vmfs/volumes/112/3040f8c5a4048d3f43a874efbfd1d07b/3040f8c5a4048d3f43a874efbfd1d07b
> -rw-r--r--    1 root     root             0 Apr  8 08:50 one-461.vmsd
> -rw-r--r--    1 root     root          1029 Apr  8 09:19 one-461.vmx
> -rw-r--r--    1 root     root           262 Apr  8 08:50 one-461.vmxf
> -rw-r--r--    1 root     root         40416 Apr  8 08:50 vmware-1.log
> -rw-r--r--    1 root     root         40248 Apr  8 09:19 vmware.log
>
> The problem resides in either the deployment file which references disk.vmdk
> instead of 3040f8c5a4048d3f43a874efbfd1d07b; or in the image link that is
> created as 3040f8c5a4048d3f43a874efbfd1d07b instead of disk.vmdk.
>
> Thanks in advance,
>
> --
> Nuno Serro
> Coordenador
> Núcleo de Infraestruturas e Telecomunicações
> Departamento de Informática
>
> Alameda da Universidade  -  Cidade Universitária
> 1649-004 Lisboa    PORTUGAL
> T. +351 210 443 566 - Ext. 19816
> E. nserro at reitoria.ulisboa.pt
> www.ulisboa.pt
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>