You are not logged in.
Hi,
running a Windows 11 (64-bit) guest works, with the exception that the shutdown does not end, but this was already a problem under 7.0.20-1, which I can live with.
Using 7.0.20-1, a Windows 10 (64-bit) guest, including the shutdown, worked perfectly smoothly. Unfortunately, the Windows 10 startup freezes using 7.1.0-1. Its log ends with "00:01:40.881013 EHCI: USB Suspended".
By the manager I changed a few settings, to use mainly the same settings for the Windows 10 guest, that are used by the Windows 11 guest. In addition I migrated from USB 2.0 to USB 1.1 for the Windows 10 guest. Now USB is operational and I couldn't see any useful information by the log file.
Has anyone had similar experiences?
FWIW pacman.log mentions an issue:
[2024-09-13T05:02:52+0200] [ALPM] upgraded virtualbox (7.0.20-1 -> 7.1.0-1)
[2024-09-13T05:02:52+0200] [ALPM-SCRIPTLET] VBoxManage: error: Failed to create the VirtualBox object!
[2024-09-13T05:02:52+0200] [ALPM-SCRIPTLET] VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
After restarting the host trying to start the VirtualBox manager GUI for the first time also failed with the object error, but after that it always started without an issue.
extra/virtualbox 7.1.0-1
extra/virtualbox-guest-iso 7.1.0-1
extra/virtualbox-host-dkms 7.1.0-1
chaotic-aur/virtualbox-ext-oracle 7.1.0-1
$ uname -r; cat /proc/cmdline
6.10.9-arch1-2
BOOT_IMAGE=/boot/vmlinuz-linux root=/dev/disk/by-label/m1.archlinux ro threadirqs ibt=off
Regards,
Ralf
Last edited by Ralf (2024-09-15 11:49:47)
Offline
It appears that you're using the standard Arch kernel, in which case you need the "virtualbox-host-modules-arch" package instead of "virtualbox-host-dkms".
if [[ $yourProblem = "fixed" ]] ;then
sed -i 's/Title/[SOLVED] Title/g' your.thread | please --thank-you
fi
Offline
Hi,
yesno [1]. I guess the last rt patched kernels that worked with virtualbox were 4.19 kernels I build myself. Since I don't use kernels build by myself anymore and linux-rt >4.19 unlikely works with virtualbox, I can migrate to extra/virtualbox-host-modules-arch and virtualbox-host-modules-lts.
# mkdir -p /usr/lib/modules/dkms_copies_for_diff{6.6.51-1-lts,6.10.9-arch1-2}
# cp -ai /usr/lib/modules/6.6.51-1-lts/updates/dkms/* /usr/lib/modules/dkms_copies_for_diff6.6.51-1-lts/
# cp -ai /usr/lib/modules/6.10.9-arch1-2/updates/dkms/* /usr/lib/modules/dkms_copies_for_diff6.10.9-arch1-2/
$ sudo pacman -Syu virtualbox-host-modules-arch virtualbox-host-modules-lts
[snip]
Packages (3) virtualbox-host-dkms-7.1.0-1 [removal] virtualbox-host-modules-arch-7.1.0-1 virtualbox-host-modules-lts-7.1.0-2
[snip]
$ cd /usr/lib/modules/
$ diff -r 6.10.9-arch1-2/extramodules/ dkms_copies_for_diff6.10.9-arch1-2/
Binary files 6.10.9-arch1-2/extramodules/vboxdrv.ko.zst and dkms_copies_for_diff6.10.9-arch1-2/vboxdrv.ko.zst differ
Binary files 6.10.9-arch1-2/extramodules/vboxnetadp.ko.zst and dkms_copies_for_diff6.10.9-arch1-2/vboxnetadp.ko.zst differ
Binary files 6.10.9-arch1-2/extramodules/vboxnetflt.ko.zst and dkms_copies_for_diff6.10.9-arch1-2/vboxnetflt.ko.zst differ
$ diff -r 6.6.51-1-lts/extramodules/ dkms_copies_for_diff6.6.51-1-lts/
Only in dkms_copies_for_diff6.6.51-1-lts/: r8125.ko.zst
Binary files 6.6.51-1-lts/extramodules/vboxdrv.ko.zst and dkms_copies_for_diff6.6.51-1-lts/vboxdrv.ko.zst differ
Binary files 6.6.51-1-lts/extramodules/vboxnetadp.ko.zst and dkms_copies_for_diff6.6.51-1-lts/vboxnetadp.ko.zst differ
Binary files 6.6.51-1-lts/extramodules/vboxnetflt.ko.zst and dkms_copies_for_diff6.6.51-1-lts/vboxnetflt.ko.zst differ
# shutdown -r now
$ sudo pacman -Syu virtualbox-ext-oracle
[snip]
warning: ignoring package replacement (virtualbox-host-modules-lts-7.1.0-2 => virtualbox-host-dkms-7.1.0-1)
[snip]
Packages (1) virtualbox-ext-oracle-7.1.0-2
[snip]
$ pacman -Ql virtualbox-ext-oracle | tail -1
virtualbox-ext-oracle /usr/share/virtualbox/extensions/Oracle_VirtualBox_Extension_Pack-7.1.0.vbox-extpack
After the upgrade from virtualbox-ext-oracle 7.1.0-1 to 7.1.0-2 I used the Oracle VirtualBox manager to uninstall and install the extension pack, then I tried to start the Windows 10 (64-bit) guest. The Windows 10 guest does still freeze at startup and the virtualbox window is still unresponsive, so that I need to run "$ sudo pkill VirtualBoxVM".
Using the Windows 11 guest still works, excepted that it still doesn't finish a shut down, hence also a "$ sudo pkill VirtualBoxVM" is required, but at least Windows 11 seems to be usable.
Regards,
Ralf
[1]
core/linux 6.10.9.arch1-2
core/linux-lts 6.6.51-1
extra/linux-rt 6.10.2.rt14.arch1-2
$ /bin/ls -hAltr /usr/lib/modules/*/updates/dkms/
/usr/lib/modules/6.10.9-arch1-2/updates/dkms/:
total 324K
-rw-r--r-- 1 root root 240K Sep 13 05:03 vboxdrv.ko.zst
-rw-r--r-- 1 root root 49K Sep 13 05:03 vboxnetflt.ko.zst
-rw-r--r-- 1 root root 31K Sep 13 05:03 vboxnetadp.ko.zst
/usr/lib/modules/6.6.51-1-lts/updates/dkms/:
total 420K
-rw-r--r-- 1 root root 102K Sep 13 04:59 r8125.ko.zst
-rw-r--r-- 1 root root 239K Sep 13 05:03 vboxdrv.ko.zst
-rw-r--r-- 1 root root 46K Sep 13 05:03 vboxnetflt.ko.zst
-rw-r--r-- 1 root root 26K Sep 13 05:03 vboxnetadp.ko.zst
/usr/lib/modules/6.10.2-rt14-arch1-2-rt/updates/dkms/:
total 332K
-rw-r--r-- 1 root root 241K Sep 13 05:03 vboxdrv.ko.zst
-rw-r--r-- 1 root root 51K Sep 13 05:03 vboxnetflt.ko.zst
-rw-r--r-- 1 root root 33K Sep 13 05:03 vboxnetadp.ko.zst
Last edited by Ralf (2024-09-14 07:59:17)
Offline
Network also isn't working for my Windows 10 guest anymore, after one of the recent pacman updates. No special config here, standard arch kernel (6.10.10-arch1-1) and these packages:
virtualbox 7.1.0-1
virtualbox-guest-iso 7.1.0-1
virtualbox-host-modules-arch 7.1.0-2
I've found a similar complaint on the VirtualBox Forums: https://forums.virtualbox.org/viewtopic.php?p=550582
So maybe it's an issue of VirtualBox 7.1 and has nothing to do with Arch.
Offline
I just remembered that I currently have a Windows 11 VM myself, and I just checked if I'm having any problems with 1.7.0-1 as well. Upon starting the VM the first time, it froze during boot for me as well. Then I made one change to the settings, switching from USB 3.0 to 1.1 like you did (1), tried booting again, and it worked. Shutting down also succeeded without problems.
Here is a screenshot of all my settings
(1) This method also worked earlier this year when I couldn't start any VMs after an update. It's quite typical for VirtualBox to break after an update, though in my experience there is always some way for the user to fix it. Best keep an eye on the VirtualBox forums for a solution.
if [[ $yourProblem = "fixed" ]] ;then
sed -i 's/Title/[SOLVED] Title/g' your.thread | please --thank-you
fi
Offline
Hi,
only the shortened story.
Migrating from Arch repos to https://download.virtualbox.org/virtual … _amd64.run (most likely) solved the issues. At least a Windows 10 (64-bit) guest as well as a Windows 11 (64-bit) guest are able to start, to download and to install updates and to shut down successfully.
The whole story might be too long to read.
My complete thread on arch-general, including the complete story how I finally was able to solve all issues: https://lists.archlinux.org/archives/li … GPPJGMTBV/
Another related thread on the Arch Linux forums: https://bbs.archlinux.org/viewtopic.php?id=299392
Regards,
Ralf
Offline