[one-ecosystem] vmware deployment problem

Tino Vazquez tinova at fdi.ucm.es
Thu Oct 21 02:43:26 PDT 2010


Hi,

Have you set the VM_DIR in $ONE_LOCATION/etc/oned.conf? I that case,
please unset it and try again.

Regards,

-Tino

--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization Technology Engineer / Researcher
OpenNebula Toolkit | opennebula.org



On Thu, Oct 21, 2010 at 11:23 AM, Paul Piscuc <paul.piscuc at sinergetic.ro> wrote:
> Hi,
>
> Well, we're having problems with the NFS setup also. The local folder is
> copied to the NFS folder (nexenta), but then OneVmmVmware.java tries to
> deploy the machine, searching for the deployment.0 file in
> /vmfs/volumes/test/47/deployment.0 . But there is actually a deployment.0
> file only in /srv/cloud/one/47/ , and the VMWare directory is
> /vmfs/volumes/test/debtest .
>
> Thank you for your help.
>
> On Thu, Oct 21, 2010 at 10:16 AM, Paul Piscuc <paul.piscuc at sinergetic.ro>
> wrote:
>>
>> Hi,
>>
>> This is the command and also the output:
>> tar -zxvf vmware-0.95.tar.gz
>>
>> gzip: stdin: not in gzip format
>> tar: Child returned status 1
>> tar: Error is not recoverable: exiting now
>>
>> I have tried in a windows environment, and still doesn't work. Also, I
>> have tried using different tools to extract it, but no success.
>>
>>
>>
>> On Wed, Oct 20, 2010 at 7:59 PM, Tino Vazquez <tinova at fdi.ucm.es> wrote:
>>>
>>> Hi Paul,
>>>
>>> Please try to untar the tar.gz inside an empty repository.
>>>
>>> If that doesn't cut it, please elaborate a bit on why you say is broken.
>>>
>>> Best regards,
>>>
>>> -Tino
>>>
>>> --
>>> Constantino Vázquez Blanco | dsa-research.org/tinova
>>> Virtualization Technology Engineer / Researcher
>>> OpenNebula Toolkit | opennebula.org
>>>
>>>
>>>
>>> On Wed, Oct 20, 2010 at 6:03 PM, Paul Piscuc <paul.piscuc at sinergetic.ro>
>>> wrote:
>>> > Hi Tino,
>>> >
>>> > The tar.gz file is broken. I have tried on different machines, and
>>> > still
>>> > doesn't work. Maybe you could provide me with another download link.
>>> > Btw,
>>> > congrationations for the opennebula project. Hopefully we would manage
>>> > to
>>> > implement it on our datacenter.
>>> >
>>> > On Wed, Oct 20, 2010 at 6:31 PM, Tino Vazquez <tinova at fdi.ucm.es>
>>> > wrote:
>>> >>
>>> >> Hi Paul,
>>> >>
>>> >> The TM SSH for VMware is at a very early stage and prone to be buggy.
>>> >> The reason it is not fully developed is that the ssh server used by
>>> >> ESX is not very reliable (dropbear) for large files. You are encourage
>>> >> to switch to the default NFS TM drivers, and also I invite you to try
>>> >> out the new VMware driver addons [1], which features a tighter
>>> >> integration of VMware and OpenNebula.
>>> >>
>>> >> Best regards,
>>> >>
>>> >> -Tino
>>> >>
>>> >> [1] http://opennebula.org/documentation:rel2.0:evmwareg
>>> >>
>>> >> --
>>> >> Constantino Vázquez Blanco | dsa-research.org/tinova
>>> >> Virtualization Technology Engineer / Researcher
>>> >> OpenNebula Toolkit | opennebula.org
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Oct 20, 2010 at 5:23 PM, Paul Piscuc
>>> >> <paul.piscuc at sinergetic.ro>
>>> >> wrote:
>>> >> > Hi. I am running opennebula 1.9.90 with a vmware esxi server,
>>> >> > connected
>>> >> > through ssh. When deploying the machine, the tm_copy copies
>>> >> > successfully
>>> >> > to
>>> >> > esxi, but failes to deploy because the deployment.0 is not found on
>>> >> > the
>>> >> > server. I have copied the deployment.0 to the folder of the VM, but
>>> >> > still
>>> >> > fails. The debug trace is:
>>> >> >
>>> >> >  java.io.FileNotFoundException: /vmfs/volumes/test/32/deployment.0
>>> >> > (No
>>> >> > such
>>> >> > file or directory)
>>> >> >         at java.io.FileInputStream.open(Native Method)
>>> >> >         at java.io.FileInputStream.<init>(FileInputStream.java:106)
>>> >> >         at java.io.FileInputStream.<init>(FileInputStream.java:66)
>>> >> >
>>> >> > The problem is that the files that opennebula has copied are located
>>> >> > under
>>> >> > /vmfs/volumes/test/debtest/ , and not under /vmfs/volumes/test/32 .
>>> >> > 32
>>> >> > is
>>> >> > the ID of the machine created by onevm create. I have tried
>>> >> > deploying
>>> >> > using
>>> >> > onevm deploy 32 0 , and onevm deploy debtest name, but the problem
>>> >> > persists.
>>> >> >
>>> >> > Thank you in advance.
>>> >> >
>>> >> > Paul
>>> >> >
>>> >> >
>>> >> >
>>> >> > _______________________________________________
>>> >> > Ecosystem mailing list
>>> >> > Ecosystem at lists.opennebula.org
>>> >> > http://lists.opennebula.org/listinfo.cgi/ecosystem-opennebula.org
>>> >> >
>>> >> >
>>> >
>>> >
>>
>
>



More information about the Ecosystem mailing list