2010/12/12 Sherif Nagy
> thank you Matthias, i did follow what you said and i find the error, I am
> connecting to vCenter server not to ESX directly and that what i have find.
>
>
> Data Object Type: *NotImplemented*
>
That's the important information. The vCenter doesn't seem to implement the
thank you Matthias, i did follow what you said and i find the error, I am
connecting to vCenter server not to ESX directly and that what i have find.
Data Object Type: *NotImplemented*
Parent Managed Object ID: *task-267*
Property Path: *info.error*
Properties
Name Type Value dynamicPropertyDy
Works for me with the given XML config.
There might be some cases that could make it fail. For example the
.vmdk file already exists, or the datastore is full, or the datastore
is NFS backed and the ESX server lost the connection, etc.
Unfortunately libvirt doesn't include detailed information in
Great ! it did pass the error of directory/file thank you for the support
now i have another problem of creating the VMDK image with this XML
test_vm/test_vm.vmdk02
and error
libvir: ESX error : internal error Could not create volume
Traceback (most recent call last):
File "", line 1, in
Fil
This XML snippet should work
test_vm/test_vm.vmdk
0
2
The error message says that the volume name doesn't have the expected
format /. The <> might be misleading here, they don't
refer to XML elements.
I can probably relax this and allow files in the datastore root. The
problem with a .vm
The XML i am trying to use is
"test_vm.vmdk02"
or
"test_vm.vmdktest_vmtest_vm.vmdk02"
and if i added directory and file directive i am still getting the same
error, i am not sure if i am doing something wrong or it is a bug , can
someone please advice me what is the correct XML structure for cre
Matthias, sounds like there's a bug or we need to update the docs?
On 02/12/2010, at 11:02 PM, Sherif Nagy wrote:
> yes i am using same template like KVM but it is not working, seems ESX driver
> has a different XML structure since it is using datatstore /dir/filename.vdk
> structure.
>
> so a
yes i am using same template like KVM but it is not working, seems ESX
driver has a different XML structure since it is using datatstore
/dir/filename.vdk structure.
so any idea what is the XML structure for creating the XML for volumes using
the ESX driver?
On Thu, Dec 2, 2010 at 12:48 PM, Justi
On 02/12/2010, at 8:18 PM, Sherif Nagy wrote:
> Hello,
>
> I am using libvirt 0.8.6 "python bindings " can someone point me to where i
> find the XML description of creating volumes using storagecolumecreateXML
> function ? i am getting libvir: ESX error : internal error Volume name
> 'name
Hello,
I am using libvirt 0.8.6 "python bindings " can someone point me to where i
find the XML description of creating volumes using storagecolumecreateXML
function ? i am getting libvir: ESX error : internal error Volume name
'name.vmdk' doesn't have expected format '/'
thank you
regards,
S
10 matches
Mail list logo
