Ticket #10357 (closed defect: obsolete)

Opened 6 years ago

Last modified 23 months ago

Virtualboxes suddenly become inaccessible

Reported by: doveman Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.10 Keywords:
Cc: Guest type: Windows
Host type: Windows


I was using Virtualbox fine yesterday and then one time I opened it and most of my Vboxes were inaccessible, as shown here:


It also warned me about some ISOs being unavailable, but when I tried to remove them it just gave me errors.

I closed Vbox and re-opened it and it seemed to sort itself out as shown here:


However, this morning it's back as it was in the first picture, is warning me about missing ISOs that I can't delete again and closing Vbox and re-opening it isn't helping.

Attachments Download (7.9 KB) - added by doveman 6 years ago.

Change History

Changed 6 years ago by doveman


comment:2 Changed 6 years ago by doveman

I'm also getting errors removing any ISO from VMM - which I've reported here.

If I remove the inaccessible machines and try to add one back, it fails saying the VDI can't be closed as it's still attached to a virtual machine (or it has the same UUID as an existing machine).

If I create a new machine and add the existing VDI, it boots partway but then hangs, although this could be a machine configuration problem.

If I then try to add the old machine, it fails but after that, my new machine is inaccessible as well and if I remove it and try to add it back, that fails with an error as well.

Version 0, edited 6 years ago by doveman (next)

comment:3 Changed 6 years ago by doveman

I also get an error when removing VDIs, but as with ISOs after restarting Virtualbox the VDI has gone from the list. After doing this for my TS25.VDI and TSBuild.VDI and restarting Virtualbox I was able to re-add my Thinstation Build machine (which has both those VDIs attached), which before I couldn't do. It's in Aborted state, which is how it was before half my machines became inaccessible. When I started it, the boot got held up for a while whilst the HD chugged away but it's working normally now.

Even after this, then removing TS25.VDI from that machine, removing it from VMM (which gives an error but removes it when I restart Vbox) I still can't re-add my Thinstation test machine though (which has TS25.VDI attached).

comment:4 Changed 23 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use