Arch Linux

Ran into this myself today. I was trying to stay on VB 6.1.40 for as long as I could but the OpenSSL 3.0 rebuild forced my hand.

The VM appears to be running per the log and Manager's activity page. Issuing an ACPI shutdown is successful. It appears the display may simply be mangled.

FWIW, I dual boot with Debian Stable for exactly this kind of reason. I booted the VM from Debian and downgraded GA to 6.1.40.

Back in Arch that did not resolve the issue... the Win11 VM is still busted. However this does appear to be specific to Win11 guest as my Win10 guest boots just fine and is running GA 7.0.2.

Attaching my log if it may help

Hi,

after downgrading the Arch guest additions package, installing the downgraded guest additions by the Windows 11 guest and restarting the Windows 11 guest, it is running for several minutes now without freezing.

$ uname -r; cat /proc/cmdline; pacman -Q virtualbox{,-ext-oracle,-guest-iso,-host-dkms}
6.0.8-arch1-1
BOOT_IMAGE=../vmlinuz-linux root=LABEL=s3.archlinux ro threadirqs initrd=../intel-ucode.img,../initramfs-linux.img
virtualbox 7.0.2-2
virtualbox-ext-oracle 7.0.2-1
virtualbox-guest-iso 6.1.40-1
virtualbox-host-dkms 7.0.2-2

Regards,
Ralf

That didn't work for me. Fortunately the VM boots just fine under Debian with VB 6.1.40 so this is simply an annoyance until resolved.

$ uname -r; cat /proc/cmdline; pacman -Q virtualbox{,-ext-oracle,-guest-iso,-host-dkms}
6.0.8-arch1-1
initrd=\intel-ucode.img initrd=\initramfs-linux.img root=UUID=d475ae3e-f8c5-4e02-9c23-541d4667d78e rw pci=noaer ibt=off nvidia_drm.modeset=1 module_blacklist=snd_hda_intel
virtualbox 7.0.2-2
error: package 'virtualbox-ext-oracle' was not found
virtualbox-guest-iso 6.1.40-1
virtualbox-host-dkms 7.0.2-2

This is all I see when booting the Win11 VM:
https://postimg.cc/MM9J8F0n

EDIT1: Not that I really suspected this to be related to kernel version but the Win11 VM also fails booting when my Arch host is using the LTS kernel 5.15.77-1 but successfully boots via Debian with kernel 5.15.77 I compiled.
EDIT2: If I disable the 3D Acceleration option the VM boots successfully. Not really a viable workaround as I need full resolution, but hopefully helps narrow the issue.
EDIT3: Looks like I _can_ get full resolution with 3D Acceleration disabled. I was then able to install GA 7.0.2 and the VM is fully functional, albeit without the aforementioned 3D Acceleration.

Per this gnome-shell issue:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6054

I built mutter 43.1 with 7e7a639c reverted:
https://gitlab.gnome.org/GNOME/mutter/-/commit/7e7a639cc5132cf3355e861235f325540fe56548

The Virtualbox issue is no longer reproducible. Bonus - some other funky stuff like broken text highlighting in firefox and borked dash-to-panel extension are working properly again too.

Hi, mutter isn't installed on my machine. I run openbox sessions without a desktop environment. Regards, Ralf

[virtualbox 7.0.2] doesn't work with a Windows 11 guest on an Arch Linux host
Upstream ticket: https://www.virtualbox.org/ticket/21268

Hi,

while downgraded guest additions solved a freeze issue with a Windows 11 guest, USB is broken.

There are no issues with a Windows 7 or a Windows 10 guest.

$ uname -r; pacman -Q virtualbox
4.19.255-rt113-0.1000
virtualbox 7.0.2-2

Windows 7

guest never updated to guest additions version 7.0.2r154219
now at version 6.1.40r154048
USB 2.0 enabled does work with my iPads connected by USB

Windows 10

guest updated to guest additions version 7.0.2r154219
now at version 7.0.2r154219
USB 2.0 enabled does work with my iPads connected by USB

Windows 11

guest updated to guest additions version 7.0.2r154219 does cause freezes
downgraded to guest additions version 6.1.40r154048
now at version 6.1.40r154048 no freezes anymore, but
USB 2.0 as well as USB 1.1 enabled do n o t work with my iPads

For more details, see [snip]

https://forums.virtualbox.org/viewtopic.php?f=7&t=107757

https://bbs.archlinux.org/viewtopic.php?id=281196

arch-general@lists.archlinux.org/thread/GSDRGWQEULBUM254XGBZLX7NCFWF5FCE/#GSDRGWQEULBUM254XGBZLX7NCFWF5FCE"> https://lists.archlinux.org/archives/list/arch-general@lists.archlinux.org/thread/GSDRGWQEULBUM254XGBZLX7NCFWF5FCE/#GSDRGWQEULBUM254XGBZLX7NCFWF5FCE

Regards,

Ralf

So the only difference between 7.0.2-1 and 7.0.2-2 is OpenSSL 3.0. It's hard to fathom that Windows 11 failing is somehow an Arch packaging bug. It seems likely upstream need to get their stuff working with OpenSSL 3.0. I cannot see an openssl version number mentioned here [1]. I wonder if other distros are building VB against OpenSSL 3.0?

