Max MD3000 virtual disk size

Similar Questions

• Reference Dell MD3000 virtual disk

  I have an environment to both nodes of ESX 4.0 and a shared storage (Dell MD3000, no iSCSI).

  On storage, I have 10 at 10K SAS drives.

  Virtual disk how I need to build? A two bigger or smaller?

  Thank you

  Max

  It is not a simple answer, because it depends on:

  • Good storage practices

  • Storage type and the type of disks

  • VM number, size and type of e/s

  • Max VM and e/s per LUN

  • Size Max LUN (less than 2 to - 512 b)

  In your case, with 10 discs and two nodes and storage running in active-passive mode, you can create 2 virtual disks.

  Create 2 different groups of RAID5 (also think about using 1 disk as a global hot spare) and in each virtual disk group build 1 (or more if the size is more than 2 TB - 512b).

  If you have a few VMS with high IO think also to use use 4 disks in RAID10 instead of RAID5 configuration.

  André

• Virtual disk size problems.

  Hello

  I have a virtual SCSI disk has a size maximum of 50 GB and divided into 2 GB files.

  My problem is that the disc takes 28 GB of space on the Mac; but I have only 14 GB used in the Windows XP virtual machine and it shows 36 GB free.

  I would like to reduce the Mac files to a more reasonable size. Is this possible?

  VMware Fusion (menu bar) > help > VMware Fusion help > creating virtual machines > VMware Tools > configure VMware Tools ("Shrink virtual disk to a virtual machine, to reclaim the unused space")

  VMware Fusion (menu bar) > help > VMware Fusion help > managing Virtual Machines > virtual hard disk management > cleaning up a hard disk

  If you try to use the information mentioned in the pointers above and you cannot because of Snapshots, then take a look at the following.

  VMware Fusion (menu bar) > help > VMware Fusion help > using snapshots and AutoProtect > deletion of snapshots

  Note: Before taking any action, I highly recommend that you at least have a data backup current full user that was created from the virtual and recorded outside the Virtual Machine itself Machine otherwise have a backup of the virtual machine and not a backup Time Machine, as it is not know properly backup of VMS in current conditions likely several.

• Save the number of the Virtual Machine: expand the size of the virtual disk of Guest OS affect the physical disk on the host operating system files?

  People,

  Hello. I use 3 Player VM and Guest OS Windows Server 2003. The host OS is Windows 7. I need to increase the size of the VM disk, so who can install several systems in the guest OS. If something bad happens during the expansion of the size of the virtual disk, the guest operating system and its Applications will not work. Thus, before expanding the size of the virtual disk, I need to back up the virtual machine hard disk external.

  I have check the disk hard host operating system Windows 7, the path is C:\VirtualMachine\WindowsServer2003\... When I get to the top of the virtual machine on the external hard drive, simply select the 'VirtualMachine' folder and save automatically. I have 3 questions as follows:

  First of all, if something bad happens during the expansion of the size of the virtual disk, the guest operating system and its Applications do not work. Can I just delete the folder 'VirtualMachine' in the host operating system?

  Secondly, the problem of the first question does not affect files in the physical hard disk to host operating system?

  Third, if something wrong happens during expand the size of the virtual disk of OS guest, I simply delete the folder 'VirtualMachine' in the host operating system and load the original 'VirtualMachine' from the external hard drive in the host operating system. Works correctly as long as one is the Virtual Machine before Stude the virtual disk size?

  Thank you.

  First of all, if something bad happens during the expansion of the size of the virtual disk, the guest operating system and its Applications do not work. Can I just delete the folder 'VirtualMachine' in the host operating system?

  Yes.

  Secondly, the problem of the first question does not affect files in the physical hard disk to host operating system?

  N °

  Third, if something wrong happens during expand the size of the virtual disk of OS guest, I simply delete the folder 'VirtualMachine' in the host operating system and load the original 'VirtualMachine' from the external hard drive in the host operating system. Works correctly as long as one is the Virtual Machine before Stude the virtual disk size?

  Yes.

  That's right, as long as you have not added and other virtual disks of different folders on the host of the virtual machine, you can probably did not.

  After developing the size of the virtual disk, you must also change the size of the partition in the guest operating system.

  André

