Reason: The called function can only be performed on partial strings. Please open the virtual disk parent.

Similar Questions

• "The virtual disk parent has changed..." "after removing a few shots

  Hey!

  I'm using VMWare Workstation and deleted a few shots via the Snapshot Manager. I used a .vhd Image from the Microsoft Site (Windows Server 2003, x 86). VMWare has created a link to this image at the beginning. I was working on this virtual machine for 2 weeks.

  Now, I have deleted 2 snapshots, including the first snapshot. When I try to start all the existing snapshots the error which is entered in the subject line of this discussion. Detailed error explains that his "cannot open disk 0 - 0000004.vmdk or one of the snapshot disks it costs on.» Reason: the virtual disk parent... »

  How can I access any of the existing snapshots in the future? I read that it is necessary to open the virtual disk images and change the CID of this disk image virtual to who should be the one parent. But how do I edit these virtual disk in windows vista? I have no command line tool that extracts only the first 20 lines of a file so that it will be impossible for me to open a vhdk with 600 or 700 MB. Another problem is that (I don't know why) my virtual disks are splitet in so many parts (I said at the beginning that the virtual disk must be a file, but I think splitet VMWare Workstation it because she had to be converted to .vhd (Microsoft) .vhdk... might be?)

  Here's a screenshot of my file of VMWare this virtual machine sorted by type and sorted by size (for a better overview, I think):

  na ja... Falls die Datei ist - wurde neulich, als VirtualPC platte used sharp available?

  Wenn nein - und nur dann!

  ersetz

  disk-0 - 000002.vmdk

  disk-0 - 000004.vmdk

  mit den editierten aus dem Anhang versions.

  Falls from the dir unsicher bist - nach frag!

  Ulli

  ___________________________________

  VMX-settings- VMware-liveCD - VM-infirmary

• Please help: the virtual disk parent has changed...

  After a few days of research about this error, I decided that I had to ask for some evidence of your experts to help me recover from this error.

  Thank you!

  It is a small desktop application:

  -Dell T410 esxi Server 5

  -a virtual machine, Windows Server 2003 with 2 discs, no fixed size

  I was help this office by managing services and updates on this Server 2003.  I ran updates on Friday and restarted.  When he came I open vSphere and found the virtual machine does not.  I tried to start it and got the error.  So, it seems I may have the CID issue that needs to be corrected.

  I don't have a direct access to this server so I'm remoting with RDS on 2003 VM server and vSphere on the esxi.  Did I make the right diagnosis and is it possible for me to make the necessary corrections to distance or I need direct access to the server?  Everything I've read has files of people editing CID numbers and it seems that they directly access the esxi server.

  Shows the data store:

  hard 'server '.

  hard 'server_1.

  'server' - 000001.vmdk

  "server_1" - 000001.vmdk

  'server' - snapshot1.vmsn

  I stuck a few newspapers below...

  DISC: Scsi0:0 [OPEN ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' persistent R]
  2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001-delta.vmdk ': open with success (10) size = 5620404224, hd = 213826. Type 8
  2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-DSCPTR: open [0]: "Server-000001 - delta.vmdk ' (0xa)
  2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-LINK: open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' (0xa): vmfsSparse, 35526656 sectors / 16.9 GB.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-flat.vmdk ': open with success (14) size = 18189647872, hd = 181059. Type 3
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-DSCPTR: open [0]: 'server - flat hard' (0xe)
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-LINK: open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk' (0xe): vmfs, 35526656 sectors / 16.9 GB.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB LINK: DiskLinkIsAttachPossible: incompatibility of the content ID (parentCID f72e60c7! = f05537b3) /vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-STRING: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk ': cannot open (the virtual disk parent has changed since the child was created.) The content of the virtual disk ID parent does not match the ID of parent for children's content).
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001-delta.vmdk ': closed.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-flat.vmdk ': closed.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-LIB: can't open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' with the virtual disk 0xa flags parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent for children (18) content.
  2012-08 - 05T 20: 00:06.035Z | VMX | DRIVE: Cannot open disk ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk ': the virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent for children (18) content.
  2012-08 - 05T 20: 00:06.035Z | VMX | Msg_Post: error
  2012-08 - 05T 20: 00:06.035Z | VMX | [msg.disk.noBackEnd] unable to open drive ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' or one of the snapshot disks it depends on.
  2012-08 - 05T 20: 00:06.035Z | VMX | [msg.disk.configureDiskError] reason: the virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent matching the child content.
  2012-08 - 05T 20: 00:06.035Z | VMX |

  Thanks again for any direction you can provide!

  / r

  John

  The parentCID of the snapshot must match the CID from its parent, as shown in the log file

  "... The content ID mismatch (parentCID f72e60c7! = f05537b3)... »

  Server.VMDK

  CID = f05537b3
  parentCID = ffffffff

  Server - 000001.vmdk

  CID = a2b9ba8b
  parentCID = f72e60c7---> f05537b3

  Make sure you change the file on the host using the vi editor or - if you want to change the file in Windows - use an editor who is aware of the line breaks Unix (do not use Notepad!)

  Once this is done, I highly recommend that you take another cliché before you on the virtual computer. This prevents existing virtual disk files to be modified, so that you can return to this State where you need. After that everything works as expected, consider deleting all snapshots.

  André

• The virtual disk parent has changed since the child was created

  Hi all, need your help with this one.

  I deleted two snapshots and now I can not start the virtual machine.

  Get the following error:

  Reason: The virtual disk parent has changed since the child was created.
  Cannot open disk ' / vmfs/volumes/4c483d34-a8c778c4-46a5-001cc460f09e/WEBPDXXXY/WEBPDXXXY_1-000003.vmdk' or one of the snapshot disks it depends on.

  I tried that link but still did not work KB: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 1007969

  I can still see the WEBPDXXXY_1 - 000003.vmdk, WEBPDXXXY_1 - 000002.vmdk and WEBPDXXXY_1 - 000001.vmdk when I browse the data store.

  WEBPDXXXY_1 - 000003.vmdk

  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.
  CID = 59fab513
  parentCID = a4a63bd5
  isNativeSnapshot = 'no '.
  createType = "vmfsSparse."
  parentFileNameHint = "WEBPDXXXY_1 - 000002.vmdk".
  # Description of the measure
  RW 157286400 VMFSSPARSE ' WEBPDWEBPDXXXY_1-000003 - delta.vmdk.

  # The database disk
  #DDB

  WEBPDXXXY_1 - 000002.vmdk
  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.
  CID = a4a63bd5
  parentCID = 0f8995f3
  isNativeSnapshot = 'no '.
  createType = "vmfsSparse."
  parentFileNameHint = "WEBPDXXXY_1 - 000001.vmdk".
  # Description of the measure
  RW 157286400 VMFSSPARSE ' WEBPDXXXY_1-000002 - delta.vmdk.

  # The database disk
  #DDB

  DDB. Deletable = 'true '.
  ddb.longContentID = "ab1b7008e386c884ae920930a4a63bd5".

  WEBPDXXXY_1 - 000001.vmdk

  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.
  CID = 0f8995f3
  parentCID = 926f96fa
  isNativeSnapshot = 'no '.
  createType = "vmfsSparse."
  parentFileNameHint = "WEBPDXXXY_1.vmdk".
  # Description of the measure
  RW 157286400 VMFSSPARSE ' WEBPDXXXY_1-000001 - delta.vmdk.

  # The database disk
  #DDB

  ddb.longContentID = "0336846d9f849b4b97ad028f0f8995f3".
  DDB. Deletable = 'true '.

  WEBPDXXXY_1.VMDK

  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.

  CID = 926f96fa

  parentCID = ffffffff
  isNativeSnapshot = 'no '.
  createType = "vmfsRawDeviceMap."

  # Description of the measure
  RW 209715200 VMFSRDM ' WEBPDXXXY_1 - rdm.vmdk '.

  # The database disk
  #DDB

  ddb.toolsVersion = "8295.
  ddb.adapterType = "free".
  DDB. Geometry.sectors = "63".
  DDB. Geometry.Heads = "255".
  DDB. Geometry.Cylinders = "13054.
  DDB. UUID = "60 00 C2 92 41 62 5 d 8f-10 59 12 60 53 0 to a8 94.
  ddb.longContentID = "b204c5bc523bbc83c01dd3ed926f96fa".
  ddb.virtualHWVersion = "7".
  DDB. Deletable = 'true '.

  Is there a chance to run ls-lisa from the command line (SSH) in the virtual machine folder and provide the output!

  I ask because I'm a little worried about the timestamp of the hard (May 2011). Depending on the size of the files in the snapshot, it seems that the second virtual disk is not really used by the guest operating system and we could come back manually (by editing the .vmx file) on the resized basic disk (100 GB compared to 75 GB for snapshots) without losing important data!

  If you want to revert manually,

  • delete the virtual machine of the inventory
  • backup and then edit the .vmx file (replace "WEBPDMAPPD_1 - 000003.vmdk" with "WEBPDMAPPD_1.vmdk")
  • Move 3 snapshots in a directory temporary sub
  • Add the virtual machine to inventory
  • create a new snapshot to prevent the current hard files to be modified
  • Turn on the virtual machine

  If everything works as expected, you can delete the snapshot files moved and remove the snapshot created in the Snapshot Manager again.

  André

• the virtual disk parent changed

  I just did something really stupid and hope someone here could help me...

  I have a virtual host named dev4, that has a snapshot created a year ago.  It has several virtual disks, one of them is dev4 - 000001.vmdk, who has a parent disk dev4.vmdk.

  Today I come to create a new virtual machine named dev5.   My intention was to disparage dev4 and use dev5 moving forward, so I want all my data in the virtual disks of dev4 is available in dev5.

  Now, it's the stupid part.  I added two dev4 - 000001.vmdk and dev4.vmdk (one at a time) to the new machine virtual (dev5) and mounted to them (I was running Fedora in two virtual machines).    It's really successful, but then I can't repeat this process and dev4 won't boot either.  "I got the error message was.

  Details: Cannot open the disc "C:\Virtual Machines\dev4\dev4-000001.vmdk" or one of the snapshot disks it depends on.

  Reason: The virtual disk parent has changed since the child was created.

  "

  Apparently the action to add the dev4.vmdk drive to dev5 or mount in dev5 led her to change.  I have a lot of data in dev4 - 000001.vmdk which are not saved.  Is it possible I could get these restored data?  Right now I can not open this vmdk due the above error.    Any help would be much appreciated!

  Sorry Peter - I guess I was kinda hard...

  It's just that in so many cases users who have encountered a problem with the snapshots do themselves more damage by acting in quick.

  Please read my full vmdk-manual so that you are better prepared next time.

  And now - please read this

  http://sanbarrow.com/VMDK-HOWTOs.html#editvmdk

  We will need it then

  _________________________

  VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

• repair broken CID-String > the virtual disk parent has changed since the child was created.

  Hello

  We have ESX 3.5 Update2

  During the withdrawal of one of the many snapshots, the process has been crushed and the CID string seems to be corrupted.

  Now the last work of x file - 000006.vmdk cannot start because the file is based on x - 000004.vmdk.

  Now, I get this message:

  Cannot open disk /vmfs/volumes...x-000007.vmdk or one of the Flash disk that it depends on.

  Reason: The virtual disk parent has changed since the child was created.

  If you provide vmdk small text files, all the vmware.logs, the vmsd file and the vmx file I can look into it

  ___________________________________

  VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

• Instant restore: the virtual disk parent has changed since the child has been created

  Buenos dias,

  A worm if someone is ha sown con este problema y me can echar UN cable.

  Al trabajar con una maquina virtual en local con el disco en un disco external depuradora, to me broken instant crear of the United Nations (por el disco local creo en lo disgrace).

  Al use esta Máquina in casa, arranco perfectly, claro, pero sin los datos del snapshot.

  Hoy al arrancarla in the oficina ha generated a conflict: "the virtual disk parent has changed, since the child was creates," ha detectado what ha modified the virtual machine after ultima grabación del snapshot, no permite arrancarla.

  Could eliminando el solucionarlo snapshot, pero no puedo perder todo lo as he ido generating information.

  Alguna idea?

  Para eso estamos DiegoPS.

  No olvides close the discusion marcandola como respondida.

  Saludos,

• Problem with a VM server: "the virtual disk parent has been changed since the child was created.

  Hello!

  I have a problem with a server that does not start.

  We had a virtual machine running on VMWare Infrastructure 3 with two hard drives and an instant backup of them.

  This machine has been removed from the inventory, but when it has been recreated, the secondary hard drive is mentioned for the basic-disk vmdk
  instead of being referenced to the instant vmdk and used for a few days.

  All changes made after the snapshot, were kept in the delta snapshot file, which is not loaded.

  We are with difficult to reference the secondary disk for the snapshot file. We tried to edit the .vmx and hard disk files
  to correct the CID made reference, but when we try to start the virtual machine, we got this error:

  "The virtual disk parent has been changed since the child was created.

  I think it happens because we made a blow-up of a secondary drive a few weeks after the backup snapshot. We spent 30 GB to 50 GB.
  And because it has been referenced and used in another vm.

  *** Log is attached

  Thank you

  Bruno.

  It is a bad sign

  next step in the usual forest is to use "testdisk" since a LiveCD to set the tables MBR and partition - if possible

• Impossible to extend the drive the called function cannot be performed on the partial channels please open the virtual disk parent

  I can not add disk space for the file mapped to the C: drive.  I read in the discussions that, sometimes, this problem occurs when a snapshot exists.   I don't see any snapshot in the Snapshot Manager, but I see a file in the list of directories.  I've attached a screenshot of my desktop, as well as the list of directories of this virtual machine.  Any ideas?  Thank you!

  OK, in this case turning off the virtual machine and close the tab in VMware Workstation to make sure that the file is not in use (No .lck files or folders). Then copy the file "Windows Server 2008 R2 x64.vmds.bak" to "Windows Server 2008 R2 x64.vmsd" and remove the 3 lines, I scored below. "" Once done, you should be able to see and remove the snapshot in the Snapshot Manager.

  To be sure, I recommend the folder before deleting the backup snapshot.

  . Encoding = "windows-1252".
  snapshot.lastUID = '1 '.
  Snapshot.Current = '1 '.
  Snapshot.MRU0.UID = '1 '.
  snapshot0.UID = '1 '.
  snapshot0. FileName = "Windows Server 2008 R2 x 64 - Snapshot1.vmsn"
  snapshot0. DisplayName = "Snapshot to Clone of Windows Server 2008 R2 x 64"
  snapshot0. Description = "created by the effect of clone."
  snapshot0.createTimeHigh = "304598.
  snapshot0.createTimeLow = "160203992".
  snapshot0.clone0 = "Windows Server 2008 R2 x 64 C:\Users\smith.john\Documents\Virtual Machines\Clone (2) \Clone of Windows Server 2008 R2 x 64 (2) .vmx".
  snapshot0.clone1 = "C:\Users\brick\Documents\Virtual Machines\Clone of Windows Server 2008 R2, Windows Server 2008 R2 x64.vmx x64\Clone"
  snapshot0.numClones = '2 '.
  snapshot0.numDisks = '1 '.
  snapshot0.Disk0.filename = "Windows Server 2008 R2 x64.vmdk"
  snapshot0.Disk0.node = "scsi0:0". »
  snapshot.numSnapshots = '1 '.

  André

• Virtual disk parent has changed since the child was created.

  I recently had one of my virtual machines go down and I couldn't connect to access anything whatsoever, so I rode as an extra hard drive to another virtual machine in order to access the data I needed.

  Once I had finished I he took off the other VM and proceeds to the power on the virtual machine, but I got an error of:

  "The virtual disk parent has been changed since the child was created." The content of the virtual disk ID parent does not match the ID of parent matching the child content. »

  Reason: The virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent matching the child content.
  Cannot open disk ' / vmfs/volumes/4e24c6fe-3c2ad61e-a57c-e4115bbbce6c/SNCTrillium/SNCTrillium-000003.vmdk' or one of the snapshot disks it depends on.

  I read upward through the knowledge base of VMWare on the modified files, but I've never had to do that before and I'm not sure about how to go on this subject as I've never used the vsphere CLI either.

  I am currently using ESXi 5.0.0 with vsphere client 5.0.0. I've attached a screenshot of the error.

  According to the snapshot between SNCTrillium - 000001.vmdk and the basic disk SNCTrillium.vmdk is broken, which means that the basic disk has been changed. I have attached an instant replacement for the SNCTrillium - 000001.vmdk with a fixed string that should allow you to open the virtual machine. However, since I do not know what and how much data has changed on the basic disk, I can't tell you how much data corruption, you will see. So you better take an another snapshot to be temporary once loading hard file attached, in order to ensure the current hard data files cannot be changed.

  André

• Help, please! Snapshot after expand VM, virtual disk parent has changed since the child was created

  OK, here's the situation, (maybe you can find a lot of discussion on this one)

  I have a vmware server running SuSE Linux Enterprise Server 10. I use as its host vmware ESX 3.0.1.

  I realize that I need to extend the drive because he must have more space disk for the production server. Then I resize the disk using vmkfstools x 90 G TARANTELA - TEST.vmdk. The bad news is, I didn't know that the server has a snapshot on VI client. As you know, the error occurred:

  Failed to open the disc

  "/ vmfs/volumes/4652e777-3eb2a038-8fce-0019bb343796/TARANTELLA-TEST-000007.vmdk" or one of the snapshot disks it depends on.

  Reason: The virtual disk parent has been changed since the child was created

  Then I remove the snapshot of the VI client and re-save the virtual machine to inventory, but it may yet open the disc unless I edited the .vmx line file:

  scsi0:0. FileName = 'TARANTELA-TEST - 000007.vmdk '.

  TO

  scsi0:0. FileName = ' TARANTELA - TEST.vmdk.

  It runs as the first time I installed the system, but all the important configuration is in 'TARANTELA-TEST - 000007.vmdk' snapshot.

  Someone there the sollution, how can I do my work of snapshot again?

  Kind regards

  Arfal

  In SL32-AP-TARANTELA - TEST2.vmdk

  change

  CID=dc621992
  

  TO

  CID=ce700012
  

  and

  RW 188743680 VMFS "SL32-AP-TARANTELA-TEST2-flat.vmdk"
  

  TO

  RW 31457280 VMFS "SL32-AP-TARANTELA-TEST2-flat.vmdk"
  

  and

  ddb.geometry.cylinders = "11748"
  

  TO

  ddb.geometry.cylinders = "1958"
  

  in SL32-AP-TARANTELA-TEST2 - 000007.vmdk

  change

  RW 188743680 VMFSSPARSE "SL32-AP-TARANTELA-TEST2-000007-delta.vmdk"
  

  TO

  RW 31457280 VMFSSPARSE "SL32-AP-TARANTELA-TEST2-000007-delta.vmdk"
  

  And then you change the changes you have made to the VMX file.

  Try power o the VM - you will get probably mistakes (inside the virtual machine).

  If this works report back (we are not yet made).

• How can I change the size of the virtual disk by default?

  Hello

  At work, we decided to start to allocate more disk space for new virtual machines that we create. and every time I create a new virtual machine, and I pass by the Configuration, the name and location, storage, reviews of operating system and network options. I get to create a disc of the options and the size of the virtual disk is set to 16 GB by default. and then I would need to change before the new virtual machine to a larger number. I thought to myself whence this 16 GB by default is set and is it possible for me to change this value by default for example 30 GB, so whenever I have create a VM I wouldn't need to change this to 30 GB.

  Thank you for taking the time to read this discussion.

  Best regards

  S.A

  It would be a feature "nice to have", if we could set up by default to different operating systems. However, I am not aware of a way to do it. The only thing you can do in a cluster is to create a VM template and clone the new virtual machines from the model.

  André

• Performance of the virtual disks

  Hello!

  Two questions

  1 - it there really a big difference in the performance of the discs thin vs thin discs? one of my friends said slim is slower because he may need more and this growing each time may reduce the speed and performance. is this really?

  2. I get no difference between the discs of updated zero lazy-reset and greedy. that means for the impatient..., are the blocks are written by 0 at the beginning?

  There are a few blocks in the disc ok? then, what is the point to write zero in each of them and then change the exact data we want to be on that block? (maybe there is 1 maybe 0)

  Thank you very much

  So I will use zero - eager to drive thick for my server files (300 users and millions of files) and lazy zero for databases and thin for operating systems and machines at low load of I/O and small changes

  I recommend thick eager-reset to zero especially for databases. It can depend on the workload, however, there are various tutorials for how to configure databases. MS - SQL I usually create virtual discs eager-reset to zero and follow the best spirit of practice of MS formatting NTFS with a 64 KB Cluster size. Where the OS is Windows 2003, don't forget to align the partition! For more information, see Disk Partition alignment Best Practices for SQL Server

  Since, as you have discovered - reset is required will certainly benefit you eager-reset of the virtual disks.

  When you use thin disks, make sure you have the alarms in place to avoid the problems of out-of-space drive!

  André

• How to read the data written to the virtual disk

  I use the following VDDK function to read the Flash disk from VMware

  http://bigchainring.kicks-ass.NET/functions/VixDiskLib_Read.html

  But areas of complete disc playback, including empty spaces. I need to back up only the data written to the Flash disk. It is to save the backup disk space (for example if 126 instant KB is written in 40 GB of disk snapshot, then we read only 126 KB and not 40 GB drive). Please suggest the correct way to read the data written to the Flash disk as well as to reproduce the same virtual disk with the data.

  VMware vSphere API queryChangedDiskAreas() can be used to obtain the data blocks in the virtual disk.

  Steps to follow:

  1. get the beaches of block of data (numbers) using queryChangedDiskAreas() API with '*' as argument.

  2 read the data of the specific blocks by using VixDiskLib_Read()

  3. write to another drive using VixDiskLib_Write()

• Unable to create the virtual disk: fault. RestrictedVersion.summary

  Hello

  Im trying to create a virtual disk using the CLI on ESX4i.  The script is:

  vmkfstools.pl - Server 10.190.2.51 - c 20 g d eagerzeroedthick - a free /vmfs/volumes/Internal/test.vmdk

  When the script runs I get error: unable to create the virtual disk: fault. RestrictedVersion.summary

  Can someone tell me why please.  Im trying to create a disk of 20 GB with adapter free with eagerzeroedthick on my internal called storage, (no subdirectory).

  The file system is THAT VMFS 3.33 maximum file size is 256 GB.  The block size is 1 MB.  If it is the block size that is the problem how can I easily change?

  It's in a laboratory, not a production environment.  I need the flag eagerzeroedthick like Im trying to create a passive active cluster node MSCS 2 on a single physical node with 2 machines VMS.

  Thank you.

  Mike.

  If you use the free version of ESXi (U4 and later versions), access to tools like the VIMA API are read-only.

  -Matt

  VCP, vExpert, Unix Geek