Not only are they reversing the virtual RAM vTax that “would have no effect” on customers and help them to “right-size their clouds” but now their marketing mouthpiece is saying that concurrent live migrations are bad. LMFAO
I love that he tries to make a point that the default maximum live migrations is 2, and that it must be sooo hard to change that number in the GUI.
This is a last grasp at trying to score points that only the most blinkered fanboy could agree with makes
Novell Netscape VMware look really bad. I love it
And don’t forget, VMware storage is insecure too.
Hey Eric, while you’re blogging, can you let the VMware customers who paid memory vTax over the last year to right-size their clouds know how they can get a refund to return to their “VM sprawl” once again?
I just realised that by reading that post, VMware seem very unsure of using vMotion to migrate VMs with production workloads. Oooh, is vMotion that fragile? I guess it might be seeing as it is allegedly based on Legato Replistor code and we all know how reliable Replistor was … oh .. right … it wasn’t that reliable at all. Don’t worry vFanboys, Live Migration always leaves your VM running, even if something bad happens. No bridges are burned; If the VM can’t migrate, it stays where it originally was, completely unharmed and uninterrupted.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.