• vSphere on iSCSI SAN disk size

  Hello

  I installed the 5.1 version and will also use VMWare View.

  I see in the documentation that there always a size of 2 TB drive but also given conflicting reports on that.  I tested it and I see that he can see more then 2 TB.

  My question is if I want to 2 TB standard or can we go more then 2 TB and if yes, what size Max now.

  Thank you.

  
  Gary

  Hello

  If you're talking about VMFS datastore now we support 64 to http://www.vmware.com/pdf/vsphere5/r50/vsphere-50-configuration-maximums.pdf

  If you talk about virtual disk, virtual disk size 2 TB less 512 bytes

  Concerning

  Mohammed

• Maximum number of virtual disk for a virtual machine in vSphere 4.1

  I read the maximum record rate and see that the maximum number of virtual disk is 16 for FT.

  I have the same document I seem not to be able to see the number max of virtual disk that can be taken in charge for a virtual machine.

  The number will be the same as the number of LUNS per host which is 256?  I know the max is for the host, but that be will come the number of Director to the total number of virtual disk that can be supported in the virtual machine?

  In fact, in a logic unit number, we can have more than one data store that can be mapped to a virtual disk.

  I'm confused.

  Thank you and have a nice week,

  Anthony.

  If I am not mistaken, you can attach up to 60 virtual disks to a virtual machine. 15 for each of the 4 virtual SCSI controllers.

  André

• How to identify a virtual disk inside a windows 2008 VM

  I created a data store ISCSI 1.98 TB for one of my VM Windows 2008. I've added four virtual disks size still 300 GB to this Windows 2008 virtual machine and now I need to extend one of the specific disks. How to identify the interface of the VM virtual disk.

  In windows, I know what drive it is how can disc 8 but I know which drive is 8 on the change settings tab? I thought I knew what disk I was growing, and it wasn't the right one. Is there a tool on the market that do that?

  Thank you

  You will need to open the properties of the disk (left) rather than any partition on this disk.

  André

• Dell virtual disk are larger. You want to increase the size of the data store.

  Hello

  I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

  I tried to follow the article here that explains how to do this via the CLI.

  Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

  Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

  I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

  ---

  I use that as a guide:

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461

  
  

  1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

  This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)

  
  

  2. open a console to the ESXi host.

  Pretty simple.

  
  

  3. get the DeviceID for the data store to change.

  ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

  System file VMFS-5, 60 extending on 1 partition.

  File system label (if applicable): datastore1

  Mode: public

  Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

  UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

  Partitions split (on 'lvm'):

  NAA.6c81f660ef0d23001ad809071096d28a:4

  
  

  A couple of things to note:

  a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

  b. the number of Partition on the disk is: 4 ' [...]: 4 "»

  c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

  4. Enter the amount of disk space available on the data store.

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1

  
  

  5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  ~ #

  
  

  According to the table in article KB

  4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

  | |        |          |   |

  | |        |          |   \---attribut

  | |        |          \---type

  | |        \---se finishing sector

  | \---a starting from sector

  partition \---Numero

  
  

  Also note how the number of section start the old end sector number is + 1.

  
  

  6 identify the partitions that need to be resized and the size of the space to use.

  We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.

  
  

  7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

  ESXi 5.x has a command to do this:

  ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

  1 5854986239

  This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

  13711360 - 5854986239 (i.e. the end of the disc)

  
  

  8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

  Using the above information, our command is:

  resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239

  
  

  9 step 8, the partedUtil command can report the warning:

  He did not. Displacement.

  
  

  10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.

  
  

  11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

  Fact.

  
  

  12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

  vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.

  
  

  It did not work. I got an error:

  / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

  23001ad809071096d28a:4 ".

  Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information

  
  

  Also the partition was very different to what I asked:

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 1560018942 251 0

  
  

  I fixed it by running these commands:

  ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

  ~ # vmkfstools v

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  Update:

  Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

  Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

