From 2f7e0d3a1f0bbf0ffc1aa703f8f0e0275e055800 Mon Sep 17 00:00:00 2001
From: Bjorn Brala <bjorn@swis.nl>
Date: Thu, 23 Mar 2017 07:54:41 +0100
Subject: [PATCH] Virtualization extensions wern't enabled for vmcx file
 format, so it didn't work for Windows 10 and up. Fixes #8402

---
 plugins/providers/hyperv/scripts/import_vm_vmcx.ps1 | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/plugins/providers/hyperv/scripts/import_vm_vmcx.ps1 b/plugins/providers/hyperv/scripts/import_vm_vmcx.ps1
index e4e13e913..7f9db5c43 100644
--- a/plugins/providers/hyperv/scripts/import_vm_vmcx.ps1
+++ b/plugins/providers/hyperv/scripts/import_vm_vmcx.ps1
@@ -16,6 +16,7 @@
     [string]$auto_start_action=$null,
     [string]$auto_stop_action=$null,
     [string]$differencing_disk=$null
+    [string]$enable_virtualization_extensions=$False
 )
 
 # Include the following modules
@@ -86,6 +87,11 @@ if (!$switchname) {
     $switchname = (Get-VMNetworkAdapter -VM $vmConfig.VM).SwitchName
 }
 
+# Enable nested virtualization if configured
+if ($enable_virtualization_extensions) {
+    Set-VMProcessor -VM $vmConfig.VM -ExposeVirtualizationExtensions $true
+}
+
 $vmNetworkAdapter = Get-VMNetworkAdapter -VM $vmConfig.VM
 Connect-VMNetworkAdapter -VMNetworkAdapter $vmNetworkAdapter -SwitchName $switchname
 Set-VM -VM $vmConfig.VM -NewVMName $vm_name