virtualbox.org

Kind of stuck as I cant find anything obvious in the log or the error message when I google around. Just find unrelated windows machines that wont boot related to this error msg. If anyone has a clue what this is about, please let me know as I really need to get this VM started..

Worth noting is that I updated to Virtualbox 6.1 just before the VM stopped starting. Using Ubuntu on the host.

Failed to open a session for the virtual machine 1.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

Belive I found the issue, the VM that im trying to start does not work on the latest Virtualbox version, needs to run on 6.1.18. Downgrading atm, will post outcome.

EDIT:

Downgrading worked.

VirtualLizard wrote:Belive I found the issue, the VM that im trying to start does not work on the latest Virtualbox version, needs to run on 6.1.18.

How did you come to that conclusion?

The first problem I see in the log is that you are trying to run a 64bit Debian guest in 512MB RAM. Unfortunately my analysis can't dig much deeper since you provided a truncated log (it ends abruptly, 2 seconds in).

You also seem to be cross referencing a shared VDI stored in an encrypted volume?

Hi All,

Seem to have the same issue since upgrade to 6.1.20. Fails to launch the VM straight away. Was fine up until the upgrade. Earlier clones have the same issue.

Failed to open a session for the virtual machine.
The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}



**Edit: Downgrading to 6.1.18 has got me going again**

Again we have a log grabbed while the VM was still running, hence the log is truncated and omits most useful information.

You need to acknowledge the error message and allow the VM to close - or tell it to close. Only then do you right click the VM in the manager UI, select "Show Log" and save "VBox.log" (no other file) to a zip file. Then attach the zip here.

The only thing that catches my eye in the log fragment provided is that the VM files have been scattered around a very strange folder structure, including one VDI located in OneDrive? Graphics RAM allocated seems a bit mean too, especially compared to GP RAM.

If downgrading versions fixes the problem that often means that a saved state is involved. Saved states are not guaranteed to be portable across versions.

The VBox logs from both reported instances appear to show a VM configuration with an LSI Logic SAS controller.
With VirtualBox 6.1.20, any VM defined with that controller appears to fail immediately with the error code shown.
The machine log is truncated at the point of failure.
See my entry (and subsequent confimation from another user) in viewtopic.php?f=1&t=102601

The Raven wrote:The VBox logs from both reported instances appear to show a VM configuration with an LSI Logic SAS controller.
With VirtualBox 6.1.20, any VM defined with that controller appears to fail immediately with the error code shown.

Good catch.

Changing the drive from SAS to SATA got the VM's to start, but Windows spat it and get stuck in a boot loop. Looks like the LsiLogic SAS controller is the problem with 6.1.20.

powerdrink wrote:Changing the drive from SAS to SATA got the VM's to start, but Windows spat it and get stuck in a boot loop.

I haven't had that problem for a while, but the traditional cure was to move the primary HD onto a IDE controller (*), but keep the SATA controller in the VM recipe. IDE allows Windows to boot, and then it will see an unknown SATA chipset and download drivers for it. Once everything is stable it should be possible to move the hd back to the SATA controller.

(*) Doesn't work for XP, you have to run MergeIDE first to make it tolerant of IDE variants. No such prep is needed by Win7 and later.

According to the changelog Vbox 6.1.22 has fixed this.

Martin wrote:According to the changelog Vbox 6.1.22 has fixed this.

Yep, this worked for me. Happy days.

Martin wrote:According to the changelog Vbox 6.1.22 has fixed this.

I am running the latest version; Windows runs; however my Ubuntu Linux guest OS fails to run with the same error. What am I missing?

VirtualLizard wrote:Belive I found the issue, the VM that im trying to start does not work on the latest Virtualbox version, needs to run on 6.1.18. Downgrading atm, will post outcome.

EDIT:

Downgrading worked.

Downgrading worked for me too. Although in my case the latest version is 6.1.36 which is problematic and downgrading to 6.1.34 solved this issue. Thank you for your post as I had no idea how to resolve it even after spending lots of time on google.

I had the same exact problem running version 6.1.38, and instead of downgrading, I solved it upgrading the VM extension from the Download section of the wiki, following the advise of topic 106804 comment 522481 (I cannot insert URLs...)

I hope this will useful to someone else coming to this exact page.

Always_learning wrote:I had the same exact problem running version 6.1.38, and instead of downgrading, I solved it upgrading the VM extension from the Download section of the wiki, following the advise of topic 106804 comment 522481 (I cannot insert URLs...)

I hope this will useful to someone else coming to this exact page.

I had the same problem on 6.1.38, and upgrading the extension pack also worked fro me.