Virtualization Short Take #41

It has been a busy week since I last posted, and the blogging/micro-blogging world has been quite busy. I’ve gathered quite the collection of links and posts over the last week or so; here are a few that caught my eye. Welcome to Virtualization Short Take #41!

  • About a month ago Rick Vanover posted a quick note about the use of Disk.SchedNumReqOutstanding as a potential performance tweak. As Rick mentions at the end of his article, it’s important to “test before and after with an intensive workload”; otherwise, you could find yourself actually hurting performance. Like so many performance tweaks, it really depends upon your specific environment and your specific workloads. Definitely refer to some of the linked resources at the end of Rick’s article (Duncan’s stuff is always helpful) for more details.
  • Speaking of Duncan, his post on vCPU limits is a great read and helps dispel a common misconception about vCPU limits. Remember the definition of a hertz folks—300 million cycles per second (300MHz) means 300 million cycles per second. It doesn’t mean 500 million cycles per second, or 700 million cycles per second.
  • Frank Denneman’s article on memory reservations and resource pools is also a really good read.
  • Kenneth van Ditmarsch has a good post on using datastore permissions to help ensure that VMs are properly placed based on SLAs. This is the kind of operational advice that I think many organizations still need.
  • Continuing our theme of resource allocation, here’s a good post on the effect of shares.
  • If you’re interested in an early look at some of the features targeted for inclusion in VMware View 4.5, have a look at Matthijs Haverink’s post on View 4.5 expected features. If Matthijs’ information is accurate, it looks like VMware has some good stuff planned.
  • I had a URL in my Yojimbo collection for part 5 of the series on Hyper-V dynamic memory, but it doesn’t seem to work anymore. I think the blog post was pulled. If anyone has a working link (yes, I’ve already checked Google), feel free to post it in the comments.
  • Jeremy Waldrop of Varrow brings to light a potential issue with the Cisco “Palo” adapter (now called the Virtual Interface Controller, or VIC) and PowerPath/VE. There is a workaround that fixes the problem. It’s important to note that the Cisco VIC isn’t fully vetted or validated for Vblock yet; that’s still in progress.
  • As a follow up from my mention of this issue in VST #40, I have more information on the Changed Block Tracking (CBT) issue. This post from VMware has more information on the specific conditions needed to produce the problem. I have to say, it looks like a pretty specific set of circumstances. I’m curious to know your thoughts: is this a corner case, or a really significant problem? Personally, I’m leaning toward the former.
  • EMC virtual appliances are really taking off; Chad unwrapped the FMA virtual appliance and fellow vSpecialist team member Nick Weaver unveiled v2 of the “Uber” Celerra VSA as well. I haven’t had the chance to play with the FMA virtual appliance yet, but I’m traveling tonight so maybe I’ll mess around with it on my laptop tonight from the hotel. (Yes, I’m a geek. What can I say?)
  • Following Citrix’s announcement of XenClient, their bare metal client hypervisor, and VMware’s response that perhaps the bare metal client hypervisor’s use cases are more limited than many might think, Citrix has responded by explaining XenClient to VMware. Bare metal hypervisors, unmanaged type 2 hypervisors, and policy-managed type 2 hypervisors all have value in the desktop virtualization space. Perhaps VMware should write a response to Citrix explaining the idea behind check-out/check-in of policy-controlled VMs? While I’m sure that I won’t be very popular with VMware for saying this, I do have to agree with Citrix here: discounting the value of bare metal client hypervisors on the basis of a single use case is a bit disingenuous, especially when you’ve been promoting client hypervisors for a while.
  • Looking to stay sharp and stay relevant in today’s changing IT landscape? Mike DiPetrillo offers some suggestions for skills that IT folks should embrace.
  • Kevin Goodman shared some information here on consolidation ratios with his Cisco UCS environment. He admits he is constrained by RAM, which is common in many data centers today. There are two answers to that problem today: full-width UCS blades with support for massive amounts of RAM; or expensive, high-capacity RAM modules to drive memory capacity higher. It also looks like the Nehalem EX chipset is going to help address that problem with support for more memory buses and more memory slots. Once again I find it interesting that virtualization is helping to drive hardware development.
  • Forbes Guthrie has published v5 of his connections and ports diagram for VMware ESX/ESXi. Definitely a useful resource!
  • This VMware KB article helps clarify the behavior of TPS with Intel Xeon 5500 (Nehalem)-based systems. This isn’t new information (I believe Duncan might have pointed it out first?), but it’s nice to see clarification of the behavior.
  • OK, I’m probably showing my ignorance here (I haven’t had the opportunity to spend as much time with View Manager as I would like), but who knew View Manager had a command-line tool?

I guess that will wrap things up for this issue of Virtualization Short Takes. I hope you’ve found something useful!

Tags: , , , , , , ,

3 comments

  1. Steffen’s avatar

    Hi Scott,

    Part 5 of the Hyper-V Dynamic Memory series can be found here (currently I can access the post with this link):
    http://blogs.technet.com/b/virtualization/archive/2010/05/20/dynamic-memory-coming-to-hyper-v-part-5.aspx

    BR
    Steffen

  2. Duncan’s avatar

    Correct about the TPS thing… But actually the knowledge base article is not 100% correct. Asked them to rephrase it as it currently states that TPS improves performance while it is Large Pages which improves it.

  3. Andrew Miller’s avatar

    The View Manager commandline tool just indirectly reaffirms my resolution to (some day) spend quality time with Powershell…

Comments are now closed.