Comments on: Sure, VMWare made a (critical) mistake, but what’s all the fuzz about ? http://virtualfuture.info/2008/08/sure-vmware-made-a-critical-mistake-but-whats-all-the-fuzz-about/ Mon, 16 Aug 2010 16:51:58 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Rob Mokkink http://virtualfuture.info/2008/08/sure-vmware-made-a-critical-mistake-but-whats-all-the-fuzz-about/comment-page-1/#comment-249 Rob Mokkink Sun, 17 Aug 2008 15:54:38 +0000 http://virtualfuture.info/?p=248#comment-249 I installed U2 in the lab. Just disable HA and set the time. And vmotion will still word ;-) I installed U2 in the lab. Just disable HA and set the time. And vmotion will still word ;-)

]]> By: Sven Huisman http://virtualfuture.info/2008/08/sure-vmware-made-a-critical-mistake-but-whats-all-the-fuzz-about/comment-page-1/#comment-246 Sven Huisman Fri, 15 Aug 2008 09:46:59 +0000 http://virtualfuture.info/?p=248#comment-246 Good points Rob. As for VMotion VM's of the host: that is not possible with the VMware bug either (unless you change the time of the ESX host). The good news is: VMware has a fix for this as well: "We are aware that you may be encountering the following challenges installing the express patches needed to correct the problem. • Internal change control procedures • No available server to VMotion running VM’s onto • Unable to schedule a maintenance window If you have one of the challenges listed above, please contact your support provider and indicate you need assistance with the U2 Alternative Install Process (U2 AIP). An alternative installation procedure is being finalized and will be provided on an as-needed basis." Good points Rob.
As for VMotion VM’s of the host: that is not possible with the VMware bug either (unless you change the time of the ESX host).
The good news is: VMware has a fix for this as well:

“We are aware that you may be encountering the following challenges installing the express patches needed to correct the problem.
• Internal change control procedures
• No available server to VMotion running VM’s onto
• Unable to schedule a maintenance window
If you have one of the challenges listed above, please contact your support provider and indicate you need assistance with the U2 Alternative Install Process (U2 AIP). An alternative installation procedure is being finalized and will be provided on an as-needed basis.”

]]> By: Rob Mokkink http://virtualfuture.info/2008/08/sure-vmware-made-a-critical-mistake-but-whats-all-the-fuzz-about/comment-page-1/#comment-245 Rob Mokkink Thu, 14 Aug 2008 07:51:31 +0000 http://virtualfuture.info/?p=248#comment-245 Every admin who installs a complety new release with so many new features straight into production, should be fired on the spot. As far for the competition, Hyper-V doesn't even come close to the performance and features of VMware Vi3. And i am hoping to see the first patchround for Hyper-V, because you can't VMotion vm's and you are stuck with downtime. Every admin who installs a complety new release with so many new features straight into production, should be fired on the spot.

As far for the competition, Hyper-V doesn’t even come close to the performance and features of VMware Vi3. And i am hoping to see the first patchround for Hyper-V, because you can’t VMotion vm’s and you are stuck with downtime.

]]> By: Matthijs Haverink http://virtualfuture.info/2008/08/sure-vmware-made-a-critical-mistake-but-whats-all-the-fuzz-about/comment-page-1/#comment-241 Matthijs Haverink Wed, 13 Aug 2008 21:39:25 +0000 http://virtualfuture.info/?p=248#comment-241 Hey Jamie thanx for your reply! As you say: it should never happen that a patch goes into prodcution immediately so everybody who does (especially with this one, as it's 90% new features and 10% bugfixes) can mainly blame themselves; it's that black-and-white ... I do agree to what you're saying about VMWare now maybe loosing a part of their advantage on their time-to-market time since this will now rule the workfloor @VMWare : "this will never happen again". And about the whole Microsoft and Citrix Xen story: I don't see this shake up having that much effect. Do you really, after this one incident, start thinking: maybe it's better to trust Microsoft for bringing out reliable patches? And sure, large chance that Microsoft will "rule the world" concerning the hypervisor because everybody swallows whatever half-complete product Microsoft ships. But I don't think that'll be relevent anymore in 10 years. In 10 years hypervisors are comodity/free like your BIOS and it doesn't matter which one you've got. What matters who has the best software to manage all those different hypervisors. But hey, that's a whole other story I'd love to go into sometime, but not now :). Hey Jamie thanx for your reply!

