id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host 19171,"On Ubuntu 18 host, Win10-64bit guest goes to GURU with VERR_VMX_UNABLE_TO_START_VM",juhan,,"Dear community, first of all, I'd like to thank all of you for supporting this awesome project! I'm very grateful being able to use such a great software in our environment. Now to my problem. I'm having trouble with a Win10 64-Bit guest on Ubuntu 18.04.3 LTS. The machine has a rather new Intel Core i7-9700, with 8 cores, and 32GB RAM. VT is available and turned on. The guest gets 8 logical cores and 16GB RAM. The VM starts normally and works as expected. Everything worked fine for weeks just until I ran the update of a DATEV software collection (a huge accounting software from germany), installed on the guest. The update runs as expected, w/o error until one particular point where the VM changes to GURU meditation. This procedure is reproducible. Having a look at the logs shows that 'VERR_VMX_UNABLE_TO_START_VM' might be the issue here. Looking deeper shows, that VT-x is supported, active and running as expected. Two particular log lines remind me of [https://forums.virtualbox.org/viewtopic.php?f=6&t=78235&sid=f021b9659edbfce8a319bca24066cbc6 this issue] I found, when searching for a solution: {{{ 00:01:11.851397 HM: VERR_VMX_UNABLE_TO_START_VM: VM-entry allowed-1 0x3ffff 00:01:11.851399 HM: VERR_VMX_UNABLE_TO_START_VM: VM-entry allowed-0 0x11ff }}} Unfortunately, as far as I understand the discusstion of the issue above, it was never solved?! I honestly can't interpret these lines, but aren't they contradictory? VMX could be allowed or not, but both?! Could it be, that the DATEV update tries to start a VM inside the guest somehow? I activated Hyper-V on guest os btw.. I already tried to activate/deactivate different settings around VT-x support including ""VT-X/AMD-V"", ""Nested VT-X/AMD-V"", ""PAE/NX"", ""Nested Paging"" etc., without any changes. I would be very greatful for any help, thank you very much in advance! Best regards PS: If this is the wrong place for this issue, I apologize politely and will post my problem in the forum.",defect,closed,other,VirtualBox 6.1.0,fixed,"guru,VERR_VMX_UNABLE_TO_START_VM",j.uha@…,Windows,Linux