freezer wrote: ↑7. Oct 2024, 20:13
...
As a test I took an existing Windows 11 23H2 VM and loaded the ISO while in Windows. From Windows I ran the installer which copies new files to the drive. It then reboots the machine to finish the install. When this reboot happens the VM hangs (Windows 11 never loads). So there's something about the Windows 11 24H2 kernel and VirtualBox.
...
so far I have only upgraded 2 vm's from 23H2 to 24H2 using the solution I found ( --hpet ) , maybe try that on the test scenario above ...
for fresh install 24H2 - have not tried myself , is your h/w compatible with win 11 ? , maybe post the fresh install log when it hangs as without it those reading dont have much to go on ...
Wicked0ne wrote: ↑15. Oct 2024, 06:24
I'm running into the same issue. Host is Windows 11 Enterprise LTSC IoT and guest is also Windows 11 Enterprise LTSC IoT. Creating a new VM and trying to boot it results in the "press any key to boot from dvd..." and then it just sits at the virtualbox splash screen. Trying to set hpet(i.e. VBoxManage modifyvm "win11" --hpet on) on results in the same thing. Disabling Nested Paging does get me to the Windows 11 installer and does the usual Windows install stuff. But after the installer ran and windows boots for the first time, Virtualbox crashes. If I then enable Nested Paging again, the virtual machine just sits at the Virtualbox splash screen.
I've attached the log file from the VM that I enabled hpet on and disabled Nested Paging to install windows 11, then re-enabled Nested Paging.
noticed in your log the chipset is ICH9 - all my win 11 are PIIX3 - think thats the default when you choose win 11 as os template to use, is this something your sure about ? )
Hmm, I didn't change anything from the defaults when creating a new VM. And weirder is if I open that VMs settings it shows PIIX3 under settings.
Hi I had the exact same issue with 24H2 and VM just hangs. The same error of 00:20:36.831651 TM: Switching TSC mode from 'VirtTSCEmulated' to 'RealTSCOffset'
00:20:36.831682 GIM0: HyperV: Enabled APIC-assist page at 0x000000000000d000
00:20:36.833968 GIM: HyperV: Guest indicates a fatal condition! P0=0x5c P1=0x110 P2=0x5250631 P3=0x14 P4=0xffffffffc0000001
00:20:36.834451 GIMHv: BugCheck 5c {110, 5250631, 14, ffffffffc0000001}
Tried on another machine which had no install of VirtualBox before and 24H2 worked first time.
Uninstalled Virtualbox again (latest Version), looked for leftover files, but could only find and renamed C:\Users\myname\.VirtualBox folder to .VirtualBoxold. Installed Virtualbox again and all works fine again. Worked for me anyway!!
I have successfully upgraded Windows 11 from 23H2 to 24H2. Before I did that I made some configuration changes:
-Settings>System>Processor and turn off checkbox "Enable Nested VT-x/AMD-V"
-Settings>System>Acceleration and turn off checkbox "Enable Nested Paging"
-VBoxManage.exe modifyvm WIN11 --vtx-vpid=off
Same issue with Windows Server 2025 Technical Preview
No idea (especially when users don't provide their VBox.log and just claim "X solves the problem) which solutions are genuine and which are not making any sense.
At last... we found a system where it happens and the bug could be fixed. Please retry with the latest 7.0 or 7.1 test build (not the development snapshot).
klaus wrote: ↑25. Oct 2024, 23:47
At last... we found a system where it happens and the bug could be fixed. Please retry with the latest 7.0 or 7.1 test build (not the development snapshot).
Using 7.1.x revision 165591 and setting hpet to on I was able to boot and install windows 11 24H2.