Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Virtualization Manager (VMAN) > Unable to Power ON VMAN 7.2 or 8.0 'The Guest Operating system 'CentOS4' is unsupported.'

Unable to Power ON VMAN 7.2 or 8.0 'The Guest Operating system 'CentOS4' is unsupported.'

Updated: October 31, 2017


This article helps you solve an issue where a newly deployed VMAN 7.2 or 8.0 does not power On when using VMware 6.5.


  • VMAN 8.0 and VMAN 7.2


This problem is caused by a compatibility issue with VMware 6.5. VMware sees VMAN 7.2 or 8.0 CentOS version as version 4/5 instead of 6.5/ or 6.8. See the screenshot below:

VMAN 72guestOS shows 4 or 5.JPG



To resolve the issue. You will need to update the VM compatibility of the VMAN virtual appliance.


  1. Right-click the VMAN VM guest.
  2. Select 'Compatibility'.
  3. Select 'Upgrade the VM compatibility'.
  4. From the drop-down menu, select 'ESX 6.5 or lower'.
  5. Try to power ON the VMAN VM.


If the VMAN VM still does not power ON, ou might need to resolve other issues on the VM guest. See below:

  1. Go to the 'Upgrade manager' of the VMAN VM.
  2. Click 'Remediate'.
  3. Power ON the VMAN VM.


If the VMAN VM console only shows a blank screen after powering ON, you might need to upgrade the VM HW (hardware) to version 13.

  1. Right-click on the VMAN VM.
  2. Select 'GuestOS'.
  3. Select 'Upgrade VM Hardware'.


Screenshots property of © 2017 Dell Technologies.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.



Last modified