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. [email protected]
www.ulisboa.pt

Tue Apr 8 09:50:13 2014 [DiM][I]: New VM state is ACTIVE.
Tue Apr 8 09:50:13 2014 [LCM][I]: New VM state is PROLOG.
Tue Apr 8 09:50:15 2014 [LCM][I]: New VM state is BOOT
Tue Apr 8 09:50:15 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/461/deployment.0
Tue Apr 8 09:50:15 2014 [VMM][I]: Successfully execute network driver operation: pre.
Tue Apr 8 09:50:26 2014 [VMM][I]: Command execution fail: /var/lib/one/remotes/vmm/vmware/deploy '/var/lib/one/vms/461/deployment.0' 'petra' 461 petra
Tue Apr 8 09:50:26 2014 [VMM][D]: deploy: Successfully defined domain one-461.
Tue Apr 8 09:50:26 2014 [VMM][E]: deploy: Error executing: virsh -c 'esx://petra/?no_verify=1&auto_answer=1' start one-461 err: ExitCode: 1
Tue Apr 8 09:50:26 2014 [VMM][I]: out:
Tue Apr 8 09:50:26 2014 [VMM][I]: 2014-04-08 08:50:23.147+0000: 4899: info : libvirt version: 0.9.12.3
Tue Apr 8 09:50:26 2014 [VMM][I]: 2014-04-08 08:50:23.147+0000: 4899: warning : esxVI_Context_Connect:687 : Found untested VI API major/minor version '5.5'
Tue Apr 8 09:50:26 2014 [VMM][I]: 2014-04-08 08:50:23.147+0000: 4899: warning : esxVI_Context_Connect:723 : Found untested ESX major/minor version '5.5.0'
Tue Apr 8 09:50:26 2014 [VMM][I]: error: Failed to start domain one-461
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
Tue Apr 8 09:50:26 2014 [VMM][I]: 
Tue Apr 8 09:50:26 2014 [VMM][I]: ExitCode: 1
Tue Apr 8 09:50:26 2014 [VMM][I]: Failed to execute virtualization driver operation: deploy.
Tue Apr 8 09:50:26 2014 [VMM][E]: Error deploying virtual machine
Tue Apr 8 09:50:26 2014 [DiM][I]: New VM state is FAILED

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Reply via email to