Page 1 of 1
Windows VMs no start after 5.1.20 upgrade
Posted: 25. Apr 2017, 23:57
by MikeGreene
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?
Re: Windows VMs no start after 5.1.20 upgrade
Posted: 26. Apr 2017, 09:11
by socratis
MikeGreene wrote:I know my setup might not be supported
If by that you mean:
VirtualBox VM 5.1.20_Gentoo r114628 linux.amd64 (Apr 24 2017 19:54:46) release log
then you would be correct. Please install the official distribution from
https://www.virtualbox.org/wiki/Downloads
Re: Windows VMs no start after 5.1.20 upgrade
Posted: 26. Apr 2017, 15:05
by Perryg
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.
Re: Windows VMs no start after 5.1.20 upgrade
Posted: 26. Apr 2017, 17:51
by frank
I assume it's
this problem. Should be fixed with the most recent 5.1.x test builds.
Re: Windows VMs no start after 5.1.20 upgrade
Posted: 27. Apr 2017, 01:27
by MikeGreene
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
Re: Windows VMs no start after 5.1.20 upgrade
Posted: 27. Apr 2017, 10:39
by frank
Gentoo bug 616238 sounds exactly like bug
16693. Please verify that the most recent 5.1.x
test builds fix your problem.
Re: Windows VMs no start after 5.1.20 upgrade
Posted: 3. May 2017, 12:39
by MikeGreene
Test build works, but the Gentoo 5.1.22 build does not.
Mike