Cannot resize the virtual disk

Similar Questions

• cannot resize the virtual disk (vmdk) after successful hyper-v conversion

  Hello

  We are experiencing an environment vSphere 4.1. I have a problem on the Ramdisk resizing.

  We had managed to convert a hyper v VM. Virtual machine operating system is Windows 2008.

  After that, I can't resize the virtual disk (GB in disk options was gray-ed out, even when the virtual machine is power down)

  It's strange

  I have attached several screenshot of the virtual machine.

  Need your advice.

  Thank you

  His grace is on the IDE interface and you can not resize. the only way is to reclone using vmware converter and resize in the wizard. For more information: http://www.yellow-bricks.com/2010/05/28/resizing-your-ide-virtual-harddisk/

• Cannot resize the virtual disk, the virtual machine by using a «child» vmdk file

  Release: VMWare workstation 9

  SE host: Windows 7 64-bit

  Screenshots below.

  I want to resize my VM from 50 GB to 100 GB.

  It seems that VMware workstation 9 uses a child for my VM vmdk.  In my case, using its "Windows Server 2008 R2 x 64 - 000001.vmdk" for its virtual disk file.  The correct file should be "Windows Server 2008 R2 x64.vmdk", I think.

  There are currently no snapshots registered for this virtual machine, I see.

  The virtual machine works well as is, but I can't resize the disk without the VMWare gui, saying I should be perform the operation on the parent vmdk file.

  It seems that I do run a snapshot that is not really a snapshot?  How to merge with the older files - Sxx.vmdk to 0000xx - Sxxx.vmdk

  I also tried to use the command line tool to manually resize the vmdk parent, but I get permission "access denied" errors.

  Kind regards

  Matt

  -------------------------------------------

  Parameters of the HARD disk:

  

  Error:

  

  Files:

  

  He no snapshots are displayed in the Manager of snapshot with the check box 'Show AutoProtect snapshots' verified then the snapshot is an orphan and the best way I use normally to fix this if I want the contents of the snapshot of orphan to be among the basic disk is with tab of the virtual machine in VMware Workstation GUI closed I simply delete the .vmsd file and then open the virtual machine tab in the VMware Workstation GUI and cover and immediately remove a snapshot in the Snapshot Manager.  This will force the orphan snapshot to merge with the parent disk.  Then to clean I still remove the .vmsd file and orphans, .vmsn and .vmem file.

  Note: Before the procedure you have a good backup of the virtual machine in case you accidentally mess something up.

• Resize the virtual disk

  I just had to re - create a virtual machine because my original size was too small.

  First, is there a way for me to expand the drive without having to recreate?  and

  I had a disk Acronis True Image backup, and I was trying just res it toe to a larger drive, but I couldn't understand how to launch True Image so that the virtual machine can boot from the disc of TI and start the restore.  I got the TI part to run (by installing the disk, thinking I could then restore the image "on"), but he could not see my USB external drive.

  It seems from what I see the recognition of the external USB drives is difficult - does include flash drives? -So how/where can I back up my VM so it will be available for a restore and visible to the Acronis boot CD - because I'm assuming that my installation of TI in the hopes of restoring the top disc would not work (in any case).

  Kind regards

  Chuck bobo

  Hello

  Please find the attached file that will help you on how to resize the VMDK without the original data.

  Thank you

  Tanav

• New OS displays cannot see the virtual disk drive

  I am creating a new of Windows XP virtual machine on a standalone ESX Server using local storage.  After crossing the start of initial installation and learn how to "To install windows press" the next screen says

  «the installation program found no hard disk units installed in your computer»

  I read in a few places this may be due to the poor selection of bus or logic LSI logic when creating the virtual machine, but I tried them both and they both have the same error.

  Is it possible that the problem is the installation media that I use?  Other Installtion disks seem to find storage that I installed a 2003 server.

  Yep for XP, you must:

  VM-> change settings-> disk-> existing Floppy image in the data store-> Browse-> vmimages-> disk-> vmiscsi *.flp

  vcbMC - 1.0.6 Beta

  Lite vcbMC - 1.0.7

  http://www.no-x.org

• Resize and repartition the virtual disk

  Hi all

  I'm under ESXi 4 Update 1 with a 1.6 to RAID 5, which is currently all dedicated to a machine virtual storage (it has no partition system on it, just the files). It currently has two partitions: a partition of 1.1 TB for files and a 500 GB partition with the old backups.

  What I want to do is to delete the partition of 500 GB, give 400GO of it to 1.1 TB partition and then resize the virtual disk so that there are 100GB left in the data store that I can attribute to another virtual machine.

  Who is? I searched, but never found any concrete answer on the subject and don't want to risk losing data to fumble with the controls.

  Thanks for any help.

  OK, now I understand your conifugration.

  You can't reach your end goal without going through a temporary storage in the Middle, like a usb orrr additiiiional on a San disk storage space or the local disk

  (1) create a vmfs on extra storage temp

  (2) use the vmware converter to clone your SBS installation to a new server with the correct (1.5 TB) disk size on the vmfs temp

  (3) delete your source VM

  (4) move the vm cloned to original VMFS

  BTW: it is not a good idea to have a 1.5 TB LUN/VMFS filled 1/2 virtual machines using the entire VMFS TB 1.5: you have no place for the exchange of memory (if needded) and for snapshots. Please allow more space on the VMFS for such tasks. Rule formula says (((maxVMs * avgSize) + 20%) + total vRAM)

