I know my setup might not be supported, but I have this problem on two different Gentoo Linux systems. After upgrading to 5.1.20, I get the following error when I start any Windows VM (XP, 7, 10):
The VM session was aborted.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
SessionMachine
Interface:
ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
Going back to 5.1.18 restores VM operation. Any ideas as to a fix?
Windows VMs no start after 5.1.20 upgrade
-
MikeGreene
- Posts: 10
- Joined: 3. Sep 2015, 18:57
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: eCS, OS/2, DOS, Win XP, 7, 10, ReactOS
- Location: Suffolk, Virginia
Windows VMs no start after 5.1.20 upgrade
- Attachments
-
VBoxSVC.log- (5.33 KiB) Downloaded 4 times
-
- VBox.log
- (2.74 KiB) Downloaded 7 times
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows VMs no start after 5.1.20 upgrade
If by that you mean:MikeGreene wrote:I know my setup might not be supported
then you would be correct. Please install the official distribution from https://www.virtualbox.org/wiki/DownloadsVirtualBox VM 5.1.20_Gentoo r114628 linux.amd64 (Apr 24 2017 19:54:46) release log
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Windows VMs no start after 5.1.20 upgrade
Actually Gentoo usually requires special and specific patches not provided by VirtualBox and as such you should address your issue with Gentoo. Their VirtualBox maintainer at gentoo portage needs to know about this so they can fix it.
-
frank
- Oracle Corporation
- Posts: 3362
- Joined: 7. Jun 2007, 09:11
- Primary OS: Debian Sid
- VBox Version: PUEL
- Guest OSses: Linux, Windows
- Location: Dresden, Germany
- Contact:
Re: Windows VMs no start after 5.1.20 upgrade
I assume it's this problem. Should be fixed with the most recent 5.1.x test builds.
-
MikeGreene
- Posts: 10
- Joined: 3. Sep 2015, 18:57
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: eCS, OS/2, DOS, Win XP, 7, 10, ReactOS
- Location: Suffolk, Virginia
Re: Windows VMs no start after 5.1.20 upgrade
Frank,
I do not think it is that Bug. There is a Gentoo bug open - Bug 616238
https://bugs.gentoo.org/show_bug.cgi?id=616238
Mike
I do not think it is that Bug. There is a Gentoo bug open - Bug 616238
https://bugs.gentoo.org/show_bug.cgi?id=616238
Mike
-
frank
- Oracle Corporation
- Posts: 3362
- Joined: 7. Jun 2007, 09:11
- Primary OS: Debian Sid
- VBox Version: PUEL
- Guest OSses: Linux, Windows
- Location: Dresden, Germany
- Contact:
Re: Windows VMs no start after 5.1.20 upgrade
Gentoo bug 616238 sounds exactly like bug 16693. Please verify that the most recent 5.1.x test builds fix your problem.
-
MikeGreene
- Posts: 10
- Joined: 3. Sep 2015, 18:57
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: eCS, OS/2, DOS, Win XP, 7, 10, ReactOS
- Location: Suffolk, Virginia
Re: Windows VMs no start after 5.1.20 upgrade
Test build works, but the Gentoo 5.1.22 build does not.
Mike
Mike