VirtualBox is stuck at 20%

[johnblood]

My system froze, so I had to perform a forced reboot. Afterward, VirtualBox started acting up. I thought that the files may be corrupt, so I reinstalled VirtualBox. I’m still running into trouble. I tried to create a new Win7 virtual machine and it is stuck at 20%.

Here is the VBox.log:

00:00:01.422820 VirtualBox VM 7.2.2 r170484 linux.amd64 (Sep 11 2025 11:31:33) release log
00:00:01.422822 Log opened 2025-10-21T23:59:56.357045000Z
00:00:01.422823 Build Type: release
00:00:01.422824 OS Product: Linux
00:00:01.422825 OS Release: 6.15.0-3-rt2-MANJARO
00:00:01.422826 OS Version: #1 SMP PREEMPT_RT Fri Aug 15 13:17:15 UTC 2025
00:00:01.422858 DMI Product Name: HP Z840 Workstation
00:00:01.422870 DMI Product Version: 
00:00:01.422878 Firmware type: BIOS
00:00:01.422919 Host RAM: 64304MB (62.7GB) total, 62723MB (61.2GB) available
00:00:01.422922 Executable: /usr/lib/virtualbox/VirtualBoxVM
00:00:01.422923 Process ID: 3132
00:00:01.422923 Package type: LINUX_64BITS_GENERIC (OSE)
00:00:01.438879 Installed Extension Packs:
00:00:01.438896   None installed!
00:00:01.440657 Console: Machine state changed to 'Starting'
00:00:01.440981 GUI: Qt version: 6.9.2
00:00:01.440988 GUI: X11 Window Manager code: 4
00:00:01.440992 GUI: HID LEDs sync is not supported on this platform
00:00:01.455814 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.456153 X Server details: vendor: The X.Org Foundation, release: 12101018, protocol version: 11.0, display string: :0
00:00:01.456159 Using XKB for keycode to scan code conversion
00:00:01.458315 SUP: seg #0: R   0x00000000 LB 0x00050000
00:00:01.458340 SUP: seg #1: R X 0x00050000 LB 0x00247000
00:00:01.458343 SUP: seg #2: R   0x00297000 LB 0x00073000
00:00:01.458346 SUP: seg #3: RW  0x0030a000 LB 0x0002db08
00:00:01.518149 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x0 x 1629x995
00:00:01.526322 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 1 work area is actually resized to: 1680x0 x 1629x1018
00:00:01.901148 GUI: UIMediumEnumerator: Medium-enumeration finished!

I’m running Manjaro MATE with the 6.15.0-3-rt2-MANJARO kernel.

Other system stats:

CPU: Intel Xeon E5-2620 v3 (24) @ 3.200GHz
GPU: NVIDIA Quadro K4200

I need this VM to run a couple of old Windows programs for work.

[soundofthunder]

@johnblood

I had to perform a forced reboot

This may well have been the precursor to your issues. It is possible to avoid hard resets or shutdowns using REISUB/REISUO:

[HowTo] reboot / turn off your frozen computer: REISUB/REISUO

Difficulty: ★★☆☆☆ This tutorial was created because people are using a hard power off during freezes, so this will teach you how to turn off your computer when everything is frozen using softer means. So whenever you see someone saying they had to “Power Off” or “Hard Reset” their system without doing a REISUB, please send them here! If you’re reading this in response to a question, please click the green link above this text to bring you to the full unabridged text of the tutorial…

---

@johnblood

I’m running Manjaro MATE with the 6.15.0-3-rt2-MANJARO kernel.

Note that kernel 6.15 reached EOL five months ago and updates are no longer provided from the Manjaro repositories.

It is strongly suggested to switch to another kernel at your earliest convenience – current viable options include kernels 6.17 or 6.12 (LTS) – the latter is generally recommended.

Manjaro Kernels

Linux Kernel

---

@johnblood

I need this VM to run a couple of old Windows programs for work.

Which programs might they be? Perhaps someone will have an alternative to suggest, or a WINE based solution.

---

Please provide system information as described (below) which may allow others to identify other possible contributors to the problem.

I’m sure someone will help when they are able.

Regards.

---

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit.

To that end, links are provided (below) - Please use them.

---

Be prepared to provide outputs from various commands when asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Waiting for others to blindly ask questions can be counter-productive – typically, nobody has a at their disposal – Instead, please help others to make informed suggestions, based on information you provide.

---

Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

inxi --filter --verbosity=8

or the short form (preferred):

inxi -zv8

• inxi man pages (Arch Manual)

@Running `inxi` in `chroot`

If you need to run inxi from within a chroot environment, and find the output is laced with unexpected 12’s, please try again with:

• Add to the long form command: --color=0
• or, change the short form to: inxi -zv8c0

@Your privacy is respected

When inxi is run using the --filter or -z parameters, any personally identifiable information is filtered from the resulting output.

Highly Recommended

• How to Post
• How to Request Support
• How to Post Command Output as Preformatted Text

Technical Resources

• Manjaro Update Announcements
• Manjaro Wiki
• Arch Wiki
• Tutorials

Required Reading

• Forum Rules
• Strict Forum Rules and Guidelines

---

