The VMware Fusion default for its .vmdk (not .vmdm) virtual hard disk is twoGbMaxExtentSparse not MonolithicSparse. You can change the disk type in the Virtual Machine Settings however unless you have some compelling reason otherwise I'd leave it as a split disk.
BTW At the present time there is not a single hard disk of the size limit of a file on the HFS+ or Mac OS Extended Filesystem! 
Which is 8 exabyte.
aliv, i had to configure the ip address direct on the physical server and enable the management network. hit f2 after esxi loads and you'll be able to see the configuration options. it'll ask you to restart the management nic - select YES and it should work after that.
USB DRIVE RECOGNITION BROKEN IN 10.0.2 UPGRADE
After upgrade to Workstation 10.0.2, my USB SD card readers mount my SD card "drives" in the Linux host, but the virtual machine lacks any awareness of their existence.
VM / SETTINGS / USB CONTROLLER is set to automatically connect (checked, but greyed out. Why greyed out??)
Trying USB 1.1, 2.0, 3.0 (install extra driver) does not help.
VMWare Tools was upgraded, no avail, reinstalled, no avail.
VM / REMOVABLE DEVICES never lists the USB drive mounted on my host, so I cannot ask to disconnect from host and connect to VM.
When it comes to plugging in a USB device, the endless loss of control with Workstation technology is in marked contrast to the smooth integration of USB devices with the Apple MacBook in the mass market "FUSION" product. Plugging in a USB device to the Mac produces a popup: connect to MAC side or VM side? Every time. End of story.
Spare me the vast knowledge base of articles on long-gone versions of the Workstation product and just make it work.
Thank you
Hello,
this is a desperate cry for help, i'm ready to hang myself (figure of speach) 
After upgrading all my vsphere components to the latest 5.x version (coming from 5.0) I installed the view connection server en security server as last components.
The view conenction server pointed me to the fact I have to setup certificates.
I've been follwing all steps, detail after detail from this KB:
I have setup a AD CA integrated with the AD, made the needed changes to the template for key usage, made the certs, checked the certs, followed the steps to enroll the certs in the SSO
Al fine, all ok....
I'm at the point of Replace the vCenter Server 5.x certificates.:
I did wat is asked and it goes wrong at the point where i'm asked to login to the MOB. (AND I found out that I locked myself out of the vcenter)
So without reloading the sslcert in the MOB, the isregtools is not ending with code:
0
0
... it ends with
9
9
I stopped here to make sure that I do not encrypt my db with the wrong cert.
I edited the VPX-ACCES table and added local credentials, nothing works...
How do I proceed? 
I have to get all up and running by tuesday or we can't use our pc rooms on faculty :/
Desperate regards
John
What is the Linux distribution and version you're using?
Do you see a vmware-usbarbitrator process running on the host? If not, does it start when running
sudo /etc/init.d/vmware-usbarbitrator start
?
--
Darius
Hmm, doesn't seem to be any confirmation that this was resolved in the 6.0.3 release notes.
VMware Fusion 6.0.3 and VMware Fusion 6.0.3 Professional Release Notes
Perhaps there's a separate set of release notes for VMWare Tools? Anyone know if Steve's fix was the fix integrated into 6.0.3?
Thanks!
Workstation 10.0.2 and Fusion 6.0.3 use the same set of VMware Tools, which contain the fix.
I don't know why it was omitted from the Fusion 6.0.3 release notes...
--
Darius
A Cloud Server is a process that runs on what’s called a hypervisor. This hypervisor software lets a single computer appear like it is a dozen or more computers. A single Cloud Server is just one of those processes. It appears to the user like a server, but it isn’t its own collection of hardware. A dedicated server is its own collection of hardware. It is a whole computer, complete with all hardware that makes up a computer including a processor, hard drive, RAM and power supply unit.
Message was edited by: Darius Davis to remove gratuitous link spam.
Dear VMware community,
I had the same issue as the original post, able to install esxi 5.1 or 5.5 but could not boot into esxi after the install, it would fail to read the install and return me back to the bios menu.
hardware:
Asus Z87 Sabertooth
Intel i7-4770
24 GB RAM (2x8, 2x4)
Intel Gigabit CT desktop adapter
Adaptec 3405 raid card
WD Green 2 TB HDD x 4
I followed the guide below to inject the system board drivers into my esxi 5.5 hypervisor iso.
ESXi 5.1U, Z87-PRO, Adaptec ASR-6805E
Then used the application rufus to create a install media on an usb stick.
Booted from the usb stick, without any other drives attached to the system board.
Installed esxi 5.5 on the usb stick, using formatmbr on the boot option.
After all that, I was able to boot esxi 5.5 Hypervisor on my test system.
Time to upgrade my hdd's and go crazy... 
Thank you for all the help.
Jason
Hello,
I started setting up a ESXi 5.5 Update 1 server this week. I didn't realize that Dell shipped the server with two Virtual Disks instead of one. I realized this _after_ I had already created the datastore and setup a few VMs within. I called Dell which sent me specific instructions to increase the delete the second (blank) virtual disk and add it to the main one. In the end, I have increased the single VD from 2TB to 3TB and I want to give the remaining space to my datastore.
I tried to follow the KB article here which explains how to do this via CLI.
Well, it didn't quite work. Fortunately, I was able to recover my datastore my setting the start and end sectors back to their original numbers. But I'm still left with this nearly 1TB of space that I can't assign to the datastore. After I rescanned storage adapters in the client, the new Dell drive size was reflected under Extent Devices. Clicking "Increase..." produces the following error which led me down the path of the CLI method:
Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" for object "ha-datastoresystem" on ESXi "[myservername]" failed.
I am going to paste my notes that I took while doing to job. Things went off the rails when I set the size of partition 4 to the larger size. Any help, please?
---
I am using this as a guide:
1. Use the boot device hardware's management tools to add additional disk capacity to the device. For more information, engage your hardware vendor.
This has been done. The new size of the Virtual Disk is 2791.88 GB (2.79188 TB)
2. Open a console to the ESXi host.
Simple enough.
3. Obtain the device identifier for the Datastore to be modified.
~ # vmkfstools -P "/vmfs/volumes/datastore1/"
VMFS-5.60 file system spanning 1 partitions.
File system label (if any): datastore1
Mode: public
Capacity 1971926859776 (1880576 file blocks * 1048576), 1042688245760 (994385 blocks) avail, max file size 69201586814976
UUID: 534e5121-260d4450-19dc-f8bc1238e18a
Partitions spanned (on "lvm"):
naa.6c81f660ef0d23001ad809071096d28a:4
A couple of things to note:
a. The Device Identifier for Datastore1 is: naa.6c81f660ef0d23001ad809071096d28a
b. The Partition Number on the disk is: 4 "[...]:4"
c. The prefix, "naa," stands for "Network Addressing Authority" The number immediately after is a unique LUN.
4. Record the amount of free disk space on the Datastore.
~ # df -h
Filesystem Size Used Available Use% Mounted on
VMFS-5 1.8T 865.4G 971.1G 47% /vmfs/volumes/datastore1
5. Equipped with the device identifier, identify the existing partitions on the device 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 chart on the KB article
4 13711360 3865468766 251 0 - Primary #4, Type 251=0xFB=VMFS, Sectors 13711360-3865468766
| | | | |
| | | | \--- attribute
| | | \------- type
| | \---------------- ending sector
| \------------------------- starting sector
\--------------------------- partition number
Also, notice how the starting section number is +1 from the previous ending sector number.
6. Identify the partitions which need to be resized, and the size of the space to be used.
We want to resize partition 4. I don't really understand the last part of this sentence, however. Read on.
7. Identify the desired ending sector number for the target VMFS Datastore's partitions. To use all space out to the end of the disk, subtract 1 from the disk size in sectors as reported in step 5 to obtain the last usable sector.
ESXi 5.x has a command for this:
~ # partedUtil getUsableSectors "/vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a"
1 5854986239
This means we want Partition 4 of "naa.6c81f660ef0d23001ad809071096d28a" to be:
13711360 - 5854986239 (i.e. the end of the disk)
8. Resize the partition containing the target VMFS Datastore using the partedUtil command, specifying the existing starting sector of the partition and the desired ending sector:
Using the above information, our command is:
# partedUtil resize "/vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a" 4 13711360 5854986239
9. During step 8, the partedUtil command may report the warning:
It did not. Moving on.
10. The partition tables have been adjusted, but the VMFS Datastore within the partition is still the same size. There is now empty space within the partition in which the VMFS Datastore can be grown.
11. Run this command vmkfstools -V to perform a refresh of the VMFS volumes.
Done.
12. Grow the VMFS Datastore in to the new space using the vmkfstools --growfs command, specifying the partition containing the target VMFS Datastore twice.
vmkfstools --growfs "/vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4" "/vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4"
This did not work. I got an error:
/vmfs/volumes # vmkfstools --growfs "/vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4" "/vmfs/devices/disks/naa.6c81f660ef0d
23001ad809071096d28a:4"
Failed to get info from head device path /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4
Also the partition was vastly different from what I asked for:
~ # 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
Thanks for this reply. I found that I could not access settings with Fusion 4 and Mavericks so upgraded to Fusion 6 and all works well thanks.
—
原来我们在裸机上运行我们的程序时，对裸机的内存是可以直接操作的（让操作系统，非标OS，即不是市面上常见的Windows，Linux，FreeBSD，Soloaris等系统，直接为应用程序保留内存），这样有一些重要信息在机器重启之后可以从保留内存读出。
虚拟化之后，原来的硬件内存实际上是由Host OS分配的了。这样如果Guest OS死机重启了，那我有什么办法获得该VM保留内存的内容呢？能让Host OS为该VM保存保留内存的内容么？
I am trying to upgrade from 5.1 to 5.5 but every time I try, I get to the welcome screen (Esc to Exit, Enter to Continue) and I cannot press enter or esc - nothing happens.
I've tried CD/DVD/USB, several different keyboards, nothing works. The keyboard works fine, as I am able to choose the image as a boot option in pre-boot, so it looks like its just the VMWare installer.
I tried using the 5.5.0 image, and 5.5 update 1 - neither works.
Any ideas?
Thanks
Have you checked if your HW is supported by 5.5? Even if it was supported by 5.1 it does NOT mean automatically it is supported by 5.5. So maybe 5.5-installer does not know how to continue. I have hit this obstacle myself: my quite new and supported (up to 5.1u1) Intel server-board for xeon/sandy cpu was suddenly dropped from HCL for ESXi 5.5...
Hi
I didn't even think of that because this server is barely 12 months old.
Looks old like support was dropped with 5.1 U2
I've got some VMs running 2012 R2, and they're having issues with external USB HDDs. It disconnects on occasion, and Windows says that it can't start the device because it couldn't get its information (or something of the sort). I was hoping 5.5 would resolve this. Can you provide any assistance?
I guess this was the problem. There is a 200 GB difference among the two datastore even after the pools was provisioned.
Thanks eeg3
Regards
John
No if you want SDRS need to leverage SDRS IO load balancing for that particular datastore, then you need to UNCHECK that option (which is enabled by default when you disable SIOC), once you uncheck, it is mean that SDRS will collect stats for IO load balancing.
Just some more info:
SIOC is getting leveraged by SDRS for VMs initial placement and IO load balancing. When you enable IO metric, SIOC gets enabled on all the datsstores in the datastore clusters automatically. Hence, SIOC helps SDRS for initial placement as well as IO load balancing, at the same time it does its intended job of distributing IOPS to each hosts based on shares when there is IO contention.
1. By default, SDRS & SIOC will be enabled. Both features would fully used.
2.If you do not want to use SIOC for IOPS distribution across hosts when there is a contention, then you can disable SIOC on particular datastore (or all datastores in DS cluser) but UNCHECK the disable storage i/o stats collection . i.e. In this case, SIOC would be used only for SDRS stats collection (which is required for SDRS initial and Io load balancing), SIOC will not distribute IO per shares. This option is introduced only from VC 5.5. There is a confusion on this option & there is NO any KB available.
3.You can use SDRS only for space capabilities as well. Then disable SIOC and do not uncheck stats collection option as well
VMware should document this option.
------------------------------------------------------------------------------------------------
If this info is useful, plz consider awarding points as correct or helpful
Hello everyone.
I'm using a 2-node VSA Cluster. I recently upgraded vCenter and both ESX hosts to 5.5 U1. The upgrade went fine including VSA Manager 5.5.
The VSA Cluster version still remains on version 5.1.1 as well the VSA Cluster Service which I back then installed on a separate Linux machine (vCenter and the VSA Cluster service on linux box runs on a third smaller ESX server independant from VSA Cluster).
Did someone already made an upgrade of the VSA Cluster from 5.1 to 5.5? The steps seems very easy, I guess first I need to change the VSA Cluster password to the default (mentioned in release notes) then shutdown all VM's (no I/O on datastores) and then press the upgrade button. But I'm a little afraid of doing that.
Any hints?
Thanks
Phil
Hi,
To monitor WSMQ you should install hyperic NOJRE agent and use IBM Java (WSMQ Java). I recommend to install the latest 5.8.1 version. This version includes support of non default installation path of WAS/WSMQ.
Before you start an agent, make sure:
If you still have problem with auto-discovery, please attach an agent.log. In addition run next command and attach output.log:
java -jar bundles/agent-XXXXX/pdk/lib/hq-pdk-XXXX.jar -p wsmq -Dplugins.include=wsmq -Dlog=debug -m discover -a metric > output.log
Hi,
You said manually using hq-pdk.jar its working. Did you use next command ? If no please do this and attach output.log. If yes, remove a platform with server ans services, delete data directory and restart an agent.
java -jar bundles/agent-XXXXX/pdk/lib/hq-pdk-XXXX.jar -p tomcat -Dplugins.include=tomcat -Dlog=debug -m discover -a metric > output.log
