Top 5 Planet V12N blog posts for week 52

Happy New Year to everyone in the VMware communities!  There were lots of great “2010 best of” blog posts this week from many of the top virtualization bloggers.  I suggest checking those out, lots of great information from the past 12 months in the virtualization space.  Here is the top 5 blog posts for the last week of 2010, enjoy!

Eric Sloof – Video – How to run Android in a VMware Virtual Machine – Android-x86 is a project to port Android open source to the x86 platform, formerly known as "patch hosting for android x86 support". In this video I’ll show you how to create a VMware vSphere virtual machine configured with the Android-x86 boot CD.

Christian Mohn – Installing and Configuring WANem Virtual Appliance – In a previous post, Using the WANem WAN Emulator Virtual Appliance, I’ve talked about how I’ve successfully used WANem to emulate different WAN scenarios. Since I work for a shipping company, the ability to emulate VSAT conditions are especially useful for testing and proof-of-concept scenarios.

Frank Denneman – Node Interleaving: Enable or Disable? – There seems to be a lot of confusion about this BIOS setting, I receive lots of questions on whether to enable or disable Node interleaving. I guess the term “enable” make people think it some sort of performance enhancement. Unfortunately the opposite is true and it is strongly recommended to keep the default setting and leave Node Interleaving disabled.

Arne Fokkema – Slow mouse performance on Windows 2008 R2 virtual machine – I wanted to migrate the lab to Windows Server 2008 R2 and found some problems with the video drivers provided with vSphere 4.0. After a quick search at http://kb.vmware.com I found the following KB article: KB1011709. This article mentioned the new WDDM driver.

William Lam – How to identify the origin of a vSphere login? – There was a pretty interesting post on the VMTN community forums recently in which a user was trying to identify a rogue vSphere login to their vCenter Server. Unfortunately, the actual user was not able to pin-point which system was logging in with his/her credentials. This potentially could have been some type of automated script that was configured and running and now has been forgotten. The vSphere admin tried to terminate the session which can be done using the vSphere Client or vSphere APIs, but the process would  be re-spawned automatically.


0 comments have been added so far

Leave a Reply

Your email address will not be published. Required fields are marked *