resize the disk space on the virtual machine

Hello!

I have a small problem, when I converted a virtual machine on my esx server so I chose 14FR for the virtual machine.

But I now realize that I need more space on the virtual machine. but the problem is that I stop the virtual machine and

give more space but the does not get more space than any alcolated in diskmgmt. and there I have to

make a new partition.

Can I add a disc more on C: by do not format the drive? or can I add more disk space to a new partition

(if I add 20 GB now and want to add 20 extra GB to the same partition in 2 months or something like that?) ??

Thank you

/ R

http://malaysiavm.com/blog/how-to-resize-Windows-2003-Server-virtual-disk-on-VMware-ESX/

Here is the guide. Hope is useful.

Craig

vExpert 2009

Malaysia, VMware communities - http://www.malaysiavm.com

Tags: VMware

Similar Questions

  • Need more disk space to run virtual machines on R710 server with no available drive slots

    Hello

    We have a server R710 with five $2.5 146 each and three 600 GB SCSI disks SCSI.  We have no more slots.

    We want another 2-4 TB of space.   This server is used to run virtual machines to test software applications.  We have need for decent speed, but more important still need a cost-effective solution for running virtual machines.

    The budget would be in the $1000 range give or take.  I might be able to get $3000, but a $10,000 would be too.  We could consider removing disks from 146 GB 5 and replacing them with those larger, but that might not be the first choice.

    Any ideas?

    Thank you!

    What you ask for is really difficult to do within the budget without sacrificing important performance (from what you have right now in performance).

    Any external storage solution (Dell) is out of the question for $3 k (think MD1200/1220).

    The market, 2.5 "drives max out at 1 TB at 7200 RPM, 900 tr/10 k or 300 GB @ 15 k RPM.

    Dell has disks 1 to 7200 RPM 2.5 "company (for PowerEdges) for ~ $440 (see here). These are not the best choice if you want any kind of good performance.

    You might look into upgrading to 900GB 10 k rpm drives. These run $799 each today on the Dell website (see here).

    If you replace one of the 146 both each and let rebuild you could then use the extra space to another virtual disk. This would give about 2800GB.

    If you can't budget 5 of them, according to the current setup of raid, you can watch a backup and restore of the virtual disk of some 146.

    You could:

    -use 2 of the existing 146 in raid 1 for operating system and the extra space

    -use 3 x 900 in raid 5 (which would give a crude 1800 (Go so ~ 1674 usable))

    -Use the 3 600 existing RAID 5 (which would give ~ 1116 GB usable)

  • Size of the virtual machines on the local data store

    What is the best way to determne the (total) disk space using a virtual machine? We have several virtual machines on local data warehouses and would like to estimate roughly how much disk space to the total number of virtual machines use to caculate how much storage SAN, they will consume. Is there an 'easy' way to socket this information?

    The most accurate way would be to calculate the total space used by the virtual machine files in the data store.

    Connect to the service console

    Navigate to the vmfs volume

    Navigate to the vm folder

    -h.

    This will give you files for this particular virtual machine related to the amount of disk space used by all the vm

    Méhul

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

    settings.jpg

    Error:

    Error.jpg

    Files:

    Files.jpg

    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.

  • Disk space used by the Virtual Machine

    I'm under VMWare Fusion worm / 3.1.4 on a MacBookPro 2010 with Windows XP Pro installed.  In My Documents, there is a folder called "Virtual Machines".  It has a file in it, "Windows XP Pro 2.vmwarevm".

    The problem is that this file is 121,95 gigabytes!  Nearly half of the size of my hard drive.


    Question 1.  Does this make any sense?

    Question 2.  This file size can be reduced to something reasonable?


    Thank you!


    IdahoBob

    According to the information of the beam support Virtual Machine has 8, not 7, Snapshots.

    Without a support package for now present the only other suggestion is to delete all the snapshots, and then reduce the virtual hard disk of the applet of control panel of VMware Tools in Windows, and then Clean Up drive from the drives Panel in the settings of the Virtual Machine.

  • When you access the virtual machine, getting the error "encountered an error when you try to use one of its virtual hard disks". Help?

    I received the "low disk space error" on a hard drive of the virtual machine dynamic expanding. I have increased my space of virtual hard disk using "My Computer" > manage > storage > "Disk management" and choose "Attach VHD" then resizing to max available (64 GB), and now I can not start the virtual machine. It gives the error: encountered an error when you try to use one of its virtual hard disks. Help?

    Hi NatalieFoster,

    The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the TechNet Forums to get help:

    Windows 7 Virtual PC and XP Mode TechNet Forums

  • 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

  • VMWare Fusion makes a break from the virtual machine because the disk is almost full.

    Is I myself am sitting at my computer this morning, I saw a message that says the guest system Windows XP Pro on my Mac Mini has been suspended.  Here is the message:

    "VMware Fusion has suspended this virtual machine because the disk on which the virtual machine is stored is almost full."

    I can't find a way to shut down Windows to resize hard disk space allocation.  I tried the Virtual Machine menu, but all the shut down/put off the power points are grayed out.

    Any ideas out there?

    You must read the message!

    BTW if force you the VM to the bottom you may corrupt the virtual system hard disk and or the VHD file and you need to just do as the message says and free up space on the OS X hard disk even if you temporarily move a few things on an external hard drive so that you can then reactivate the Virtual Machine and continue on the it.

  • Error: "VMware Workstation has suspended this virtual machine because the disk on which the virtual machine is stored is almost full."

    I get this error message:

    VMware Workstation has suspended this virtual machine because the disk on which the virtual machine is stored is almost full. To continue, free 1.3 GB of additional disk space.

    I read up on the subject and found that I have to re size a partition. Anyone know what it could be? I can't find anything that looks like it has something to do with VMware. Does anyone know what size and what file system is it?

    My OS:
    Tumbleweed OpenSUSE x 64

    Thanks in advance

    On more creative, my home and root file systems were not extended to my full disk space :^)

  • Disks of the virtual machine consolidation is necessary - vCenter 5.1 U1 + ESXi 5.1 + VDP 5.8.0

    Hello

    I am facing problem as many other people do, when snapshot is deleted, the delta files are still there and warning message "consolidation of disks of virtual machines is necessary" is shown on the virtual machine.

    It happened only few but try to find the root cause. He arrived only on virtual machine located on ESXi 5.1 build 799733 which is located in the task of the WTP 5.8.0 backup.

    Is this snapshot problem, a bug in the version of ESXi?

    Unable to find the release notes, where this is documented as bug.

    Thank you

    Finally, I found a reason, therefore, for other users... ESXi 5.1 build 799733 has a bug that is resolved in the update 1 and higher and is connected to the suspended snapshots created by POS, that is why are there so many discs of delta.

    ESXi 5.1 Update 1 Release Notes

    • When the slowdown of snapshot fails the redo logs are not consolidated

      • When you try to take a snapshot of the suspension of a virtual machine, if the snapshot operation fails near the end of its realization, recovery logs created as part of the snapshot are not consolidated. Recovery logs can consume a lot of space to store data.
      • This issue is fixed in this version. If the snapshot suspended operation fails, the redo log files are consolidated.
  • Deployment of a virtual machine from a store of data with less space, but enough for the virtual machine

    I received this delicate task, and I can understand not just how to replace all parts.

    I need to create a script that will be smartly decided what data store to deploy a virtual computer.  We do not want to deploy in a data store that has the most space, we want to deploy to the data store that has the least space but can still account for the space for the (vm + 5%) and still leave 50 GB free on the lun after the move.

    Thus, for example, if the virtual machine is 40 GB, we want the script to select the data store that has a close to 90 GB available without being under.

    So my thought for this approach is:

    • Create the query to get all the relevant LUNS.  This excludes all the LUNS with the 'local' name in it and excludes all LUN owners (who have a slightly different naming convention then our general shared storage LUNS)
      • This piece, which I partially understood
        • Get-datastore. WHERE-object {($_.)} Name: corresponds to "PAR0 [1-4] _ [edp] * disk *")- and ($_.) "." Name - notmatch 'local')}
      • Now, I need to get all of their total size and free space.  Perhaps export this list to a CSV, however if I have to.
      • Create a variable that contains: the size of the total virtual machine to the virtual machine that is deployed before its deployment.
      • Deduct vm size against each data store size and pull in some way that that also close to 50 GB free on the data store and still facilitates the deployment of the vm.

    I have a few other scripts, I scrounged on the internet that I tried to restore... but I just don't calm not having all the pieces...

    • Get-Datastore. Where-Object {$_.} ParentFolder-match 'Internal'} ' | Select-Object - property data center, FreeSpaceMB, CapacityMB name, ' | Tri-objet-property FreeSpaceMB
    • Select-Object Name,@{n="CapacityGB";e={[math]::round (($_.)) {{(CapacityMB/1024))}}, @{n = "FreeSpaceGB"; e = {[math]: round (($_.))}} {{(FreeSpaceMB/1024))}}, @{n = "FreeSpacePercent"; e = {[math]: round (($_.))}} FreeSpaceMB / $_. {{(CapacityMB*100))}} | Sort-Object FreeSpaceGB

    Any help would be greatly appreciated!

    -Knotz

    Try something like this

    # Get all data warehouses

    $ds = get-Datastore. Where-Object {($_.)} Name: corresponds to "PAR0 [1-4] _ [edp] * disk *")- and ($_.) "." Name - notmatch 'local')} |

    Select-Object Name,

    @{n = "CapacityGB"; e = {[math]: round (($_.))}} {{(CapacityMB/1024))}}.

    @{n = "FreeSpaceGB"; e = {[math]: round (($_.))}} {{(FreeSpaceMB/1024))}}.

    @{n = "FreeSpacePercent"; e = {[math]: round (($_.))}} FreeSpaceMB / $_. {{(CapacityMB*100))}}

    {foreach ($vm in Get - VM)

    # Find possible candidates

    $candidates = $ds | where {($_.)} FreeSpaceGB - $vm. (UsedSpaceGB-50) - gt 0}

    # Find the best candidate

    $target = $candidates | Tri-objet-property FreeSpaceGB-descending | Select - 1 first

    Write-Output "VM $($vm.). Name) can go to $($target.) (Name) ".

    }

  • Could not start the virtual machine after you use vmkfstools to resize - HELP!

    I thought I knew what I was doing, but apparently not...

    I tried to increase the size of a VM over 36 GB drive and now I can not start the server. Here's the change front of directory list:

    -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

    -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

    -rw - 1 root root 4096 9 February 14:55 PJAEast-DL01-000002 - delta.vmdk

    -rw - 1 root root 277 9 February 14:55 PJAEast-DL01 - 000002.vmdk

    -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

    -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

    -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

    -rw - 1 root root 8684 25 August at 21:03 PJAEast - DL01.nvram

    -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

    -rw - r - r - 1 root root 1042 28 August to 01:52 PJAEast - DL01.vmsd

    -rwxr-xr-x 1 root root 2779 Feb 9 15:10 PJAEast - DL01.vmx

    -rw - r - r - 1 root root 267 Feb 9 15:10 PJAEast - DL01.vmxf

    -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

    -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

    -rw - 1 root root 73728 9 February 14:55 PJAEast-DL01_1-000002 - delta.vmdk

    -rw - 1 root root 283 9 February 14:55 PJAEast-DL01_1 - 000002.vmdk

    -rw - 1 root root 36322836480 28 August at 01:41 PJAEast-DL01_1 - flat hard

    -rw - 1 root root 597 25 August at 15:18 PJAEast - DL01_1.vmdk

    -rw - r - r - 1 root root 78710 25 August at 16:06 vmware - 1.log

    -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

    -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

    -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

    -rw - r - r - 1 root root 69453 9 February 14:54 vmware.log

    Then, I run the command:

    vmkfstools x 256g PJAEast - DL01_1.vmdk

    And now the virtual machine does not start, return an error: "the virtual disk parent has been changed since the child was created."

    The directory listing is now ("BOLD" indicates the change of information post-vmkfstools):

    -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

    -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

    -rw - 1 root root 4096 Feb 9 16:12 PJAEast-DL01-000003 - delta.vmdk

    -rw - 1 root root 277 Feb 9 16:12 PJAEast-DL01 - 000003.vmdk

    -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

    -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

    -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

    -rw - 1 root root 8684 Feb 9 16:12 PJAEast - DL01.nvram

    -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

    -rw - r - r - 1 root root 1015 28 August 01:52 PJAEast - DL01.vmsd

    -rwx - 1 root root 2779 Feb 9 16:12 PJAEast - DL01.vmx

    -rw - 1 root root 267 Feb 9 16:12 PJAEast - DL01.vmxf

    -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

    -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

    -rw - 1 root root 73728 Feb 9 16:12 PJAEast-DL01_1-000003 - delta.vmdk

    -rw - 1 root root 283 Feb 9 16:12 PJAEast-DL01_1 - 000003.vmdk

    -rw - 1 root root 274877906944 28 August 01:41 PJAEast-DL01_1 - flat hard

    -rw - 1 root root 599 9 Feb 16:11 PJAEast - DL01_1.vmdk

    -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

    -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

    -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

    -rw - r - r - 1 root root 69453 9 February 14:54 5.log - vmware

    -rw - r - r - 1 root root 39510 Feb 9 16:12 6.log - vmware

    -rw - r - r - 1 root root 39411 Feb 9 16:12 vmware - 7.log

    -rw - r - r - 1 root root 39410 Feb 9 16:14 vmware.log

    I can't do anything else until I get comments. Can anyone recommend a way to solve this problem?

    I thought I knew what I was doing, but apparently not...

    I agree

    Two a problem with the new drive.

    1. You get the error message comes from the basic disk with a different size than the disks of the snapshot.
    2. With a size of 256 GB, you will not be able to create snapshots of the disk (on ESXi prior to 5.0 with a block size of 1 MB)

    What you can try to do is to edit the file PJAEast - DL01_1.vmdk :

    • 536870912 VMFS 'PJAEast-DL01_1 - flat hard' RW--> RW 70943040 VMFS 'PJAEast-DL01_1 - flat hard. "
    • DDB. Geometry.Cylinders = "33418'-> ddb.geometry.cylinders = '4416.

    After that, I would recommend to clone the virtual disk to a new one, replace the virtual disk in the virtual machine settings and resize it to a maximum of 254GB (see "calculates the time system required by the snapshot files" at http://kb.vmware.com/kb/1012384)

    • vmkfstools-i PJAEast-DL01_1 - 000003.vmdk PJAEast - DL01_1a.vmdk

    André

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

  • 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

  • I get an error "the disk hard virtual parent is in a saved state. Discard the saved state or stop the virtual machine and try again. "during the installation of XP mode.

    I have Win7 Pro SP1 x 64.  I downloaded WindowsXPMode_en - us.exe (from Microsoft downloads) and run it.  The installation seems to work OK (I've specified a different location for the parent virtual hard disk file).  Then, installation happening and I provide the information requested (name of user and password for the XP Mode), updates Windows and OK to the issue of sharing.  The installation program then reports the following error:

    The disk hard virtual parent is in a saved state.  Discard the saved state or stop the virtual machine and try again.

    I get the error even if I try manually configure XP Mode (use the Setup Wizard).  I downloaded the installer XPMode (3 times) and reinstalled several times, always with the same result.  If it helps, I can't locate anywhere .vsv file.

    Any idea what's going on?

    Original title: XP Mode Setup error

    Hi smithnr10,

     

     

    You must post your question in the TechNet forums because it caters to an audience of it professionals.

    To do this, you must consult the link-

    http://social.technet.Microsoft.com/forums/en-us/w7itprovirt/threads

     

    Hope this helps!

Maybe you are looking for