VirtualBox 升级破坏了我的虚拟机 [英] VirtualBox upgrade trashed my virtual machine

问题描述

我让 Virtual Box 3.2 运行良好，在 64 位 Windows 7 主机中模拟 32 位 Windows XP.然后我升级到 VirtualBox 4.0.4，一切似乎都正常(在我安装了一些东西之后——USB2.0 支持、Guest Additions).
然后我恢复了一个在3.2版本下拍摄的快照，现在我已经失去了一切.我收到错误消息:

所选的虚拟机*不可访问*.请检查显示的错误消息如果要重复可访问性检查，请按 **Refresh** 按钮:找不到 UUID {b0e666ef-1041-415a-8329-876b337e1958} 的打开硬盘.结果代码:VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)成分:虚拟盒子界面:IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff}

我尝试从 vdi 文件创建一个新的虚拟机，但它在加载 WINDOWS\System32\DRIVERS\lfsfilt.sys 时锁定.我尝试重新安装 3.2 版，但我遇到了完全相同的问题.

我的 .VirtualBox 目录中有一个 VirtualBox.xml 文件，.VirtualBox 目录中有各种文件(Virtual Dell.xml、Virtual Dell.xml-prev 等)代码>.VirtualBox\Machines\Virtual Dell.

请帮忙！如何恢复我的虚拟机?

解决方案

这个 bug 最近发生在我身上(我假设它是 VirtualBox 的 bug)在 v4 中使用快照.

我修复了打开 VirtualBox.xml 文件并:

1. 搜索丢失驱动器的 UUID(在本例中为 b0e666ef-1041-415a-8329-876b337e1958)，通常是一个标签(注意/>).
2. 删除产生错误的标签.
3. 现在，如果有问题的 HardDisk 标签位于另一个 HardDisk 标签(一个带有打开和关闭标签的标签)内，则无需关闭即可将最后一个标签重新转换为一个标签.

对不起，我的英语不够好，无法很好地解释，让我举个例子:

原始的非工作 XML 片段:

<前><硬盘><硬盘uuid="{ac511969-288a-44b4-b7ac-df5808c1a4ca}"location="/home/me/.VirtualBox/HardDisks/machine_name.vdi"格式=VDI"类型=正常"><硬盘uuid="{e4e44e9d-aad0-4e2f-8ef8-d3d4d64f997f}"location="/home/me/.VirtualBox/Machines/machine_name/Snapshots/{e4e44e9d-aad0-4e2f-8ef8-d3d4d64f997f}.vdi"格式=VDI"/><!-- 有问题的快照--></硬盘></硬盘>

固定的 XML 片段:

<前><硬盘><硬盘uuid="{ac511969-288a-44b4-b7ac-df5808c1a4ca}"location="/home/me/.VirtualBox/HardDisks/machine_name.vdi"格式=VDI"类型=正常"/><!-- 请注意，我们已经更改了这个标签并删除了他的结束标签，因为它不再需要了 --></硬盘>

这至少对我有用，我丢失了快照但恢复了虚拟机.

希望对您有所帮助.

I had Virtual Box 3.2 working fine, emulating 32-bit Windows XP in a 64-bit Windows 7 host. Then I upgraded to VirtualBox 4.0.4, and everything seemed to work (after I installed a couple of things -- USB2.0 support, Guest Additions).
Then I restored a snapshot that was taken under version 3.2, and now I've lost everything. I get the error message:

The selected virtual machine is *inaccessible*. Please inspect the error message shown
below and press the **Refresh** button if you want to repeat the accessibility check:

Could not find an open hard disk with UUID {b0e666ef-1041-415a-8329-876b337e1958}.
Result Code: 
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Component: 
VirtualBox
Interface: 
IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff}

I tried creating a new virtual machine from the vdi file, but it locks up when loading WINDOWS\System32\DRIVERS\lfsfilt.sys. I tried re-installing version 3.2, but I get exactly the same problems.

I have a VirtualBox.xml file in my .VirtualBox directory, and various files (Virtual Dell.xml, Virtual Dell.xml-prev etc.) in .VirtualBox\Machines\Virtual Dell.

Help please! How do I get my virtual machine back?

解决方案

This bug happened to me recently (I assume it's a VirtualBox bug) using snapshots in v4.

I fix'em opening the VirtualBox.xml file and:

1. Search the UUID of the missing drive (b0e666ef-1041-415a-8329-876b337e1958 in this case), normally will be a tag (notice the />).
2. Remove the tag which generate the error.
3. Now, if the problematic HardDisk tag was inside another HardDisk tag (one with open and close tag) reconvert this last tag in one without close.

Sorry, my english it's not good enough for a good explanation, let me show you an example:

Original non-working XML piece:

<HardDisks>
    <HardDisk uuid="{ac511969-288a-44b4-b7ac-df5808c1a4ca}" 
        location="/home/me/.VirtualBox/HardDisks/machine_name.vdi" 
        format="VDI" type="Normal">
        <HardDisk uuid="{e4e44e9d-aad0-4e2f-8ef8-d3d4d64f997f}" 
            location="/home/me/.VirtualBox/Machines/machine_name/Snapshots/{e4e44e9d-aad0-4e2f-8ef8-d3d4d64f997f}.vdi" 
            format="VDI"/>  <!-- Problematic snapshot -->
    </HardDisk>
</HardDisks>

Fixed XML piece:

<HardDisks>
    <HardDisk uuid="{ac511969-288a-44b4-b7ac-df5808c1a4ca}" 
        location="/home/me/.VirtualBox/HardDisks/machine_name.vdi" 
        format="VDI" type="Normal" /> <!-- Notice we've changed this tag and remove his closing tag since it's not more needed -->
</HardDisks>

This at least works for me, I loose the snapshot but recover the virtual machine.

Hope this help you.

这篇关于VirtualBox 升级破坏了我的虚拟机的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！