Hi, the shortened story first. Migrating from Arch repos to https://download.virtualbox.org/virtualbox/7.1.0/VirtualBox-7.1.0-164728-Linux_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 Windows and iTunes 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/list/arch-general@xxxxxxxxxxxxxxxxxxx/thread/GAKLLN3QMEO4EUY45B6UTVKGPPJGMTBV/ My whole thread on Arch Linux forums without my detailed description: https://bbs.archlinux.org/viewtopic.php?pid=2196023 Another related thread on the Arch Linux forums: https://bbs.archlinux.org/viewtopic.php?id=299392 I uninstalled everything VirtualBox related from the repositories and then installed from virtualbox.org. • rocketmouse@archlinux ~ $ mkdir /.tmp/VirtualBox-7.1.0-164728 • rocketmouse@archlinux ~ $ cd /.tmp/VirtualBox-7.1.0-164728/ • rocketmouse@archlinux /.tmp/VirtualBox-7.1.0-164728 $ wget https://download.virtualbox.org/virtualbox/7.1.0/VirtualBox-7.1.0-164728-Linux_amd64.run [snip] • rocketmouse@archlinux /.tmp/VirtualBox-7.1.0-164728 $ chmod a+x VirtualBox-7.1.0-164728-Linux_amd64.run • rocketmouse@archlinux /.tmp/VirtualBox-7.1.0-164728 $ ./VirtualBox-7.1.0-164728-Linux_amd64.run --help [snip] • rocketmouse@archlinux /.tmp/VirtualBox-7.1.0-164728 $ su Password: • root@archlinux /.tmp/VirtualBox-7.1.0-164728 # ./VirtualBox-7.1.0-164728-Linux_amd64.run --accept Verifying archive integrity... 100% MD5 checksums are OK. All good. Uncompressing VirtualBox for Linux installation 100% VirtualBox Version 7.1.0 r164728 (2024-09-06T16:34:41Z) installer Installing VirtualBox to /opt/VirtualBox Python found: python2.7, installing bindings... Python found: python3.12, installing bindings... ./routines.sh: line 408: 106965 Segmentation fault (core dumped) $SHELL -c "cd ${PYTHON_INSTALLER_PATH} && ${PYTHON_BIN} ./vboxapisetup.py install --record $CONFIG_DIR/python-$CONFIG_FILES" A copy of VirtualBox is currently running. Please close it and try again. Please note that it can take up to ten seconds for VirtualBox to finish running. VirtualBox has been installed successfully. You will find useful information about using VirtualBox in the user manual /opt/VirtualBox/UserManual.pdf and in the user FAQ http://www.virtualbox.org/wiki/User_FAQ We hope that you enjoy using VirtualBox. The installation log file is at /var/log/vbox-install.log. Opening Oracle VirtualBox manager works. But you never know, and doing something stupid can't hurt. • root@archlinux /.tmp/VirtualBox-7.1.0-164728 # ps aux | grep -i -e[v]box -e[v]irtual root 108921 0.0 0.0 0 0 ? I< 11:24 0:00 [kworker/R-iprt-VBoxWQueue] root 108924 0.0 0.0 0 0 ? S 11:24 0:00 [iprt-VBoxTscThread] • root@archlinux /.tmp/VirtualBox-7.1.0-164728 # kill -9 108921 108924 • root@archlinux /.tmp/VirtualBox-7.1.0-164728 # ps aux | grep -i -e[v]box -e[v]irtual root 108921 0.0 0.0 0 0 ? I< 11:24 0:00 [kworker/R-iprt-VBoxWQueue] root 108924 0.0 0.0 0 0 ? S 11:24 0:00 [iprt-VBoxTscThread] • root@archlinux /.tmp/VirtualBox-7.1.0-164728 # ./VirtualBox-7.1.0-164728-Linux_amd64.run --accept Verifying archive integrity... 100% MD5 checksums are OK. All good. Uncompressing VirtualBox for Linux installation 100% VirtualBox Version 7.1.0 r164728 (2024-09-06T16:34:41Z) installer Removing previous installation of VirtualBox 7.1.0 r164728 from /opt/VirtualBox Installing VirtualBox to /opt/VirtualBox Python found: python2.7, installing bindings... Python found: python3.12, installing bindings... /tmp/selfgz11025711484/routines.sh: line 408: 111635 Segmentation fault (core dumped) $SHELL -c "cd ${PYTHON_INSTALLER_PATH} && ${PYTHON_BIN} ./vboxapisetup.py install --record $CONFIG_DIR/python-$CONFIG_FILES" A copy of VirtualBox is currently running. Please close it and try again. Please note that it can take up to ten seconds for VirtualBox to finish running. VirtualBox has been installed successfully. You will find useful information about using VirtualBox in the user manual /opt/VirtualBox/UserManual.pdf and in the user FAQ http://www.virtualbox.org/wiki/User_FAQ We hope that you enjoy using VirtualBox. • root@archlinux /.tmp/VirtualBox-7.1.0-164728 # exit • rocketmouse@archlinux /.tmp/VirtualBox-7.1.0-164728 $ wget https://download.virtualbox.org/virtualbox/7.1.0/Oracle_VirtualBox_Extension_Pack-7.1.0.vbox-extpack --2024-09-15 11:45:50-- https://download.virtualbox.org/virtualbox/7.1.0/Oracle_VirtualBox_Extension_Pack-7.1.0.vbox-extpack Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt' Resolving download.virtualbox.org (download.virtualbox.org)... 95.101.196.74 Connecting to download.virtualbox.org (download.virtualbox.org)|95.101.196.74|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 22885754 (22M) [text/plain] Saving to: ‘Oracle_VirtualBox_Extension_Pack-7.1.0.vbox-extpack’ Oracle_VirtualBox_Extension_Pack-7.1.0.vbox-ext 100%[======================================================================================================>] 21.83M 6.92MB/s in 3.2s 2024-09-15 11:45:54 (6.92 MB/s) - ‘Oracle_VirtualBox_Extension_Pack-7.1.0.vbox-extpack’ saved [22885754/22885754] I opened VirtualBox Manager again. For some reason File > Tools > Extention Pack Manager claims that 6.1.50r161033 is active. Actually the last installed extension pack was 7.1.0. After removing the extension pack I installed the downloaded 7.1.0 extension pack. The Windows 11 guest started by a fbpanel menu entry and run successfully, but a shut down doesn't finish, I needed to switch to tty2 and run # pkill VirtuialBoxVM. The Windows 10 guest failed to start 2 or more times by a fbpanel menu entry. The Window appeared and closed immediately. The Windows 10 guest started and run successfully when using VirtualBox Manager. A shut down failed, but I could use a GUI terminal emu to run # pkill VirtualBoxVM. Again I tried to start the Windows 11 guest by a fbpanel menu entry exactly 2 times, it failed, but starting by VirtualBox Manager works. Checking the guest additions confirmed that I already installed them when using Virtualbox from the repositories. The shut down failed, but I was able to use a GUI teminal emu to run pkill. Again I started the Windows 10 guest this time via VirtualBox Manager in the first place. The guest additions were still 7.0.20, so I installed the current guest additions and restarted the guest, no pkill was required. A check confirmed that the 7.1.0 guest additions are installed. Shut down didn't finish, running pkill could be run by a GUI terminal emu. For the Windows 10 guest I changed the chipset from ICH9 to PIIX3 which I used originally for Windows 10. Now Windows 10 does start, run and shut down. For the Windows 11 guest I changed the chipset from ICH9 to PIIX3. ICH9 worked with Virtualbox 6. It failed to start and even failed to start when reverting to PIIX3 with some strange memory error. I closed and opened the Manager .... Hm? After restarting the Arch Linux host starting, running and shutting down the Windows 11 guest, this time with chipset PIIX3 worked, vie the Manager and via the fbpanel menu. I forgot to revert USB from 1.1 to 2.0 for the Windows 10 guest, a setting I changed when VirtualBox from the repositories failed to work, so I set it to 2.0. again. Ok, now a test including the network. 1. Windows 10 (64-bit) started by my fbpanel entry 1.1 Startup: ok 1.2 Network: Downloading and installing Windows updates worked Downloading and installing an iTunes update worked, too 1.3 Restart: ok 1.4 Shut down: ok 2. Windows 11 (64-bit) started by my fbpanel entry 2.1 Startup: ok 2.2 Network: Checking for Windows updates worked, but non were available. Downloading and installing an iTunes update worked 2.3 Restart: ok 2.4 Shut down: ok Regards, Ralf
