tag:help.appveyor.com,2012-11-13:/discussions/problems/22269-packer-build-fails-on-vboxmanage-error-vboxmanage-error-vt-x-is-not-available-verr_vmx_no_vmxAppVeyor: Discussion 2019-03-22T00:48:09Ztag:help.appveyor.com,2012-11-13:Comment/470791942019-03-16T06:15:23Z2019-03-16T06:15:24ZPacker build fails on VBoxManage error: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)<div><p>Update: Windows box returns the SAME error!</p>
<pre>
<code>
virtualbox-iso: Transferred: http://releases.ubuntu.com/16.04/ubuntu-16.04.6-server-amd64.iso
==> virtualbox-iso: Starting HTTP server on port 8662
==> virtualbox-iso: Creating virtual machine...
==> virtualbox-iso: Creating hard drive...
==> virtualbox-iso: Creating forwarded port mapping for communicator (SSH, WinRM, etc) (host port 2720)
==> virtualbox-iso: Executing custom VBoxManage commands...
virtualbox-iso: Executing: modifyvm packer-ubuntu-16.04.6-amd64_mysql --memory 4096
virtualbox-iso: Executing: modifyvm packer-ubuntu-16.04.6-amd64_mysql --cpus 4
==> virtualbox-iso: Starting the virtual machine...
virtualbox-iso: The VM will be run headless, without a GUI. If you want to
virtualbox-iso: view the screen of the VM, connect via VRDP without a password to
virtualbox-iso: rdp://127.0.0.1:5953
==> virtualbox-iso: Error starting VM: VBoxManage error: VBoxManage.exe: error: The native API dll was not found (C:\windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
==> virtualbox-iso: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
==> virtualbox-iso: VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
==> virtualbox-iso: Deregistering and deleting VM...
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Error starting VM: VBoxManage error: VBoxManage.exe: error: The native API dll was not found (C:\windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole</code>
</pre></div>henryfbptag:help.appveyor.com,2012-11-13:Comment/470791942019-03-22T00:25:19Z2019-03-22T00:25:19ZPacker build fails on VBoxManage error: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)<div><p>Hi Henry.</p>
<p>Sorry for delay with reply. Right now we are testing new build worker image called <code>Windows Server 2019</code> which runs on Azure <code>Standard_D2s_v3</code> VMs with nested virtualization enabled.</p>
<p>This image is not publicly available yet, we enable it for people as needed. It has been enabled for you. Please try and let us know if this works.</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/470791942019-03-22T00:38:15Z2019-03-22T00:38:15ZPacker build fails on VBoxManage error: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)<div><p>Hi Ilya,</p>
<p>Thanks for the reply.</p>
<p>As I unfortunately have moved to using self-hosted Jenkins with Hyper-V on Windows 10, I probably won't be using Appveyor.</p>
<p>However, you are free to use my repo's code to test your virtualization.</p></div>henryfbptag:help.appveyor.com,2012-11-13:Comment/470791942019-03-22T00:44:29Z2019-03-22T00:44:29ZPacker build fails on VBoxManage error: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)<div><p>OK, sorry. Virtualization is tested: <a href="https://ci.appveyor.com/project/appveyor-tests/win2k19-azure">https://ci.appveyor.com/project/appveyor-tests/win2k19-azure</a>.</p>
<p>It would be cool if you delete AppVeyor projects you do not use so your commits do not trigger unneeded builds.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/470791942019-03-22T00:46:00Z2019-03-22T00:46:00ZPacker build fails on VBoxManage error: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)<div><p>Will delete my projects. Thanks again.</p></div>henryfbp