2012
03.16

I’ve just read Dear Hyper-V fans, I’ll take that apology now by apparent VMware apologist Ken Hess on ZDNet.  I guess this fanboy who poses as a journalist is upset over the recent hypervisor vote on ZDNet where Hyper-V beat vSphere.

In his article, Hess says:

If you used VMware, you wouldn’t have to reboot your vulnerable systems after patching for the RDP Worm today. Sure, you’ll still have to patch all of your Windows VMs that ride on top of your VMware hosts but at least you don’t have to patch and reboot the VMware host system.

Huh!  Strange that.  Is Hess saying that VMware never releases patches for vSphere?  I think if you follow that link then you might find a different answer to that.  Or maybe the almighty VMware never have to release a security fix for vSphere?  Woops, wrong again Kenny-boy.  Maybe vSphere security fixes don’t require a host reboot?

Host Reboot Required

Yes

Oh it appears they do. 

OK, we don’t have downtime for VMs then?

Virtual Machine Migration or Shutdown Required Yes

Damn.  Ken must have seen something.  I know; patching vSphere must be easy just like it is for Hyper-V (where Automatic Updates, WSUS, System Center Configuration Manager, System Center Virtual Machine Manager 2012, or Windows 8 Cluster Aware Update are all options):

ESXi hosts can be updated by manually downloading the patch ZIP file from the VMware download page and installing the VIB by using the esxcli software vib command. Additionally, the system can be updated using the image profile and the esxcli software profile command

Dagnammit, that sounds like a lot of work to me.  At least the patch is probably small.

297.7 MB

OK, so is Ken Hess just a fill of it, so-called-journalist, FUD fool, or is he just an uneducated moron?  Hey real journalists, I respect your ability to report news fairly, but guys like this do your trade no good.  But I guess maybe Hess isn’t a journalist. 

Maybe he’s a consultant or admin – I’d sure hate to be his client or employer because it appears that Kenny-boy has never checked the vSphere site for patches.  The fact is that any complex piece of code requires bug fixes and security patches.  To deny that … well … to deny that makes you moron.

Me wonders if Windows Server 8 Hyper-V has ‘em scared? Winking smile

Technorati Tags: ,

13 comments so far

Add Your Comment
  1. Thank you Aidan.. Just what I needed today… Gave me a great laugh!

    • All part of the service, Chris :)

      • Its not like this was hard to patch.. I put into our Patch Management system, forced it to workstations, and scheduled the servers in a maintenance window.

        I remember doing a security fix on VMware ESX in 3.5… Holy cow was that a pain on 5 hosts!

  2. Whahaha… Good and solid response! :-D

    • Nothing like the hard cold facts to back up an argument :)

  3. Hey Aiden,

    I’ve just been patching our ESXi 5.0 hosts this week, with the whopping 564mb vSphere 5.0 Update 1 (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2010823) (for a 144mb hypervisor?) today, and my god, if I didn’t use vCenter Update Manager in our lab, it would be flippin hard work.

    Here’s what I went through prior to VUM, just to see what it was like…

    1) Enable SSH on ESXi using vSphere Client connected to ESXi 5.0 host #1.
    2) Download a product called WinSCP to access the datastores of the ESXi hosts, to drop the update ZIPs on the hosts
    3) Spin up Putty, and run the command esxcli software vib install -d then a long path (like a GUID) and then the zip file
    4) reboot
    5) rinse and repeat for all hosts

    I was only doing it on 3 hosts but it was a killer, but VUM makes it a doddle, but VUM isn’t free, yet nor is VMM today, or in 2012, however the inbox WSUS, or hell, even just going to Windows Update manually on each host makes things much more simple, especialy for a Windows guy like me ;-)

  4. Aidan, be sure to tell us how you really feel!

    Good article!

    JamesNT

  5. LOL. Funny. Actually, I won the debate, so you might want to correct that. Yes, VMware has patches too. My point was that I had just pointed this out during the debate. It was just a timely thing.

    • Seriously Ken, you need to go see a doctor to see if you have a case of dementia; you LOST that debate 54-46. No your point was to try make it look like only Hyper-V had tp be patched. You lose … again.

      Seriously, are ZDNet really paying you? The standards in media really are dropping.

    • Dear Ken Hess,
      After your post, your comment should be turned around… you should be appologizing to all of us Hyper-V fans.

      Your post has only that you clearly ddon’t have a clue howto patch an hypervisor environment, doesn’t matter if it’s VMWare or Microsoft based.
      Both require reboots, the trick is to schedule such opperations in maintenance windows and migrate the active VM’s to other hosts before you do some maintenance on a host… and do so without causing disruption of the connections to those VM’s.
      And for automating the patching of systems, hosts or VM’s, both vendors have their own automated solutions. Microsoft offers systems such as WSUS and VMWare offers vCenter. Key in this all is to automate the entire process… migrate resources to other cluster nodes just before rolling out updates, and preferably without manual labor of the administrator.
      So the arguments in your article are just a bunch of crap… Please come back down to the real world and build your own VMWare and Hyper-V environment and manage it. It should be a true eye opening experience for you.

      And while you’re add appoligizing. I think you should also appologize to VMWare and their fans, since you just made a fool out of them by representing them in such a way that just about the entire world, also some VMWare fans, are just laughing at/about you.

      Regards,
      Jeff

  6. Just to add, patching the free ESXi is such a PITA I’d bet most go unpatched.

    At least Microsoft don’t cripple the feature set of the free Hyper-V server. Sure, it does not have the GUI – but so what, all of the MS remote management solutions will work.

    James

  7. Thank you, Mr. Finn, for addressing my number one pet peeve that comes out of the VMWare Myth Generator. May your post be shared and shared often.

  8. Well said Aidan and the fact that Ken is visiting your site, good for him as well. Times are changing and times are hard for business and saving money as a TCO is the real battle and then keeping IT Staff employed a close second as far as IT issues of today. I used to be a decision maker in a past life, and often the deciding factor was price. IT Professionals need to learn to adapt and stop being biased on what they will not do for work or what they will use when doing IT work.

    Am I saying Microsoft is cheaper? Today, I think they are and they look to be cheaper over the long run and into the future. In the end, IT staffing should find ways to create savings for the company they are working for.

    Thank you for being a voice for the Hyper-V community. In the world of technology, some things are better than others, some things people just think are better than others. Then you have people that are just confused and buy what is cool and have a need to compare what they have with what others have, with hopes of making themselves feel good.

    //Chris

Get Adobe Flash player