[1] https://www.virtualbox.org/wiki/Linux%20build%20instructions

Obviously an upstream bug in 7.0.2 does cause an incompatibility with Windows 11. Since installing Windows 11 as a virtualbox guest is already tricky, I'm not surprised.
I build virtualbox 6.1.40 against core/openssl 3.0.7-2 and there are no issues at all when running the Windows 11 guest in virtualbox 6.1.40.
The script to build it in a clean chroot: https://pastebin.com/sKzMmun4

$ pacman -Qi virtualbox virtualbox-host-dkms virtualbox-guest-iso|grep -eVe -ed\ D
Version : 1:6.1.40-702.2
Build Date : Sun 13 Nov 2022 21:24:27 CET
Version : 1:6.1.40-702.2
Build Date : Sun 13 Nov 2022 21:24:27 CET
Version : 6.1.40-1
Build Date : Sat 15 Oct 2022 12:18:22 CEST
$ /usr/bin/ls -l /usr/share/virtualbox/extensions/*
-rw-r--r-- 1 root root 11233264 Oct 11 18:15 /usr/share/virtualbox/extensions/Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-extpack

Building virtualbox takes around 50 minutes on my machine, if there is a bump of the community/virtualbox 7.0.2 pkgrel, to rebuild it against updated dependencies, I'll try to rebuild virtualbox 6.1.40, too.
For the time being this seems to be the only workaround.

Is this still happening with latest pkg updates?

My apologies,

it's on my todo list. It is unlikely that I can risk to break my working environment before February or March. At the moment I need to rely on the Windows 11 guest to run properly, so I compile 6.1.40 against shared library updates whenever necessary.

Regards,
Ralf

$ pacman -Q virtualbox
virtualbox 7.0.4-3

After installing the new guest additions I can move the mouse, but after a while neither host, nor Windows 11 guest care about mouse clicks anymore. Strg+Alt+F2 and "kill -9" PID of virtualbox processes makes the host responsive again.

To my knowledge, W11 cannot be used with VB7 on Arch ATM. Is this an Arch issue? What do Arch devs need to fix?
It's quite annoying that I cannot use W11 within my usual work environment since several months.

I suspect it's got nothing to do with Arch specifically, but rather the combo of Win11 guest under VB 7.0.x with GA 7.0.x.

See the following upstream bug reports:

Freezes:
https://www.virtualbox.org/ticket/21291
https://www.virtualbox.org/ticket/21431
https://www.virtualbox.org/ticket/21448
https://www.virtualbox.org/ticket/21492

Artifacts / 3D Accel:
https://www.virtualbox.org/ticket/21136
https://www.virtualbox.org/ticket/21233
https://www.virtualbox.org/ticket/21433
https://www.virtualbox.org/ticket/21515

And Virtualbox forums thread:
https://forums.virtualbox.org/viewtopic.php?f=7&t=108440&p=532943#p532943

I continue to employ the workaround of using (currently) 6.1.42 GA with VB 7.0.6.
When using the older Guest Additions none of the linked issues occur.

On my old Intel hardware I could run a Windows 11 guest when using virtualbox 6.1.40 build in a clean chroot. On my new Intel hardware neither virtualbox 6.1.40 build in a clean chroot, nor community/virtualbox 7.0.8-1 do run at all.

$ grep "virtualbox (" /var/log/pacman.log | grep grade | tail -2
[2023-04-19T07:11:33+0200] [ALPM] upgraded virtualbox (1:6.1.40-706.3 -> 1:6.1.40-708.1)
[2023-04-19T11:03:17+0200] [ALPM] downgraded virtualbox (1:6.1.40-708.1 -> 7.0.8-1)
$ hwinfo --cpu | grep Model | sort -u
Model: 6.191.5 "13th Gen Intel(R) Core(TM) i3-13100"
$ cat /sys/devices/virtual/dmi/id/board_{vendor,name}
Gigabyte Technology Co., Ltd.
B760M DS3H DDR4

JFTR QEMU/KVM does run on the new hardware, too. I only use it for a Linux guest without sharing data between host and guest.
I don't have much time at the moment and I'm considering whether I should spend the time troubleshooting virtualbox or converting Windows 7, 10 and 11 for use with QEMU/KVM and learning how to share data between guest and host.

CPU: 12th Gen Intel i9-12900K
GPU: NVIDIA GeForce GTX 1050 Ti

Running virtualbox 7.0.8-1 with Win11 guest all morning without issue here simply by installing Guest Additions 6.1.44.

Using Guest Additions 7.0.8 results in the same guest unresponsive/freeze as reported upstream in the various tickets I linked.

Nothing informative is logged at the time of freeze, just:
0:02:52.712472 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

I have a Debian partition on this system. When I have time I'll install 7.0.8 on there and see if I can reproduce freeze.

If I can reproduce the Win11 guest freeze on Debian, I'll unsubscribe from this flyspray, having absolved Arch in the matter.