virtualbox.org

Hi,

I recently installed kali as a vm on my windows laptop, it worked fine for about a week, but now having problems with loading, usually getting the message BUG: soft lockup - CPU#11 stuck for 22s ..., or similiar. I've tried increasing and decreasing RAM size, memory, video settings, turning hyper v off. Still no luck. Heres the specs for my windows:

Device name LAPTOP-SU7PKHUS
Processor 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz 2.42 GHz
Installed RAM 8.00 GB (7.73 GB usable)
Device ID C533D4DD-0100-4547-832E-787418837822
Product ID 00342-20735-87388-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

I have attached the log file below. Many thanks in advance, really apprieciate some help on this

It seems to be a problem with the RAM. I backed the processor off to 1, disabled audio, used 1024MB for motherboard setting and now it seems to be working again. Also when not using firefox on host it seems to make it more stable. Maybe 8GB of RAM on host really not enough?? Hope this will help anyone that has similiar problem

Did you upgrade to VB 6.1.32 during the week?

It probably worked after you disabled hyper-v as 6.1.32 has issues with some configurations with hyper-v. If you need hyper-v try 6.1.30.

8GB is fine for the host, so long as you are not running allot of things at once. Things === check ram usage so you do not get low.

RAM has to be husbanded somewhat carefully on this PC:

00:00:02.591260 Host RAM: 7915MB (7.7GB) total, 3524MB (3.4GB) available
00:00:02.741464 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)

Looks like you could handle 2GB normally, or more if you're careful not to start lots of other host apps before starting the VM.

Your host has Hyper-V running. This might be causing trouble, or the 6.1.32 bug might be involved. Since you've posted a 6.1.32 log (thanks for that!) you could try reverting to 6.1.30 as Andy suggests and see if the VM has better operation.

Our forum guru 'fth0' has done some troubleshooting and pins down these possibilities to try (HCVI = Microsoft 'Memory Integrity'):
6.1.32 without Hyper-V
6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.

AndyCot wrote:Did you upgrade to VB 6.1.32 during the week?

It probably worked after you disabled hyper-v as 6.1.32 has issues with some configurations with hyper-v. If you need hyper-v try 6.1.30.

8GB is fine for the host, so long as you are not running allot of things at once. Things === check ram usage so you do not get low.

Hi. Thanks for your reply. Nope I reactivated hyperv after it continued failing booting. I noticed the hyperv did appear in the log, I'm still learning with respect to reading logs, but I googled it and and a couple of results did seem to indicate what you're saying, Seems to be working ok now....if I have anymore problems I'll try your suggestion of using 6.1.30

thanks again,

scottgus1 wrote:RAM has to be husbanded somewhat carefully on this PC:

00:00:02.591260 Host RAM: 7915MB (7.7GB) total, 3524MB (3.4GB) available
00:00:02.741464 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)

Looks like you could handle 2GB normally, or more if you're careful not to start lots of other host apps before starting the VM.

Your host has Hyper-V running. This might be causing trouble, or the 6.1.32 bug might be involved. Since you've posted a 6.1.32 log (thanks for that!) you could try reverting to 6.1.30 as Andy suggests and see if the VM has better operation.

Our forum guru 'fth0' has done some troubleshooting and pins down these possibilities to try (HCVI = Microsoft 'Memory Integrity'):
6.1.32 without Hyper-V
6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.

Hey thanks,this is all good info. Yes my gut feeling was that I was pushing the machine to hard in terms of RAM. Last night I tried running the VM on 1 processor and touch wood seems to be ok now. Interesting about the hyperv, I'm tempted to revert back to 6.1.30 today to see if it makes a difference.

Thanks again

scottgus1 wrote:RAM has to be husbanded somewhat carefully on this PC:

00:00:02.591260 Host RAM: 7915MB (7.7GB) total, 3524MB (3.4GB) available
00:00:02.741464 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)

Looks like you could handle 2GB normally, or more if you're careful not to start lots of other host apps before starting the VM.

Your host has Hyper-V running. This might be causing trouble, or the 6.1.32 bug might be involved. Since you've posted a 6.1.32 log (thanks for that!) you could try reverting to 6.1.30 as Andy suggests and see if the VM has better operation.

Our forum guru 'fth0' has done some troubleshooting and pins down these possibilities to try (HCVI = Microsoft 'Memory Integrity'):
6.1.32 without Hyper-V
6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.

Hi, just thought I would update this. I tried reverting to 6.1.0, without HVCI and still no luck. I tried disabling HyperV and also didnt work. So I installed 6.1.26, had to disable both HyperV and HVCI and now its working perfectly!! So thank you for this. Last week using version 6.1.32, the CPU was maxing out whenever I successfully ran kali as VM, now its running at less than 10% or so and is working much much better. One last question, is it safe to run windows 11 with HVC1 disabled??? This is the only I feel a bit weary about.

Many thanks, much appreciated

Windows 11 and HVCI are new wrinkles in the 'Virtualbox / Hyper-V Coexistence Saga'. I'm quite sure that the devs will get Virtualbox to run under HVCI in time, especially as Oracle's corporate customers who use the pay-for Oracle virtualization engine (which is pretty much Virtualbox with a support contract) move to Windows 11/Server2022 hosts.

Glad you have a working system now! As for running sans HVCI, be web-safe, keep malware off the host, and you'll probably be OK.

scottgus1 wrote:I'm quite sure that the devs will get Virtualbox to run under HVCI in time

Strictly speaking, that's already the case with VirtualBox 6.1.32. "Only" running a VirtualBox VM with Hyper-V active is a problem for several users. Some users didn't have a problem when using only 1 vCPU with Hyper-V and HVCI both being active.