• Increase in the size of the virtual disk after update comments

  Hello

  I'll put up a basic using Fedora 11 virtual machine. I installed it with the installer in text mode to get a basic system with a small footprint. Once installation is complete, the size of the folder for the virtual machine is 564 MB. After you have installed a few programs (presto, nano) and run yum update, the size of the folder double almost to .97GB when the virtual machine is shut down. There is no snapshot on each machine. Disk settings are a single virtual disk of 8 GB, 2 GB split, not preallocated. The OS is Vista Business 32-bit. VMware Workstation is 6.5.3 Build 185404.

  What is all that extra space? I tried the yum and several options reset but no luck. I ran - x - m - max-depth = 1 / in computers with the following results:

  On the virtual machine without Update:

  0/dev

  10/var

  1/Media

  1/home

  1 / opt

  1/boot

  6 "/ bin"

  0/proc

  14/etc

  72/lib

  1 /srv

  0/sys

  310/usr

  1/MNT

  0 /selinux

  1 / lost + found

  11/sbin

  1/root

  1/tmp

  421.

  The virtual machine with updates:

  0/dev

  14/var

  1/Media

  1/home

  1 / opt

  1/boot

  6 "/ bin"

  0/proc

  15/etc

  126/lib

  1 /srv

  0/sys

  314/usr

  1/MNT

  0 /selinux

  1 / lost + found

  11/sbin

  1/root

  1/tmp

  484.

  From there, everything looks normal without any increase in the brightness of the use of the disc between the virtual machines.

  Here is what the comments files look like:

  Free update:

  555,483,136 Fedora11_TM - s001.vmdk

  33,882,112 Fedora11_TM - s002.vmdk

  393 216 Fedora11_TM - s003.vmdk

  2 424 832 Fedora11_TM - s004.vmdk

  65 536 Fedora11_TM - s005.vmdk

  8 684 Fedora11_TM.nvram

  607 Fedora11_TM.vmdk

  0 Fedora11_TM.vmsd

  2 099 Fedora11_TM.vmx

  266 Fedora11_TM.vmxf

  74 448 vmware - 0.log

  95 278 vmware - 1.log

  68 005 vmware.log

  With updates:

  1,001,127,936 Fedora11_TM - s001.vmdk

  47,710,208 Fedora11_TM - s002.vmdk

  393 216 Fedora11_TM - s003.vmdk

  2 818 048 Fedora11_TM - s004.vmdk

  65 536 Fedora11_TM - s005.vmdk

  8 684 Fedora11_TM.nvram

  607 Fedora11_TM.vmdk

  0 Fedora11_TM.vmsd

  2 099 Fedora11_TM.vmx

  266 Fedora11_TM.vmxf

  68 109 vmware - 0.log

  68 265 vmware - 1.log

  68 172 vmware - 2.log

  72 328 vmware.log

  This something that escapes me that would cause this increase in space?

  Thank you.

  When you don't have vmware tools installed vmware-vdiskmanager shrink is indeed very.

  You first need to wipe unused space with zeros.

  If DD \u003d/dev/zero of = 0bits bs = # 20971520 bs = 20 m rm 0bits

  The two commands will create a such wiperfile.

  You must run these commands for every single partition that you use.

  When done turn off the virtual machine and run vmware-vdiskmanager with option to shrink again.

  This time, it will be more efficient

  ___________________________________

  VMX-settings- VMware-liveCD - VM-infirmary

• Increase the size of the virtual disk.

  I just installed Windows virtual PC on Windows 7 64 bit and I try to install a program of 6 GB.  He said that there is not enough memory.
  The size of the virtual disk in less than 2 GB and I can't find any way to increase this size.  I tried to create a second virtual disk with more memory, but the same error comes back.  Is there a way I can increase the size of the primary virtual disk?

  Post here http://social.answers.microsoft.com/Forums/en-US/w7install/threads or here http://social.answers.microsoft.com/Forums/en-US/w7programs/threads instead.

