Virtualization Short Take #17

News, views, events, and commentary from around the virtualization world that struck my fancy over the past few weeks—that’s what you’ll find in Virtualization Short Take #17!

  • I stumbled across this series of podcasts on building a scalable virtual desktop deployment. It’s a four part series: Part 1, Part 2, Part 3, and Part 4. I’m still struggling with finding a way to incorporate podcasts into my day; I’m drinking from the firehose as it is. For those that do listen to podcasts, perhaps this series will prove helpful.
  • Apparently, the argument about VMware violating the GPL (I wrote about that here quite some time ago) has surfaced again. Gordon Haff promptly and rather cleanly squashes that concern. Well said, Gordon.
  • Tim Jacobs posts a great article on matching LUNs between ESX and the VCB proxy server. This is just one of several good posts by Tim; here’s another one on VSS snapshots with ESX 3.5 Update 2. This is a web site to watch.
  • Ben Armstrong reminds us that Hyper-V requires NTFS in order to work. Isn’t it time for FAT32 to go away?
  • Will VMware ESX/ESXi 3.5 Update 2 be the first hypervisor validated under the SVVP? Gabe posts some information on his site to that effect, indicating that VMware expects to announce validation before VMworld. That would be a strong competitive advantage, indeed.
  • VMware is also hitting hard with performance advantages and ties to hardware acceleration, as indicated by John Troyer’s post regarding VMDq, VMware Netqueue, and VMDirectPath (seen via VMblog.com). The coolest part about this stuff is that a lot of it is already available. We’re not waiting for a future version of VMware Infrastructure to take advantage of this stuff; instead, we’re waiting for the hardware. Now how’s that for a change!
  • Rich over at VM /ETC gives us a great breakdown on licensing Windows VMs for a non-Microsoft virtualization solution. He comes to the same conclusion some of my customers have already made: licensing Windows Server 2008 Datacenter Edition may make the most sense. Good job, Rich!
  • Duncan alerts us to a potential problem with HP Insight Manager agents on VMware ESX 3.5 Update 2. I share Duncan’s view; I try to avoid agents in the Service Console wherever possible. That’s why I was glad to see VMware add the Health Status functionality in Update 2, as this gives you some hardware monitoring functionality without any agents in the Service Console. I don’t know that I’ve quite arrived at the same place as Duncan; I like the Service Console. I guess that’s because I’m accustomed to it. In any case, if you’re running HP hardware with the IM agents, be on the lookout for this issue. Thanks for bringing this to everyone’s attention, Duncan!
  • Interested in keeping up with all the various goings-on at VMworld? David Davis turns us on to a few additional sources of information (as if we needed anything more!).

Also, I’m excited to announce that my blog has been selected for inclusion in a new blog aggregation site, VirtualizationFeed.com. Patrick over at Microsoft announced the new site yesterday via the Virtualization Team Blog with this post. I’m thrilled to be included and I hope to be able to continue to deliver quality information. Thanks for reading!

Tags: , , , , , , , , ,

Scott,

Thanks for link, and congrats on being aggregated in on VirtualizationFeed.com.

I always enjoy reading your blog, but think I must point out that the warning about HP agents is a bit misleading.

As far as I can tell from my own research and postings on the web the problem is not with the HP agents beeing installed, but rather with the interaction between HP SIM and “cimserver” - which is a part of Pegasus, and not a part of the HP agents.

If HP SIM is configured with usernames and passwords for WBEM in global settings it tries to use these credentials to log on to CIM, and apparently this causes the CIM process to hang if the credentials are wrong.

The workaround, from http://communities.vmware.com/message/1036631:

“In SIM if you go to Options, Protocol Settings, System Protocol Settings, select your vm servers, On the next page in the WBEM settings select the Use Values Specified below, and add your username and password.”

Geir,

Thanks for the clarification! I’ll add an update to the post itself (since many readers don’t read the comments) with that information.