Virtualization not working without VT-x in the newer versions (5)

[kaisbe]

After upgrading VBox from 4.3 to 5.1.20 (the latest version), my Windows VM has failed to start, along with VBox showing the following error message:

Invalid parameter. (VERR_INVALID_PARAMETER)
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

This issue is specific to the version 5 of VBox, because this error didn't occur at all before the upgrade.

This is the log prior to the upgrade can be found ​here. The log resulted after the upgrade can be found ​here.

This issue affects many users, and needs some action.

[Frank Mehnert]

The actual forum topic can be found ​here.

[Frank Mehnert]

Added a comment to the forum topic (asking for the VM settings file of that VM).

[kaisbe]

Added the VM settings file as an attachment to the forum topic.

[Frank Mehnert]

Checked the Win7.vbox.txt file and it looks harmless. But the settings file does not correspond to the VBox.log file. For example, CPU execution cap is set to 80 according to Win7.vbox.txt but set to 100 according to the VBox.log file. Please could you

1. try to start the VM with 5.1.20, better 5.1.22
2. attach the resulting VBox.log file to this ticket
3. attach the corresponding .vbox settings file at this time to this ticket.

Thank you!

[kaisbe]

settings

[Frank Mehnert]

Still unable to reproduce and this error does make any sense to me. Do you have any special host kernel running? Some Linux kernel address space modifications? Maybe some kernel options for embedded kernels? What is actually your host? I see you are using the Debian 8 package but you certainly don't use the Qt library which comes with Debian 8.

[kaisbe]

kernel configuration

[kaisbe]

Replying to frank:

Do you have any special host kernel running? Some Linux kernel address space modifications? Maybe some kernel options for embedded kernels?

I'm not sure, but you can have a look at the attached kernel configuration file 'kconf' above.

What is actually your host?

uname -a
Linux devuan 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2 (2017-04-30) x86_64 GNU/Linux

I see you are using the Debian 8 package but you certainly don't use the Qt library which comes with Debian 8.

apt list --installed libqt5*
Listing... Done
libqt5clucene5/unstable,now 5.7.1-1 amd64 [installed,automatic]
libqt5concurrent5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed,automatic]
libqt5core5a/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed]
libqt5dbus5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed,automatic]
libqt5designer5/unstable,now 5.7.1-1 amd64 [installed,automatic]
libqt5designercomponents5/unstable,now 5.7.1-1 amd64 [installed,automatic]
libqt5gui5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed]
libqt5help5/unstable,now 5.7.1-1 amd64 [installed,automatic]
libqt5network5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed,automatic]
libqt5opengl5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed]
libqt5opengl5-dev/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed,automatic]
libqt5printsupport5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed]
libqt5qml5/unstable,now 5.7.1-2+b2 amd64 [installed,automatic]
libqt5quick5/unstable,now 5.7.1-2+b2 amd64 [installed,automatic]
libqt5quicktest5/unstable,now 5.7.1-2+b2 amd64 [installed,automatic]
libqt5quickwidgets5/unstable,now 5.7.1-2+b2 amd64 [installed,automatic]
libqt5script5/unstable,now 5.7.1~20161021+dfsg-2 amd64 [installed,automatic]
libqt5sql5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed,automatic]
libqt5sql5-sqlite/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed,automatic]
libqt5svg5/unstable,now 5.7.1~20161021-2+b2 amd64 [installed,automatic]
libqt5test5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed,automatic]
libqt5webkit5/unstable,now 5.7.1+dfsg-1 amd64 [installed,automatic]
libqt5widgets5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed]
libqt5x11extras5/stable,now 5.3.2-2 amd64 [installed]
libqt5xml5/unstable,now 5.7.1+dfsg-3+b1 amd64 [installed,automatic]
libqt5xmlpatterns5/unstable,now 5.7.1~20161021-3 amd64 [installed,automatic]

[kaisbe]

(UPDATE) this is the log I got after upgrading to the latest version 5.1.22

[kaisbe]

(UPDATE) this is the log I got after upgrading to the latest version 5.1.22

[kaisbe]

I've got the VM working after discarding its saved state, and starting it again .. What might be causing the problem?

[Socratis]

In the ​discussion in the forums, you were specifically told to ​discard the saved state, and your reply was that no matter what, ​it didn't work. So what changed?

And to give you a rough idea of what happens if you upgrade VirtualBox with a VM in saved state (and it's a really, really bad idea), it's like putting your computer to hibernate in your host, and while it's hibernating, you move the HD to a completely different computer with a completely different set of hardware, and expect the whole thing to wake up from hibernation like nothing happened. Can't.