Opened 7 years ago
Last modified 7 years ago
#17254 new defect
VM inaccessible due to guest additions attach issue
| Reported by: | Rafcio | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.0 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Windows |
Description
After upgrading to version 5.2 initially there was no issue with the guest (eComStation) and I was able to start it a few times and also installed the new guest additions in it. Last time it seemed to shut down fine, but now I'm unable to start the guest. In the GUI is shows as inaccessible.
The error message is:
Cannot attach medium 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' {a2ff5d7d-6ede-4ade-80df-1ffc0ccfa03c}: medium is already associated with the current state of machine uuid {ee69103a-fec1-489f-adf2-25eb10922ba1}!.
Result Code:
VBOX_E_OBJECT_IN_USE (0x80BB000C)
I don't understand how this non-essential medium can make the guest inaccessible, however the worst thing is that the Settings icon is disabled for the client, so I can't detach the guest addition image nor make any changes. And the guest addition image is there and I even re-installed it with no effect.
The log file seems to be from the time the last successful launch of the guest.
Attachments (2)
Change History (7)
by , 7 years ago
comment:1 by , 7 years ago
Medium registry conflicts prevent loading of VM configs, as you noticed. This is a safety measure, as such inconsistencies can lead to data loss. That it fires for the guest additions ISO isn't typical, and shouldn't happen "out of the blue".
To help you I'd need the .vbox file, and I hope I can find a hint why you get this particular error. It's not the usual problem, so it needs a bit more care (the typical trouble with guest additions is that 2 VMs use it with a different UUID, but that's give a rather different error message).
comment:2 by , 7 years ago
It's weird that it happened out of the blue, but I'm more worried that the Settings is disabled, so I can't do nothing on my own and I wouldn't risk editing .vbox file manually. Could that be something in 5.2? After all the GUI seem to be quite refreshed.
comment:4 by , 7 years ago
You have 2 DVD drives, with the same medium. Not allowed (and the API should refuse this). Delete line 104 from your .vbox file if you want to get it fixed minimally (i.e. you want to keep the 2nd DVD drive), or lines 103 to 105 if you want to get rid of the 2nd DVD drive (rarely needed).
comment:5 by , 7 years ago
Actually I've fixed that by restoring (quite old) .vbox file from backup. However I'm wondering how could this happen? I did the same thing I always do and for years I didn't have this issue. Somehow 5.2 code must be doing something differently as this happened "on its own". As you've said the code should not allow it. I have the additions in the first optical drive and the second is normally empty. I don't remember if I've additionally "loaded" additions image from the window menu, but even if so the code should know it was already loaded and don't load it again into a second drive. Something for developers to look into as I didn't specifically load a second copy.


Log file