Activation of virtual disk

Similar Questions

• Failed to retrieve the info on drive & virtual disk service

  I did research all day for the solution to this irritating problem!
  I get upgraded my Eee PC (it has system requirements) of Windows XP Home Edition - Service Pack 3 for Windows 7 Starter.
  Whenever I try to install the OS, this message always appears at the top:

  Windows could not retrieve information about the disks on this computer.

  I found that many people have solved this by activating the virtual disk Service and by assigning the value automatic. My problem is that I don't have such a service on my computer. The WIS IS NOT in the list.
  I tried Googling on how to install the service, but I simply find the answer.

  If anyone has a solution to my problem, that would be greatly appreciated!

  Starter is not available in the trade. Go to Home Premium or Professional. See also http://technet.microsoft.com/en-us/library/dd799282 (WS.10) .aspx Frenchie

• VRTX - Server, fabric, PERC, Virtual Disk - understanding of the FAILURES of components

  I am trying to better understand the inner workings of the VRTX.  Here's my setup to help my question:

  Failover cluster of Hyper-V 2012 with 1 M520 as DC and 3 M620s as host servers with two cards of mezz for fabric B and C.

  Two controllers SPERCS (CSV and witness of the virtual disks controlled by SPERCS 1 and SPERCS 2 as backup/failover)

  I noticed that the SPERCs are each connected to a fabric switch (SPERCS 1--> B Switch fabric) and 2 SPERCS--> C switch fabric.

  What will happen if I pass a fabric failure?  Let's say its B fabric switch, so I have more access to the SPERCS 1 and, therefore, my virtual disks.  Because everything goes well with SPERCS 1, will my failover of virtual disks to SPERCS 2?

  And if anyone knows Hyper-V well enough, say the Mezz B PCIe card fails in one of my M620s, will be VMs on that host failover because they can't reach the CSV more?

  Any thoughts are greatly appreciated!

  Matt K

  Mattkane85,

  With sharing Perc 8 installed and configured for the fault tolerance, then it will work as you said. Perc cards are configured in an active/passive configuration, so when a Perc fails, the other Perc card takes control, which covers the controller. Now with your question, you asked in the case when a switch fails to will it still tipping? It would also be a Yes. With the active support of Multipath, which is necessary with the Fault Tolerant shared Perc 8 configuration, then uses redundant physical components, such as switches, cables and adapters to create logical paths between the server and the storage device. In the event that one of these components fails, Multipathing logic uses the controller replacing so that applications can still access their data.

  You can find more information and details on these configurations here, on page 6.

  Let me know if it helps.

• Virtual disk strange behaviour - please help

  Hi all

  I wonder if anyone can help. I started to experience a strange problem on one of my VM today.  I have a virtual machine running freenas.  The storage drives the actions of free storage to sit on are physical disks connected directly to the virtual machine and run normally, because of the way the works of freenas real HDD can be small enough and for the virtual machine, it's a prealloue virtual disk is 16 GB in size.  It is the only virtual machine sitting on a physical hard drive 256 GB. Today, I noticed a problem that the file for the virtual machine has become 240 GB in size, is probably not a normal behavior for a 16 GB VM.

  I checked snapshots which he had two auto protect snapshots which I deleted and disabled auto protect. This was reported to the size of the folder up to 182 GB.

  On the use of exploerer to view the folder it seems to be a large number of files, as shown below. Can someone explain if it should be there?  Also, how else remove them safely.

  Thanks in advance

  Thanks for the offer, but after a lot of interference and a virtual machine rebuild I managed to solve the problem.

  The solution was to set the 2 drives physical independent mode with persistent active. for some reason unknown to me this seems to prevent the creation of multiple disk files, it seems workstation creates them even when there are no snapshots.

  Time will tell us but seems to have solved the problems. Fingers crossed

  Thanks for all the help guys.

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

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

