ESX3.5U4/VC2.5 - move vmdk to adequate data store and extend the drive on the virtual machine

Similar Questions

• Pass a VMDK to a data store to another is not free up space as expected

  Hi, I'm ability on my local data store.  To remedy this, I created an iSCSI data store and used the vSphere client to move unused VMDK to it.  Unfortunately, the free space of the local data store won't upward.  I checked the guest VM that I removed the VMDK from and it shows the use of the appropriate space.  In addition, it has none of the snapshots for her.  Any help would be appreciated.

  you right-click on the DS in question and choose "Refresh".

• Move the virtual machine from one host to another with shared storage

  Hello

  I have a question on how to move a virtual machine from one ESX 4 host to a host ESXi 5.  These hosts have access to the same shared storage but the ESX 4 host is outside the network and host ESXi 5 is inside the network so vMotion is not an option.  They are in different groups.  I know that there must be an easy way to move this virtual machine, but for the life of me, I can't find it.  I guess I have remove the virtual machine from the external cluster but how to make the virtual machine in the internal cluster?

  Thanks in advance...

  If both host access to the data store even where VM's store, just stop the virtual machine, remove inventory on ESXi 4, go to ESXi 5 vSphere vSphere, browse the data store where the VM is stored, do a right-click on the .vmx file and add to the inventory.

• Storage vMotion - impossible to move the virtual machine

  All,

  I have recently upgraded to version 4.1 ESXi 4.1 U3 of VC2.5 ESX 3 vCenter Essentials - I decided to make my new vCenter server a VM - everything went well on the upgrade so I am now looking to do work on my storage system (EMC Celerra). I have virtually no space on my LUN and my CIFS shares are increasingly full also... However I have a file inside the EMC system which is 6 to size which houses a 200 GB LUN - it's the logic unit number that contains my VM vCenter. What I want to do is... move this vCenter VM off this LUN to local storage, reassign 6 TB to the pool file system and extend the 3 TB CIFS file system and then present the rest of the space as LUNS for VMware. My problem is that I'm not licensed for storage vMotion and they only way I can storage vMotion, VM off the coast of this LUN is to stop it and move it but because it's my vCenter Server I can perform this action by the customer.

  I guess I might need to drill holes in the host using putty to move the vmdk file, but I'm looking for any useful measure to enable me to move this virtual machine.

  Thank you

  If you are not allowed to Storage vMotion, then you can watch using VMware Converter and do a V2V.  Once the VM vCenter has been "copied" in the new destination LUN, it works, make sure that everything is right, then delete the 'old' vCenter VM disk.

• Expand or move the virtual machine to another partition / hard disk

  I tried to expand my 90 GB disk but nothing changes, i.e. the virtual machine is still to 60 GB. I have VMware Fusion 6 (Mac/Windows 10) and my VM is monolithic mode. In this true HD, I even 50 GB free and I can't increase the amount again in an attempt to rectify this problem and I can not to decrease either. I thought to change the location of the virtual machine to another partition/hd with more space, but I don't know how. So I need little help to choose and implements one of the solutions below:

  - or regularise space for the new amount

  - or move the virtual machine (vmdk) to an another partition/HD

  - or to convert monolithic mode to 2 GB split

  What is the best solution?

  Thanks in advance

  It's help me;

  Resize a Windows Partition with disk management tool

  When you maximize your virtual hard disk, you must also expand partition of your guest operating system to take advantage of the extra space.

  Fusion resizes the partition of the guest operating system when you resize the virtual hard disk. If you hold the Option key when you click apply to resize the drive, you can manually resize the Windows partition. For Windows 8, Windows 7 and Windows Vista you can use the operating system's disk management tool to resize a partition.

  Prerequisites

  Check that your virtual hard disk is large enough to accept the increase in the size of the partition. See resize a hard disk.

  Procedure

  1 right click on computer and select Manage.

  2. double-click on storage.

  3 double-click disk management.

  4 in the list, right click on the partition to expand and select Extend the Volume.

  5 follow the prompts to resize the partition and click complete and the question of the partition in the disk management pane displays its new size.

  6. close the computer management window

