[Exception resolution] VirtualBox from. VDI backup files new/restored virtual machines (including recovery of individual backup nodes)

First, preface:

Virtual machines in VirtualBox on Ubuntu can cause the entire virtual machine to break if it shuts down improperly, and it is difficult to restart it with various debug methods. You can only restore the system using the individual VDI files that you previously backed up. There is another scenario where you re-install a virtualbox that you want to rebuild in the new VirtualBox with the virtual machines in the old other VirtualBox, including the individual snapshot nodes. Online also have information, but often only text, I looked for a long time have not done. Finally decide to try it yourself, here is a successful graphic tutorial:

Second, step:

　2.0, First look at the old virtual machine snapshot, take a photo to save their UUID tree-like structure (this is very important!). To rebuild the snapshot tree next! ）：

　2.1, first find the old VirtualBox folder:

　　2.2 . Find the Win7-64 folder before the bad, and find the *.vdi file in Win7-64.vdi and snapshots

　　

　　

　2.3, cut WIN7-64.VDI and snapshots to other temporary folders, and then completely delete the win7-64 virtual machine in VirtualBox, remove to VirtualBox The VMs folder goes down to confirm that the Win7-64 folder has not been.

　　2.4 . Create a new win7-64 virtual machine with the same name in VirtualBox, when you arrive at step: ① to VirtualBox VMs folder found VirtualBox has created an empty win7-64 folder ② cut the WIN7-64.VDI and snapshots from the temporary folder to win7-64; ③ and then, when creating a new Virtual PC, choose to use the existing virtual hard disk file and go to VirtualBox vms/ Select the Win7-64.vdi file under Win7-64, ④ the next step until you create a new virtual computer.

2.5, We imitate the structure of the 2.0 old snapshot tree, in the new WIN7-64 the structure of the same tree-like structure (the name can be different):

　　2.6 . Locate the Win7-64.vbox file under the new win7-64 folder:

　2.7, find the following 4 UUID part of the Win7-64.vbox, according to the UUID of 2.0, replace the corresponding UUID with the old (with replace All), save as to the other temporary folder ~

　　

2.8, shutdown, delete the useless VDI file under VirtualBox vms/win7-64/snapshots (the filename is the UUID), Replace the Win7-64.vbox with the temporary vbox file saved in 2.7 (because the virtual shutdown is updated, so the previous step needs to be backed up). This opens the virtual machine, then completes the ~

Third, Dessert:

All of my exception resolutions are placed under this category, saving some exception problem solutions that take a little time to fix.

　

_==/i i \==_
/xx/|\___/| \xx\
/xxxx\ |            Xxxxx| /xxxx\
  |    Xxxxxx\_ _xxxxxxx_ _/xxxxxx| @beautifulzzzz 2016-01-14 continue~
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx e-mail:[email protected]
| Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx|
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
| Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx|
xxxxxx/^^ ^^ "\xxxxxxxxxxxxxxxxxxxxx/^^ ^^ ^\xxxxxx
|xxx| \xxx/^^ \xxxxx/^^ \xxx/|xxx|
\xx\ \x/\xxx/\x//xx/
"\" \x/"/"

[Exception resolution] VirtualBox from. VDI backup files new/restored virtual machines (including recovery of individual backup nodes)