• Installed ESXi on USB/Flash but swap does not seem to have been placed on the virtual disk

  Hello

  I've read several times that when you install ESXi 5.1 on flash media he creates a work space available on a virtual disk of 4 GB in/tmp/scratch so that the USB itself is not used for temporary data to extend the life of the USB.  However, this doesn't seem to be from my experience and I was wondering if someone can help me to confirm that my disc scratch is actually on a virtual disk or whatever on the USB.  I should mention as well as installing ESXi has identified correctly as 'flash' disc type and the disc as a "Generic USB drive»

  After installation, I noticed two things:

  1 log-in user activity logs are able to survive a reboot (I don't think they should the ramdisk is dissolved after a reboot)

  2. There is no directory with the path/tmp/scratch

  Unfortunately I can not directly determine where the partition scratch is (be it on USB or RAM) because I did not have a file ' / etc/fstab "watching (even if I under ESXi 5.0 disk a hard base install?) and it doesn't seem to be a 'mount' command I can use to look at the existing mounts either.

  Can anyone tell me what can I do to verify that the directory used for temporary files is actually a virtual disk and not on the USB drive itself?  Hours of research are presented only the forum messages and documentation clearly indicating that the file will use "/ tmp/scratch", but that just isn't the case.

  Thanks in advance for all your help.

  As you can see from the output

  ~ snip ~

  drwxr-xr-t 1 root root 1260 28 Dec 23:08 50de22a5-f4afafa0-f7b5-001517197ad8
  root drwxr-xr-x 1 root 8 1 January 1970 50df4c30-82b86e61-8522-001517197ad8
  lrwxr-xr-x 1 root root 35 1 Jan 22:21 640GB_WD_Black_AALS-1 -> 50de22a5-f4afafa0-f7b5-001517197ad8

  ~ snip ~

  the UUID is a store existing data "640GB_WD_Black_AALS-1".

  This proves that with an existing data store, a folder ".locker" (which is a ScratchLocation) is automatically created.

  André

• The virtual disk is either corrupt or not a format supported.

  We have a 2008 R2 SP1 VM Datacenter we cannot snapshot.

  A manual snapshot of in the Client vSphere indicates the following in the tasks and events:

  The virtual disk is either corrupt or not a format supported.

  Our NetBackup software is automatic snapshots for VM backups and generates these three errors in the tasks and events:

  Cannot run a snapshot operation
  

  Operation timed out
  

  A general error occurred: VMX protocol error.

  The virtual machine has two virtual disks:

  [vmds-standard: (1) default] outhostname/ourhostname - 000001.vmdk

  [vmds-standard: (1) default] outhostname/outhostname_1 - 000001.vmdk

  Virtual disk files seem to be the usual file names. Instead, they resemble snapshot files or something similar.

  I don't know what is happening. Can anyone help?

  The file names are correct, since there is an active snapshot on the virtual computer. I found a few entries in the log file that we/you can see:

  08:01:25.543 Mar 23: vmx | DICT scsi0:2.deviceType = scsi-disk hard
  08:01:25.543 Mar 23: vmx | DICT scsi0:3.deviceType = scsi-disk hard

  There are some entries of old/orphaned for already deleted virtual disks! However, it should ask the question.

  21:13:06.212 25 March: vmx | In SUMMARY: SnapshotBranch failed: changes, followed by target file already exists (5).

  That's what I think is related to the question. For me, it looks like a problem once with block change tracking, which may have left orphans. What I would do, is first of all to delete all the .ctk files in the folder of the virtual machine on the data store (they will be recreated, only the next incremental/differential backup will take more time). If this is not enough, you can try to disable - at least temporarily - CBT for the virtual machine or remove the virtual machine to inventory, delete the .ctk files and then add it to the inventory...

  André

• Virtual machine allows you to re-creating virtual disks

  I have a virtual machine running as a server VCB proxy for arcserve backup under iSCSI r15. the system has three hard drives, today I noticed that I had a very small amount of space on my data store that extract of these records. It seems that there are three copies of each virtual disk in the data store, taking up all my space. Why are they here? I need to get this machine to only have a copy of each virtual disk.

  Perhaps mean you that your have several active snapshots?

  Check the VM shapshot and delete them.

  André

• 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 MD3000i not on the path preferred because of the AVT/RDAC failover

  Hello

  I am having some problems with my MD3000i failover to a non-prefere path.

  The MD3000i up the old mistake "Not on virtual disk preferred path due the AVT/RDAC failover" several times a day.

  It happened from time to time with ESX 3.5, but not much more happenging with version 4.

  In the var, I get the following:

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.926: 355597326227us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab80000067c48281b88. Vmhba40:C2:t0:L2 path is down. 2 remaining active paths. Touch of data warehouses: «DataStore3 - MD3000i (1 mb)»

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.934: 355597333792us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000438fa20000068b482818af. Vmhba40:C2:t0:L3 path is down. 2 remaining active paths. Touch of data warehouses: «DataStore4 - MD3000i (8 MB)»

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.942: 355597341892us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab8000017ae48d8991a. Vmhba40:C2:t0:L4 path is down. 2 remaining active paths. Touch of data warehouses: «DataStore1 - MD3000i (1 mb)»

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.949: 355597348866us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000438fa20000170448d8965d. Vmhba40:C2:t0:L5 path is down. 2 remaining active paths. Touch of data warehouses: «DataStore2 - MD3000i (1 mb)»

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.995: 355597394915us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab800002d8149242090. Vmhba40:C2:t0:L7 path is down. 2 remaining active paths. Touch of data warehouses: «VDIStore2 - MD3000i (1 mb)»

  24 July 11:49:13 tdvserver1 vobd: 24 Jul 11:49:13.004: 355597404112us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab800003d4c4a2ba941. Vmhba40:C2:t0:L8 path is down. 2 remaining active paths. Touch of data warehouses: «VDIStore1 - MD3000i (2 MB)»

  24 July 11:49:13 tdvserver1 vobd: 24 Jul 11:49:13.013: 355597413405us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab800006a5e4a6474e4. Vmhba40:C2:t0:L9 path is down. 2 remaining active paths. Touch of data warehouses: unknown.

  24 July 11:49:13 tdvserver1 vobd: 24 July 11:49:13.020: 355597420334us: connectivity lost http://vprob.storage.connectivity.lost to naa.6001e4f000436ab800006b684a65595d of storage device. Vmhba40:C2:t0:L10 path is down. Touch of data warehouses: «DataStore5 - MD3000i (4 MB)»

  24 July 11:49:17 tdvserver1 vobd: 24 July 11:49:17.375: 355601775018us: http://vprob.vmfs.heartbeat.timedout 49248754-672e53f0 - 38 b 7-00151778736 d VDIStore2 - MD3000i (1 MB).

  24 July 11:49:22 tdvserver1 vobd: 24 July 11:49:22.006: 355606406026us: http://vprob.vmfs.heartbeat.recovered 49248754-672e53f0 - 38 b 7-00151778736 d VDIStore2 - MD3000i (1 MB).

  And the following in/var/log/vmkernel:

  July 24, 11:51:03 tdvserver1 vmkernel: 4:02:48:27.601 cpu7:4206) WARNING: NMP: nmp_DeviceAttemptFailover: try tipping unit "naa.6001e4f000436ab800002d8149242090" world - order 0x41000812bc80

  July 24, 11:51:03 tdvserver1 vmkernel: 4:02:48:27.601 cpu2:6691) NMP: nmp_CompleteRetryForPath: Retry world the component 'naa.6001e4f000436ab800002d8149242090 '.

  July 24, 11:51:06 tdvserver1 vmkernel: 4:02:48:30.549 cpu0:4107) NMP: nmp_CompleteCommandForPath: command 0 x 12 (0x4100081c8300) for device NMP 'mpx.vmhba32:C0:T0:L0' failed on the physical path 'vmhba32:C0:T0:L0' H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 5 0 x 24 0 x 0.

  July 24, 11:51:06 tdvserver1 vmkernel: 4:02:48:30.549 cpu0:4107) ScsiDeviceIO: 747: command 0 x 12 for the device "mpx.vmhba32:C0:T0:L0" has no sense H:0 x 0 D:0 x 2 P:0 x 0 valid data: 0 x 5 24 0 x 0 x 0.

  July 24, 11:51:06 tdvserver1 vmkernel: 4:02:48:30.693 cpu1:4097) NMP: nmp_CompleteCommandForPath: command 0 x 12 (0 x 410008106500) for device "mpx.vmhba33:C0:T0:L0" NMP failed on the physical path 'vmhba33:C0:T0:L0' H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 5 0 24 x 0 x 0.

  July 24, 11:51:06 tdvserver1 vmkernel: 4:02:48:30.693 cpu1:4097) ScsiDeviceIO: 747: command 0 x 12 for device "mpx.vmhba33:C0:T0:L0" has no sense H:0 x 0 D:0 x 2 P:0 0 valid x-data: 0 x 5 0 24 x 0 x 0.

  July 24, 11:51:13 tdvserver1 vmkernel: 4:02:48:38.059 cpu0:4107) NMP: nmp_CompleteCommandForPath: command 0 x 12 (0x41000811f800) for device NMP 'mpx.vmhba32:C0:T0:L0' failed on the physical path 'vmhba32:C0:T0:L0' H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 5 0 x 24 0 x 0.

  July 24, 11:51:13 tdvserver1 vmkernel: 4:02:48:38.059 cpu0:4107) ScsiDeviceIO: 747: command 0 x 12 for the device "mpx.vmhba32:C0:T0:L0" has no sense H:0 x 0 D:0 x 2 P:0 x 0 valid data: 0 x 5 24 0 x 0 x 0.

  July 24, 11:51:13 tdvserver1 vmkernel: 4:02:48:38.202 cpu1:4097) NMP: nmp_CompleteCommandForPath: command 0 x 12 (0x4100081d2300) for device "mpx.vmhba33:C0:T0:L0" NMP failed on the physical path 'vmhba33:C0:T0:L0' H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 5 0 24 x 0 x 0.

  July 24, 11:51:13 tdvserver1 vmkernel: 4:02:48:38.202 cpu1:4097) ScsiDeviceIO: 747: command 0 x 12 for device "mpx.vmhba33:C0:T0:L0" has no sense H:0 x 0 D:0 x 2 P:0 0 valid x-data: 0 x 5 0 24 x 0 x 0.

  I spoke with people from Dell and Vmware support.

  Support for VMWare counterpart said that it is a matter of Dell... that VMware is a path problem and do what it is supposed to do.

  The Dell guy says there is nothing wrong with the MD3000i and the problem is with VMWare.

  None of them seem interested in helping me out more.

  I tried using MRU (default) & political pathing Round-Robin and set up iscsi on the host esx, in accordance with the following document:

  http://www.delltechcenter.com/page/VMware ESX4.0andPowerVault MD3000i

  I can vmkping for all the guests of all the peoples on the MD3000i without any problem.

  If someone saw, I would be very grateful.

  Thank you

  Jason

  Hmmm...  Well, if they are flipping back has nothing to do with VMWare, it is certainly a matter of Dell.  Have you tried their repatriation to the correct drives and then just reboot the stupid thing?

  Jason Litka

  http://www.jasonlitka.com

