Results 1 to 5 of 5
How do I import an existing Virtual Machines, like if I have a dualboot and make a new VM in the other OS or if I reformat and transfer the ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 12-10-2009 #1
Virtualbox: Import existing Machines
How do I import an existing Virtual Machines, like if I have a dualboot and make a new VM in the other OS or if I reformat and transfer the files back in.
- 12-10-2009 #2
Instead of coping partitions with dd or messing up around.
1. Create a new VM with New Virtual Hard Drive
2. Do not import the old VM.
3. Just add the old Virtual Hard Drive to new VM.
4. Install the OS on new VM on new hard disk.
5. New OS will automatically create a dual boot. most Linux distros will.
6. But if new OS is Windows install it first and then add old disk.
- 12-10-2009 #3
- 12-11-2009 #4
- 12-12-2009 #5
- Join Date
- Nov 2006
We managed to do this - use an existing virtualbox file, copied over from one PC, and onto another.
The way is to run the VirtualBox application on the original setup. Go to the configuration choices, and have it release the virtual drive. I am guessing that this act writes something into the .vdi to make it happen.
Then, move the .vdi to its new home. In my case, I made the new VirtualBox configuration exactly the same in respect of how much memory was allocated, what the maximum size of the drive would be, size of video memory, etc. I do not know if this was strictly necessary, but I did not want to go exploring. I just wanted it to work!
The usual (default) place the virtual drive lives is in /home/username/.VirtualBox/HardDisks/the-name.vdi, but it does not have to be. I like to put them where there is space elsewhere.
Then, on the destination VirtualBox system, when it comes to setting up the hard drive, click the Hard Disks setup. Get to the place where you add an Attachment, navigating to your .vdi and selecting it. You can also check to see which others are "attached", and, of course, "release" any you want to move or trash. If you separately delete a .vdi virtual drive, VirtualBox will complain, until you also remove (ie. release!) it from the list of drives it considers "attached".
I should also mention that at the time, I had help. I was just watching, and that was the process as I understood it. If any of the above is wrong in some detail, I am sure there are folk here who can help.