@Notice

The above content is partially pre-prepared as an introduction for new or returning forum Users. Please take the time to follow any links given and discover how to use the Manjaro forum features effectively.

[linux-aarhus]

@johnblood

My system froze, so I had to perform a forced reboot

It is impossible to guess what happened … but your issue look like - albeit which another origin

→ Since May/June 2025: VirtualBox - cannot create new VMs and add existing VMs

→ Virtualbox: cannot create new VMs nor add existing VMs

@johnblood

I’m running Manjaro MATE with the 6.15.0-3-rt2-MANJARO kernel.

I don’t know if your use of an RT kernel is necessary - but if it is - you can get a supported kernel.

I suggest you switch to a supported kernel.

sudo mhwd-kernel -i linux617-rt

Or the LTS version

sudo mhwd-kernel -i linux612-rt

[Nachlese]

@johnblood

with the 6.15.0-3-rt2-MANJARO kernel.

There are reasons to want to run a real time kernel.
For most people it is not a good idea.
Try installing and booting a “normal” one.

[johnblood]

@linux-aarhus

I suggest you switch to a supported kernel.

sudo mhwd-kernel -i linux617-rt

I tried to run that command and got this error:

johnblood@dreadnought ~> sudo mhwd-kernel -i linux617-rt
Error: Please make sure if the given kernel(s) exist(s).
available kernels:
   * linux510
   * linux515
   * linux54
   * linux61
   * linux612
   * linux616
   * linux617
   * linux66
   * linux61-rt
   * linux612-rt
   * linux615-rt
   * linux616-rt
   * linux66-rt

These are the kernels listed in my Manjaro Settings Manager:

[Nachlese]

Then choose one of the

@johnblood

available kernels: ...

preferably one that has not got a -rt extension to it’s name
(unless you actually do need to use a -rt kernel for your specific purpose)

[linux-aarhus]

Yes - I see - 6.17-rt is in testing.

But as I suggested - you also have the option 6.12 as rt.

[johnblood]

@Nachlese

unless you actually do need to use a -rt kernel for your specific purpose

Nope. I’m just a normal user.

[soundofthunder]

A realtime kernel is typically used for specific professional application; music production (as one example), and even then very rarely.

Do you have a valid reason for using a realtime kernel?

If not, I’d strongly suggest using a standard kernel – as mentioned earlier, kernel 6.12 (LTS) or 6.17 are viable.

Of course, older LTS kernels are also available but the presumption is that you don’t want any of those.

@johnblood

@linux-aarhus

I suggest you switch to a supported kernel.

sudo mhwd-kernel -i linux617-rt

I tried to run that command and got this error

I believe the intention was to convey that you shouldn’t be using 6.15…

Note that linux617-rt is not (yet) available to Stable branch, but it is in Unstable and Testing. You *could’ switch to either of these branches to use that kernel immediately; or you could wait until it reaches Stable.

Manjaro Kernels

---

Edit:-

@johnblood

@Nachlese

unless you actually do need to use a -rt kernel for your specific purpose

Nope. I’m just a normal user.

A realtime kernel gives you no advantage;
Use one of the initially suggested kernels instead.

[BG405]

Just to add my 2p worth:

A while back I tried a real-time Kernel and found that VirtualBox would not run correctly (locked up after a short period).

[linux-aarhus]

I have done some superficial research on the topic of a default Linux kernel and the real-time kernel - dubbed (RT).

I won’t pretend I know a lot - but from my reading - I got the bigger picture.

Some applications are very sensitive to the timing when receiving and processing data from multiple sources - the completion time must be known beforehand.

One example is an A/V mixing application which may receive input from numerous sources at the same time - thus such application may benefit from RT kernel.

I am saying may because recent kernels have some built in configuration which makes it next to obsolete to use a special RT kernel.

[SOLVED] Real time kernel packaging / Kernel & Hardware / Arch Linux Forums

So my initial suggest still stands - remove the RT kernel - unless you specifically know you require a kernel compiled for RT for use with a given application.

@johnblood

Nope. I’m just a normal user.

As per you own comment - you don’t need an RT kernel - and with reference to

@BG405

A while back I tried a real-time Kernel and found that VirtualBox would not run correctly (locked up after a short period).

It is the advise to remove the RT kernel and use the default provided in the repo either the current mainline stable linux617 or the current LTS linux612.

Check the running kernel

mhwd-kernel -li

Then - if the running kernel is linux615-rt - run the following command

sudo pacman -Syu
sudo mhwd-kernel -i linux617 rmc

Otherwise run

sudo mhwd-kernel -i linux617

Finally restart your system - ensure you hit grub menu using a hotkey and verify if the issue persist.

Real-time operating system

[johnblood]

Sorry for not replying sooner. I switched to the 6.17 kernel and now VirtualBox works. I didn’t realize that it would cause an issue because I’ve been on an rt kernel for several months without issue. Thanks for all your help.

[BG405]

Glad it’s working now; however, it is customary to mark the post which most helped you as the Solution.

Cheers

[soundofthunder]

@johnblood

I switched to the 6.17 kernel and now VirtualBox works.

Then let’s mark the post that makes better sense as the solution, shall we.