I actually managed to fix it. The issue is the name for the second vmdk ( the
-flat one ) was not correct. I renamed it and i worked afterwards. I still have
some issues, if i don't find a way to solve them i will come back with
questions, but thanks for the help, so far. It has been really help
Hi,
My guess here is that the registered disk is not a valid vmdk:
/vmfs/volumes/101/f82b9d8fb979e76b33bb8c53ae899527/disk.vmdk
To validate this vmdk, try to create a VMware VM using the VI client
from that existing disk. If it doesn't work, I would suggest
registering the image again from a vmd
~ # ls /vmfs/volumes/101/f82b9d8fb979e76b33bb8c53ae899527
Win2k8R2-flat.vmdk disk.vmdk
So it exists, and contain those files. Any other ideas?
Cosmin
On Thursday, November 7, 2013 5:41 PM, Tino Vazquez wrote:
Hi,
Can you check if this file exists in the ESX node?
/vmfs/volumes/101/f82
Yes , it fails, with the following message :
DiskLib_Check() failed for source disk The system cannot find the file
specified (25).
Cosmin
On Thursday, November 7, 2013 7:54 PM, Tino Vazquez wrote:
Hi,
So, the error referred in the log is:
Error cloning OpenNebula:/vmfs/volumes/101/f8
Hi,
So, the error referred in the log is:
Error cloning OpenNebula:/vmfs/volumes/101/f82b9d8fb979e76b33bb8c53ae899527
to 192.168.10.10:/vmfs/volumes/100/37/disk.0
which comes from the following line:
vmkfstools -i /vmfs/volumes/101/f82b9d8fb979e76b33bb8c53ae899527/disk.vmdk
-d thin /vmfs/volume
Hi,
Can you check if this file exists in the ESX node?
/vmfs/volumes/101/f82b9d8fb979e76b33bb8c53ae899527
If it doesn't, you may need to register the image again.
Regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructur
Any ideas on this new error?
Thanks,
Cosmin
On Wednesday, November 6, 2013 1:18 PM, cosmin cucu
wrote:
It was indeed a permission issue, i managed to make it working. I did create
the image, and the template. But when i deploy a VM i get the following error
in it's log :
Wed Nov 6 06
It was indeed a permission issue, i managed to make it working. I did create
the image, and the template. But when i deploy a VM i get the following error
in it's log :
Wed Nov 6 06:12:07 2013 [TM][I]: clone: Cloning
OpenNebula:/vmfs/volumes/101/f82b9d8fb979e76b33bb8c53ae899527 in
192.168.10
Hi,
Let's try and solve the local error first (the windows VM). From the log I see
On Tue, Nov 5, 2013 at 2:57 PM, cosmin cucu wrote:
> scp -r /home/oneadmin/Windows2k8R2/*
> 192.168.10.10:/vmfs/volumes/101/bf485f995dac3989c8d4b0bfd8d250b8" failed:
> /home/oneadmin/Windows2k8R2/Win2k8R2-flat.vmd
No , it was deleted. I tried to reimport the CentOS image, and the error now is
:
Tue Nov 5 07:41:23 2013 : Error copying image in the datastore: Error
renaming file /tmp/d0395e950bb37dd9cc184cc909253395/ to
/tmp/d0395e950bb37dd9cc184cc909253395/disk.vmdk
In /tmp i have the following files/f
Hi,
I've just tried importing the image and is working for me. Do you
still have the following directory?
/tmp/65d9c81c5059f6f39c1cd8a63ec3f806
if so, what are its contents?
About the second error, does /home/oneadmin/Windows2k8R2 contain vmdk
files? If so, please send more context from oned.l
Hello,
Anyone has any idea on why this is happening? I have also tried to create a
image with a preexisting windows VM , after i copy the files in the open Nebula
server and i try to import them , i get the following error :
Tue Nov 5 05:10:51 2013 : Error copying image in the datastore: Erro
Hello,
I have a open nebula 4.2 setup with 3 ESX hosts, and 2 vmfs datastores ( image
and system ) . The issue is that when i try to import a centOS image from the
default marketplace i get the following errors :
Mon
Nov 4 06:33:53 2013 : Error copying image in the datastore: Error
renamin
13 matches
Mail list logo
