I read an interesting article regarding VMotion Sickness : “Virtualization Will Cross the Chasm in Two Years” by Greg Ness
VMotion Sickness is a term coined to describe the effects from too many virtual machines moving around and VM Sprawl. This causes everything to run slower due to the overhead associated with VMs moving. This negates the basic virtualization benefits of better utilization of resources. VMotion is of course a management tool yet it can be a part of your virtualization management problem.
How do you deal with VMotion Sickness?
It starts with planning and management. Do a comprehensive capacity plan and implement structured management. Here are three keys to success:
1. Monitor right from beginning so you have a long history of data to troubleshoot problems
2. Keep a keen eye out for any virtualization bottlenecks
3. Know what is running on your infrastructure – keep details and avoid server sprawl
You may also want to read this article: “ Virtualization Will Cross the Chasm in Two Years”:
http://web2.sys-con.com/node/1203744
Monday, December 07, 2009
Subscribe to:
Post Comments (Atom)
And you can use the Reflex VMC product to track, manange, and set policy that can prevent this malady.
ReplyDeleteIt's also worthwhile monitoring application performance and availability within the VM. Remember a "sick" application within a VM will remain "sick" even if it is vMotioned or FT'd.
ReplyDelete