Kaonashi42
Contributor
Contributor

Error: Module 'Monitor' power on failed. Failed to start the virtual machine.

Hello,

Edit:

I did install Valorant before having the problem.

So I have been trying to create virtual machine with VMware workstation 15 pro and was not able to power it on.

Here is the message I get when i use "power on this virtual machine":

This virtual machine failed to switch to 64 bit mode. This failure might be due to a lack of available memory on the host.

Module 'Monitor' power on failed.

Failed to start the virtual machine.

vm1png.png

I am using:

- Ubuntu LTS 18.04 iso

My computer has:

- Windows 10 Education

- 16Gb RAM

- More than 100Gb of free space (hard disk)

- Motherboard: an asrock phantom

- CPU: amd ryzen 5 3600x

- Antivirus: Windows defender

I have tried:

- Rebooting

- Updating windows (normal updates)

- Keeping the default parameters while creating the vm

- Limiting the RAM to 250mb

- limiting the hard disk to 1Gb

- Checking that SVM and SMT are enabled for virtualization in the Bios

- Using VMware workstation Player 15, same issue

- Using virtualbox with the same configuration, it is working

- enabling/disablings Windows Hyper-V

- Disabling windows defender my firewalls

Here is my vmware.log file:

https://easyupload.io/e9r0n7

Here are the last lines if you do not wish to dl the entire file:

2020-04-19T19:23:13.805+02:00| vmx| I125: Host AMD-V Capabilities:

2020-04-19T19:23:13.805+02:00| vmx| I125: SVM Revision:           1

2020-04-19T19:23:13.805+02:00| vmx| I125: ASIDs Supported:        32768

2020-04-19T19:23:13.805+02:00| vmx| I125: Nested Paging:          yes

2020-04-19T19:23:13.805+02:00| vmx| I125: SVM GMET:               yes

2020-04-19T19:23:13.805+02:00| vmx| I125: LBR Virtualization:     yes

2020-04-19T19:23:13.805+02:00| vmx| I125: SVM Lock:               yes

2020-04-19T19:23:13.805+02:00| vmx| I125: NRIP Save:              yes

2020-04-19T19:23:13.805+02:00| vmx| I125: TSC Rate MSR:           yes

2020-04-19T19:23:13.805+02:00| vmx| I125: VMCB Clean Bits:        yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Flush by ASID:          yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Decode Assists:         yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Pause Filter:           yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Pause Filter Threshold: yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Monitor_PowerOn: HostedVSMP skew tracking is disabled

2020-04-19T19:23:13.805+02:00| vmx| I125: Loaded crosspage: .crosspage. Size = 4096 bytes.

2020-04-19T19:23:13.805+02:00| vmx| I125: vmm64-modules: [vmm.vmm64, vmce-vmce.vmm64, viommu-none.vmm64, vprobe-none.vmm64, hv-svm.vmm64, gphys-npt.vmm64, callstack-none.vmm64, swstats-none.vmm64, gi-none.vmm64, gmm-none.vmm64, ahci-ahci.vmm64, !ahciRegs=0x0, !ahciShared=0x1000, !e1000Shared=0x1c00, !vmSamples=0x2480, !theIOSpace=0x24c0, !ttGPPerVcpu=0x8800, {UseUnwind}=0x0, numVCPUsAsAddr=0x1, {SharedAreaReservations}=0x8840, {rodataSize}=0x20915, {textAddr}=0xfffffffffc000000, {textSize}=0x8b65e, <MonSrcFile>]

2020-04-19T19:23:13.805+02:00| vmx| I125: vmm64-vcpus:   1

2020-04-19T19:23:13.818+02:00| vmx| I125: Module 'Monitor' power on failed.

2020-04-19T19:23:13.818+02:00| vmx| I125: VMX_PowerOn: ModuleTable_PowerOn = 0

2020-04-19T19:23:13.818+02:00| vmx| I125: Vix: [mainDispatch.c:1163]: VMAutomationPowerOff: Powering off.

2020-04-19T19:23:13.819+02:00| vmx| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Users\X\Documents\Virtual Machines\Ubuntu 64-bit\Ubuntu 64-bit.vmpl", ...) failed, error: 2

2020-04-19T19:23:13.819+02:00| vmx| I125: Policy_SavePolicyFile: invalid arguments to function.

2020-04-19T19:23:13.819+02:00| vmx| I125: PolicyVMX_Exit: Could not write out policies: 15.

2020-04-19T19:23:13.819+02:00| vmx| I125: WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

