Who cares about Guest OS Version in vCenter

For years I’ve been setting the Guest OS type in VMware vSphere and Workstation and for years it’s bugged me.  What does it really do?  Does it really matter?  Sometimes just for fun I like to set the version to Windows but install Linux.  Each time I’ve always looked out the window towards the sky to make sure it’s not falling.

In the past if I needed to change the Guest OS type (i.e someone was being silly and set a Linux VM to a Windows Guest OS type) I would just power down the VM and change the setting.  Recently I noticed in my vSphere 5.1 environment I couldn’t change the Guest OS anymore.   In vCenter 5.1 there are now two options.  Guest OS and Guest OS Version.  A little research later and as of vSphere 5.1 you cannot change the Guest Operation System settings once the VM has been created.  They will appear greyed out.

guestos01

First, the most obvious thing it does is give us a whole bunch of default recommended values for the specified OS Version when creating a VM.  It can also restrict what devices are available to us to use.

For example if we set the OS Version to MS-DOS we get 16 MB has the default recommended memory and a 2 GB Hard Disk using an IDE controller.

guestos02

If we set it to Windows 2008 R2 (64-bit) we get a default value of 4096 MB for memory and a 40 GB Hard Disk using an LSI Logic SAS Controller.

guestos03

Second, it defines maximum values we can use.   This can be a little misleading because your true maximum values are always dictated but your Sphere version and edition.  I won’t get into this too much as this blog revolves around Guest OS type.  If we set the OS type to Windows 2000 our max vCPU is 8.  Whereas if I set the OS to Windows Server 2012 (64-bit) our max vCPU is 64 under Enterprise Plus Edition.  If I was running Standard Edition we would be limited to 8 vCPUs for both OS types.  Confused yet.

guestos04

Third, and now a more important consequence of selecting the right OS Version is VMware Tools.  If you push out VMware Tools via vCenter it will use the Guest OS Version to determine what Tools version it will attempt to deploy.  Mixing Linux and Windows OS Versions will cause VMware Tools deployment to fail.

Forth, we have a few lesser consequences.  Some VM options are only enabled and available to certain OS Versions.  Fault Tolerance is not supported on certain types of OS and selecting the wrong OS version in vCenter could disable this setting.  The same can be said for HotAdd/Hot-Plug.  The wrong OS version can prevent this feature being used.

In conclusion, setting the OS Type / Version to match the underlining OS is recommended.

  • It provides recommended devices and values for your OS.
  • It limits your maximum values to what the underlining OS will support.
  • Helps in deploying the correct VMware Tools version
  • It allows the use of advanced (yet less common) features like Fault Tolerance and HotAdd/Hot-Plug support.
  • Once it’s set it can’t be change (vSphere 5.1)

References

Ensuring the guest operating system type is set correctly (1005870)

Cannot change the guest operating system selection of a virtual machine in ESXi 5.1 (2020801)

Compare vSphere Editions

Processors and guest operating systems that support VMware Fault Tolerance (1008027)

  1. How can I get guest os release version like Ubantu Linux 11.1.3 ?

Leave a Comment


NOTE - You can use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>