The below illustrated scenario would never be acceptable for production scale, but may illustrate something odd with the COS/VMKernel? Scenario...
HP server
1 2.8 32-bit XEON processor
2 GB RAM
5302-128 Smart Array Controller
ESX 3.5 build
2 SCSI drives RAID-1 for ESX OS
6 SCSI drives RAID-5 for VMFS3
1 IDE 30 GB drive with USB interface for EXT2
1 IDE 20 GB drive for EXT2
2 VMs, Windows 2008 Core only
Of course this is a lab box for experimentation of doing nasty things in the COS. But here is the problem(?), 1) run vcbMounter to snapshot first VM, ok running in first virtual console, 2) start vcbMounter snapshot on second VM, ok, running, in second virtual console.
But here is the kicker, the COS is all but frozen, it is SO slow, inconsistent, logging into a third virtual console is almost impossible? This does not make sense. vcbMounter is a hog, but should not be that much of one. Was not expecting anything wonderful, but so slow it takes TOP 5 or so minutes to dispaly anything on 3rd virtual console? 3rd virtual console seems to get cycles is short windows, sometimes keystroke response is smooth other times it is very choppy and lags.
Load Average is showing 5.66, 5.88, 4.23, and bouncing around with 1 point of each. Ok, this makes a bit of sense given the hammering that is going on. Is IDE really that inefficient on ESX OS?
Anyone else see this behavior? Expected this specific setup not to be a speed daemon, but if vcbMounter can nail the COS like this, it makes for interesting issues of the box really is under distress. COS needs to be responsive in emergency situations, this is not a warm fuzzy. Unfortunately, for various reasons we did not do this specific test on this specific hardware with the Beta, or RC releases, wish we had for comparison.