Might be a little tricky, marketing wise. Why would VMware want to submit themselves to this kind of testing which would have to involve VMotion and HA when Microsoft would almost certainly put so many caveats around support for a Guest that had been VMotion-ed to a different host?
How does my brain tell the story?
Q. Why isn’t VMware on the list?
A. Because MS won’t support VMotion-ed Guests
Q. Why?
A. Because MS don’t have that capability yet.
Q. Why?
A. Because the product is too immature and relies on never-very-confidence-inspiring cluster technology for multi-host resilience.
Q. Not very good for a load balancing option though, and certainly no cross site capability.
A. No, indeed.
Q. So, there’s no point VMware getting involved unless MS agree to support a Guest that has been VMotion-ed or HA’d to another guest and MS aren’t going to do that as it will only draw attention to the fact that MS lack a fundamental part of the virtualization story?
A. You might think that, I couldn’t possibly comment.
I think they should do it for their base product though, that is a step in the right direction. It is configuration based according to the website, so they don’t submit the HA/VMOTION configs. However in their shoes I would, let MSFT beat it up and publicly state what is wrong and then give the counterpoints to it.
Might be a little tricky, marketing wise. Why would VMware want to submit themselves to this kind of testing which would have to involve VMotion and HA when Microsoft would almost certainly put so many caveats around support for a Guest that had been VMotion-ed to a different host?
How does my brain tell the story?
Q. Why isn’t VMware on the list?
A. Because MS won’t support VMotion-ed Guests
Q. Why?
A. Because MS don’t have that capability yet.
Q. Why?
A. Because the product is too immature and relies on never-very-confidence-inspiring cluster technology for multi-host resilience.
Q. Not very good for a load balancing option though, and certainly no cross site capability.
A. No, indeed.
Q. So, there’s no point VMware getting involved unless MS agree to support a Guest that has been VMotion-ed or HA’d to another guest and MS aren’t going to do that as it will only draw attention to the fact that MS lack a fundamental part of the virtualization story?
A. You might think that, I couldn’t possibly comment.
I think they should do it for their base product though, that is a step in the right direction. It is configuration based according to the website, so they don’t submit the HA/VMOTION configs. However in their shoes I would, let MSFT beat it up and publicly state what is wrong and then give the counterpoints to it.
Someone must have kicked someone up the ass http://www.chriswolf.com/?p=183
Sweet.