Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
-
- Posts: 6
- Joined: 21. Jan 2022, 22:41
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
I am having this issue as well. After upgrading to v6.1.32, a 64 bit W10 21H2 guest running on a 64 bit W10 21H2 host takes over 20 minutes to boot to the login screen. Likewise an Ubuntu 20.04 guest is so slow as to be unusable. I can't even complete the Guest Additions upgrade on either system. The host is not starved for resources and remains responsive, indicating 25-35% CPU usage per running VM, whereas the CPU load in the session information window shows pinned 100% pretty much continuously.
In my case I upgraded directly from v6.1.26 because I was experiencing issue issue #20627 (Failed to load R0 module) with v6.1.28 and 6.1.30. 26 itself isn't entirely stable but it runs for a good couple of days before it starts acting up.
Just noticed I left the W10 VM sitting on the login screen while I registered for this forum and wrote this message, and it has had a spontaneous BSOD with an IRQL NOT LESS OR EQUAL error and rebooted itself. Performance remains abysmal.
In my case I upgraded directly from v6.1.26 because I was experiencing issue issue #20627 (Failed to load R0 module) with v6.1.28 and 6.1.30. 26 itself isn't entirely stable but it runs for a good couple of days before it starts acting up.
Just noticed I left the W10 VM sitting on the login screen while I registered for this forum and wrote this message, and it has had a spontaneous BSOD with an IRQL NOT LESS OR EQUAL error and rebooted itself. Performance remains abysmal.
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Yes, I concur. It is unusable now and was ready to blame my Win 11 host. My guests are Redhat and Windows Server 2022.
-Phil
-Phil
-
- Posts: 339
- Joined: 9. Jul 2007, 20:02
- Primary OS: MS Windows other
- VBox Version: OSE other
- Guest OSses: Windows and macOSes
- Location: An Ant Farm
- Contact:
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Thanks. Please do post your logs of these issues.philt wrote:Yes, I concur. It is unusable now and was ready to blame my Win 11 host. My guests are Redhat and Windows Server 2022.
-Phil
-
- Posts: 6
- Joined: 21. Jan 2022, 22:41
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
One thing I have noticed is if I set my VMs down to 1 processor they become much more responsive. Still jerky and unstable but in the case of the W10 VM I was able to complete the Guest Additions upgrade, which ultimately made no difference. They still aren't usable in this state. I have attached the log (split into 2 parts) of my last run with 1 processor.
- Attachments
-
- Win10 VM-2022-01-21-21-20-50 part2.log
- log is too big to attach in one piece
- (79.85 KiB) Downloaded 7 times
-
- Win10 VM-2022-01-21-21-20-50 part1.log
- running with 1 cpu is unstable but sorta works.
- (77.33 KiB) Downloaded 7 times
-
- Posts: 339
- Joined: 9. Jul 2007, 20:02
- Primary OS: MS Windows other
- VBox Version: OSE other
- Guest OSses: Windows and macOSes
- Location: An Ant Farm
- Contact:
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
My guest VMs were already at one processor. Thanks for sharing your logs. Hopefully, the developers can look into our issues, fix, and release ASAP.postnobills wrote:One thing I have noticed is if I set my VMs down to 1 processor they become much more responsive. Still jerky and unstable but in the case of the W10 VM I was able to complete the Guest Additions upgrade, which ultimately made no difference. They still aren't usable in this state. I have attached the log (split into 2 parts) of my last run with 1 processor.
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Can you try 6.1.30 as there have been a number of posts with 6.1.32 where the guests run like a dog and/or intermittently crash or not work correctly.
I had to go back to 6.1.30 as 6.1.32 was sloooow to start both Windows and Linux guests.
I had to go back to 6.1.30 as 6.1.32 was sloooow to start both Windows and Linux guests.
-
- Posts: 339
- Joined: 9. Jul 2007, 20:02
- Primary OS: MS Windows other
- VBox Version: OSE other
- Guest OSses: Windows and macOSes
- Location: An Ant Farm
- Contact:
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Who are you talking to? Me? If so, then I had to downgrade to that version to use my VMs.AndyCot wrote:Can you try 6.1.30 as there have been a number of posts with 6.1.32 where the guests run like a dog and/or intermittently crash or not work correctly.
I had to go back to 6.1.30 as 6.1.32 was sloooow to start both Windows and Linux guests.
-
- Posts: 6
- Joined: 21. Jan 2022, 22:41
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
I have now gone back to 6.1.26 and everything is working as it did before I upgraded to 32.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Can you provide a (zipped) VBox.log file of that VM running under VirtualBox 6.1.32?ant wrote:I don't have this problem with my old 32-bit Windows XP Pro.
-
- Posts: 339
- Joined: 9. Jul 2007, 20:02
- Primary OS: MS Windows other
- VBox Version: OSE other
- Guest OSses: Windows and macOSes
- Location: An Ant Farm
- Contact:
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
I attached my zipped 32-bit Windows XP Pro SP3's VB v6.1.32's vbox.log from 1/18/2022 1:41 PM PST. I haven't touched it since then.fth0 wrote:Can you provide a (zipped) VBox.log file of that VM running under VirtualBox 6.1.32?ant wrote:I don't have this problem with my old 32-bit Windows XP Pro.
- Attachments
-
- XP Pro SP3 (Slipstreamed)-2022-01-18-13-41-00.zip
- 32-bit Windows XP Pro SP3's VB v6.1.32's vbox.log working nicely with a quick test.
- (24.87 KiB) Downloaded 6 times
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Thanks for the Windows XP VM's log file, which shows that this VM was not affected at all. This matches other reports that VMs with 1 vCPU are less affected than VMs with 2 or more vCPUs, if at all.
-
- Posts: 339
- Joined: 9. Jul 2007, 20:02
- Primary OS: MS Windows other
- VBox Version: OSE other
- Guest OSses: Windows and macOSes
- Location: An Ant Farm
- Contact:
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Interesting. My 64-bit W7 HPE SP1 VM only uses 1 vCPU.fth0 wrote:Thanks for the Windows XP VM's log file, which shows that this VM was not affected at all. This matches other reports that VMs with 1 vCPU are less affected than VMs with 2 or more vCPUs, if at all.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Thanks for the pointer. On one end, we have the Windows XP VM exhibiting no slowness whatsoever. On the other end, we have the Windows 10 VM exhibiting the slowness with explicit log messages (heartbeat issues). In the middle we have the Windows 7 VM exhibiting the slowness only via the time stamps of the log messages, so you need a trained eye to see it.
One difference I noticed is the I/O APIC setting. It is necessary for multi core CPUs (e.g. Windows 10 VM), but not for single core CPUs (e.g. Windows XP VM). It is currently enabled in the Windows 7 VM. AFAIK, you cannot enable it for an installed Windows XP, but you can disable it for an installed Windows 10. For an installed Windows 7, I don't know if it can cope with such a hardware change. You could try how your Windows 10 VM behaves when giving it only 1 vCPU with and without the I/O APIC.
General notice: If you want to provide further VBox.log files, please power down the VM beforehand, so that the log files contain the statistics at the end.
One difference I noticed is the I/O APIC setting. It is necessary for multi core CPUs (e.g. Windows 10 VM), but not for single core CPUs (e.g. Windows XP VM). It is currently enabled in the Windows 7 VM. AFAIK, you cannot enable it for an installed Windows XP, but you can disable it for an installed Windows 10. For an installed Windows 7, I don't know if it can cope with such a hardware change. You could try how your Windows 10 VM behaves when giving it only 1 vCPU with and without the I/O APIC.
General notice: If you want to provide further VBox.log files, please power down the VM beforehand, so that the log files contain the statistics at the end.
-
- Posts: 6
- Joined: 21. Jan 2022, 22:41
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Thought I'd take another run at this, having installed Hyper-V and VMware Player in the meantime. The VMware installer detected the presence of Hyper-V and I believe it was actually running on the Hyper-V engine. It performed okay but I prefer to stick with VirtualBox for a variety of reasons. I thought perhaps if VMware made use of Hyper-V maybe VirtualBox would as well, but it appears not. The Runtime Information continues to report the VM Execution Engine as Native API. Is there a way to force it onto the Hyper-V engine?
Log from my 2 CPU W10 VM is attached. Note there was a BSOD within the first minute then it booted again. Still dead slow, still reporting 100% Guest load and nearly 0% VMM load almost continuously. Interestingly if I close the window and choose 'send the shut down signal' it seems to spur the VM to life for a few seconds, but only a few seconds, and the guest never behaves like it's been told to shut down.
Log from my 2 CPU W10 VM is attached. Note there was a BSOD within the first minute then it booted again. Still dead slow, still reporting 100% Guest load and nearly 0% VMM load almost continuously. Interestingly if I close the window and choose 'send the shut down signal' it seems to spur the VM to life for a few seconds, but only a few seconds, and the guest never behaves like it's been told to shut down.
- Attachments
-
- Win10 VM-2022-02-11-17-34-13.zip
- (38.65 KiB) Downloaded 4 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Is anyone else having problems with VB v6.1.32 booting up 64-bit Windows in 64-bit W10?
Looks like this is the new bug in 6.1.32, based on:
(HCVI = Microsoft 'Memory Integrity')
6.1.32 without Hyper-V
6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.
Our forum guru 'fth0' has done some troubleshooting and pins down these possibilities to try as temporary workarounds:6.1.32 Hyper-V Glitch (remove left 9 characters, time offset in seconds, less than 1 second normal)
00:19:35.949277 /TM/VirtualSync/CurrentOffset 989429822321 ns
(HCVI = Microsoft 'Memory Integrity')
6.1.32 without Hyper-V
6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.