This needs two fixes actually. But one thing first: while you do these changes there must be no VirtualBox related running. Check with the command
that nothing is active. As long as the command shows any output you can't start.
Fix 1: Use some sensible text editor which doesn't do automatic line breaks and some such. Should be the case for all of them on Linux if you don't tell them to do something odd.
Initially it has the following section:
Code: Select all
<HardDisks>
<HardDisk uuid="{c397907f-74e8-41b8-873d-083cb9a23c9e}" location="Parrot Sec.vdi" format="VDI" type="Normal">
<HardDisk uuid="{7afa0321-00f4-4578-9f81-d4c819973c68}" location="Snapshots/{7afa0321-00f4-4578-9f81-d4c819973c68}.vdi" format="VDI">
<HardDisk uuid="{c964f084-67a3-40ae-8c92-75d9b6188d58}" location="Snapshots/{c964f084-67a3-40ae-8c92-75d9b6188d58}.vdi" format="VDI"/>
<HardDisk uuid="{c1c90f08-6f8d-467f-91a9-a5f5e1c8ad81}" location="Snapshots/{c1c90f08-6f8d-467f-91a9-a5f5e1c8ad81}.vdi" format="VDI"/>
</HardDisk>
</HardDisk>
</HardDisks>
which you need to turn into
Code: Select all
<HardDisks>
<HardDisk uuid="{c397907f-74e8-41b8-873d-083cb9a23c9e}" location="Parrot Sec.vdi" format="VDI" type="Normal">
<HardDisk uuid="{7afa0321-00f4-4578-9f81-d4c819973c68}" location="Snapshots/{7afa0321-00f4-4578-9f81-d4c819973c68}.vdi" format="VDI">
<HardDisk uuid="{c964f084-67a3-40ae-8c92-75d9b6188d58}" location="Snapshots/{c964f084-67a3-40ae-8c92-75d9b6188d58}.vdi" format="VDI">
<HardDisk uuid="{c1c90f08-6f8d-467f-91a9-a5f5e1c8ad81}" location="Snapshots/{c1c90f08-6f8d-467f-91a9-a5f5e1c8ad81}.vdi" format="VDI"/>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisks>
Probably the best approach is using copy/paste (the forums have the "CODE: SELECT ALL" link which should help getting the right thing into the clipboard, but be extra careful that you don't change/delete anything else.
Guess now you know why I insisted you create a backup, because worst case you can restart...
Fix 2: Repair the broken parent UUID. The command you found is in principle correct, but the error message hinted to use the wrong UUID due to the additional VM config screwup.
Code: Select all
VBoxManage internalcommands sethdparentuuid '/home/abc/VirtualBox VMs/Parrot Sec/Snapshots/{c1c90f08-6f8d-467f-91a9-a5f5e1c8ad81}.vdi' c964f084-67a3-40ae-8c92-75d9b6188d58
Once that's done you can fire up the VirtualBox GUI. First you should check that the yellow blobs you had in your img_001.png screenshot are gone (in Virtual Media Manager), and it's a 'linear chain' (previously c1c9... and c964... were at the same level, now c1c9 should be one level below c964). If that's the case and you see no other problems (the VM shouldn't show up as 'Inaccessible') then you can start it.
Fingers crossed.
(I'll be likely offline over the weekend, will see the success report hopefully on Monday.)