2020-04-19T19:23:13.819+02:00| WinNotifyThread| I125: WinNotify thread exiting

2020-04-19T19:23:13.822+02:00| vmx| I125: Vix: [mainDispatch.c:4215]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0

2020-04-19T19:23:13.822+02:00| vmx| I125:

2020-04-19T19:23:13.822+02:00| vmx| I125+ Power on failure messages: This virtual machine failed to switch to 64 bit mode. This failure might be due to a lack of available memory on the host.

2020-04-19T19:23:13.822+02:00| vmx| I125+ Module 'Monitor' power on failed.

2020-04-19T19:23:13.822+02:00| vmx| I125+ Failed to start the virtual machine.

I cannot seem to find any related issues or solutions that fits my problem.

Thank you in advance for any help provided.

30 Replies
madoxav
Contributor
Contributor

Hello,

Same here, with Workstation Pro 15.5.0 (EDIT : I updated to 15.5.2, same problem), trying to boot a debian 10 (I tried 32 and 64b) with 1GB Memory, on a windows 10 1909 up-to-date.

Same errors on Reddit.

Tried to enable/disable SVM and SMT in BIOS.

I have a Ryzen 2600x on x470, 16GB Memory (12GB free).

Anonymized vmware.log can be found here.

0 Kudos
dariusd
Leadership
Leadership

Hi,

The consensus on the Reddit thread is that a Windows Update has arrived and the problem has only surfaced since then.  Let's see if we can figure out what has happened... Could you please try setting Gathering Debugging Information to "Full"​ and then power on the VM.  It will probably still fail, but the resulting vmware.log file might have more useful information in it.  If you could post that vmware.log (just use the Attach link in the bottom-right corner of the window when composing a reply), that'd be super helpful.

Thanks,

--

Darius

0 Kudos
dariusd
Leadership
Leadership

It also might be worth checking in the Windows Event Viewer to see if any relevant events are logged at the instant that the virtual machine fails.

Thanks,

--

Darius

0 Kudos
madoxav
Contributor
Contributor

Find attached the anonymized vmware.log when VM is on Full logging mode.

I found nothing related to VMWare in event log (Application / Security / System).

0 Kudos
dariusd
Leadership
Leadership

Thanks for that – and thanks for upgrading to 15.5.2... that was going to be my very next suggestion.  I'll file a bug report here and we will investigate.

In the meantime... Depending on what your requirements are, the VMware Workstation Tech Preview 20H1​​ might be able to run your virtual machines.  Note that it is a Tech Preview so it should be considered pre-release "beta" quality, and it does have some limitations (specifically regarding nested virtual machines and with snapshot/suspend compatibility), so be sure to read through the supporting documentation before deciding to give it a try, and maybe check that you have a good backup of your VMs, just in case...

Thanks,

--

Darius

0 Kudos
madoxav
Contributor
Contributor

I just tried the 20H1 as you suggested, with the same behavior.

I alors tried to reboot / disable virtualization / try again / reboot / re-enable / try again, still without any luck.

Thanks for you bug report!

0 Kudos
havlli
Contributor
Contributor

I have same issue all my virtual machines stop working, what should i do, my work is halted, i tryed everything i could found, reenabling cpu virtualization, instaling your beta version of software, nothing worked so far, i need solution ASAP!!!! I need to have my machines up and running

0 Kudos
riversde
Contributor
Contributor

For me uninstall this Windows update fix the problem KB4549951

Smiley Happy

0 Kudos
dariusd
Leadership
Leadership

VMware engineering has not been able to reproduce this failure in the lab.

Summarizing the linked Reddit thread and this one, we have a few folks reporting success through various means:

  • Going into the host BIOS and disabling Virtualization Technology (Intel VT or AMD-V) and then going back into BIOS a second time and re-enabling it.
  • One user here has uninstalled KB4549951.
  • One user on Reddit has reported that there was another Windows update but has not provided any details.
  • One user has reported that Windows had re-enabled Hyper-V and they just needed to disable it again for Workstation to start working.

So we really have no clear idea what is happening right now.  Changes in Intel VT or AMD-V state sometimes require that the system be completely powered off, so I wonder if it would be sufficient to just power off completely (i.e. unplug from the wall) for 30 seconds?

One thing that is clear is that this problem affects a small subset of our users... we have had 10+ reports, not 1000+.  Perhaps if we can start posting more details of affected systems we can narrow it down a little bit more.  The sort of information which could be relevant would include:

  • Host CPU model
  • Host motherboard vendor/model or host system vendor/model
  • Host OS version/build
  • Any antivirus or endpoint security software installed on the host OS.