• Unable to create the virtual disk: fault. RestrictedVersion.summary

  Hello

  Im trying to create a virtual disk using the CLI on ESX4i.  The script is:

  vmkfstools.pl - Server 10.190.2.51 - c 20 g d eagerzeroedthick - a free /vmfs/volumes/Internal/test.vmdk

  When the script runs I get error: unable to create the virtual disk: fault. RestrictedVersion.summary

  Can someone tell me why please.  Im trying to create a disk of 20 GB with adapter free with eagerzeroedthick on my internal called storage, (no subdirectory).

  The file system is THAT VMFS 3.33 maximum file size is 256 GB.  The block size is 1 MB.  If it is the block size that is the problem how can I easily change?

  It's in a laboratory, not a production environment.  I need the flag eagerzeroedthick like Im trying to create a passive active cluster node MSCS 2 on a single physical node with 2 machines VMS.

  Thank you.

  Mike.

  If you use the free version of ESXi (U4 and later versions), access to tools like the VIMA API are read-only.

  -Matt

  VCP, vExpert, Unix Geek

• In any case about 512GB cap on virtual disks? / DRS issue?

  Hi all

  My first question is this:

  I have a San with about 1.7 TB Free however when I go to create virtual disks for one of my Vm It CAPS he died in 512 GB of space, is anyway around this hairstyle? other then extended partitions within windows using with 2 VMDK?

  My second question is when you have activated DRS, but value manual for all your machines, there is in any case to prevent it from asking which server you want to start the virtual machine on every time you have to start the virtual machine.  Even when I have the virtual machine created on one of the ESX servers in the cluster and go to start from this server, he always asks what server I wish on the VM with.

  (1) Yes, but not after you create the file system on the LUN - choose a new size of block to the VMFS is a destructive operation.

  (2) it is normal, expected behavior.  His request because potentially the best server to start the virtual machine on may not be the current.

  -Matt

