Windows 2008 R2 64 bit V2V conversion fails with “Unable to determine Guest Operating System” error

Windows 2008 R2 64 bit V2V conversion fails with the below error:










The V2V was across the VC with both the source and destination (vCenter and ESXi) being on 4.0 U2 and VMware convertor running on 4.0.1 Build -161434

Resolution: Just change the guest OS type (Right Click the VM> Edit Settings> Options tab)  to anything below 2008 R2 on the source machine and the V2V should go through fine

Thanks to:

P2V Consideration and Pre-Post Migration Checklist

Candidate selection:

Use capacity tools (Capacity Planner for ex.) to qualify a physical server as a P2V candidate, some points to note:

  • Small to medium sized workloads which use less SpecInt are the best fit for Virtualization, the SpecInt can eventually increase with the influx of new hardware which has increased CPU speeds. But most of the applications are not CPU intensive
  • Check the memory utilization at 95th Percentile, Memory allocation can be huge, more than 30+ GB, but keep a check on Active Memory, which is always the key
  • Average Disk Read/Write at the 95th percentile should not be way too high, benchmarks are set within the organization depending on their bandwidth and usage, same goes with network
  • It’s the Storage Protocol which dictates your disk space requirements, SAN can be an expensive deal, but worth looking at Thin provisioning (NFS) if there are large disk space requirements with low “Disk Usage”
  • Set benchmarks for OS drives, only if your applications and DB reside on Data volume
  • Application which does not have low latency requirements
  • Can be anything, Exchange, SQL, Oracle, SAP or any business critical application as long as it gets the required resources

Some showstoppers which might prevent candidate selection:

  • Applications with low latency
  • Very large workloads and large data sets
  • Non Standard hardware requirements, modems, fax cards, dongles etc

Pre Migration Checks:

  • Use Capacity tools to qualify a physical server as a P2V candidate, preferably Capacity Planner
  • Hostname
  • OS Type
  • Server Model
  • # of CPU sockets and Cores
  • Physical memory installed
  • Disk Capacity requirements, any LUNS from FC or SCSI or NFS mount points (CIFS)
  • CPU, Memory and Disk usage (Capacity tools can give an insight)
  • Decide on vCPU’s, Virtual Memory and Disk space to be allocated
  • It’s always good to have a local Administrator account on the physical box prior to P2V, else login atleast once using your domain credentials so that it’s stored in the local SAM
  • Record the IP configuration, possibly a screen dump of ipconfig
  • iLO information
  • Check for disk defragmentation
  • Check whether the applications are hardcoded to any IP/Mac addresses
  • RDP access
  • Information about all the applications and check which services are required to be stopped during migration
  • Possibly a runbook, which provides an update on the milestone, P2V started, in progress, successful or failed etc
  • On board resources from OS and Application teams, their contact information
  • Ensure there are no Hardware dongles, take note of compatibility, else the effort is wasted
  • Ensure the firewall rules are opened for the destination network, if applicable
  • Ensure your ESX/ESXi host’s management port group is connected to atleast 1GB port

Post Migration Checklist:

  • Ensure to power off the physical server before powering on the VM, else ensure the Network Adapter is disabled on the VM
  • Install VMware tools and ensure the Hardware Version is compliant with the ESX/ESXi version
  • Removed unwanted serial ports and uninstall all the Hardware Services, HP Insight Manager etc
  • Ensure there are no yellow exclamation marks in the Device Manager
  • Check and Adjust the Hardware Abstraction Layer, if required
  • Once the server is powered on, enable the NIC and assign the IP address
  • Start up all the disabled Application services if any, also check all the Automatic Services are started
  • Ensure the Physical Server is no longer pingable in the network, else you may run into Duplicate entries in AD
  • Get your OS teams (Check Windows Events log) and Application team for stress testing
  • Test Network and Disk latency
  • Most importantly “User Experience”

Please feel free to add if I have missed anything critical