• MD3000 cannot change virtual disk ownership / preffered path - ERROR 29

  Current configuration

  PowerVault MD3000 (deleted by the moderator) - attached to two servers PowerEdge R610 using Dell SAS 5/e card in each r610. The R610s act as a host ESX VMWare ESXi 5.5.0

  We have created multiple LUNS on the storage array and noticed that traffice all happening through a RAID controller or another module (and it seems to me not change without prompting when you look at the storage Bay). I turned off a two different virtual machines to try to change the path and had an error with a certain delay - I stuck this error below. I also tried to redistribute virtual disks tab the MDSM software nothing works support.

  By reading, it seems that the LUN should be attributed to a particular raid controller before all I / 0, but I still feel like're missing us something as to why we cannot distribute the traffic properly.

  According to some records for a MD3200 -.

  "If the host has a path of data unique to the MD, the virtual disk storage array.
  must be owned by the controller to which the host is connected.
  That's what we're trying to accomplish. I don't know if the hosts are to be physically detached from the SAN, or if there is a bit of software to fail us.
  Thank you in advance! If I failed to provide all the details, please let me know and I'll try to gather the information.
  Here's the error output:

  OPERATING ENVIRONMENT DATA

  Name of the client system: FLMGMT01
  Client OS: Windows Server 2008 R2

  Application version: 03.35.G6.88
  Storage management of version table: 03.35.G6.88
  Name of storage array: VAB-NAS-01
  Firmware version: 07.35.39.64
  Management class: devmgr.v1035api01.Manager

  **************************************************

  DATA ERROR

  Command sent to the RAID controller module to the location: 0
  Host name: 192.168.19.233
  IP address: 192.168.19.233

  Return code: error 29 - this operation cannot complete because there was a failure of authentication of security on a parameter in the command sent to the RAID controller module.

  Try the operation again. If this message persists, contact your Technical Support representative.
  Operation when the error occurred: PROC_assignVolumeOwnership
  Timestamp: August 25, 2014 16:18:59

  DATA BATTERY

  devmgr.v1035api01.Sam.JAL.ManagementOperationFailedException:
  at devmgr.v1035api01.sam.jal.SYMbolClient.dispatchOperation (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.issueCommand (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommandCommon (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommand (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.assignVolumeOwnership (unknown Source)
  at devmgr.v1035api01.sam.configuration.controller.ChangeControllerOwnershipDialogPanel.performCommitAction (unknown Source)
  to devmgr.v1035api01.shared.wizard.DialogPanel$ NotifyBackgroundTaskAdapter.performOp (unknown Source)
  at devmgr.v1035api01.shared.AbstractTaskAdapter.run (unknown Source)

  THREAD DATA

  Thread [reference Manager 10, System]
  Thread [finalizer, 8, System]
  Thread [dispatcher Signal, 9, System]
  Thread [attach auditor, 5, System]
  Thread [Java2D grinder, 10, System]
  Thread [TimerQueue, 5, System]
  Thread [Swing-Shell, 6, System]
  Thread [AWT-closure, 5, main]
  Thread [AWT-Windows, 6, main]
  Thread [EventQueueMonitor-ComponentEvtDispatch, 5, main]
  Thread [Thread-3, 5, main]
  Thread [AWT-EventQueue-0, 6, main]
  Thread [DestroyJavaVM, 5, main]
  Thread [SwingWorker-pool-2-wire-1, 5, main]
  Thread [ChangeDetector, 6, main]
  Thread [PreferenceStoreChangeDetector, 6, main]
  Thread [LogMsgThread, 6, main]
  Thread [Np_Link_Monitor0, 6, main]
  Thread [DMVGarbageCollectorThread, 6, main]
  Thread [RecoveryProfile-27, 6, main]
  Thread [NEA-28, 6, main]
  Thread [RecoveryProfile-30, 6, main]
  Thread [NEA-31, 6, main]
  Thread [Timer 0, 6, main]
  Thread [RecoveryProfile-35, 6, main]
  Thread [NEA-36, 6, main]
  Thread [RecoveryProfile-38, 6, main]
  Thread [NEA-39, 6, main]
  Thread [Timer 1, 6, main]
  Thread [Timer 2, 6, main]
  Thread [Timer-3 6, main]

  
  Thread [RecoveryProfile-48, 6, main]
  Thread [NEA-49, 6, main]
  Thread [Timer-4 6, main]
  Thread [RecoveryProfile-53, 6, main]
  Thread [NEA-54, 6, main]
  Thread [Timer-5 6, main]
  Thread [SwingWorker-pool-2-wire-2, 5, main]
  Thread [RecoveryProfile-69, 6, main]
  Thread [NEA-70, 6, main]
  Thread [Timer-14, 6, main]
  Thread [Timer-91, 6, main]
  Thread [host 2.3, principal of the Image]

  Hello MrRedPants,

  Since you are using a configuration not redundant you will have problems trying to modify the paths between the controllers since the two hosts have only a single connection to the MD3000.  What you could do if possible is to get 2 more SAS cables & connect ports second on the MD to RAID opposite that the host is currently connected to.

  Now, if this isn't an option so that you can make is to have 2 disk groups and assign the virtual disks / LUNS that are connected to each host in their own disk group.  If you go to each host their own groups of disks, then you will need to stop the e/s as you move the Ramdisk to the new group of disks so that you want to discard any data loss.

  Please let us know if you have any other questions.

• The virtual hard disk size

  For worker Analyzer IO VM, it is recommended to create a larger second virtual hard disk that serves as a target IOmeter.

  
  

  Is the size of the virtual hard drive exactly the same workload working set size, which means that all data in the virtual disk is read from or written to storage during the race?

  Do you have other recommendations to decide what size the second virtual hard disk should be a VM worker?

  Thank you

  Rebecca

  Hi RS_1, it's useful, but I was looking for some additional tips for the user guide.

  I received responses from some of the developers of IO parser and also ran a few tests of my own.

  Iometer generates its I/O based on the number of blocks of target disc (i.e. the manually added virtual hard disk on the worker VM).  The size of the disk hard virtual will be be equivalent to e/s working set size.

  For a virtual hard drive that strikes only cache, a rule would be its size to 100 MB.

  For a virtual hard drive that hits the disk, the virtual hard disk could be sized anywhere from 10 GB to the top. The drive, / o most actually hits disc rather than cache.

  To do this, I created a 200 GB thin provisioned virtual hard disk for my e/s VM Analyzer worker. As I ran the Iometer workload, I could see the thin disc quickly increase from almost nothing to its size fully provisioned. This means that the new virtual hard disk sectors were continually being read and written by Iometer. Interestingly, it only took about 5 minutes to flesh out a whole 200 GB drive. Obviously, this speed would depend on the type of I/O profile used.

  I also tested a 20 GB disk Iometer vs virtual a virtual drive of 200 GB. Average latency, IOPS / s and flow were all better for 20 GB disk - because a greater proportion of e/s in this case was hit the cache, tilt the numbers positively.

  So, even at the drive hard virtual, sizes last 10 GB, size of the VHD will affect yet observed performance to Iometer.

• Machine virtual hard disk (virtual disk) of the upper size limit put into service

  Hi there, so I'm trying to create a hard drive or a virtual disk in a Virtual Machine in order to configure the virtual machine as a file server. The data store is a Promise VTrak M610P and I installed the vtrak as a type of VMFS5 5,46 TB of space (4 2 hard disks to each RAID 5). In the virtual machine, I added a hard drive and selected the store data vtrak and tried to set the provisioned to 5.46 TB size and type thick lazy disposition to zero, but I get an error of DiskCapControl with the range values. I changed the size set in service and 4 TB and he accepted the new hard drive. I can't find anything on the actual limit on the creation of hard disk in a virtual computer.

  
  

  I'm running a server Supermicro X7DAL-E with VMware ESXi 5.5 U2.

  Any ideas would be useful. Thank you.
  

  I forgot I asked a similar question on a different section of the forum (shame on me), but I found a solution. Please see the following post Re: SMB access using esxi host and manage with MS server 2008 storage

  Here's what I wrote on the link above:

  So it turns out that there seems to be something wrong with vClient when you add a hard disk (virtual disk) to a virtual machine of size greater than 4 TB. Article VMware KB: value of range error message when you add more than 4 TB capacity discs in vSphere Client describes this if you encounter this problem, add the hard drive via vSphere CLI, CLI power or vmkfstools. So this seems to be a known issue on vClient. What I ended up doing was using vClient, creation of hard disk, adding to the virtual machine (size of the hard drive is to 5.45) and when I would get the error message on the DiskCapControl out of reach, I would just click OK and then finalize the creation of the hard drive on the virtual machine. Once the process is complete, I selected the virtual machine and noticed that he indeed added a new HDD size 5.45 TB even if he's complained about it. I pulled to the top of the virtual machine with windows server 2008 R2 installed and was able to create a new disk under windows and set it up as a shared drive on the network. Looks like vClient must be updated by VMware and correct this bug, if it's a bug that I think. Thank you for the help vervoort!

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

  Hello

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

  Thank you for taking the time to read this discussion.

  Best regards

  S.A

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

  André

• What is the maximum size of virtual disk in machines virtual esxi 4.0

  I am trying to create a virtual disk to a virtual machine, I want to make the size of the 300 GB disk but its not allowing to create.

  Can I know what is the maximum size of virtual disk, we can create in machines virtual esxi 4.0 with vmfs3 partition

  
  

  The maximum size of the virtual disk that you can use depends on the size of the selected block when formatting of the data store. With the default of 1 MB block size, the maximum size of virtual disk on a VMFS-3 datastore is ~ 256MB.

  André