Windows 10 VM aborting during boot

Discussions related to using VirtualBox on Linux hosts.
Post Reply
nhaggin
Posts: 2
Joined: 21. Jul 2022, 04:55
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Windows 10
Location: USA

Windows 10 VM aborting during boot

Post by nhaggin »

Greetings, all. I hope this is not a redundant question; I have searched extensively and found nothing quite like it.

VB 6.1.36 r152435
Extension pack 6.1.36 r152435
Host: Linux Mint 20, kernel 5.13.0-52
Guest: Windows 10 x64
Bridged LAN

I have a Windows 10 guest that was running fine until this evening. Yesterday I updated to 6.1.36 r152435 from the PPA and tonight I likewise updated the extension pack to the same version, and then attempted to boot the guest. It is now aborting after a short time on every boot and the OS does not finish booting. I have attached the log of my most recent attempt below.

In dmesg I also see something like the following, with slightly different addresses each time, on every boot attempt:

Code: Select all

EMT-1[28470]: segfault at 0 ip 00007f4163fdc56b sp 00007f41994f8bc0 error 4 in VBoxDD.so[7f4163f1d000+178000]
Googling suggests this is usually caused by a mismatch between hypervisor and extension pack, but as stated I am running equivalent versions of each. Is this perchance a bug in my installed release? Would it be worth attempting to downgrade?
Attachments
win10-2022-07-20-21-37-17.log.zip
Windows 10 guest boot log
(18.42 KiB) Downloaded 14 times
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Windows 10 VM aborting during boot

Post by fth0 »

VBoxDD.so contains all sort of device drivers, and the last log message ("xHCI: Hardware reset") is part of the guest-side USB device initialization.

For a test, remove USB and perhaps other optional virtual hardware (e.g. audio, network) from the VM configuration and see if the issue persists.
nhaggin
Posts: 2
Joined: 21. Jul 2022, 04:55
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Windows 10
Location: USA

Re: Windows 10 VM aborting during boot

Post by nhaggin »

That helped a lot. Turning off USB got it to boot correctly. It won't be a long-term solution as I usually connect my USB flash card reader to this VM when it's running, but at least the system isn't completely toast.

Any suggestions on where to go from here? I expect that simply re-enabling USB will bring the problem back.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Windows 10 VM aborting during boot

Post by mpack »

Try accessing storage as a shared folder - USB can usually be easily avoided IME.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Windows 10 VM aborting during boot

Post by fth0 »

You could create a ticket in the Bugtracker.
Shaboobaroo
Posts: 2
Joined: 1. Aug 2022, 18:24

Re: Windows 10 VM aborting during boot

Post by Shaboobaroo »

I am having the same issue with a Windows 10 VM aborting during boot after upgrading to 6.1.36 r152435. Other VMs (Windows 7 & Fedora) boot without issue.

VB 6.1.36 r152435 (Qt5.15.3)
Extension pack 6.1.36 r152435
Host: Pop!_OS 22.04 LTS, kernel Linux 5.18.10-76051810-generic
Guest: Windows 10 x64
Bridged LAN

Like the OP, fth0's suggestion of Disabling the USB Controller allowed me to boot up the Win10 VM for the first time since I upgraded VirtualBox to 6.1.36 r152435. :D It is a great work around for now but I am running legacy software on the Win10 VM that will only allow me to back up onto a USB, so I need to re-enable the USB at some point.
I have the same legacy software installed on my Win7 VM but if I enable USB on that VM it also aborts while attempting to start up! :?:
Shaboobaroo
Posts: 2
Joined: 1. Aug 2022, 18:24

Re: Windows 10 VM aborting during boot

Post by Shaboobaroo »

I am not the OP but I wanted to give everyone an update because I am having the same issue. In my previous post I stated that I had an issue a Windows 10 VM aborting during boot after upgrading to VirtualBox 6.1.36 r152435. I also said that other VMs (Windows 7 & Fedora) boot without issue.

Thanks to fth0's suggestion of Disabling the USB Controller, I was able to get the Win10 VM to boot up. I realized that I did not have the USB enabled on my Win7 VM & my Fedora VM.

-I tried enabling the USB 3.0 (xHCI) Controller on the Win7 & Fedora VMs and they both aborted when attempting to start them up.

-I then tried enabling the USB 2.0 (OHCI + EHCI) Controller on the Win10, Win7 & Fedora VMs and they would not start. Instead of saying aborted, this time they all said "Failed to open a session for the virtual machine".

-I tried enabling the USB 1.1 (OHCI) Controller on the Win10, Win7 & Fedora VMs and ALL THREE VMs STARTED UP :!: :D So I can start all VMs with the USB Controller Enabled, but only with USB 1.1.

VB 6.1.36 r152435 (Qt5.15.3)
Extension pack 6.1.36 r152435
Host: Pop!_OS 22.04 LTS, kernel Linux 5.18.10-76051810-generic
Guests: Windows 10 x64, Windows 7 x64, Fedora 36
Bridged LAN

I still have legacy software on the Win10 & Win7 VMs that need a physical USB to back up to. It takes over an hour on USB 3.0. USB 1.1 is a workaround but it will probably take all day for me to back up.

I wonder if VirtualBox's USB 3.0 (xHCI) Controller needs to be updated?
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Windows 10 VM aborting during boot

Post by mpack »

That would make sense, because this is looking like a mismatch of some kind between extension pack and VirtualBox itself. However USB 1.1 does not use the extension pack, that's only for USB2 and USB3 (i.e. EHCI and xHCI).
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Windows 10 VM aborting during boot

Post by fth0 »

This issue should be fixed in the VirtualBox test builds 6.1.39r153816 and newer.
Post Reply