• takes forever to expand the virtual disk

  I am expanding my virtual disk using the pdf file;  "Resize a virtual disk for Windows clients."

  A few months ago, I used this tutorial to resize with success of 20 to 40 GB but now I need more space.  But something does not work at the moment.  I am stuck at part 1, step 5.  I downloaded the most recent vdiskmanager GUI (I think it's more up-to-date, it is dated from 18/06/2007) and launched the MISTLETOE, my hard file selected, choose 75 GB and results opens the window.  BUT it has now been about 45 minutes and as far as I can say that nothing is happening.

  It takes so long?  Any suggestions?

  Thank you

  Bonnie

  If the actual size of the existing virtual hard disk is close to full capacity of 40 GB then it can take some time to develop.  Also because it creates a new file (s) hard, you must also make adequate free space on the host HDD to finish the process and because you use a 3rd party utility to interface with the VMware real Fusion of the program that is doing the job, the actual process may have a problem and do not make it to the 3rd party utility.

  What version of Fusion are you using?  If 2.x you do not need the 3rd party utility and make a resizing of the setting of Virtual Machines

  You can use the activity monitor to see if the process is still ongoing and or if there is the disk activity as in the file is always written.

  VMware-vdiskmanager is what did increase it then look for vmware-vdiskmana (full name does not show in the activity monitor) and see what's under its weight.

• How to install Firefox 7 on a virtual disk in Windows 7?

  Firefox automatically installs in my program files and won't let me change that. I have a permanent virtual disk. I think that Firefox would go faster if I installed it on the ram disk.

  That will probably not noticeable different because Firefox loads the files of program in memory after loading and the profile folder with all the personal data is located elsewhere.
  
  It is usually written causing the more delays, especially if anti-virus software checks each entry.

  See the Firefox profile folder:

  • http://KB.mozillazine.org/Profile_folder_-_Firefox
  • Help > troubleshooting information > profile directory: opens showing the file