Virtual box machines fails and got frozen and unusuable anymore

[negroscuro]

Hello,
I am struggling with this since some days ago while I tried to create several virtual machines and seems not to work at some point. I got some traces on VM screen and then it get frozen.

I have Vbox 6.1.4 r136177 (Qt5 6.2)

It is on a Windows 10 version 10.0.18362 compilacion 18362 in a Laptop X64 Lenovo Mt 20LX BU think FM thinkpad L580 modelo del sistema 20LXS5PE03
BIOS: LENOVO R0QET59W (1.36) 16/10/2019 (SMBIOS 3.0) controlador 1.36 UEFI

I created a VM:
Ubuntu server 18.04.4 bionic [ 8-RAM 3-CPU 30gb DISK ]
I installed postrgesql 10, then postgis 2.4, java -11 jdk, tomcat 8.5.6 and nodejs and was about to install docker.

Then I saw I got some traces in the screen of the VM (I was workin through ssh with putty so I noticed it then once a CURL command got stucked):

Since I am new user I am not allowed to put an image. "You must be a member for 1 days and have 1 posts before you can post urls."
So I will attach it.

The trace on Virtualbox (too long for the post max sixe) "Your message contains 160836 characters. The maximum number of allowed characters is 60000."
So I will attach it.

The virtual machine got frozen and had to shut it down. Once I restarted it seemed to work well but after login appears then the trace come again and the VM gots frozen again.
I am desperate with this, once and again redoing all work and loosing hours of work.
I am starting to think it could be due to my Windows10 OS.

Any clue?
Thank you in advance.

[mpack]

too big, I had to cut it.

Actually, all you had to do was zip it.

Bits of logs are not useful.

[negroscuro]

Compressed as ZIP and attached the whole log file to the first post.

[mpack]

00:00:02.078423 Host RAM: 16262MB (15.8GB) total, 8848MB (8.6GB) available
...
00:00:02.855485 RamSize <integer> = 0x0000000200000000 (8 589 934 592, 8 192 MB, 8.0 GB)

You are too close to exhausting host RAM. Reduce to 4GB or 6GB.

Also, you have assigned 3 vCPUs to the VM, leaving one for the host. This is usually a mistake. A fairer share is two cores each. But congratulations on not confusing threads with cores.

00:00:02.855697 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)

Graphics RAM basically not assigned at all. Even in headless mode I think you'd need more VRAM than that. I'd say increase to 128MB.

00:00:29.978732 VMMDev: Guest Additions information report: Version 5.2.8 r120774 '5.2.8_KernelUbuntu'

Those are not the official GAs, that's from the Ubuntu VirtualBox fork. You might want to install the official GAs once other issues are fixed.

I'm also seeing a lot of audio mixer being continually turned on and off. You might want to disable audio for now.

Finally, I'm not seeing any sign that the VM crashed, and your screenshot shows only the guest OS crashing. Not every guest software crash is due to a VirtualBox problem. You might want to consider what exactly the guest was doing when it crashed.

[negroscuro]

00:00:02.078423 Host RAM: 16262MB (15.8GB) total, 8848MB (8.6GB) available
...
00:00:02.855485 RamSize <integer> = 0x0000000200000000 (8 589 934 592, 8 192 MB, 8.0 GB)

You are too close to exhausting host RAM. Reduce to 4GB or 6GB.

Also, you have assigned 3 vCPUs to the VM, leaving one for the host. This is usually a mistake. A fairer share is two cores each. But congratulations on not confusing threads with cores.

00:00:02.855697 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)

Graphics RAM basically not assigned at all. Even in headless mode I think you'd need more VRAM than that. I'd say increase to 128MB.

00:00:29.978732 VMMDev: Guest Additions information report: Version 5.2.8 r120774 '5.2.8_KernelUbuntu'

Those are not the official GAs, that's from the Ubuntu VirtualBox fork. You might want to install the official GAs once other issues are fixed.

I'm also seeing a lot of audio mixer being continually turned on and off. You might want to disable audio for now.

Finally, I'm not seeing any sign that the VM crashed, and your screenshot shows only the guest OS crashing. Not every guest software crash is due to a VirtualBox problem. You might want to consider what exactly the guest was doing when it crashed.

First of all I am pretty far from being an expert in all this.
Second thank you very much for your advice and time you spent to help me.

Regarding CPU, my machine has 8cpu so I asigned 3 but anyway I will leave just 2 for the VM
I will reduce RAM as you pointed to 6gb. My laptop is 16gb.
I will increase video ram as you indicated to 128mb.

I will disable audio, I never had such a problem but I am not using it so I will disable it just in case...
I will try to find out which are the GAs you refer. But I did not install any ... I only use GA's with Ubuntu with GUI.

Well not sure if crashing but it does not respond in any way.

I also disabled PAE/NX, but I am not sure what is this for...


--------------CHANGES TESTED------------------

I started it with 2 fails one of those is some kind of system daemon but I did had not the chance to read it in order to write it down...

Then I stoped and restarted to try to catch that fails with print screen but everything worked. Anyway I still have this on login screen and after login another trace frozen the VM

I attached both screenshots and new log file.

[fth0]

