Page 1 of 1

Config mismatch for Xubuntu VM

Posted: 4. Oct 2020, 23:17
by Theodin
Hello,

Recently faced an error with starting VM and it is giving me the attached error.
Looked online but most posts talked about snapshots (I did not create/delete any snapshots).
Also tried looking for any similar threads on this forum but the closest only seems to have 4 comments and seems incomplete?

Log files are too big and it doesn't let me post URLs.

Appreciate all your input. Thanks!

Re: Config mismatch for Xubuntu VM

Posted: 4. Oct 2020, 23:43
by scottgus1
You may have a saved state, meaning the guest was turned off while it was running, such that it can come back to where it was, similar to Windows Hibernate.

Did you recently update Virtualbox? If so, and you care about the saved state, downgrade Virtualbox to the version you had before then start the guest, shut it down fully from within the guest OS, then re-upgrade Virtualbox.

If you don't care about the saved state, right click the guest in the main Virtualbox window's guest list and choose Discard Saved State.

Re: Config mismatch for Xubuntu VM

Posted: 5. Oct 2020, 22:40
by Theodin
Thank you for getting back.

I haven't updated Virtualbox and would ideally like to recover the state or atleast the files if possible.

Would discarding the saved state erase the files within VM too?

Re: Config mismatch for Xubuntu VM

Posted: 5. Oct 2020, 23:10
by scottgus1
Discarding saved state will delete unsaved data in the guest.

Essentially, something on the host changed enough that the guest saved state no longer matches. What it is we unfortunately can't say.

When the guest has the saved state discarded then you start it again, it will restart as if it had a power loss.

Re: Config mismatch for Xubuntu VM

Posted: 6. Oct 2020, 18:45
by Theodin
I ended up discarding the saved state. It let me start the VM and I can access my files now.

Really appreciate your help, thank you!

Re: Config mismatch for Xubuntu VM

Posted: 6. Oct 2020, 19:34
by scottgus1
Great! Glad you're up and running.