JeffJoe Tracker

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

JeffJoe — Fri, 23 Nov 2018 08:26:03 GMT

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

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

JeffJoe — Thu, 15 Nov 2018 08:23:26 GMT

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.

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

JeffJoe — Mon, 12 Nov 2018 08:59:37 GMT

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

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

JeffJoe — Thu, 25 Oct 2018 12:26:03 GMT

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

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

JeffJoe — Fri, 12 Oct 2018 08:51:44 GMT

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.

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

JeffJoe — Thu, 11 Oct 2018 15:16:55 GMT

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

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

JeffJoe — Thu, 11 Oct 2018 13:38:34 GMT

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 specific goals: using…

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.

Dynamic Probes no longer supported?

JeffJoe — Sat, 08 Aug 2015 09:34:18 GMT

I am running on VMWare Workstation 11:

(vprobe GUEST:0x8173ae25

(printf "Syscall %s\n" (curprocname)))

C:\Program Files (x86)\VMware\VMware Workstation>vmrun vprobeLoadFile "C:\Users\

admin\Documents\Virtual Machines\Windows 10\Windows 10.vmx" "C:\Users\admin\Desk

top\test.vp"

vprobeLoadFile: error: invalid static probe: GUEST:0x8173ae25

vprobeLoadFile: 0 warnings, 1 errors

Error: Unknown error

Kind Regards

Joe