Thanks,

--

Darius

onefourtyseven
Contributor
Contributor

I just wanted to add to this - I had the same issue, went through all of the steps and found the only fix to be uninstalling KB4549951. Might want to look into what specifically that update changed? Happened on both the tech preview and 15.5.2.

PC info:

Intel i9-9900k

Gigabyte Z390 Designare

Currently on 1909 18363.720 - but happened on 1903 as well.

No AV other than windows defender.

0 Kudos
Kaonashi42
Contributor
Contributor

Hello,

Thank you for your help.

My problem is solved however I am still unsure how I did it.

Yesterday I decided to go dual boot on my pc. Today I saw a window update 1909, dl/installed it, tried to start vmware. It worked. I uninstalled the update to make sure that was what solved the problem but it still worked afterwards.

Edit: Since Valorant/Vanguard seems to be the problem, I did start the game that day and an update from Valorant may have helped.

0 Kudos
thecatishere
Contributor
Contributor

I've got the same problem

Intel i7 3770

Gigabyte GA-P75-D3

Windows 10/ Build 1909 latest update as for 25/4/2020

Nothing else than windows defender

0 Kudos
SniparsZach
Contributor
Contributor

I am having the same problem even going through the solutions listed,

CPU: i7-4790k

Mobo: MSI Z87-GD65

OS Build: 17763.1158

  |   Version: 1809

AVAST Antivirus

0 Kudos
dariusd
Leadership
Leadership

Hi everyone!

There is some discussion on Reddit regarding a potential incompatibility between the Vanguard anti-cheat system (included with the game Valorant) and VMware Workstation/Player:

https://www.reddit.com/r/VALORANT/comments/g61i4v/with_the_new_update_vmware_virtual_machines_broke/

https://www.reddit.com/r/VALORANT/comments/g5jaxh/first_patchnotes_of_beta/fo791oj/

If you are affected by this particular failure, specifically with the error message that includes "This virtual machine failed to switch to 64 bit mode", can you please report back here with an indication of whether or not you also have (or did previously have) Valorant installed on the affected system?

Thanks for your patience!

--

Darius

0 Kudos
THEmi132
Contributor
Contributor

Hi Darius,

Yeah I do have VALORANT and for me, I have to disable-enable hardware virtualization so VMware works. If I do, the hardware virtualization I think it reset or something, so VMware works but, if I try to play the game it says that I need to reboot because the anti-cheat system needs to be installed (wich I already did). When I reboot the game works but VMware doesn't so yeah, the issue is that I can't have them both working at the same time.

I do explain myself better in this comment from reddit.

https://www.reddit.com/r/vmware/comments/g4e0o1/vmware_error_while_powering_on_module_monitor/fohoaq...

So yeah, I had the suspicion that the problem was VALORANT because I have this problem since I installed the game but I wasn't sure.

Thank you in advance.

0 Kudos
Rakinare
Contributor
Contributor

Hello,

just came to this thread since I do have the same problem. I also do have Valorant and therefore Vanguard installed. So this might be the key?

Edit: Uninstalling Vanguard fixed the problem. So it is 100% that.

0 Kudos
SniparsZach
Contributor
Contributor

Disabled 'vgc' in services which I assume is the vanguard anticheat and disabled-enabled the hypervisor and it works, guess I'm not playing Valorant anytime soon

Thank you very much for linking this thread.

0 Kudos
yzere
Contributor
Contributor

Hello Guys,

I've just had the same problem and it turnes out that it is in fact a Vanguard influence in how virualisation takes place. Vanguard scans machine from its kernel so that there will be no cheats unnoticed. It can also tend to see virtualisation as a possible threat and does things to cut off possibility to proceed any of this. It may be the case that other core-intrucive programs could block startup of VM but it shows up only in VMWare Workstation. Maybe it is coused by difference in virualization beetwen products that makes only this one vulnerable. Nevertheless I disabled Vanguard and it works all good.

Hope it can lead someone to better understanding and to solving this weird problem.

Thanks for help.

0 Kudos
zajacz
Contributor
Contributor

I think you will find that just disabling vgc in services is not enough to stop the error.  The error will still be there sometimes.  You need to completely uninstall Riot Vanguard in order for the error not to return.  That is what I believe fixes it for good.  I found even if I left the vgc in its default state of manual in the services setting, sometimes when I would just reboot, the error would be gone and other times the error would there.  It would seem random whether the error would show up regardless of the vgc setting at manual or disabled.  Again, completely uninstall Riot Vanguard to not get the error.

0 Kudos