TerryE, thanks again for trying to help me. I've got it to that sate that I can see both VM's in main VirtualBox window (accepted as common VM's made by it). It's a really complicated way... In short what I did is:
1). Modify %USERPROFILE%\.VirtualBox\VirtualBox.xml:
Code: Select all
<MachineRegistry/>
--- replace with:
<MachineRegistry>
<MachineEntry uuid="{776eacc7-0fa0-49e9-aaec-37b67d9d1965}" src="D:\VM\VB\W7B1\W7B1.xml"/>
<MachineEntry uuid="{75da2984-4b2d-4380-8944-5cfc81620b22}" src="D:\VM\VB\WXP-SP3\WXP-SP3.xml"/>
</MachineRegistry>
where: "{75da2984-4b2d-4380-8944-5cfc81620b22}" is taken from "D:\VM\VB\WXP-SP3\WXP-SP3.xml" ( <Machine uuid="{75da2984-4b2d-4380-8944-5cfc81620b22}" ...).
2). Go to "File | Virtual Media Manager | CD/DVD Image" and add new image pointing to an ISO file. Click OK. Exit VirtualBox.
3). Open %USERPROFILE%\.VirtualBox\VirtualBox.xml file and note new uuid associated with added ISO file.
Code: Select all
<DVDImages>
<Image uuid="{0bf774e9-b973-4b7a-9d48-2a1cccbd196a}" location="D:\Storage\m$\en_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-73974.iso"/>
<Image uuid="{13ac756a-7667-4d3b-b2a1-43119480e8ca}" location="\\192.168.11.6\archive\Soft\m$\OS\W7B1\W7B1_256MB.ISO"/>
</DVDImages>
4). Edit "D:\VM\VB\WXP-SP3\WXP-SP3.xml" replacing:
Code: Select all
<DVDDrive passthrough="false">
<Image uuid="{a485ea0a-ad7e-4214-b448-864a4a5460f9}"/> <-- old value
</DVDDrive>
--- replace with:
<DVDDrive passthrough="false">
<Image uuid="{0bf774e9-b973-4b7a-9d48-2a1cccbd196a}"/> <-- new value
</DVDDrive>
5). Add hard disk(s) in "VirtualBox File | Mirtual Media Manager | Hard Disks" and Add new one pointing to root VDI files.
6). If there are snapshots (like with W7B1) - edit %USERPROFILE%\.VirtualBox\VirtualBox.xml:
Code: Select all
<HardDisks>
<HardDisk uuid="{e3e4629e-77ef-4945-b2fb-8e309c5d697c}" location="D:\VM\VB\W7B1\W7B1.vdi" format="VDI" type="Normal">
<HardDisk uuid="{47f19991-2d74-4b6c-b249-143f6f99cded}" location="D:\VM\VB\W7B1\Snapshots\{47f19991-2d74-4b6c-b249-143f6f99cded}.vdi" format="VDI"/>
</HardDisk>
<HardDisk uuid="{dfb22f7f-121b-4bbc-8893-ce496ea6c2c5}" location="D:\VM\VB\WXP-SP3\WXP-SP3.vdi" format="VDI" type="Normal"/>
</HardDisks>
Note: snapshot hard disk file is within main hard disk and it doesn't have "type" attribute.
Note2: snapshot hard disk in W7B1.xml file has associations:
Code: Select all
<Snapshot uuid="{af986cbf-9c83-440d-91dc-617d7d9d30e5}" name="Just installed" timeStamp="2009-01-16T07:22:51Z" stateFile="Snapshots\{af986cbf-9c83-440d-91dc-617d7d9d30e5}.sav">
...
<HardDiskAttachments>
<HardDiskAttachment hardDisk="{e3e4629e-77ef-4945-b2fb-8e309c5d697c}" bus="IDE" channel="0" device="0"/>
</HardDiskAttachments>
</Snapshot>
...
<HardDiskAttachments>
<HardDiskAttachment hardDisk="{47f19991-2d74-4b6c-b249-143f6f99cded}" bus="IDE" channel="0" device="0"/>
</HardDiskAttachments>
</Machine>
Note3: Snapshot folder contains 3 files:
Code: Select all
{af986cbf-9c83-440d-91dc-617d7d9d30e5}.sav - made earlier (at snapshot time) - ref. as snapshot HD
{776eacc7-0fa0-49e9-aaec-37b67d9d1965}.sav - made later, it's uuid of machine
{47f19991-2d74-4b6c-b249-143f6f99cded}.vdi - made later, it's current HD of machine
main folder contains:
Code: Select all
W7B1.vdi - associated with uuid="{e3e4629e-77ef-4945-b2fb-8e309c5d697c}" (snapshot HD, not machine HD)
Now I can see both VM's in VB. WXP-SP3 has editable properties (right side of VB has Genera, Hard Disks, etc. as links) and W7B1 has undeniable properties (all those links items are just a names, not links). And so far I do not know why.
I've made copy of WXP-SP3 by copying its .vdi file, changing its uuid (using "VBoxManage.exe internalcommands setvdiuuid D:\Path\aFile.vdi" command). Both WXP-SP3 and WXP-SP3_2 were started successfully (I'm not so confident with W7B1 machine - so far I've not attempted to run it yet). I'm starting experiencing problems with VB v2.1.2 crashing on WXP-SP3_2 guest machine more often than I have seen it with old version v2.1.0. I think it's a separate case and is not related to what we're discussing here. So, I've posted it in another thread on this forum (
http://forums.virtualbox.org/viewtopic.php?t=13612).
Looking at the complexity of the way to fix the problem - I think that if 'aVirtualMachine.xml' file contained all setting related to that VM in one place (instead of spreading uuid's among all virtual machines and one "VortualBox.xml" file as it's done now) it would make this job easier. But frankly I expect that this process should be done automatically by VB itself... It's a common case (re-using VM, copy VM to another place, backup VM, etc.) and it should be easier for users like me. don't you think?