Hi
I got this error message:
---------
Hard disk '/Users/********/Library/VirtualBox/HardDisks/WinXPHome.vdi' with UUID {0937df07-60c8-4360-ac63-56b39241777d} cannot be directly attached to the virtual machine 'WinXPHome' ('/Users/********/Library/VirtualBox/Machines/WinXPHome/WinXPHome.xml') because it has 1 differencing child hard disks.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {6d9212cb-a5c0-48b7-bbc1-3fa2ba2ee6d2}
----------
I found an entry in the forum which explains how to overcome it (http://forums.virtualbox.org/viewtopic. ... 17&start=0) but the solution was to clone the snapshot VDI and attach it to a new VM.
Now, this works to some extent (the machine is fine though there is something quirky about the screen size). However, it does not actually fix my original machine.
Is there a way to fix my orignal machine and get rid of the error?
Thanks,
Y.Farkash
Inaccessible VDI
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Inaccessible VDI
The point of cloning is that you create a new VM around the clone, make sure it works, then delete the original. You do that because once a snapshot tree goes awry it can be difficult to fix. Difficult meaning you would need an expert on hand to do it.
Having said that, the error message you report doesn't look very serious. It's a message you usually see when you try to attach a VDI+offshoots to a second VM, which VBox doesn't like for technical reasons (hence clone first, attach clone to 2nd VM). The VDI should however still be working fine in the original VM, which was the one that created the snapshots. Unless you have skipped something in your description of the problem?
Having said that, the error message you report doesn't look very serious. It's a message you usually see when you try to attach a VDI+offshoots to a second VM, which VBox doesn't like for technical reasons (hence clone first, attach clone to 2nd VM). The VDI should however still be working fine in the original VM, which was the one that created the snapshots. Unless you have skipped something in your description of the problem?