VMLite and VirtualBox are actually the same

VMLite and VirtualBox are actually the same
 
 
 
Today, I want to run the previously installed VMLite virtual machine, but it cannot be started. I want to fix it, but I have already installed VirtualBox. It seems that I have not installed VirtualBox.
 
However, since I installed it, I simply uninstalled VMLite and installed VirtualBox.
 
After it is installed, you cannot import virtual machines created by VMLite.
 
The configuration file extension of VMLite is xml, while that of VirtualBox is vbox.
 
However, the original format is the same.
 
Therefore, you can import the xml file into vbox.
 
However, there are two problems:
 
1. It is about to be re-activated.
 
2. The Network Name of the original shared space is different:
 
\. Host \ sfs \ vboxsvr \
 
1. Configuration File
 
The configuration file of VMLite is in % USERPROFILE % \ VMLite \ VirtualBox. xml
 
The VirtualBox configuration file is in % USERPROFILE % \. VirtualBox \ VirtualBox. xml
 
To manually modify the configuration file of VMLite, you must stop two processes: VMLite and VBoxSvc. In fact, you must stop the second process. As long as you have run VMLite, the two processes will be resident, and the first process will be added each time it runs. Therefore, it will be aborted by the way. If you do not stop the two processes, the manually modified configuration is invalid. That is, all the configurations of VMLite are restored when you start it. At the beginning, I noticed that the process was not aborted. For this reason, I looked around to see if there are configuration files elsewhere. Of course not.
 
Second, the configuration file is divided into two parts. One is the global configuration file, which mainly describes the locations of each virtual machine, virtual hard disk, and snapshot. The other is the configuration file of a specific virtual machine, which is saved in the directory of each virtual machine. The file name is the name of the virtual machine, and the extension is also. xml.
 
Third, VMLite does not enable the VM function. That is to say, once the master configuration file is lost, it will be very troublesome. However, the new version of VirtualBox has the OPEN function, which is more convenient.
 
 
 
2. Coexistence of VMLite and VirtualBox
 
Create two batch files respectively:
 
1. VMLite
 
D:
 
Cd "D: \ Program Files \ VMLite Workstation"
 
Start/waittaskkill/f/im vboxsvc.exe
 
Start/waittaskkill/f/im vmlite.exe
 
Start/waittaskkill/f/im virtualbox.exe
 
 
 
Regsvr32/svboxc. dll
 
Start vboxsvc
 
Vmlite
 
 
 
2. VirtualBox
 
D:
 
Cd "D: \ Program Files \ Oracle \ VirtualBox"
 
Start/waittaskkill/f/im vboxsvc.exe
 
Start/waittaskkill/f/im vmlite.exe
 
Start/waittaskkill/f/im virtualbox.exe
 
 
 
Regsvr32/s/uvboxc. dll
 
Regsvr32/svboxc. dll
 
Start vboxsvc
 
Virtualbox
 
 
 
The reason for adding start is to end the process that cannot exit normally, and to execute the next command to start the virtual machine before vboxsvc exits. Because VirtualBox cannot be started if it exits.
 
 
 
3. Use VBoxManage of a higher version for management
 
1. Modify the uuid of the disk.
 
Use internalcommans sethduuid
 
Commands of earlier versions can only be uuid again, but uuid cannot be specified.
 
During VMLite exploration, the existing virtual machine function was not registered, and the method of creating a virtual machine from the disk was used, resulting in a new disk uuid, it is inconsistent with the existing description in the configuration file. Of course, if the disk does not have a snapshot, just change the uuid in the configuration. However, if a disk has a snapshot, it not only has a uuid, but also has a name called parentuuid, pointing to the parent disk. At this time, if the uuid of the parent disk is not reset, there is no way to access the snapshot.
 
2. Modify the disk's parentuuid
 
Use internalcommanssethdparentuuid
 
However, it fails. Although the command has no error, it seems that it has no effect.
 
3. Modify the location of the default configuration file.
 
Not found yet.

From hadstj's column