You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/04/28 16:59:04 UTC
[jira] [Commented] (VCL-974) VMware VMs may fail to power on if
host does not support nested VMs
[ https://issues.apache.org/jira/browse/VCL-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989155#comment-15989155 ]
ASF subversion and git services commented on VCL-974:
-----------------------------------------------------
Commit 1793117 from arkurth@apache.org in branch 'vcl/trunk'
[ https://svn.apache.org/r1793117 ]
VCL-974
Added a is_nested_virtualization_supported subroutine to VIM_SSH.pm and vSphere_SDK.pm.
Added call to is_nested_virtualization_supported to VMware.pm::prepare_vmx. The .vmx parameters required for nested VMs now only get added if it can be verified that the host supports it.
> 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
>
> Attachments: ept.png
>
>
> {{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:
> !ept.png!
> 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.15#6346)