Tino, The copy of the image occurs without problems.
The path " /volumes/vmfs/<ds_id>/12/disk.0" exists and the disk file is copied with the original filename like RHEL-x64.vmdk. But when the BOOT will occurrs, the Nebula script is using "disk.vmdk" instead of the "RHEL-x64.vmdk" When I import the image, it supposed to be renamed to disk.vmdk? Eduardo On Thu, Dec 5, 2013 at 8:55 AM, Tino Vazquez <cvazq...@c12g.com> wrote: > Hi Eduardo, > > All registered vmdks (regardless or whether they are compressed or > not) are renamed to disk.vmdk, for internal handling. > > The problem you are experiencing is that the prolog is not copying the > image properly, probably due to a misconfiguration. > > Could you check that the following path exists in the relevant ESX host? > > /volumes/vmfs/<ds_id>/12/disk.0 > > Where ds_id is the system datastore identifier. > > If it doesn't, check oned.log and the vm log for hints on why the > image hasn't been copied, or send them through for analysis. > > 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 ab...@c12g.com and delete the e-mail and > attachments and any copy from your system. C12G thanks you for your > cooperation. > > > On Wed, Dec 4, 2013 at 2:56 PM, Eduardo Roloff <rol...@gmail.com> wrote: >> Hello, >> >> I configured a ONE 4.4 installation with CentOS in the front end and >> ESXi on hosts. >> >> I uploaded an vmware image through sunstone (RHEL-x64.vmdk) using the >> tar.gz format. >> >> But when I try to instantiate a VM using this image the front end >> tranfer the image to the host, but when it tryes to start it it is >> using a diferent vmdk (disk.vmdk), according with the error below. >> >> Wed Dec 4 11:50:26 2013 [VMM][I]: error: internal error Could not >> start domain: FileNotFound - File [0] 12/disk.0/disk.vmdk was not >> found >> >> It is mandatory to use "disk.vmdk" as the disk name for vmware? And in >> case of a slipted disk? >> >> Regards, >> Eduardo >> _______________________________________________ >> Users mailing list >> Users@lists.opennebula.org >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org