Andy Kurth created VCL-974:
------------------------------
Summary: VMware VMs may fail to power on if host does not support
nested VMs
Key: VCL-974
URL: https://issues.apache.org/jira/browse/VCL-974
Project: VCL
Issue Type: Bug
Components: vcld (backend)
Affects Versions: 2.4.2
Reporter: Andy Kurth
Assignee: Andy Kurth
Fix For: 2.5
{{VMware.pm}} is adding the following to the .vmx file to allow a VM to run
nested VMs:
{noformat}
"monitor.virtual_mmu" => "hardware",
"monitor.virtual_exec" => "hardware",
"vhv.enable" => "TRUE",
{noformat}
On some hosts, these settings cause the VM to fail to power on. In the VM's
working directory, {{vmware.log}} contains the following:
{noformat}
2016-07-21T17:04:18.801Z| vmx| I120: Msg_Question:
2016-07-21T17:04:18.801Z| vmx| I120: [msg.cpuid.noVHVQuestion] Virtualized
Intel VT-x/EPT is incompatible with this virtual machine configuration.
2016-07-21T17:04:18.801Z| vmx| I120+ Continue without virtualized Intel
VT-x/EPT?
2016-07-21T17:04:18.801Z| vmx| I120: ----------------------------------------
2016-07-21T17:04:18.801Z| vmx| I120: MsgIsAnswered: Using builtin default '_No'
as the answer for 'msg.cpuid.noVHVQuestion'
{noformat}
There is no way I have found to override the _msg.cpuid.noVHVQuestion_
parameter in the .vmx file. If you comment out _msg.autoAnswer_ in the .vmx
file or set it to false, the following appears in the vSphere Client:
It may be possible to detect whether or not the host will experience this
problem by querying the _HV Replay Capable_ parameter from _esxcfg-info_:
{noformat}
[root@bn17-21:~] esxcfg-info | grep '\-HV Replay Capable'
|----HV Replay Capable.....................................false
{noformat}
On hosts which don't experience this problem, the value is true.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
