Have you ever had a user running IOmeter on a virtual machine just to ‘test’ the performance of the virtual disk… at 9am…on a Monday morning??
Well it might happen to you once but not twice as you would immediately have powered off the virtual machine and eventually head shoot the user🙂
There is a more elegant way to mitigate the risk of having a valid virtual machine though but still able to put down your storage on its knee and ruining your Monday morning.
- Power off the virtual machine
- Click Edit Settings.
- Click the Options tab.
- Under the Advanced: General section, click the Configuration Parameters button.
- Click the Add Row button.
- Add one or both of these settings for each virtual disk device:
sched. < diskname > .throughputCap = < value >< unit >
For example: sched.scsi0:0.throughputCap = 10KIOps
sched. < diskname > .bandwidthCap = < value >< unit >
For example: sched.scsi0:0.bandwidthCap = 10KBps
<value> is either
off or an integer, and is a string beginning with
GIOps). If no units are specified, the default of
K is assumed.
[UPDATE] You can cap below the k (thousand) by omitting K, M or G. e.g. 100IOps will cap at maximum 100 IO per second.
- Start the virtual machine. The virtual machine I/O is limited to the specified values.
This is only available in vSphere 4.1
Source: VMware KB 1038241