vcpu-0:NOT_IMPLEMENTED vmcore/vmm/hv/vt/hv-vt.c:3281 on 15 Pro

[JeffJoe]

We use VMware Workstation in nested virtualization mode:

hypervisor.cpuid.v0 = "FALSE"

mce.enable = "TRUE"

vhu.enable = "TRUE"

With VMWare Workstation Pro 12 and 14 we were able to run any kind of Hypervisor. For instance simple visor:

GitHub - ionescu007/SimpleVisor: SimpleVisor is a simple, portable, Intel VT-x hypervisor with two s...

Unfortunately, SimpleVisor no longer works on version 15. As soon as the driver is launched VMware crashes:

To us it looks like VMWare simple forgot to implement some parts for nested virtualization. We already provided all logs to VMware but so far we did not get any reply.

[JeffJoe]

We are also able to produce this bug by installing Kaspersky Antivirus and call the Safe Money function:

[wjwj]

Hi JeffJoe,

Thanks for reporting the issue. Could you please attach the log files in this thread?

[JeffJoe]

Sure attached. Please note that bug is not just on VMWare Workstationi it also exists in latest ESXi 6.5:

2018-10-12T10:48:13.824Z| vcpu-1| W115: A core file is available in "/vmfs/volumes/5bc06fc1-e5aa13a4-3a81-d067e5441edc/Windows 10/vmx-zdump.001"

2018-10-12T10:48:13.824Z| vcpu-1| I125: Msg_Post: Error

2018-10-12T10:48:13.824Z| vcpu-1| I125: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vcpu-1)

2018-10-12T10:48:13.824Z| vcpu-1| I125+ vcpu-0:NOT_IMPLEMENTED vmcore/vmm/hv/vt/hv-vt.c:3231

2018-10-12T10:48:13.824Z| vcpu-1| I125: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/5bc06fc1-e5aa13a4-3a81-d067e5441edc/Windows 10/vmware.log". 

2018-10-12T10:48:13.824Z| vcpu-1| I125: [msg.panic.requestSupport.withoutLog] You can request support. 

2018-10-12T10:48:13.824Z| vcpu-1| I125: [msg.panic.requestSupport.vmSupport.vmx86]

2018-10-12T10:48:13.824Z| vcpu-1| I125+ To collect data to submit to VMware technical support, run "vm-support".

2018-10-12T10:48:13.824Z| vcpu-1| I125: [msg.panic.response] We will respond on the basis of your support entitlement.

2018-10-12T10:48:13.824Z| vcpu-1| I125: ----------------------------------------

Attached you find a log from VMware Workstation.

[wjwj]

Thank you, JeffJoe, for the cooperation. We have an internal bug to track the issue. Thanks.

[wjwj]

Hi JeffJoe,

Would you please do us a favor, can you share your repro environment with us?

Would you upload the VM with SimpleVisor setup which can reproduce the issue? Please let me know your folder name. Thank you very much for your cooperation!

1. Log in ftpsite.vmware.com through https://ftpsite.vmware.com
2. Username: inbound        password: inbound
3. After logging in above site, then change directory to “workstation” and upload the VM accordingly.

[JeffJoe]

Hi Wjwj,

you find the Simple Visor binary here:

File-Upload.net - shv.sys

To reproduce the issue / bug:

* Install Windows 10 x64 on VMware Workstation Pro 15 or latest ESXi

* Enable nested virtualization:

hypervisor.cpuid.v0 = "FALSE"
mce.enable = "TRUE"
vhu.enable = "TRUE"

* Enable test signing. Execute from an evaluated cmd prompt and reboot:

bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set nointegritychecks ON

* Store shv.sys to C:\

* Download Kernel-Mode Driver Loader v1.2 from https://www.novirusthanks.org/products/kernel-mode-driver-loader/

* In the Driver File input field, type: C:\shv.sys then Load

* VMware crashes

To reproduce the issue / bug with Kaspersky:

* Install Windows 7 or Windows 10 x64 on VMware Workstation Pro 15 or latest ESXi

* Enable nested virtualization:

hypervisor.cpuid.v0 = "FALSE"
mce.enable = "TRUE"
vhu.enable = "TRUE"

* Install latest Kasperksy Internet Security trial

* Open the Safe Money Tool

* VMware crashes

[JeffJoe]

Today VMWare Workstation 15.0.1 appeared. The bug is still present! Not really have the feeling VMware does anything about bugs!

[rianquinn]

I am seeing the same issue with the latest VMWare Fusion running Bareflank (which is similar to SimpleVisor). I think the issue likely is in the VMWare hypervisor that is shared across all of their products and is basically just broken for Windows. This does not seem to be an issue with Linux based guests. Older versions of VMWare worked fine.

[JeffJoe]

Here is VMware's official answer:

We have been unable to reproduce the issue internally by performing the steps and shv.sys file provided on a Windows 10 x64 VM.

We would like to inform that we do not support nested virtualization.

I have the strong impressing VMware just ignores such bugs.

[shucaimao]

HI,JeffJoe

My name is Harrsion LI,I'm from china.

I have the same question with you.

the reproduce steps is:

1.enable the vmware 15 nested virtualization

2. and then install qihoo 360 from http://dl.360safe.com/setupbeta.exe

3. restart the X64 GUEST OS.

the attach is the error log.

[Zongmin]

Hi JeffJoe,

Thank you for reporting this issue. It looks like there was a miscommunication.

Regarding to this issue, we have been actively working on this issue and will include the fix in an update release asap.

Thanks,

VMware Workstation Team

[Zongmin]

Workstation 15.0.2 is just released. Upgrade to this build and pls let us know if this issue is fixed.

Thanks,

VMware Workstation Team

[JeffJoe]

Super, great work! I confirm the issue is fixed! Thank you to the whole VMware team!

[Zongmin]

VMware Fusion 11.0.2 was just released hours ago. Upgrade to this build and pls let us know if this issue is fixed.

Thanks,

VMware Fusion and Workstation Team

[bitlock]

VMware Fusion 11.0.1 - issue is reproduced

VMware Fusion 11.0.2 - issue is fixed

Note:

host: macmini (late 2014), OSX 10.13.5, VTx=On, IOMMU=On

guest: win10x64 rs4  +  KTS 2019

testcase: start Safe Browser