Virtualbox migration from drive C

 

Even if virtualbox is installed on another disk, the Virtual Machine (system, hard disk) made of it will still be generated to the system disk by default, and the default is C: disk, as the number and content of virtual machines increase, it is inconvenient to squeeze out the system disk space that is not large.

 

Start to mount C: Under the disk. everything in the virtualbox directory is copied elsewhere. In the file/environment settings of virtualbox, modify the "Default hard disk directory" and "Default hypothetical Machine", but virtualbox does not recognize the account. It is suspected that path-related content is written in the registry or UUID.

 

Delete the existing virtualbox (do not save the content in. virtualbox ). After the installation is re-installed, it is taken for granted that no information is available, but do not rush to back up the hard disk and Vm information at that time, such data will not be lost, the driver settings of the secondary VM should not be lost.

 

Next, create a new VM.

1. In the file/environment settings of virtualbox, direct the "Default hard disk directory" to the backup location, and direct the "Default hypothetical Machine" to the system directory, because this cannot be changed and the VM

The size is not very large. It is acceptable to store it on the C drive.

2, and then start to create a VM. After setting the memory size of the VM, do not select the new specification for setting the VM hard disk, but choose to use the existing hard disk. Done!

However, network settings are lost, and these are saved to the XXX of each VM in the machines directory. XML, but backup is not available. XML to overwrite the new machine. it is useless to overwrite the XML file. The UUID contains information related to the directory, time, and so on. inconsistency may cause unavailability of new machines. I do not know whether the uuid replacement is valid. I have not tried the time relationship.

Above.