• What is the right way to expand the virtual disk and then the OS partition?

  I have a Windows XP operating system in a virtual machine VMware.  I have

  you want to increase the size of the hard drive.  It currently has a 50 GB

  partition on a 50 GB VHD.  I increase the size of the

  50 GB to 100 GB in VMware virtual hard drive.  Then, can I use

  Windows disk management to increase the size of my partition of the

  side OS to use all the 100GB he sees now?  Or will

  corrupt my data or cause a problem as I really need to

  use a third party tool like EAUSUS inside Windows to extend Windows

  on the size of the virtual hard disk?

  In fact the way you describe, resize the virtual disk and then developing the partition are the way to go. But there are some things that you should be

  aware of.

  -If the VHD is on an IDE controller, you may not be able to resize the virtual disk. In this case use the converter. With the converter, you can resize the disk including the partition and - if desired - replace the IDE controller by a SCSI controller.

  -If you have only one partition under XP (that is, drive c :)) you cannot extend the partition with the diskmanager/diskpart. In this case, start your virtual machine from a CD/DVD Vista/Windows 7 in Repair Mode, open a command line and use "diskpart" from there to "extend" your partition.

  André

• Consolidation of many to one of the virtual disks?

  Hello world

  I use a XP client inside a Windows 7 host (using 8 workstations).

  In the configuration of my XP virtual machine I previously assigned (of 50 gigabytes) of disk space into separate virtual folders, about 2 GB each, as shown below.

  

  I now want to have a single vmdk file, with the pre-allocated 50 GB of capacity.

  Is it possible that I can achieve this goal, while keeping my VM in tact? For example can I create a second virtual disk, and then use a cloning tool (from the client) BONE to make a copy to the new virtual drive?

  Here, any help will be greatly appreciated.

  Kind regards

  DAVO

  Hello world

  This can indeed be done! Because I started with a scalable, split, virtual disk, there were several steps; Here's the gist of these measures-

  (1) using the vmware-vdiskmanager merge files into a single.

  http://hostilecoding.blogspot.com.au/2013/06/VMware-merge-multiple-VMDKs-into-single.html

  Note: when running this utility do not forget to include the '2' parameter, which refers to the creation of a virtual disk prealloue, otherwise the following steps (use the shrinkvd program will NOT work!).

  Here is a screenshot of the order that worked for me-

  

  (2) add the newly created virtual disk, 'merged.vmdk' to the existing virtual machine, using these installation instructions.

  https://www.VMware.com/support/WS5/doc/ws_disk_add_virtual.html

  (3) remove the existing virtual machine virtual drive

  (4) to start the Virtual Machine (you will probably be asked if you have moved or copied the VM, I responded with "Proposed").

  (Optionally)-rename the virtual disk of "merged" into something else by renaming the files in the ".vmx" and "hard" files.

  (5) using the shrinkvd resize the virtual disk

  http://www.Softpedia.com/get/system/system-miscellaneous/shrinkvd.shtml

  

  Above, note that the first time, I ran the command it failed with the message "ddb.deletable" is the crux of the problem. I just deleted this line in the relevant file "hard" and the command is represented.

  Now, when I boot on my virtual XP I use only 24 GB of space, and I am able to transfer the Virtual Machine to a smaller drive. in this case a 30 Gig old SSD.

  I hope this helps others.

  Kind regards

  DAVO

• 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é

• VMDKMounter gets error "could not open the virtual disk.

  I have two Win7 x 64 virtual machines running fine with VMware Fusion 4.1.2.  I installed VMDKMounter from VMware 3.1.3 and OSXFuse 2.3.9.  I can ride one of the files hard with VMDKMounter very well, but others told "Cannot open the virtual disk" when I try to mount it.

  8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: could not parse the instant string ' / Users/finchr/Documents/VirtualMachines.localized/hoth.univ.dir.wwu.edu.vmwarevm/hoth.univ.dir.wwu.edu.vmx '. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: will not be able to take an informed decision, based on partial information. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: mount the drive read-only instead. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: failed to open the disc: disc encoding error (261993021117)

  The virtual machine that VMDKMounter fails to mount was created by VMware vCenter Converter 5.0 of a physical machine.  The virtual machine that works was created in VMware Fusion 4.

  Of course, the hard I really want to ride with VMDKMounter is he who fails.  No idea how to make so that he can get?

  Well, I see nothing in the disc DescriptorFile which prevents the hard mounted.

  So right now, you can mount other hard files, but not this one, then I have two suggestions...

  It would be to use vmware-vdiskmanager to create a new hard that will not go up and the other would create a new empty hard, then add it to a virtual machine, as well as one that will not go up and then start with appropriate optical disk or an ISO Image containing the appropriate tools/utilities in order to image the drive to the new empty.  I usually use Symantec Norton Ghost for operations like this.  Then maybe a new mounts with VMDKMounter.

