Page 1 of 1

Second "Detachable" VM fails on login.

Posted: 3. Apr 2017, 16:46
by Tronmech
Got a good one here that I'm still diagnosing... I moved 4 VM's from Windows to a Linux host, including 3 that were the template and 2 linked clones. After fixing the storage issues (hardcoded "F:\vmstorage\..." storage paths in the .vbox file really upset Linux), I'm left with an "interesting" conundrum: I cannot start 2 of *these* VM's as detachable.

When I do, I get the following error message *after successful login to the guest*:
Failed to set the extra data for key GUI/LastGuestSizeHint of machine to value {800,600}
The object is not ready
ResultCode: E_ACCESSDENIED (0x80070005)
Component: SessionMachine
Interface: Imachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

The VM then goes into "aborted" state.

A VM that starts it's life on Linux works fine, and these VM's all start fine in detachable on Windows without issue.

I don't SEE anything in the VM log about this. The Virtualbox version is the current 5.1.18 download. As are the guest additions.

My guess is that something goes horribly wrong in the guest additions, since the VM is going fine until I log in, but ONLY if the start as detachable.

Re: Second "Detachable" VM fails on login.

Posted: 3. Apr 2017, 17:04
by mpack
Sounds like a permissions issue on the host: .vbox file not writable, e.g. because it's not in the current user's data folder.

Re: Second "Detachable" VM fails on login.

Posted: 3. Apr 2017, 20:22
by Tronmech
mpack wrote:Sounds like a permissions issue on the host: .vbox file not writable, e.g. because it's not in the current user's data folder.
Unfortunately, this cause is ruled out because if the problem host is started as the FIRST detachable instance, it works perfectly. Then there is the "always works if started normally" behavior as well.

EDIT: Spelling/word choice error

Re: Second "Detachable" VM fails on login.

Posted: 4. Apr 2017, 01:03
by socratis
First of all, your log is not from a complete session. The procedure is: Launch the VM from a cold boot, observe the problem, shutdown the VM (not pause, not saved state, full shutdown), post the appropriate zipped log. But it's not vital for your case.

Second, what's the output of:
  • ls -alR "/mnt/exthd/data/RHEL 6.4 CC 9.0.0.3/"
And finally, right-click on the VM, show in ..., zip that '.vbox' file and attach it as well to your response.