• Impossible to turn on the virtual machine with the following error: could not open the disk ' / path/to/vmdk-0001.vmdk ' or one of the Flash disk it depends on. Reason: Broken pipe.

  After the movement of virtual machines in VmWare Server 2 for ESX 4i, I get this error when you try to start the virtual machine:

  Impossible to turn on the virtual machine with the following error: could not open the disc

  "/ path/to/vmdk-0001.vmdk" or one of the Flash disk it depends on.

  Reason: Broken pipe.

  Anyone's idea what is the problem here?

  How did you move virtual machines?

  Did you use the converter (https://www.vmware.com/tryvmware/?p=converter)

  Otherwise try converter

• How can I move the "Virtual Machines" folder to the My Documents folder?

  VMwareFusion is to put the "Virtual Machines" folder in the Documents folder in the home folder (/users/ [username] / Documents), how can I move elsewhere (as/Library/Application Support)? The user Documents folder is not the right place for automated it system files, it is intended for personal documents.

  
  

  I am running VMware Fusion on OS X Yosemite (and the virtual machine is Windows 7).

  You can keep your virtual machines anywhere you want. Here are the steps to move:

  1 exit VMware Fusion. You can stop first of all of your running virtual machines.

  2. drag your virtual computers folder or the individual VM "files" where you / them. Filenames usually end in ".vmwarevm". There is no need to call the new folder "Virtual Machines" - you can call it anything you like.

  3. Launch VMware Fusion. If the library of the Virtual Machine window is not open, open it (Windows menu-> Virtual Machine library).

  4. ensure that all of your icons for the virtual machine are light gray and say "file not found".

  5. right click on each virtual machine in turn, and select Remove. When you are done, leave the window of Machine virtual library empty open.

  6. in the Finder, drag the icons of file virtual machine in their new location and drop them in library of virtual machines VMware Fusion window. Drop them one by one in the original order, you got, or rearrange icons later.

  7. run your virtual machines as before.

  When you create new virtual computers, navigate to the desired file before the Save.

  IMPORTANT NOTE: If you your folder of Machines ~/Documents/Virtual excluded from backups Time Machine, don't forget to change the exclusion to the new folder.

  Time Machine backups are not reliable for virtual machines. You must have another strategy. (I shut the virtual machine down, compress the 'file', and then move the compressed file to a folder that is included in the Time Machine backups. This isn't the only strategy, but it works for me.)

• How to move the Virtual Machine VMWare Workstation 10 to a completely different computer

  I have a laptop that is going to become my 'old' laptop, I bought and am always set up a new computer.

  I have a VM THAT evolution created on the 'old' portable using VMWare Workstation 10.  I installed the software VMWare Workstation 10 on the new laptop computer and am ready to move to the existing VM development since the old laptop again to continue the development of software on the virtual machine to the new machine.

  I never moved a computer virtual from one computer to another, and I guess that all I have to do is to copy and move the folder and all its content from the old laptop to the new, and then I'll be back in business?

  Just make sure it is this simple before doing so.

  Thanks for any input.

  It's as simple as that. When you start in the new machine, it should ask if you copied or moved. Answer that you moved it will keep the same MAC address and you will not be able to connect the two copies at the same time. You copied it saying assigns a new MAC and they both can connect, but a Windows machine can ask to reactivate. Seems to me he asked also to reactivate when I copied it for an Intel system AMD system, but it was a long time ago

  Lou

• How to move the virtual machine from one cluster to another cluster

  How to move the virtual machine from one cluster to another cluster

  If two Clusters are in the same data center, you could do a 'live' migration or vMotion, if that's the case.   If the virtual machine is turned off, it may be migrated regardless of the data center.

• You press on delete all selected items by browsing the data store and accidentally deleted a vmdk file which has the OS on it

  I accidentally deleted the vmdk file that has my OS on it by pressing the "Delete selected items" button in the window of browser data store. Is there anyway to recover? I have a snapshot that doesn't seem to work. There is still the VMDK file in there, but it has now 'delta' be added at the end. Now I get an error message when I try to turn on my VM saying that he doesn't get the vmdk file, of course.

  

  

  From the screen shots looks you have deleted only the descriptor hard files that can be recreated. To ensure this is the case, please provide a complete list of the files in the folder of the virtual machine and attach the last file.log of vmware(from the virtual work computer) to a post response to view required details.

  André

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

• . VMDK missing but they are and fix the CID

  Hello everyone,

  I'm trying to restore a virtual machine to Vmware Workstation 8.x, from a backup, I use the same version of VMware Workstation used before (8.0.5).

  These are the files that I have in the directory:

  31/08/2012 11:16 2.147.483.648 Macbeth - 8b31b655.vmem
  25/03/2012 19:12 2.147.483.648 Macbeth - Snapshot1.vmem
  25/03/2012 19:12 40.171.327 Macbeth - Snapshot1.vmsn
  19/05/2012 23:21 37.313.493 Macbeth - Snapshot2.vmsn
  20/05/2012 18:53 2.147.483.648 Macbeth - Snapshot3.vmem
  20/05/2012 18:53 37.385.117 Macbeth - Snapshot3.vmsn
  10/02/2012 00:10 Macbeth.nvram 74.232
  25/03/2012 17:42 Macbeth.vmdk 2.386
  10/02/2012 00:10 Macbeth.vmsd 1,363
  10/02/2012 00:10 2,748 Macbeth.vmx
  23/12/2012 19:43 < DIR > Macbeth.vmx.lck
  31/08/2012 11:16 365 Macbeth.vmxf
  26/03/2012 09:18 1,213 MacbethOs
  19/05/2012 23:20 502.267.904 MacbethOs-000001 - s001.vmdk
  19/05/2012 23:20 327.680 MacbethOs-000001 - s002.vmdk
  19/05/2012 23:20 12.779.520 MacbethOs-000001 - s003.vmdk
  19/05/2012 23:20 26.542.080 MacbethOs-000001 - s004.vmdk
  19/05/2012 23:20 410.255.360 MacbethOs-000001 - s005.vmdk
  19/05/2012 23:20 1.933.443.072 MacbethOs-000001 - s006.vmdk
  19/05/2012 23:20 2.146.762.752 MacbethOs-000001 - s007.vmdk
  19/05/2012 23:20 2.133.852.160 MacbethOs-000001 - s008.vmdk
  19/05/2012 23:20 1.157.890.048 MacbethOs-000001 - s009.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s010.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s011.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s012.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s013.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s014.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s015.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s016.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s017.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s018.vmdk
  19/05/2012 23:21 327.680 MacbethOs-000001 - s019.vmdk
  19/05/2012 23:21 1.114.112 MacbethOs-000001 - s020.vmdk
  19/05/2012 23:21 65,536 MacbethOs-000001 - s021.vmdk
  23/12/2012 19:02 MacbethOs - 000001.vmdk 1.265
  20/05/2012 18:52 89.980.928 MacbethOs-000002 - s001.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s002.vmdk
  20/05/2012 18:52 3.932.160 MacbethOs-000002 - s003.vmdk
  20/05/2012 18:52 12.189.696 MacbethOs-000002 - s004.vmdk
  20/05/2012 18:52 35.586.048 MacbethOs-000002 - s005.vmdk
  20/05/2012 18:52 50.724.864 MacbethOs-000002 - s006.vmdk
  20/05/2012 18:52 499.908.608 MacbethOs-000002 - s007.vmdk
  20/05/2012 18:52 629.211.136 MacbethOs-000002 - s008.vmdk
  20/05/2012 18:52 720.109.568 MacbethOs-000002 - s009.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s010.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s011.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s012.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s013.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s014.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s016.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s017.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s018.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s019.vmdk
  20/05/2012 18:52 327.680 MacbethOs-000002 - s020.vmdk
  20/05/2012 18:52 65,536 MacbethOs-000002 - s021.vmdk
  23/12/2012 19:02 1,277 MacbethOs - 000002.vmdk
  23/12/2012 17:01 224.133.120 MacbethOs-000003 - s001.vmdk
  23/12/2012 17:01 327.680 MacbethOs-000003 - s002.vmdk
  23/12/2012 17:01 9.830.400 MacbethOs-000003 - s003.vmdk
  23/12/2012 17:01 493.748.224 MacbethOs-000003 - s004.vmdk
  23/12/2012 17:01 694.943.744 MacbethOs-000003 - s005.vmdk
  23/12/2012 17:01 458.883.072 MacbethOs-000003 - s006.vmdk
  23/12/2012 17:01 334.168.064 MacbethOs-000003 - s007.vmdk
  23/12/2012 17:01 77.266.944 MacbethOs-000003 - s008.vmdk
  23/12/2012 17:01 1.459.814.400 MacbethOs-000003 - s009.vmdk
  23/12/2012 17:01 2.146.762.752 MacbethOs-000003 - s010.vmdk
  23/12/2012 17:01 931.069.952 MacbethOs-000003 - s011.vmdk
  23/12/2012 17:01 327.680 MacbethOs-000003 - s012.vmdk
  23/12/2012 17:01 327.680 MacbethOs-000003 - s013.vmdk
  23/12/2012 17:01 327.680 MacbethOs-000003 - s014.vmdk
  23/12/2012 17:01 327.680 MacbethOs-000003 - s015.vmdk
  23/12/2012 17:01 327.680 MacbethOs-000003 - s016.vmdk
  23/12/2012 17:01 327.680 MacbethOs-000003 - s017.vmdk
  23/12/2012 17:01 327.680 MacbethOs-000003 - s018.vmdk
  23/12/2012 17:01 327.680 MacbethOs-000003 - s019.vmdk
  23/12/2012 17:01 720.896 MacbethOs-000003 - s020.vmdk
  23/12/2012 17:01 65,536 MacbethOs-000003 - s021.vmdk
  23/12/2012 19:02 1,277 MacbethOs - 000003.vmdk
  25/03/2012 19:11 322.764.800 MacbethOs-s001
  25/03/2012 19:11 2.146.762.752 MacbethOs-s002
  25/03/2012 19:11 2.079.391.744 MacbethOs-s003
  25/03/2012 19:11 2.146.697.216 MacbethOs-s004
  25/03/2012 19:11 2.146.762.752 MacbethOs-s005
  25/03/2012 19:11 392.101.888 MacbethOs-s006
  25/03/2012 19:11 327.680 MacbethOs-s007
  25/03/2012 19:11 327.680 MacbethOs-s008
  25/03/2012 19:11 327.680 MacbethOs-s009
  25/03/2012 19:11 327.680 MacbethOs-s010
  25/03/2012 19:11 327.680 MacbethOs-s011
  25/03/2012 19:11 327.680 MacbethOs-s012
  25/03/2012 19:11 327.680 MacbethOs-p014
  25/03/2012 19:11 327.680 MacbethOs-s015
  25/03/2012 19:11 327.680 MacbethOs-s016
  25/03/2012 19:11 327.680 MacbethOs-s017
  25/03/2012 19:11 327.680 MacbethOs-s018
  25/03/2012 19:11 327.680 MacbethOs-s019
  25/03/2012 19:11 479.264.768 MacbethOs-s020
  25/03/2012 19:11 MacbethOs 131,072-s021

  Correctly, I can open the virtual machine in and find its configuration. I have a problem only with the disk receving the error message:

  The parent of this virtual disk could not be opened.

  Well, in the .vmx file I have:

  scsi0:0. Present = 'TRUE '.
  scsi0:0. FileName = "MacbethOs - 000003.vmdk".

  I have three snapshots for this virtual machine. I checked back the 3 .vdmk related descriptors and their data and CID seems appropriate. Analysis each file hard seems, I have all the files listed hard in and none of this is 0 size.

  Sorry for the post long post, I stick just to check everything to look:

  MacbethOs - 000003.vmdk:

  # Disk DescriptorFile
  version = 1
  Encoding = "windows-1252".
  CID = 74cb395a
  parentCID = e993bfa4
  isNativeSnapshot = 'no '.
  createType = "twoGbMaxExtentSparse.
  parentFileNameHint = "MacbethOs - 000002.vmdk".
  # Description of the measure
  RW SPARSE 4192256 ' MacbethOs-000003 - s001.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s002.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s003.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s004.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s005.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s006.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s007.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s008.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s009.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s010.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s011.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s012.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s013.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s014.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s015.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s016.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s017.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s018.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s019.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000003 - s020.vmdk.
  RW SPARSE 40960 ' MacbethOs-000003 - s021.vmdk.

  # The database disk
  #DDB

  ddb.longContentID = "152e926bd42e5dba4f1181f2f7ea75ee".

  MacbethOs - 000002.vmdk:

  # Disk DescriptorFile
  version = 1
  Encoding = "windows-1252".
  CID = e993bfa4
  parentCID = 70 c 20312
  isNativeSnapshot = 'no '.
  createType = "twoGbMaxExtentSparse.
  parentFileNameHint = "MacbethOs - 000001.vmdk".
  # Description of the measure
  RW SPARSE 4192256 ' MacbethOs-000002 - s001.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s002.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s003.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s004.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s005.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s006.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s007.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s008.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s009.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s010.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s011.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s012.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s013.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s014.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s015.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s016.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s017.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s018.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s019.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000002 - s020.vmdk.
  RW SPARSE 40960 ' MacbethOs-000002 - s021.vmdk.

  # The database disk
  #DDB

  ddb.longContentID = "152e926bd42e5dba4f1181f2f7ea75ee".

  MacbethOs - 000001.vmdk:

  # Disk DescriptorFile
  version = 1
  Encoding = "windows-1252".
  CID = 70 C 20312
  parentCID = f7ea75ee
  isNativeSnapshot = 'no '.
  createType = "twoGbMaxExtentSparse.
  parentFileNameHint = "MacbethOs".
  # Description of the measure
  RW SPARSE 4192256 ' MacbethOs-000001 - s001.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s002.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s003.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s004.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s005.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s006.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s007.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s008.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s009.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s010.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s011.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s012.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s013.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s014.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s015.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s016.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s017.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s018.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s019.vmdk.
  RW SPARSE 4192256 ' MacbethOs-000001 - s020.vmdk.
  RW SPARSE 40960 ' MacbethOs-000001 - s021.vmdk.

  
  

  # The database disk
  #DDB

  
  

  ddb.longContentID = "152e926bd42e5dba4f1181f2f7ea75ee".

  MacbethOs:

  # Disk DescriptorFile
  version = 1
  Encoding = "windows-1252".
  CID = f7ea75ee
  parentCID = ffffffff
  isNativeSnapshot = 'no '.
  createType = "twoGbMaxExtentSparse.

  
  

  # Description of the measure
  RW 4192256 SPARSE "MacbethOs-s001.
  RW 4192256 SPARSE "MacbethOs-s002.
  RW 4192256 SPARSE "MacbethOs-s003.
  RW 4192256 SPARSE "MacbethOs-s004.
  RW 4192256 SPARSE "MacbethOs-s005.
  RW 4192256 SPARSE "MacbethOs-s006".
  RW 4192256 SPARSE "MacbethOs-s007.
  RW 4192256 SPARSE "MacbethOs-s008.
  RW 4192256 SPARSE "MacbethOs-s009".
  RW 4192256 SPARSE "MacbethOs-s010.
  RW 4192256 SPARSE "MacbethOs-s011.
  RW 4192256 SPARSE "MacbethOs-s012.
  RW 4192256 SPARSE "MacbethOs-s013.
  RW 4192256 SPARSE "MacbethOs-p014.
  RW 4192256 SPARSE "MacbethOs-s015.
  RW 4192256 SPARSE "MacbethOs-s016.
  RW 4192256 SPARSE "MacbethOs-s017.
  RW 4192256 SPARSE "MacbethOs-s018.
  RW 4192256 SPARSE "MacbethOs-s019.
  RW 4192256 SPARSE "MacbethOs-s020.
  RW 40960 SPARSE "MacbethOs-s021.

  
  

  # The database disk
  #DDB

  
  

  ddb.virtualHWVersion = '8 '.
  ddb.longContentID = "152e926bd42e5dba4f1181f2f7ea75ee".
  DDB. UUID = "60 00 C2 98 35 e8 84 99 9 d 9 c 37 69 17 1 d f2 f8"
  DDB. Geometry.Cylinders = "5221.
  DDB. Geometry.Heads = "255".
  DDB. Geometry.sectors = "63".
  ddb.adapterType = "free".
  ddb.toolsVersion = "8449.

  I do not understand what is missing. I seem to have all the data but like I've totally lost my vm .

  Really, any help will be apreciated.

  Thank you

  Eddie

  After taking an another close look at the list of files, it looks in "MacbethOs-000002 - s015.vmdk ' is missing. The size of the other "s015" files, it seems that this file does not contain already actual data, so you could probably solve this problem by recreating the file (for example copy "MacbethOs-000002 - s014.vmdk").

  André

• Move the virtual machine to the workstation from 9 to 7 Workstation

  Hi all

  I have created a virtual machine (PBX) on VMWare Workstation 9 and I need to move it to Workstation 7.1.  I tried to create an ovf file using ovftool, but I couldn't expand the FVO on the side 7.1.  Is there anything else I can do to move the machine to the course?

  Thanks for your time.

  Martin

  "You can just copy the file to the virtual machine with all its files, this will keep even the machine virtual UUID and MAC address if you select 'I moved' we ' when you start the virtual machine after you have copied. However, before copy on the virtual machine, make sure that you go to compatibility mode (formerly hardware version) from the 9 VMware Workstation interface.

  André

• Move the virtual machine in another data store

  I don't know what's going on, I have two data warehouses and I moved my vm from one to the other, I had to create a new virtual machine to import the files migrated, when I opened the store of data for import only saw two files vmdk files, the first 00001 others a single vmdk file that contains 00 001 not opened when you import the second succeeded, but when the server starts, it goes up a very old version, as if it was newly installed windows 2003, I saw in the dishes, delta files files but don't know what to do, I tried to check the Snapshot Manager, but did not find anything there.

  Have you ever tried to fix things? The attached .vmx file points to the correct instant hard file (scsi0:0.fileName = "Cezzanne - 000001.vmdk"), but the parentCID in this hard file is not correct!

  In any case, after replacing "Cezzanne - 000001.vmdk" with that of archive attached, you should be able to restart the virtual machine. BTW. You can delete the file «.lck...» ». This is necessary on a NFS datastore.

  Next time you copy a VM, do not create a new virtual machine. Only delete the virtual machine to inventory before moving and after moving it, click right the VM .vmx file and choose "add to the inventory.

  André

• Best practices for moving to the 1 of 2 VMDK to different data store

  I have several virtual machines who commit a good amount of data on a daily basis.  These virtual machines have two VMDK; one where the operating system and that where data is committed to.  Virtual machines are currently configured to store in the same data store.  There is a growing need to increase the size of the VMDK where data are stored, and so I would like these put special in a separate data store.  What is the best practice to take an existing virtual computer and moving just a VMDK in another data store?

  If you want to split the vmdks (HDDs) on separate data warehouses, just use Storage vMotion and the "Advanced" option