virtualbox 7.0.16 and Windows 11 guest
Hi, today I removed virtualbox6.1-bin 6.1.50 and installed virtualbox 7.0.16, because 6.1.50 doesn't work anymore [1] and I got rid of fixing virtualbox 6+ again and again. Doing a first short test a Windows 10 guest seems to run, but a Windows 11 guest seems to cause issues, at least a shutdown of the Windows 11 guest with _not_ updated guest additions didn't finish and locked the host or rather it was possible to push Ctrl+Alt+F2 and to run pkill VirtualBoxVM to get back a responding Arch Linux host. For other reasons I'm restoring another backup of Windows 11, which will take more than an hour, since the the vdi's size is > 700 GiB, so in the meantime I want to gather information. I will take a look at the settings mentioned by the Arch Wiki [2], [3]. Are there more settings I can check? It's an Intel CPU wit integrated GPU. • rocketmouse@archlinux ~ $ hwinfo --cpu | sort -u | grep Model Model: 6.191.5 "13th Gen Intel(R) Core(TM) i3-13100" • rocketmouse@archlinux ~ $ hwinfo --memory | grep Size Memory Size: 32 GB Regards, Ralf [1] "Could you still start Windows guests with virtualbox6.1-bin 6.1.50-1 or do you also experience guru meditations? I'm currently trying extra/virtualbox 7.0.16-1, which gets rid of the gurus, but so far a Windows 11 guest is not doing well." - https://aur.archlinux.org/pkgbase/virtualbox6.1-bin#comment-968033 [2] "4.11.1 Creating the virtual machine A VirtualBox virtual machine must be manually created. As of now do not add any storage device any disk to the virtual machine, it will be done manually later. Configure the virtual machine with the following settings (settings panel can be opened by clicking the "Settings" button in the main toolbar): View: System: Tab: Motherboard: mark Enable I/O APIC; mark Enable EFI; mark Hardware Clock in UTC Time if is your case. Tab: Processor: mark Enable PAE/NX; mark Enable Nested VT-x/AMD-V; Tab: Acceleration: Choose the paravirtualization interface Hyper-V from the drop down menu; mark Enable Nested Paging. Optionally you can enable also the following settings: View: Display Tab: Screen mark Enable 3D Acceleration. Note that it could cause glitches. Note: The Hyper-V setting is not required in order for the system to operate correctly, but it may help avoid licensing issues." - https://wiki.archlinux.org/title/VirtualBox#Creating_the_virtual_machine [3] "5.22 Random freezing in guests with Intel GPU With Intel CPU and graphics, allocating more processors for the guest can lower render performance, thus cause random freezing. Allocating less processors can help." - https://wiki.archlinux.org/title/VirtualBox#Random_freezing_in_guests_with_I...
PS: After restoring the wanted Windows 11 state from a backup, which was faster than expected, I ensured that all settings are as mentioned by the Arch Wiki: "Enable I/O APIC" was already checked "Enable EFI" was already checked "Enable PAE/NX" was already checked "Enable Nested VT-x/AMD-V" was already checked Processors was set to 2 CPUs. I changed it to 1 CPU. "Hyper-V" was already selected "Nested Paging" was already checked "3D Acceleration" was already disabled Apart from this I resized the vdi from "Virtual Size 740.00 GB / Actual Size 723.02 GB" to ""Virtual Size 840.00 GB". At next I started the Windows 11 guest, upgraded the guest additions and restarted the Windows 11 guest. The next step was to shutdown the Windows 11 guest. It seems to be unable to finish the shutdown, but at least the host isn't locked yet. The Window title bar shows "[Stopping]" and the Window contend is a black screen.
On 4/18/24 03:21, Ralf Mardorf wrote:
At next I started the Windows 11 guest, upgraded the guest additions and restarted the Windows 11 guest. The next step was to shutdown the Windows 11 guest. It seems to be unable to finish the shutdown, but at least the host isn't locked yet.
The Window title bar shows "[Stopping]" and the Window contend is a black screen.
You are far braver than I. I'm still running 6.50, but have no Win11 - and no problems. I'll get to 7x as soon as I have time to set aside to go through what you are going through. In the past on both 5x and 6x I've run into "windows hangs on shutdown" issues with virtualbox. I've straced the sessions and sent that info to the vbox devs and there hasn't been a "this is the problem, we can fix it moment". However, I've not experienced one of those hang on shutdown issues in a long time (year or so). All guests are Win10, Win7 (even old XP), Arch, SuSE, and a smattering of stray distros. One issue I do recall that caused some issues in the 5x - 6x change was the default video driver vbox uses. I've had less problems sticking with the legacy driver running vbox on Linux. At least worth a check to see if that may be a subtle issue, if only part of the problem. Good luck, and drop many breadcrumbs for those that are following behind you ... -- David C. Rankin, J.D.,P.E.
On Fri, 2024-04-19 at 00:43 -0500, David C. Rankin wrote:
Good luck, and drop many breadcrumbs for those that are following behind you ...
David, I hope I can gain some time by a workaround to continue using virtualbox 7 [1]. However, I consider to migrate my Windows guests or at least the Windows 11 guest to QEMU. It's just that I don't have time at the moment to learn how to set up Samba or to follow any alternative approach mentioned by https://wiki.archlinux.org/title/QEMU#Sharing_data_between_host_and_guest . I'm already running a QEMU/KVM Linux guest using Virtual Machine Manager. It's as easy as using virtualbox, just sharing data isn't that straight forward. Virtualbox 6.1.50 doesn't work anymore on my machine [2]. Maybe I just need to rebuild it against some probably updated dependency or maybe I need to downgrade the kernel or to run the LTS kernel or ... or ... [1] https://bbs.archlinux.org/viewtopic.php?pid=2165804#p2165804 [2] https://aur.archlinux.org/pkgbase/virtualbox6.1-bin#comment-968033
Am Freitag, dem 19.04.2024 um 09:03 +0200 schrieb Ralf Mardorf:
On Fri, 2024-04-19 at 00:43 -0500, David C. Rankin wrote:
Good luck, and drop many breadcrumbs for those that are following behind you ...
David, I hope I can gain some time by a workaround to continue using virtualbox 7 [1]. However, I consider to migrate my Windows guests or at least the Windows 11 guest to QEMU. It's just that I don't have time at the moment to learn how to set up Samba or to follow any alternative approach mentioned by https://wiki.archlinux.org/title/QEMU#Sharing_data_between_host_and_guest . I'm already running a QEMU/KVM Linux guest using Virtual Machine Manager. It's as easy as using virtualbox, just sharing data isn't that straight forward.
Virtualbox 6.1.50 doesn't work anymore on my machine [2]. Maybe I just need to rebuild it against some probably updated dependency or maybe I need to downgrade the kernel or to run the LTS kernel or ... or ...
I came across this article to set up a Windows VM using docker: https://linuxtldr.com/windows-docker-container/ Not sure how feasible it is though. But since I might have to deal with Windows in the near future it looks tempting to me. KR Frank
On Fri, 2024-04-19 at 16:47 +0200, Frank wrote:
Thank you. The article doesn't mention how to share data between "host" and "guest"/container. The article doesn't mention, if it's possible to migrate the license from my current Windows 11 install to the Docker's Windows 11. Another problem might or might not be licenses of the installed software. IIUC the Affinity license allows me to install Photo 2, Designer 2 and Publisher 2 on as much Windows machines that I own. While I'm using Pianoteq only on Linux and iPadOS, I don't really understand the "activation slot" model and I'm unsure, if I'm missing something comparable to the Pianoteq's "activation slot" model for my Affinity V2 Universal Licence. At least I need to carefully read the terms of the Affinity V2 Universal Licence first. However, another pitfall is, that it was very, very time consuming and annoying to get rid of almost all the undesirable features, odd recommendations, advertisements and manipulative messages of a default Windows 11 install. My Windows 11 is nearly as clean as my Arch Linux Openbox. It wasn't easy for me to get Windows 11 that clean. I don't know if converting the existing Windows 11 vdi to a QEMU/KVM format does work without breaking licenses, but at least it's not a completely new install, so chances are probably quite good, that a migration doesn't cause licensing issues.
On Fri, 2024-04-19 at 16:47 +0200, Frank wrote:
Thank you. The article doesn't mention how to share data between "host" and "guest"/container. The article doesn't mention, if it's possible to migrate the license from my current Windows 11 install to the Docker's Have you been able to further advance, either witht he docker setup or your Virtualbox? I installed Win in the above mentioned docker container and that went
Am Freitag, dem 19.04.2024 um 17:31 +0200 schrieb Ralf Mardorf: pretty smooth, though I haven't figuered out how to share data with the host. One issue I have is that there's no sound output, does this work with Virtualbox? Frank
Am Mittwoch, dem 05.06.2024 um 13:59 +0200 schrieb Frank:
Am Freitag, dem 19.04.2024 um 17:31 +0200 schrieb Ralf Mardorf:
On Fri, 2024-04-19 at 16:47 +0200, Frank wrote:
I installed Win in the above mentioned docker container and that went pretty smooth, though I haven't figuered out how to share data with the host. One issue I have is that there's no sound output, does this work with Virtualbox? Frank ok, I've been playing around a little more and with the right settings in Remmina I can connect to the container via RDP incl. data sharing between host and client as well as sound in/output working.
Frank
Hi Frank, On Wed, 2024-06-05 at 13:59 +0200, Frank wrote:
Have you been able to further advance, either witht he docker setup or your Virtualbox?
I haven't tested docker.
One issue I have is that there's no sound output, does this work with Virtualbox?
I don't need audio output, but yes, it does work when using virtualbox. After a Windows 11 shut down I run "pkill VirtualBoxVM" with root privileges. The "Affinity V2 Universal Licence" Apps, Photo 2, Designer 2 and Publisher 2 most of the times hang at "Lizenskonfiguration wird überprüft..." (Licence configuration is checked...), so the apps don't open. That's new. Today I sent an email to Affinity support. On the iPad Pro there are no Affinity license issues. I wonder if it has something to do with the broken shut down. extra/virtualbox 7.0.18-1 core/linux 6.9.3.arch1-1 (actually linux 6.9.3.arch1-1 was installed when it was in testing) FWIW: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-linux root=/dev/disk/by-label/m1.archlinux ro threadirqs ibt=off ipv6.disable=1 and I still load the microcode by the bootloader initrd /boot/intel-ucode.img /boot/initramfs-linux.img I had no time to change this, but it shouldn't matter. Regards, Ralf
participants (3)
-
David C. Rankin
-
Frank
-
Ralf Mardorf