Your guest OS crashes while doing disk I/O, so my first thought was to check for disk space on the host. But then I saw the following lines in your VBox.log file:

00:00:04.677731 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:04.728592 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
[...]
00:00:04.733161 CPUM: No hardware-virtualization capability detected

You'll find a lot of posts in this forum regarding VT-X and Hyper-V when searching for those lines. I recommend the posts from scottgus1 ...

[negroscuro]

Space on mu host is 150gb out of 240gb so I think it should be fine.

But regarding those virtualization issues that is was I was expecting... I ensure Windows devide guard is disabled and I manage then to enable virtualization from BIOS and WINDOWS but I will seek for those forum threads you said to see if I can improve my laptop's current configuration in any way.

Thank you for your help, really appreciated!

[negroscuro]

I just checked windows properties and Hyper-V was disabled so I enabled it and restarted windows but after restart I changed VM name and tried to start it but it fails... O_o

I disabled it again, I restarted my laptop and same error hapens... I attached the log.

[fth0]

You'll find a lot of posts in this forum regarding VT-X and Hyper-V when searching for those lines. I recommend the posts from scottgus1 ...

For example: viewtopic.php?f=6&t=97501&p=473074#p473074

[negroscuro]

I disabled Hyper-V again, I shut laptop down for some time and still haveing the same issue:

VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API (VERR_NEM_MISSING_KERNEL_API).
VT-x is not available (VERR_VMX_NO_VMX).

To turn Hyper-V off completely, do this:
1. Shut down all programs. You will have to reboot your host.
2. Find the Command Prompt icon, right click it and choose Run As Administrator.
3. Enter this command:
bcdedit /set hypervisorlaunchtype off
4. Enter this command:
shutdown -s -t 2
5. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.


Still the same result.

I checked virtualization active in BIOS and it is active. I checked core isolation is disabled and it is disabled....

Do not know what else to do.

[negroscuro]

I disabled from windows features:

- Hyper-V
- Virtual Machine Platform
- Windows Hypervisor platform

Two last features were enabled... seems to be the reason.
Now VM started, but I still have the same traces on login and after login.

[fth0]

The key to success is the bcdedit command. If it is correctly executed and the results are in effect, all the Windows features explicitly or implicitly trying to use Hyper-V can't succeed any more, and VirtualBox shouldn't see Hyper-V any more. To verify the result, please open the Command Prompt as Administrator, execute the bcdedit command without parameters and post the results.

[negroscuro]

Well Hyper-V was not activated but there were other two features which were activated and they should not. Now are all 3 disabled.

I ran BCDEDIT command:

Code: Select all

Administrador de arranque de Windows
----------------------------------
Identificador           {bootmgr}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  es-ES
inherit                 {globalsettings}
badmemoryaccess         Yes
isolatedcontext         Yes
fverecoveryurl          https://account.activedirectory.windowsazure.com/r#/profile
default                 {current}
resumeobject            {adb09f25-4cbb-11ea-959a-9e7ad06fdfb3}
displayorder            {current}
                        {adb09f29-4cbb-11ea-959a-9e7ad06fdfb3}
toolsdisplayorder       {memdiag}
timeout                 30

Cargador de arranque de Windows
-----------------------------
Identificador           {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  es-ES
inherit                 {bootloadersettings}
recoverysequence        {adb09f27-4cbb-11ea-959a-9e7ad06fdfb3}
displaymessageoverride  Recovery
recoveryenabled         Yes
badmemoryaccess         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {adb09f25-4cbb-11ea-959a-9e7ad06fdfb3}
nx                      OptIn
bootmenupolicy          Standard
claimedtpmcounter       0x10002

Cargador de arranque de Windows
-----------------------------
Identificador           {adb09f29-4cbb-11ea-959a-9e7ad06fdfb3}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             W10 No Hypervisor
locale                  es-ES
inherit                 {bootloadersettings}
recoverysequence        {adb09f27-4cbb-11ea-959a-9e7ad06fdfb3}
displaymessageoverride  Recovery
recoveryenabled         Yes
badmemoryaccess         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {adb09f25-4cbb-11ea-959a-9e7ad06fdfb3}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Off
claimedtpmcounter       0x10002

[negroscuro]

I started today the VM and got frozen with those traces after login screen and had to shut it down... (I attached logs)

Is there any problem with Guests additions? I would say I did not installed any... I thought GA's are for SO with GUI... anyway I did not install any GAs as far as i know...
Seems like they are there and giving problems but I tried to insert iso guest aditions (VBoxGuestAdditions_6.1.0_RC1.iso), mount and seems nothing is in hte mount folder (I am very new in ubuntu to know about how mount works) then I run the comand to install guest additions and was not found. I just follow a tutorial I found on the internet.
(https://virtualzero.net/blog/how-to-ins ... -18.04-lts)

I noticed Snappy daemon is the one failing on startup. I have no idea about waht is or why is it failing...

[fth0]

The bcdedit output shows that you have two Boot Menu Entries in the Windows Boot Manager called "Windows 10" (with Hyper-V) and "W10 No Hypervisor" (without Hyper-V). You issued the bcdedit command while running "Windows 10", and VirtualBox is not expected to run fast enough then. Boot into "W10 No Hypervisor", and VirtualBox should work much better.