Cannot extend a virtual disk in vSphere

Similar Questions

• How to extend a virtual disk on WS7?

  I use a virtual machine of WS7 running Win7x64 as my software development system.

  He has a 100 GB virtual disk and now I try to install Embarcadero RAD Studio XE7 on that, but is greeted by a message saying that the 33.6 GB of free space is not enough...

  He needs 37 a few GB.

  So now that I look at my options and the first, we must somehow extend the virtual disk (vmdk file) to a larger size.

  Is it possible at all the tool magic VMware or what I need to create a new record and the use of some software cloning inside the VM for Win7 to transfer the content courses like the one made when moving to a bigger real physical drive?

  Looks like it should be possible so to increase the size of the car without touching the data such that the partition holding the 100 GB drive is not now the disk is full.

  In this case, I use Win7 tools to extend the partition to use the full disk.

  Any advice/suggestions?

  Expand a virtual disk is a fairly straightforward task. Make sure that the virtual machine have Active snapshots and then increase the size of the virtual disk by typing in its new size in settings of the virtual machine HARD drive. After increasing the virtual disk, you must increase the partition within the guest OS. For Windows 7, this can be done in the disk management interface.

  Remember that when you set up a monolithic virtual disk for the virtual machine (i.e. a single hard large file), a new virtual disk will be created and all content will be copied on to this new hard file, which will have some time at the end, but it will also take the additional temporary disk space.

  André

• Cannot create a virtual disk existing; problem with files hard?

  Yes... This is a recurring problem since mid-December, and we finally decided to rebuild our vCenter on another host server.  I went and did the things of the new Virtual Machine and has "custom", so that I can browse and recover files hard and * _1.vmdk of our SAN for discs.

  Now, this large all worked Friday.  I just today... and it doesn't work.  D: drive (* _1.vmdk) disappeared, and I can't either remote on the server.  I can't vSphere, nothing!

  Then... we rebuild, changing the name of the server that we just built _old after stopping.

  When I go to recover files hard again, they are changed...?  I can't explain it!  I've attached a screenshot of what I take everything.

  Now... there at - it a way to solve this problem?  And if not, is it possible to find the information that was in these folders to manage our environment?
  
  Help?

  What you're saying gives me a really bad feeling.

  Sorry about that, I really want to tell you something more encouraging, but...

  Assuming that the snapshot you posted shows the old vCenter server folder, you can see that there are no configuration (.vmx) file more. I can tell you with certainty if the virtual machine has been removed (you can check the tasks and events) or if for example a backup application attempted to do his work but because of the virtual disks had reused problem!

  If you still want to use the existing virtual disks, you must move them to the folder of the new virtual machine in order to avoid any confusion.

  André

• 7 virtual disk added vSphere data protection

  Hi, we are deploying vSphere Protection of data in the model of the FVO, after completion, we found 7 virtual disk listed in the properties of the vm disk of 1x100GB and 6x256GB of the disc, we could just understand why the model gave us 7 disc, a google search didn't really give us any idea either.

  Few can have space constraints. This is for flexibility.

  Other than 1, the disks are disks of data and you have the possibility to migrate to different data warehouses after deployment.

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

• How to extend a virtual disk in a workflow

  Hello together,

  I have a problem in the creation of a Workflow.

  I want to deploy a virtual with a CustSpec computer (works fine). After the deploymente, I want to thank the disc - it's my problem.

  Did anyone of you knows how to expand a virtual disk to a virtual machine?

  Thank you very much

  Marc

  I have not tried this at my end, but you can try something like this:

  You need create a scriptable task and the research of the class script VirtualLsiLogicController from the API Explorer. The properties that need are required to set as seen in the reference of vSphere are:

  -busnumber (can be set to 0)

  -button (can be set to 0)

  -sharedBus (set VirtualSCSISharing.physicalSharing) / / VirtualSCSISharing is an enum type, consult the API Explorer

  After you set the object above (VirtualLsiLogicController), it defined in the the virtualdeviceconfigspec object and the value of this deviceconfigspec to the devicechange of the virtualmachine context property (as previously done for adding a virtual disk).

  I hope that helps!

  -Angela-

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

• 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

• Cannot resize the virtual disk

  My vm upgraded allows no expansion vdisk in the pane settings; said must delete all snapshots, yet no old clichés exist. Version 2.0.2 (147997) to run on a MBP 17 "intel 2.16 g.

  Based on list stamps and the date/time of file on the files, you have a snapshot in place and you can try to remove it by trying the following with the not suspended, and Virtual Machine within Windows to stop.

  Take a snapshot, and then immediately delete the snapshot.

  Note: I personally don't do without first making sure that I have all the user data saved from within the Virtual Machine from a store outside of the Virtual Machine and or a manual full copy of all of the Virtual Machine.  Just in case!

• Cannot delete a virtual hard disk

  Hello!

  I use Fusion - 5.0.2 and you cannot delete a virtual disk. As you can see from the screenshots, the VM (called backup) IS off and there is NO snapshots...

  

  ... and the virtual machine has no "restrictions".

  

  The button "Remove Hard Drive" is still just gray.

  Anyone know why I can't remove VHDs from Fusion?

  Best regards

  -Green Morten Hermansen

  Hello!

  The problem is that in order to remove a vDisk, encryption must be removed first.

  Best regards

  -Morten Hermansen, Fanitas Green

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

• Permissions to expand virtual disks?

  I tried to create a role that gives permissions to manage virtual machines and the possibility of extending a virtual disk. I don't seem to be able to do. I gave the following permission:

  data store: Browse, allocate space, operations of low level file, delete the file

  Host: System Management, reconfigures the virtual machine

  VM: all rights

  I got these file, cluster level and level of datastore folder-level rights.

  What Miss me?

  Thank you!

  Tom

  Hi Thomas,

  If the VM object and the object data store (located vmdk) have the permission your grant, who has the word. The following steps are how to optimize permission to expand virtual disks, please check to see what stage you missed.

  Environment:

  ' 1) ' clusters ' with 'vm1', the vmdk vm1 locates at "datastore1".

  ' (2) ' datastore1 ' is under folder data store "ds_folder1".

  1 change the role of 'virtual machine user (sample)' with the right permission

  Change the default role "user (sample) virtual machine", adds the "VM-> Configuration"(vous pouvez voir"Extend disque virtuel"est inclus et puis ajoutez le"Datastore-> Allocate espace".) ". These permissions and the default permission of the role of 'virtual machine user (sample)' can be the role with permission to drive virtual extend.

  2. choose the right object to add the authorization

  You should the 'cluster' and the datastore "ds_folder1" folder to add authorization: Add a user, and then choose her user (sample) 'virtual machine' in the role

  And then the VM1 to the title 'group' and the datastore1 under "ds_folder1" must have the permission. (You can check the label of Permissions)

• 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

• Cannot extend the disk in virtual machines on ESXi4.1

  Hi people,

  Sorry if its posted in the wrong forum. I am unable to extend the VM disk but its having enough space I added it drive. The problem here is one of the disks are having 2 C and D partition on the same drive / same vmdk. Therefore, it is possible to expand the D drive shows unallocated after adding the space. I know through Standalone VMware converter 5.0 we can resize. If any other option other than that. Any help on this will be appreciated. Please see the screenshot.

  Thank you

  vmguy

  Hello.

  I have met many of them, and Converter is the best way to address them. When c is first, you can copy other data readers to new VMDK, but Converter is often easier and faster than that.

  Good luck!