VM Startup error

[wazlecracker]

Getting the following error after running the generated script and attempting to open the VM for the first time:

Failed to open a session for the virtual machine Scam-baitin.

The VM session was aborted.

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

I do store my VMs on a separate drive and I suspect that's why. How can I edit the script if that's what's causing this?

[nsmfoo]

Hi @wazlecracker sorry for my late reply, if the issue still persist, we can try to figure it out. For example, Is there any other errors that are displayed or visible?

[nsmfoo]

If possible please try the latest "version", your issue might have been re-solved. If not please let me know

[tsilvs]

@nsmfoo I'm having the same issue on latest master branch version (latest commit from 21 January 2021).

I also store my VM on a separate external drive.

[tsilvs]

@nsmfoo another issue is with <ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiSystemSKU" value="0704"/> inside .vbox. Virtualbox refuses to run it with Configuration error: Querying "DmiSystemSKU" as a string failed (VERR_CFGM_NOT_STRING).

A possible fix is to set value="string:0704". But after that for me it is a Error: ACPI tables bigger than 64KB (VERR_TOO_MUCH_DATA), so I don't really know does this fix work or not.

[nsmfoo]

@JeffRockatansky I almost missed your issues, as you posted in an old issue =)

1. For the first problem do you have any visible error messages? And can you share the patch as written in the template? I should be able to figure something out
2. That looks like an oversight on my end. Let me look at it during next week, setting the DmiSystemSKU to a string from the start should be not problem (I hope)
3. Sadly this is an issue that lies with the Virtualbox team, I have poked them a couple of times over the years, without any progress. I will see if I can chat with them to make them understand better. Also if you do have the time, open a case (over at VirtualBox.org) saying that they should support ACPI tables bigger than 64KB