• Cannot change the size of the virtual disk in a converted VM

  Hi, I have converted many physical machines into virtual machines using the VM converter. All off them were converted using the minimum for their HDs size so that the conversion process minutes last as little as possible. Because now there are in all readers of 'C' for all virtual machines only 1 GB of free space I want to resize their virtual disks. The problem is that I can resize them to a larger size, but Windows does not allow me to expand the volume inside Windows. When I want to expand the size of the Windows volume shows me a message saying "the selected volume is a system disk or a boot disk, or it was created in an earlier version of Windows, a basic disk. It cannot be extended.

  I am attaching two files. The first is the configuration of the VM. The second is the error that appears inside of Windows. The message is in Spanish cause that Windows is in that languaje, but I have translated from English in the previous paragraph.

  Is anyone of you know why this kind of errors appear? Does perform a work around? It seems that the problem is because the converted Convert the HD as a base virtual HD. In this format (Basic) Windows does not allow to expand. You have to change its format in Dynamics to develop, but when you try this error appeard.

  The first work-around, I thought to do is to make a picture of this disc with Ghost and try to paste this image into a new hard drive for the virtual machine, but I don't know if it will work.

  Thank you.

  Warlock.

  I have had success in utility Dell ExtPart help to resize on the fly without interruption of service to initialize volumes (drives C :).  Other methods such as attaching the drive as a data volume to another server or using GParted require at least downtime of this virtual machine and often down more than one time.  With ExtPart, I was able to avoid it completely.

  Check out this blog for more information post:

  http://blogs.kraftkennedy.com/index.php/2009/06/30/expand-virtual-machine-boot-volumes-with-no-downtime/

• Cannot increase the size of the virtual disk

  I do this kind of maintenance all the time. Usually on Windows 2008 R2 servers where I can just go to the VM > settings > hard and develop it for my pleasure, and then add the space from the host 'to hot' without having to reload or use third-party tools 'boot' to develop (IE. GParted).

  We run vSphere 5.0. The virtual machine for this case is a Win2k8 R2 64 bit on a host 4.1. Our warehouses are NFS volumes on NetApp storage infrastructure. It is now the question:

  On the same data store, same OS (2 k 8 R2) I can change the settings on virtual machines to increase the disk space and the others, I can't. It is:

  • same data store (NFS - Yes, there is enough space to grow)
  • different hosts
  • same operating system
  • all of them are defined for Thin Provisioning
  • VMware tools are running and up to date

  For some reason some VMS allow me to develop their hard drive (size available xxx.xxGB) and others do not grow (available s/o): click the arrows to increase the hard drive is greyed out.

  Ideas?

  Thank you!

  Alex

  You can not. Unfortunately, it is not possible to resize a virtual disk with snapshots.

  André

• Workstation 8; cannot resize the disk on the full clone

  I have a related clone I want to create a complete clone so that I can expand the virtual hard disk.  But after I created the full clone and try to use the indicator Workstation 8 utility I have an error message: "You can't develop this virtual disk because it is a linked clone."  I tried this three times, with great attention the last two times to read all dialog boxes to make sure I'm not a mistake, but the same error comes back every time.

  Here are the steps I go through:

  (1) turn off the linked clone

  (2) delete all snapshots for the linked clone

  (3) file-> open-> choose the clone of linke

  (4) VM-> manage-> Clone - to pen the Clone Virtual Machine Wizard. in the wizard:

  (5) "The current state of the virtual machine" pick (I tried as long as and create a snapshot and try to clone from that)

  (6) select "CREATE FULL CLONE' (not ' create a linked clone)

  (7) name the new complete cloned machine, and then click on finish

  After about 10-15 minutes, I get a message indicates the complete clone is finished.  I then close VMware, open it back up, open the new full clone that I created and select chose to: edit virtual machine settings-> tab-> click on the hard drive to extend hardware-> utilities-> Expand.  The error box I mentioned above pop and 8 workstations does not indicator the hard drive.and error as described above.

  Am I missing something here?

  If you can confirm the virtual disk of the new virtual machine is not a Flash disk (i.e. with 00000x.vmdk in its name) and the vmware.log file (created after you turn on the virtual machine) shows not all other hard files, you can check if the .vmsd of the virtual machine file contains incorrect entries. Essentially - after making sure that no other hard files are used - you could just delete the .vmsd file.

  André

• How to resize the size of the virtual disk for Linux guest OS

  Hello

  I installed VMWare WS 6.5 on my host OS (Vista) and have created a guest VM with RedHat like OS.  When creating, I've specified to create a virtual disk with a size of 8 GB, but have not selected the option of immediate creation - it being understood that VM is assigned additional as needed.  But now, on the comments and space use is 100%.  How can I allocate extra space for the virtual machine?  Also, is it possible to go beyond 8 GB, if so how.

  Enjoy your time, help.

  Concerning

  VMware-vdiskmanager allows to extend the virtual disk and use a third-party utility to extend the partition of guest operating system after having developed the virtual disk.

  Make a backup of your virtual machine before you do anything and you ensure that you don't have any snapshots

• 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é