All Posts

Hi I'm interested in a feature, and I want to know if VDDK has such a feature. I want to register my own callback which will be called before calling th read() and write() funcntions to t... See more...
Hi I'm interested in a feature, and I want to know if VDDK has such a feature. I want to register my own callback which will be called before calling th read() and write() funcntions to the vmdk. Or maybe create a new vmdk for a VM and register my own read and write which will perform some operations and then call the regular read and write functions. Thanx Wagde
Please make sure the files libeay32.dll, ssleay32.dll (among others) are on the PATH or in the same directory as the binary. Thanks,
While running this sample program on Windows 2003, I'm getting error: SSLLoadSharedLibrary: Failed to load library libeay32.dll:126 - Failed to resolve dbghelp.dll symbols. No backtrace.--... See more...
While running this sample program on Windows 2003, I'm getting error: SSLLoadSharedLibrary: Failed to load library libeay32.dll:126 - Failed to resolve dbghelp.dll symbols. No backtrace.---- Win32 object usage: GDI 5, USER 0 CoreDump: Writing minidump to C:\Documents and Settings\Administrator\Application Data\VMware\vixDiskLibSample-5756.dmp Any ideas why and how to resolve this?
I do not know the answer to your question regarding vmfsctl . However, a solution that relies on software inside cos is not going to work on ESX versions that do not have COS (e.g. ESX3i). Per... See more...
I do not know the answer to your question regarding vmfsctl . However, a solution that relies on software inside cos is not going to work on ESX versions that do not have COS (e.g. ESX3i). Perhaps the cloning functionality in VDDK (either the C library or the vmware-vdiskmanager) might work for you? -Sudarsan
You can create a new virtual disk using the vddk. For sharing it as an ISCSI target, you would need to do additional things - one option is to add the new disk to a VM that has an iSCSI t... See more...
You can create a new virtual disk using the vddk. For sharing it as an ISCSI target, you would need to do additional things - one option is to add the new disk to a VM that has an iSCSI target software running. -Sudarsan
May i know using vmware virtual disk development kit can create a virtual disk and share like iscsi ? Or can do such like iSCSI Target ? Client's pc can connect with the virtual disk and r... See more...
May i know using vmware virtual disk development kit can create a virtual disk and share like iscsi ? Or can do such like iSCSI Target ? Client's pc can connect with the virtual disk and read it. Thank You !
Hi, With 1.0 release of VDDK, multi-byte characters in file names arent supported. Internationalization support is planned for a future release of VDDK. Hari
The file name is Wide Character, then I call the Win32 API WideCharToMultiByte to change it MultiByte. uint32 openFlags = VIXDISKLIB_FLAG_OPEN_READ_ONLY; char fn[MAX_PATH]=; WideCharToMu... See more...
The file name is Wide Character, then I call the Win32 API WideCharToMultiByte to change it MultiByte. uint32 openFlags = VIXDISKLIB_FLAG_OPEN_READ_ONLY; char fn[MAX_PATH]=; WideCharToMultiByte(CP_OEMCP,0,fullPathName.c_str(),fullPathName.size(),fn,MAX_PATH,NULL,NULL); VixDiskLib_Open(connection, path, flags, &_handle); after execute this , it's seem the SDK can't handle this kind of encode. But anyway, the english file name of VMDK file can be opened successfully. But if the chinese file name, it will failed. This the error message box popup screen-shot. Does anyone could give me idea ? How to covert the wide character to multi-byte character to conform the VixDiskLib_Open function requier ?
VirtualMachineConfigInfo DataObject, has a property hardware, which lists out the virutal hardware of a vm. You can get the a list of the set of virtual devices belonging to the virtual machin... See more...
VirtualMachineConfigInfo DataObject, has a property hardware, which lists out the virutal hardware of a vm. You can get the a list of the set of virtual devices belonging to the virtual machine, by fetchine the device property from the virtual hardware list. This list is unordered. foreach (@$vm_views) { my $vm_view = $_; Util::trace(0,$vm_view->config->name); my $len = @{$vm_view->config->hardware->device}; while($cnt<$len) }
Hi Niket, Thanks for the reply. I tried the steps you suggeted.still get the same error. I am also enclosing the code changes.Let me know if something needs to be hanged ... See more...
Hi Niket, Thanks for the reply. I tried the steps you suggeted.still get the same error. I am also enclosing the code changes.Let me know if something needs to be hanged Regards Neela array<VirtualDeviceConfigSpec > vdCfgSpec = gcnew array<VirtualDeviceConfigSpec^>(1); vdCfgSpec[0] = gcnew VirtualDeviceConfigSpec(); vdCfgSpec[0]->operation = VirtualDeviceConfigSpecOperation::add; vdCfgSpec[0]->operationSpecified = true; vdCfgSpec[0]->device = gcnew VirtualDisk(); VirtualDiskRawDiskMappingVer1BackingInfo^ backingInfo = gcnew VirtualDiskRawDiskMappingVer1BackingInfo(); backingInfo->compatibilityMode = "physicalMode"; /// Need to be changed to the canonical name backingInfo->deviceName = "vmhba1:0:1:0"; //p_VDisk->; backingInfo->diskMode = "persistent"; backingInfo->lunUuid = "01000100003030303032374535303031464d61676e6974"; // uuid we can get from the Host //backingInfo->datastore = nullptr; backingInfo->fileName = "[storage1] TestVM/TestVM_1.vmdk"; // Note: set any *Specified values to true vdCfgSpec[0]->device->backing = backingInfo; vdCfgSpec[0]->device->connectable = gcnew VirtualDeviceConnectInfo(); vdCfgSpec[0]->device->connectable->allowGuestControl = true; vdCfgSpec[0]->device->connectable->connected = true; vdCfgSpec[0]->device->connectable->startConnected = true; vdCfgSpec[0]->device->controllerKey = 1000;//vdary[iSCSIControllerIndex].key; // you may have one already, or have to create one in this same spec. vdCfgSpec[0]->device->controllerKeySpecified = true; vdCfgSpec[0]->device->key = -1; // all devices can be -1, but. all SCSI controllers must have unique -ve values vdCfgSpec[0]->device->unitNumber = 6; // next device # in SCSI chain... vdCfgSpec[0].device.unitNumberSpecified = true; vdCfgSpec[0]->device->unitNumberSpecified = true; VimApi::Description^ deviceInfo = gcnew VimApi::Description(); deviceInfo->label = "ShivaDisk"; deviceInfo->summary = ""; vdCfgSpec[0]->device->deviceInfo = deviceInfo; /// Create the Virtual Machine managed object VimApi::ManagedObjectReference ^vm = gcnew VimApi::ManagedObjectReference(); vm->type = "VirtualMachine"; vm->Value = "16"; // Create the VirtualMachineConfigSpec object VimApi::VirtualMachineConfigSpec^ virtualMacConfigSpec = gcnew VimApi::VirtualMachineConfigSpec(); virtualMacConfigSpec->deviceChange = vdCfgSpec; m_pVimSvc->ReconfigVM_Task(vm,virtualMacConfigSpec);
Hi, It looks like you problem is in defining vdCfgSpec of type VirtualDeviceConfigSpec. DeviceChange property of virtualMacConfigSpec needs an array object of type VirtualDeviceConfigSpec and... See more...
Hi, It looks like you problem is in defining vdCfgSpec of type VirtualDeviceConfigSpec. DeviceChange property of virtualMacConfigSpec needs an array object of type VirtualDeviceConfigSpec and setting for each device, which needs to set using the index of array something like this. vdCfgSpec[0]->operationSpecified = true; Finally you should call populate the property device change like this. virtualMacConfigSpec->deviceChange = vdCfgSpec //vdCfgSpec should already defined as an array in the starting of program. While you code snippet virtualMacConfigSpec->deviceChange = gcnew array ; is not getting an array of VirtualDeviceConfigSpec and moreover no property didn't set for an element of VirtualDeviceConfigSpec object. I hope it helps to make the changes in the code and would work. Please let us know, if you still facing the issue. Thanks Niket
Apologies if this is the wrong community for this question, but it seemed the closest to what I want. My company is working on a tool that, among other things, creates VMDKs for use with E... See more...
Apologies if this is the wrong community for this question, but it seemed the closest to what I want. My company is working on a tool that, among other things, creates VMDKs for use with ESX. We're working on a way to automatically upload the created VMDKs to ESX servers. One problem we're running in to is that best practices for VMFS suggest VMDKs should be pre-allocated and that using tools like scp to copy VMDKs over to ESX is a bad idea due to the fact that scp will keep appending to the file until it's transferred, as opposed to preallocating it first. Users of SCP are told to use Veem's tool or use vmfsctl to copy the VMDK into the repository, but neither of those options are acceptable to us for various reasons. My question, then, is this: From C code running on the service console, what is the proper way to create a VMDK and subsequently populate it with data such that VMFS is properly utilized and an excess of SCSI reservations are not generated? Is there a VMFS system call for this, or a function exported from a library? How does vmfsctl accomplish it? Thanks in advance for any help. Adam
Hi, I am now getting the new error "Failed to power on scic0:6(/vmfs/volumes/.......). What is the problem.Any help from anyone. Thanks Neela ... See more...
Hi, I am now getting the new error "Failed to power on scic0:6(/vmfs/volumes/.......). What is the problem.Any help from anyone. Thanks Neela
The question is do we need to create vmdk file in before hand or will it be created automatically by creating rdm using the file name specified in file path? Thanks in advance ... See more...
The question is do we need to create vmdk file in before hand or will it be created automatically by creating rdm using the file name specified in file path? Thanks in advance Regards Neela
Hi Mac, For creating RDM we need to do the following: Create the VirtualDeviceConfigSpec and set its properties. Create VirtualMachineConfigSpec object and set the VirtualDeviceCo... See more...
Hi Mac, For creating RDM we need to do the following: Create the VirtualDeviceConfigSpec and set its properties. Create VirtualMachineConfigSpec object and set the VirtualDeviceConfigSpec to the device change property of VirtualMachineConfigSpec object. 3. Call the ReconfigVM_Task. If I follow the process 1 specified below getting the error “Incompatible device backing specified for device 0 “ as it is unable to create the vmdk file with the path specified in backingInfo->fileName. If I specify backingInfo->fileName=”[datastorename]” then it is creating Virtual Disk with unknown size which is not RDM. But if I follow the process 2 , first create vmdk file and then specify this file in backingInfo->fileName, its working fine. But the problem is it works only in case of ESXServer not Virtual Center because for creating VirtualDisk_Task, it takes VirtualDiskManager as Parameter which is not set in case of Virtual Center. So we are unable to understand why it is failing to create the RDM in process 1. I am also enclosing the link where the guy is able to create RDM using Process 1. Link : We came to know how to set the values for the following properties also backingInfo->lunUuid vdCfgSpec->device->unitNumber vdCfgSpec->device->controllerKey I also tried setting the below property in process 1 but no use vdCfgSpec ->fileOperation = VirtualDeviceConfigSpecFileOperation::create; vdCfgSpec ->fileOperationSpecified = true; I am still working on this, but if you find any solution on process 1, please let me know. Thanks & Regards Neela 1.Process to create a RDM (Error : Incompatible device backing specified for device 0) ================== /// Create VirtualDeviceConfigSpec object and set its properties VimApi::VirtualDeviceConfigSpec^ vdCfgSpec = gcnew VimApi::VirtualDeviceConfigSpec(); vdCfgSpec->operation = VirtualDeviceConfigSpecOperation::add; vdCfgSpec->operationSpecified = true; vdCfgSpec->device = gcnew VirtualDisk(); VirtualDiskRawDiskMappingVer1BackingInfo^ backingInfo = gcnew VirtualDiskRawDiskMappingVer1BackingInfo(); backingInfo->compatibilityMode = "physicalMode"; /// Need to be changed to the canonical name backingInfo->deviceName = "vmhba1:1:17:0"; //p_VDisk->; backingInfo->diskMode = "independent_persistent"; backingInfo->lunUuid = 01002d00003030303032374443303030374d61676e6974; // uuid we can get from the Host backingInfo->fileName = "[Primary] vm.vmdk"; // Note: set any *Specified values to true vdCfgSpec->device->backing = backingInfo; vdCfgSpec->device->connectable = gcnew VirtualDeviceConnectInfo(); vdCfgSpec->device->connectable->allowGuestControl = true; vdCfgSpec->device->connectable->connected = true; vdCfgSpec->device->connectable->startConnected = true; vdCfgSpec->device->controllerKey = 1000;//vdary[iSCSIControllerIndex].key; // you may have one already, or have to create one in this same spec. vdCfgSpec->device->controllerKeySpecified = true; vdCfgSpec->device->key = -1; // all devices can be -1, but. all SCSI controllers must have unique -ve values vdCfgSpec->device->unitNumber = 3; // next device # in SCSI chain... vdCfgSpec[0].device.unitNumberSpecified = true; vdCfgSpec->device->unitNumberSpecified = true; VimApi::Description^ deviceInfo = gcnew VimApi::Description(); deviceInfo->label = "HardDisk123"; deviceInfo->summary = ""; vdCfgSpec->device->deviceInfo = deviceInfo; /// Create the Virtual Machine managed object VimApi::ManagedObjectReference ^vm = gcnew VimApi::ManagedObjectReference(); vm->type = "VirtualMachine"; Morpheus::Model::VMW_ModelObjectId^ VMobj = safe_cast<Morpheus::Model::VMW_ModelObjectId^> (this->ObjectId); vm->Value = VMobj->MOB->Value; // Create the VirtualMachineConfigSpec object VimApi::VirtualMachineConfigSpec^ virtualMacConfigSpec = gcnew VimApi::VirtualMachineConfigSpec(); virtualMacConfigSpec->deviceChange = gcnew array<VimApi::VirtualDeviceConfigSpec^> ; m_pVimSvc->ReconfigVM_Task(vm,virtualMacConfigSpec); 2. Process to create a RDM by creating the vmdk file first and then creating RDM (But works only with ESXServer not Virtual Center) ================================================================================================ // Create the VirtualDiskManager MO VimApi::ManagedObjectReference ^virtualDiskManager = gcnew VimApi::ManagedObjectReference(); virtualDiskManager->type = "VirtualDiskManager"; virtualDiskManager->Value = "ha-vdiskmanager"; /// create a DeviceBackedVirtualDiskSpec ob VimApi::DeviceBackedVirtualDiskSpec^ virtualDiskSpec = gcnew VimApi::DeviceBackedVirtualDiskSpec(); virtualDiskSpec->diskType = "rdm"; virtualDiskSpec->adapterType = "lsiLogic"; virtualDiskSpec->device = p_VDisk->VMWDevicepath; pVim->CreateVirtualDisk_Task(virtualDiskManager,"[Primary] vm.vmdk",nullptr,virtualDiskSpec); /// Create VirtualDeviceConfigSpec object and set its properties VimApi::VirtualDeviceConfigSpec^ vdCfgSpec = gcnew VimApi::VirtualDeviceConfigSpec(); vdCfgSpec->operation = VirtualDeviceConfigSpecOperation::add; vdCfgSpec->operationSpecified = true; vdCfgSpec->device = gcnew VirtualDisk(); VirtualDiskRawDiskMappingVer1BackingInfo^ backingInfo = gcnew VirtualDiskRawDiskMappingVer1BackingInfo(); backingInfo->compatibilityMode = "physicalMode"; /// Need to be changed to the canonical name backingInfo->deviceName = "vmhba1:1:17:0"; //p_VDisk->; backingInfo->diskMode = "independent_persistent"; backingInfo->lunUuid = 01002d00003030303032374443303030374d61676e6974; // uuid we can get from the Host backingInfo->fileName = "[Primary] vm.vmdk"; // Note: set any *Specified values to true vdCfgSpec->device->backing = backingInfo; vdCfgSpec->device->connectable = gcnew VirtualDeviceConnectInfo(); vdCfgSpec->device->connectable->allowGuestControl = true; vdCfgSpec->device->connectable->connected = true; vdCfgSpec->device->connectable->startConnected = true; vdCfgSpec->device->controllerKey = 1000;//vdary[iSCSIControllerIndex].key; // you may have one already, or have to create one in this same spec. vdCfgSpec->device->controllerKeySpecified = true; vdCfgSpec->device->key = -1; // all devices can be -1, but. all SCSI controllers must have unique -ve values vdCfgSpec->device->unitNumber = 3; // next device # in SCSI chain... vdCfgSpec[0].device.unitNumberSpecified = true; vdCfgSpec->device->unitNumberSpecified = true; VimApi::Description^ deviceInfo = gcnew VimApi::Description(); deviceInfo->label = "HardDisk123"; deviceInfo->summary = ""; vdCfgSpec->device->deviceInfo = deviceInfo; /// Create the Virtual Machine managed object VimApi::ManagedObjectReference ^vm = gcnew VimApi::ManagedObjectReference(); vm->type = "VirtualMachine"; Morpheus::Model::VMW_ModelObjectId^ VMobj = safe_cast<Morpheus::Model::VMW_ModelObjectId^> (this->ObjectId); vm->Value = VMobj->MOB->Value; // Create the VirtualMachineConfigSpec object VimApi::VirtualMachineConfigSpec^ virtualMacConfigSpec = gcnew VimApi::VirtualMachineConfigSpec(); virtualMacConfigSpec->deviceChange = gcnew array<VimApi::VirtualDeviceConfigSpec^> ; m_pVimSvc->ReconfigVM_Task(vm,virtualMacConfigSpec); Regards Neela
Hi all, For creating RDM we need to do the following: 1.Create the VirtualDeviceConfigSpec and set its properties. 2.Create VirtualMachineConfigSpec object and set the... See more...
Hi all, For creating RDM we need to do the following: 1.Create the VirtualDeviceConfigSpec and set its properties. 2.Create VirtualMachineConfigSpec object and set the VirtualDeviceConfigSpec to the device change property of VirtualMachineConfigSpec object. 3. Call the ReconfigVM_Task. If I follow the process 1 specified below getting the error "Incompatible device backing specified for device 0 " as it is unable to create the vmdk file with the path specified in backingInfo->fileName. If I specify backingInfo->fileName="[datastorename]" then it is creating Virtual Disk with unknown size which is not RDM. But if I follow the process 2 , first create vmdk file and then specify this file in backingInfo->fileName, its working fine. But the problem is it works only in case of ESXServer not Virtual Center because for creating VirtualDisk_Task, it takes VirtualDiskManager as Parameter which is not set in case of Virtual Center. So we are unable to understand why it is failing to create the RDM in process 1. I am also enclosing the link where the guy is able to create RDM using Process 1. Link : http://communities.vmware.com/thread/38923;jsessionid=14172672B2B1D99EBB70617BD6066CE5?tstart=15 We came to know how to set the values for the following properties also backingInfo->lunUuid vdCfgSpec->device->unitNumber vdCfgSpec->device->controllerKey I also tried setting the below property in process 1 but no use vdCfgSpec ->fileOperation = VirtualDeviceConfigSpecFileOperation::create; vdCfgSpec ->fileOperationSpecified = true; I am still working on this, but if you find any solution on process 1, please let me know. Thanks & Regards Neela 1.Process to create a RDM (Error : Incompatible device backing specified for device 0) ================== /// Create VirtualDeviceConfigSpec object and set its properties VimApi::VirtualDeviceConfigSpec^ vdCfgSpec = gcnew VimApi::VirtualDeviceConfigSpec(); vdCfgSpec->operation = VirtualDeviceConfigSpecOperation::add; vdCfgSpec->operationSpecified = true; vdCfgSpec->device = gcnew VirtualDisk(); VirtualDiskRawDiskMappingVer1BackingInfo^ backingInfo = gcnew VirtualDiskRawDiskMappingVer1BackingInfo(); backingInfo->compatibilityMode = "physicalMode"; /// Need to be changed to the canonical name backingInfo->deviceName = "vmhba1:1:17:0"; //p_VDisk->; backingInfo->diskMode = "independent_persistent"; backingInfo->lunUuid = 01002d00003030303032374443303030374d61676e6974; // uuid we can get from the Host backingInfo->fileName = "[Primary] vm.vmdk"; // Note: set any *Specified values to true vdCfgSpec->device->backing = backingInfo; vdCfgSpec->device->connectable = gcnew VirtualDeviceConnectInfo(); vdCfgSpec->device->connectable->allowGuestControl = true; vdCfgSpec->device->connectable->connected = true; vdCfgSpec->device->connectable->startConnected = true; vdCfgSpec->device->controllerKey = 1000;//vdary[iSCSIControllerIndex].key; // you may have one already, or have to create one in this same spec. vdCfgSpec->device->controllerKeySpecified = true; vdCfgSpec->device->key = -1; // all devices can be -1, but. all SCSI controllers must have unique -ve values vdCfgSpec->device->unitNumber = 3; // next device # in SCSI chain... vdCfgSpec[0].device.unitNumberSpecified = true; vdCfgSpec->device->unitNumberSpecified = true; VimApi::Description^ deviceInfo = gcnew VimApi::Description(); deviceInfo->label = "HardDisk123"; deviceInfo->summary = ""; vdCfgSpec->device->deviceInfo = deviceInfo; /// Create the Virtual Machine managed object VimApi::ManagedObjectReference ^vm = gcnew VimApi::ManagedObjectReference(); vm->type = "VirtualMachine"; Morpheus::Model::VMW_ModelObjectId^ VMobj = safe_cast (this->ObjectId); vm->Value = VMobj->MOB->Value; // Create the VirtualMachineConfigSpec object VimApi::VirtualMachineConfigSpec^ virtualMacConfigSpec = gcnew VimApi::VirtualMachineConfigSpec(); virtualMacConfigSpec->deviceChange = gcnew array ; m_pVimSvc->ReconfigVM_Task(vm,virtualMacConfigSpec); 2. Process to create a RDM by creating the vmdk file first and then creating RDM (But works only with ESXServer not Virtual Center) ================================================================================================ // Create the VirtualDiskManager MO VimApi::ManagedObjectReference ^virtualDiskManager = gcnew VimApi::ManagedObjectReference(); virtualDiskManager->type = "VirtualDiskManager"; virtualDiskManager->Value = "ha-vdiskmanager"; /// create a DeviceBackedVirtualDiskSpec ob VimApi::DeviceBackedVirtualDiskSpec^ virtualDiskSpec = gcnew VimApi::DeviceBackedVirtualDiskSpec(); virtualDiskSpec->diskType = "rdm"; virtualDiskSpec->adapterType = "lsiLogic"; virtualDiskSpec->device = p_VDisk->VMWDevicepath; pVim->CreateVirtualDisk_Task(virtualDiskManager,"[Primary] vm.vmdk",nullptr,virtualDiskSpec); /// Create VirtualDeviceConfigSpec object and set its properties VimApi::VirtualDeviceConfigSpec^ vdCfgSpec = gcnew VimApi::VirtualDeviceConfigSpec(); vdCfgSpec->operation = VirtualDeviceConfigSpecOperation::add; vdCfgSpec->operationSpecified = true; vdCfgSpec->device = gcnew VirtualDisk(); VirtualDiskRawDiskMappingVer1BackingInfo^ backingInfo = gcnew VirtualDiskRawDiskMappingVer1BackingInfo(); backingInfo->compatibilityMode = "physicalMode"; /// Need to be changed to the canonical name backingInfo->deviceName = "vmhba1:1:17:0"; //p_VDisk->; backingInfo->diskMode = "independent_persistent"; backingInfo->lunUuid = 01002d00003030303032374443303030374d61676e6974; // uuid we can get from the Host backingInfo->fileName = "[Primary] vm.vmdk"; // Note: set any *Specified values to true vdCfgSpec->device->backing = backingInfo; vdCfgSpec->device->connectable = gcnew VirtualDeviceConnectInfo(); vdCfgSpec->device->connectable->allowGuestControl = true; vdCfgSpec->device->connectable->connected = true; vdCfgSpec->device->connectable->startConnected = true; vdCfgSpec->device->controllerKey = 1000;//vdary[iSCSIControllerIndex].key; // you may have one already, or have to create one in this same spec. vdCfgSpec->device->controllerKeySpecified = true; vdCfgSpec->device->key = -1; // all devices can be -1, but. all SCSI controllers must have unique -ve values vdCfgSpec->device->unitNumber = 3; // next device # in SCSI chain... vdCfgSpec[0].device.unitNumberSpecified = true; vdCfgSpec->device->unitNumberSpecified = true; VimApi::Description^ deviceInfo = gcnew VimApi::Description(); deviceInfo->label = "HardDisk123"; deviceInfo->summary = ""; vdCfgSpec->device->deviceInfo = deviceInfo; /// Create the Virtual Machine managed object VimApi::ManagedObjectReference ^vm = gcnew VimApi::ManagedObjectReference(); vm->type = "VirtualMachine"; Morpheus::Model::VMW_ModelObjectId^ VMobj = safe_cast (this->ObjectId); vm->Value = VMobj->MOB->Value; // Create the VirtualMachineConfigSpec object VimApi::VirtualMachineConfigSpec^ virtualMacConfigSpec = gcnew VimApi::VirtualMachineConfigSpec(); virtualMacConfigSpec->deviceChange = gcnew array ; m_pVimSvc->ReconfigVM_Task(vm,virtualMacConfigSpec);
Hi all, Can any one know about how to get the virtual device node list. in Virtual infrastructure client while creating rdm/vmdk the create wizard will ask to select any one virtual... See more...
Hi all, Can any one know about how to get the virtual device node list. in Virtual infrastructure client while creating rdm/vmdk the create wizard will ask to select any one virtual device node. i need to do this programatically,is there is any property in esxsever to get these virtual device list, i attached screen shot Sample.jpg just have a look.if any one having sample code please paste it. Thanks karthik.
Hi Sidharth , Thanks for your reply, after seeing your code i modified my code actually i am working c++/CLi it's working fine but some times it's causing problem, this sample co... See more...
Hi Sidharth , Thanks for your reply, after seeing your code i modified my code actually i am working c++/CLi it's working fine but some times it's causing problem, this sample code helped me a lot. thanks --karthik
Wow - sounds pretty cool. I was under the impression that vdiskmanager with -r option must create the output-vmdk itself. hearing that it can convert into an existing disk is good news - I'll t... See more...
Wow - sounds pretty cool. I was under the impression that vdiskmanager with -r option must create the output-vmdk itself. hearing that it can convert into an existing disk is good news - I'll test and report. What about size ? - I guess the target vmdk on ESX must be slightly larger than the source ? Thanks Ulli ___________________________________ description of vmx-parameters: VMware-liveCD:
Perhaps I am missing something here - however: Assuming you created the destination VM (and the disk) thru some other mechanism : you can use vmware-vdiskmanager.exe -r with the destination E... See more...
Perhaps I am missing something here - however: Assuming you created the destination VM (and the disk) thru some other mechanism : you can use vmware-vdiskmanager.exe -r with the destination ESX . vmware-vdiskmanager.exe -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com -u username -f passwordfile "\[storage1]/path/to/targetDisk.vmdk" You might also be able to use RCLI which has similar functionality. -Sudarsan