Guest Freeze: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [firefox:3744]

[Tzahi]

I searched a lot for a similar problem and could not find one. The problem occurs with both 5.1.12 or 5.0.30 and also earlier versions for a few months now. I tried ubuntu 16.04 64bit VM and also Debian machine 32 bit with jessie and now stretch. I recompiled the kernel, 4.8.15 same thing. I am using docker to run the firefox so that is an important information. The freeze occurs after a while using the firefox. I don't have an idea why it happens or in what situation. Sometimes it can run for a long time, sometimes not. It is sporadic.

[Tzahi]

VBOX log from a debian stretch with a custom kernel

[Tzahi]

the output from the netconsole log. The cannot be seen by /var/log/messages

[Tzahi]

I can add that this happened on a Windows 7 host machine as well with both 5.1.12. 5.0.30 seemed to be working for a day but i did not check it that far. The linux guest on the osx host is stalling a few times a day for a few months. I was thinking this was due to 64 bit kernel or something like that so when i switched to 32 bits i was surprised it still occured. I tried several versions of docker. Nothing helps, it always stalls.

The machine sometimes is semi responsive by returning pings or allowing the port to be opened but not further than that.

[Klaus Espenlaub]

Try setting paravirtualization to None (your VM uses default, which translates to KVM). Could be that something with the KVM clock virtualization is going wrong.

[Tzahi]

That seem to be helpful, It will take a few days to make sure but already a 24hrs free from freezes. Thanks!

But I wonder why this is not fixed for almost 6 months now...

[Tzahi]

No freeze till now. Guess this proves it. The KVM is broken. 6 months of freezes with all the versions 5.0 and 5.1 tried.

[Tzahi]

Still not freezing. Now I am sure. The KVM acceleration is broken.

[MerkUriy]

A similar scenario occurs within a few days with me. But before, I such cases had not noticed.

It was not associated with changes in version VirtualBox. At that time, I have not changed anything, and not updated.

Host = for Windows 10. Guest = Ubuntu 16.04. Paravirtualization = default = KVM (for Ubuntu x64).

VirtualBox 5.1.6 (Guest Additions 5.1.6) and 5.1.14 (Guest Additions 5.1.14) (I update later, when tried to fix the problem, ).

Freezing occurs after using any apps, such as IntelliJ IDEA? Or even when copying files. It works not for long - 5-30 min. If do nothing, guest OS can work longer.

I changed Paravirtualization to None. 1 days - not freezing. But now there is a small brakes in Guest OS.

[MerkUriy]

Already 5 days there are no freezes. But the guest system noticeably slows down when configuring Paravirtualization = None.

Very much waiting for fixes for normal operation of the guest OS with the settings Paravirtualization = default = KVM (for Ubuntu x64).

[Frank Mehnert]

MerkUriy, please attach a VBox.log file of a VM session, no matter if paravirtualization is enabled or not. I would like to have a look at your VM configuration.

[Frank Mehnert]

Still relevant with VBox 5.1.22? If so, please attach VBox.log files.

[mgarstin]

I'm new to this. I just downloaded VirtualBox 5.1.28 (from 5.1.26) and now my Ubuntu 16.04 LTS guest (host is Windows 7) runs painfully slow. During boot up I get several of the 'soft lockup' messages on various CPU's (I have it set to 28 because my host machine is a dual Zeon processor with 56 CPU's). Previously this would boot up in less than a minute (now it takes about 15 minutes).

My Yocto builds of a Linux kernel would take about 10 minutes. I recently had to kill the machine after 2 hours (it appeared to have made it about half way through the build). According to Windows Task Manager the VM is using only 18 to 20 CPU's at about 50%. Previously it would use all 28 CPU's flat out at 100% each (dang was that sweet).

Oh ya, after the upgrade my VW for the Ubuntu Linux had all of its parameters reset. It was even switched back to Windows instead of Linux.

I'm attaching my VBox.log file of my most recent boot up.

Any help would be greatly appreciated.

Cheers,

Mark

[mgarstin]

Vbox.log file for problem after 5.1.28 upgrade -mgarstin.

[mgarstin]

I solved my own problem. A short while back something went wrong with my Ubuntu and the whole Linux system locked up. This happens every now and again (about once a month and I'm using the system nearly constantly for 8 hours every work day). The only solution I've found to this lock up problem is to power cycle the virtual machine.

But when this happened the last time I was getting this notice to upgrade to 5.1.28 which I did (that turned out to be a red herring for my problem... I think). When I tried to start up my Ubuntu again, all of the settings in the virtual machine had been cleared out (???!). I went about resetting everything except for three somewhat obscure settings. Here are the settings and what I set them to in order to get my machine working again:

Settings->System->Acceleration->Paravirtualization Interface: set to Default Settings->System->Acceleration->Enable VT-x/AMD-V: set to checked Settings->System->Acceleration->Enable Nested Paging: set to checked.

It all runs fine now.

Cheers,

Mark

[William Ruppel]

This just happened to me.

VBox: 5.2.12
Guest: Oracle Linux 7.3 with KVM paravirtualization
Host: Windows 10 17134.112

Please find attached the VBox.log file.

[William Ruppel]

Incident with 5.2.12