virtualbox.org

Hello all,

I've done some digging through the forum here and I've seen a lot of people having at least somewhat related problems as I am with Mojave, but I want to fully disclose that I am not a programming/developer/ or even IT guy. I'm simply the only one at my job that knows how to use a computer so I'm stuck trying to figure this all out haha. Therefore, I apologize in advance for not knowing any of the lingo or how to do anything...please dumb it down for me.

For the past 8 years I've been running a VM with Windows XP on my iMac so that I can run some CRM software (that doesn't work on macs). This CRM software has our entire collections database in it, so it's quite important I can use it. Anyways, I have no idea what version of VirtualBox I was running...I honestly don't remember updating it for the past 8 years so I'm sorry that I can't give you more info.

To get to the problem, when we updated to Mojave (10.14) I tried to open the VM and it crashed immediately...kept saying something about no longer valid or unable to open. I know I'm terrible for not knowing exactly what it said, but that was a few weeks ago. So, I went and updated the VirtualBox hoping that would help. I'm currently using Version 5.2.22 r126460 (Qt5.6.3). The good news is after installation VirtualBox opens fine and showed the saved VM with our software. The bad news is when I go to open the VM, it says restoring and runs some scripts and then inherently crashes and says it failed and can't open. There is a dropdown arrow that would likely give me more info on why it failed, but my mouse and keyboard are no longer functioning when it fails...they must be captured in the VM and without being able to use the VM to release them I'm forced to restart the iMac before I can do anything.

I'm attaching a screenshot of the VM general information...maybe that'll help? Hoping someone here can save me.

Kenny L. wrote:I'm attaching a screenshot of the VM general information...maybe that'll help?

There was at least one thing that I was hoping to see from the screenshot, but you most probably have that category hidden (could be by accident). Right-click on any free space on that Details area and select USB. That's what I wanted to see...

But there's another, more accurate way for me to see everything:

1. Right-click on the VM in the VirtualBox Manager. Select "Show in Finder".
2. ZIP the selected ".vbox" file and attach it to your response.

Kenny L. wrote:I tried to open the VM and it crashed immediately...kept saying something about no longer valid or unable to open.

You don't have to open the VM for this:

1. Right-click on the VM in the VirtualBox Manager. Select "Show Log...".
2. Save it (only the first VBox.log), ZIP it and attach it to your response.

Thanks, hope this helps:

00:00:05.094589 Changing the VM state from 'CREATING' to 'CREATED'
00:00:05.286951 Changing the VM state from 'CREATED' to 'LOADING'
00:00:05.287412 SSM: File header: Format 2.0, VirtualBox Version 4.3.26 r98988, 64-bit host, cbGCPhys=8, cbGCPtr=8
...
00:00:08.720493 Changing the VM state from 'LOADING' to 'LOAD_FAILURE'

You are trying to load a saved state, a rather old saved state. Hence the crash. You need to discard the saved state by clicking on the Discard button in the toolbar. BTW, this reveals your last VirtualBox version used.

In the future remember it's safer to just shutdown the guest from within the guest, instead of just closing the VM window from the host. Especially when you're upgrading VirtualBox.

Thanks Socratis,

Just to be clear...if I'm not loading the saved state, will all of my files still be in the VM? And if so, how do I open it without using the saved state? I see I can right click the VM and "discard saved state" but I always assumed that would discard the whole VM?

No, discarding the saved state is like losing power on a desktop computer without UPS, i.e. losing all the RAM contents. If you've saved whatever you were working on in the guest's hard drive, then you shouldn't have a problem.

Okay thanks...I'll give it a try. I'm actually not sure if I have saved everything...I had assumed it auto-saved but now I'm worried it didn't.

Kenny L. wrote:Okay thanks...I'll give it a try

You don't have an alternative I'm afraid...

Haha, that's true...other than using Time Machine to go backwards.


So I cleared the saved state and opened--it worked, but I still had an issue. My keyboard and mouse were locked out, I had assumed they were captured by the VM but I couldn't use them within it and I couldn't figure out the release key (or it didn't work). Any suggestions?

Kenny L. wrote:So I cleared the saved state and opened--it worked

\ο/

Kenny L. wrote:My keyboard and mouse were locked out

I'm going to have to take a fresh look at the VM "recipe" and a fresh VBox.log. For the recipe, the .vbox file:

1. Right-click on the VM in the VirtualBox Manager. Select "Show in Finder".
2. ZIP the selected ".vbox" file and attach it to your response.

And for the VBox.log:

1. Start the VM. Not from a saved or paused state. Clean start.
2. Take the steps required to generate/observe the error.
3. Shut down the VM (if it hasn't aborted by itself). Not saved or paused. Completely shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
4. Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
5. Save it (only the first VBox.log), ZIP it and attach it to your response.

socratis wrote:I'm going to have to take a fresh look at the VM "recipe" and a fresh VBox.log. For the recipe, the .vbox file:

1. Right-click on the VM in the VirtualBox Manager. Select "Show in Finder".
2. ZIP the selected ".vbox" file and attach it to your response.

Okay, .vbox attached.

Unfortunately I'm not sure I can get the Vbox.log, because I can't shut down the VM after opening it -- I can't do anything, either with the VM or my host since the keyboard and mouse both become unusable. If it matters at all, both are bluetooth (however I don't have usb versions to test). I can open the VM, but then I'm froze out of both and forced to hard reboot the host.

EDIT: Zipped the vbox.log but since it's from a hard reboot and not a clean power down or crash of the VM I'm not sure if it'll have what you need.

[quote=""PastPerfect VM.vbox""]

<USBController enabled="true" enabledEhci="true">
  <DeviceFilter name="New Filter 1" active="true"/>
</USBController>

[/quote]
You have a blank USB filter in your VM, which is grabbing every USB device in the known universe, including your host's keyboard, mouse, and everything else USB connected.

Go to the VM Settings » Ports » USB. In the Filter list, you'll see a "New Filter 1". Delete that filter. Start the VM. Enjoy your mouse and keyboard...

socratis wrote: Start the VM. Enjoy your mouse and keyboard...

You're a genius! Thank you SO much!

Glad I could help. And thank you for marking the topic as [Solved]...