question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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?

Issue Analytics

  • State:open
  • Created 3 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
nsmfoocommented, May 2, 2021

@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
0reactions
JeffRockatanskycommented, Mar 23, 2021

@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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Failed to power on virtual machine (82542) | VMware KB
The failure of a VM to power on may be caused by any of the following reasons: ESXi OS problems. File corruption.
Read more >
I am unable to start Windows: troubleshooting virtual machine ...
Your Windows virtual machine (or another OS) no longer boots, and you cannot start it. You get an error message when you try...
Read more >
Virtual Machine – What to Do When Yours Doesn't Boot Up
The most common reason why virtual machine boot failures occur is that the required hardware resources aren't available. Microsoft Hyper-V and ...
Read more >
Troubleshooting Virtual Machine boot failures on AHV cluster
Verify if VM has the correct boot device selected. Refer to KB 4294 for details. If a virtual machine has multiple disks attached,...
Read more >
Virtual machine startup problem - IBM
Virtual machine startup problem · There is not enough resources in vSphere HA to run new VMs. · vSphere checks the amount of...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found