Search This Blog

Sunday, March 29, 2020

Unable to Boot Nutanix AHV VM When running Nutanix CE 2019.11.22

During testing, we have encountered an issue whereby new VM created from Nutanix CE 2019.11.22 was unable to boot. From the console, we found out that it stuck at bios.

Here is how it look when console to VM:



After troubleshooting, we found that it is a bug when running on nested virtualization.

If you encountered the same issue, please follow this step which I found from Nutanix Forum.  Here is the copy/paste workaround.


a) Add pmu state in svm template by following the next steps:
  • Boot CE VM
  • Login with root / nutanix/4u
  • Navigate to /home/install/phx_iso/phoenix/svm_template/kvm

Note: If this does not appear, you need to start creating a dumb VM first.

  • Edit default.xml and add pmu state value. default.xml should look like the below screenshot:
«apic 
Off 
</features>
b)
  • Navigate to /var/cache/libvirt/qemu/capabilities/
  • There should be 1 xml file, in my case it's 3c76bc41d59c0c7314b1ae8e63f4f765d2cf16abaeea081b3ca1f5d8732f7bb1.xml

Note: Modified both xml if you got multiple xml. The second xml will appear after create a dummy VM

Edit the file and at the bottom you have different machine types defined
remove the line


Edit the line



To the following



Final config should look like similar to this:

pc-i440fx-rhe17.2.W 
hotplugCpus•'yes' 
nane.'rhe16.3.0' 
hOtp maxCpus•' 240 
nane.'rhe16.4.0' 
hOtp maxCpus•' 240 
nane.'rhe16.0.0' 
hOtp yes maxCpus•' 240 
pc-i440fx-rhe17.1.0' hotplugCpus—'yes' 
name—• pc-q35-rhe17.3.0' alias—'q35' 
<machi ne 
qemuCaps> 
name-•rhe16.5.0' 
rhe16.6.0' 
name—' rhe16.1.0' 
rhe16.2.0' 
hotplugCpus— ' yes 
hotplugCpus— ' yes ' 
hotpl ugCpus— ' yes ' 
hotplugCpus— ' yes ' 
hotplugCpus— yes 
maxCpus— ' 240 ' 
maxCpus— ' 240 ' 
maxCpus— ' 240 ' 
maxCpus— ' 240 '

Save the file and reboot the VM, after this you can login with install and proceed as normal.


Thanks to Matmassez who provide this workaround. Infomation took from here.
.