As you say: it should never happen that a patch goes into prodcution immediately so everybody who does (especially with this one, as it’s 90% new features and 10% bugfixes) can mainly blame themselves; it’s that black-and-white …

I do agree to what you’re saying about VMWare now maybe loosing a part of their advantage on their time-to-market time since this will now rule the workfloor @VMWare : “this will never happen again”.

And about the whole Microsoft and Citrix Xen story: I don’t see this shake up having that much effect. Do you really, after this one incident, start thinking: maybe it’s better to trust Microsoft for bringing out reliable patches?

And sure, large chance that Microsoft will “rule the world” concerning the hypervisor because everybody swallows whatever half-complete product Microsoft ships. But I don’t think that’ll be relevent anymore in 10 years. In 10 years hypervisors are comodity/free like your BIOS and it doesn’t matter which one you’ve got. What matters who has the best software to manage all those different hypervisors. But hey, that’s a whole other story I’d love to go into sometime, but not now :) .

]]> By: Rich http://virtualfuture.info/2008/08/sure-vmware-made-a-critical-mistake-but-whats-all-the-fuzz-about/comment-page-1/#comment-238 Rich Wed, 13 Aug 2008 15:37:04 +0000 http://virtualfuture.info/?p=248#comment-238 Matthijs, Great post! My thoughts related to patching and change control along with other opinions about how this bug happened at http://vmetc.com/2008/08/13/my-thoughts-on-the-reactions-to-the-esx-35-update-2-bug/ Matthijs,

Great post! My thoughts related to patching and change control along with other opinions about how this bug happened at http://vmetc.com/2008/08/13/my-thoughts-on-the-reactions-to-the-esx-35-update-2-bug/

]]> By: jamie http://virtualfuture.info/2008/08/sure-vmware-made-a-critical-mistake-but-whats-all-the-fuzz-about/comment-page-1/#comment-237 jamie Wed, 13 Aug 2008 15:18:54 +0000 http://virtualfuture.info/?p=248#comment-237 The "Fuzz" is that we as VI admins are now forced to NEVER be "bleeding-edge" again. In the past, ESX patches and/or upgrades have been basically rock-solid. Yes, it's true, no patch should EVER go immediately into production, but like it or not, it happens, and especially more so now that ESX 3.5 has "matured" more over time. This bug has brought on a lot of changes, not only at vmware, but in every VI on the planet who knows of this incident. It's almost akin to someone backdooring the code, in which case it would have been worse publicity-wise, but you get my point. it should never have happened. it's the sloppiest software release story of all time on the planet as of yesterday.. Overall Trust in VMWare's hypervisor and release practices have been compromised, and frankly, this has shaken up the entire Virtualization community - Perhaps it will make VMWare think twice about including "experimental" code in production GA releases, but I doubt it since that was not the issue either... In any event, it only helps MS/Xen and the rest, as the timing could not have been worse given the current playing field. Vmware has lost another bleeding-edge shop, and I'm sure we are not alone. Now, bugs will be uncovered slower, MS will advance faster, and vmware will likely be in the dust in less than 10 years due to Hyper-V. ... mark those words. MS can beat anyone - it's been proven over and over , ie netscape, and the countless other competition the illegal monopolist has trampled on and squashed over the years. Jamie The “Fuzz” is that we as VI admins are now forced to NEVER be “bleeding-edge” again. In the past, ESX patches and/or upgrades have been basically rock-solid. Yes, it’s true, no patch should EVER go immediately into production, but like it or not, it happens, and especially more so now that ESX 3.5 has “matured” more over time. This bug has brought on a lot of changes, not only at vmware, but in every VI on the planet who knows of this incident. It’s almost akin to someone backdooring the code, in which case it would have been worse publicity-wise, but you get my point. it should never have happened. it’s the sloppiest software release story of all time on the planet as of yesterday..

Overall Trust in VMWare’s hypervisor and release practices have been compromised, and frankly, this has shaken up the entire Virtualization community – Perhaps it will make VMWare think twice about including “experimental” code in production GA releases, but I doubt it since that was not the issue either…

In any event, it only helps MS/Xen and the rest, as the timing could not have been worse given the current playing field.

Vmware has lost another bleeding-edge shop, and I’m sure we are not alone. Now, bugs will be uncovered slower, MS will advance faster, and vmware will likely be in the dust in less than 10 years due to Hyper-V. … mark those words. MS can beat anyone – it’s been proven over and over , ie netscape, and the countless other competition the illegal monopolist has trampled on and squashed over the years.

Jamie

]]>