VirtualBox

Opened 13 years ago

Closed 12 years ago

#8768 closed defect (fixed)

inaccessible virtual machine

Reported by: $roman Owned by:
Component: virtual disk Version: VirtualBox 4.0.2
Keywords: Cc:
Guest type: Windows Host type: Windows

Description (last modified by Frank Mehnert)

I created a v.m. with Windows Server 2003 and took some snapshots. I then created another v.m. and told it to use the original drive or one of the snapshots (don't exactly remember) for its hard drive. I have done this in previous versions of VirtualBox with no problem. At one point I realized that I had named my second v.m. wrong and changed the name. Everything seemed fine until I needed to reboot the host machine for some reason. So when I restarted VirtualBox, I immediately got a warning about media not accessible. And the VM that I had created with the shared hard drive was inaccessible. It said in the right hand pane: A differencing image of snapshot {###...} could not be found. Could not find an open hard disk with UUID {###...}. Result Code: E_FAIL (0x80004005) Component: SnapshotMachine Interface: IMachine {###...} On the Warning message, there is a check option to open the Virtual Media Manager. Selecting that, I can see that under a .vdi file that I created with a machine (the one assigned to my inaccessible virtual machine) attached to it is another VDI, the last differencing VDI in the list, and it's inaccessible--{###...}.vdi. The location is C:\Documents and Settings\admin\VirtualBox VMs\pc1pepo01_tst2\Snapshots\{###...}.vdi. And below it says, Attached to: Not Attached. One thing to note is that I originally named the v.m. pc1pepo01_tst2, but then changed it to mc1pepo01_tst2 and the folder name and everything changed as it is supposed to. So, something did not get automatically changed here. I changed all the names of the files in the virtual machine's directory back to a p from an m and also changed that in the .vbox file and also in the main virtualbox.xml file. Then when I started up VirtualBox I had the same inaccessible message, but in the Virtual Media Manager there was no error, though the one disk and a couple of other .vdi's (like the one right above it) also say Not Attached. An extra data disk that I had added now also says Not Attached.

What's going on here? How can I get my virtual machine back? All of the referenced snapshots and vdi files seem to be here.

Host: Windows XP Guest: Windows Server 2003 V.B. version: 4.0.2

Change History (2)

comment:1 by Frank Mehnert, 12 years ago

Sorry for not getting back to you earlier. Is your problem still reproducible with VBox 4.1.6?

comment:2 by Frank Mehnert, 12 years ago

Description: modified (diff)
Resolution: fixed
Status: newclosed

No response, closing.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use