Moving your VMs to a new VirtualBox. (or fixing a broken one)

This is for discussing general topics about how to use VirtualBox.

Moving your VMs to a new VirtualBox. (or fixing a broken one)

Postby MiloTheDev » 14. Jan 2019, 02:40

Most of VirtualBox relies on its VMs.

But sometimes, Your VirtualBox can break. Before you attempt to fix it, (or your trying to get a new virtualbox version)
Lets make sure your VMs are safe so that you don't have to spend your stress reinstalling them,

First, Open the VirtualBox VMs Folder. (it is mainly found in your personal folder and is not hidden.)

Then go into each of your VM Folders and take out the .vhd or .vdi files (in my case its .vhd) and put them on your desktop.

Now, make a Folder on your desktop and put the VHDs or VDIs in them.

Now it is safe to reinstall virtualbox or do whatever you need to do w/ it.

Once you have done that, Remake ALL of your vms, and This time, Don't create the Hard disk. Just use the one you put in your folder on the desktop that corresponds the OS you want.

When you startup your VMs, They will have an OS w/ all your saved VM files on them.

That's how to do it!

Thanks and Hope this helped!

--MiloTheDev.
From, MiloTheDev.
MiloTheDev
 
Posts: 25
Joined: 27. Dec 2018, 02:35
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Windows 7, Windows 8.1, Windows 10 1809,

Re: Moving your VMs to a new VirtualBox. (or fixing a broken one)

Postby socratis » 14. Jan 2019, 03:46

MiloTheDev wrote:That's how to do it!

ABSOLUTELY NOT!

I'm sorry, but this is not the best VirtualBox related advice I've seen, on the contrary! Why would you want to do all that? Just because of a very, very specific problem in your case?

If you are interested in giving advice and guides, consider all the cases. And your suggestion doesn't. It's convoluted, it's error prone, it's simply the wrong way. There's a better one: BACKUP!!!

MiloTheDev wrote:go into each of your VM Folders and take out the .vhd or .vdi files (in my case its .vhd) and put them on your desktop.
Are you going to do that for all ninety (90) of my VMs? Are you sure you want to do it like that?

MiloTheDev wrote:Now it is safe to reinstall virtualbox or do whatever you need to do w/ it.
The two are not related. At all actually!

MiloTheDev wrote:Once you have done that, Remake ALL of your vms, and This time, Don't create the Hard disk.
Are you sure you want to recreate 90 VMs? Do you remember the settings for 90 VMs? I most certainly don't. That's why I make a

    BACKUP!!!
Or two.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 21487
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Moving your VMs to a new VirtualBox. (or fixing a broken one)

Postby MiloTheDev » 14. Jan 2019, 03:53

SHUSH
From, MiloTheDev.
MiloTheDev
 
Posts: 25
Joined: 27. Dec 2018, 02:35
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Windows 7, Windows 8.1, Windows 10 1809,

Re: Moving your VMs to a new VirtualBox. (or fixing a broken one)

Postby MiloTheDev » 14. Jan 2019, 04:00

socratis wrote:BACKUP!!


Well how would you do that if...

windows errorz.PNG
windows errorz.PNG (17.91 KiB) Viewed 178 times
From, MiloTheDev.
MiloTheDev
 
Posts: 25
Joined: 27. Dec 2018, 02:35
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Windows 7, Windows 8.1, Windows 10 1809,

Re: Moving your VMs to a new VirtualBox. (or fixing a broken one)

Postby socratis » 14. Jan 2019, 05:21

MiloTheDev wrote:SHUSH

Come again? Are you actually trying to "shush" another user? Seriously?
The Forum Posting Guide wrote:Whilst we accept that some robust debate may be appropriate, we will not accept unnecessarily aggressive or rude behavior. So please, no matter what your personal frustration, try to keep your comments constructive. If you cross this line then the moderators will delete your posts.

This time it's a warning only; the first and last one. I do not want to see such behavior again!
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 21487
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Moving your VMs to a new VirtualBox. (or fixing a broken one)

Postby andyp73 » 14. Jan 2019, 10:35

MiloTheDev wrote:Well how would you do that if...

Document is empty.
Location C:\Users\milo4\.VirtualBox\VirtualBox.xml

I would either restore C:\Users\milo4\.VirtualBox\VirtualBox.xml from a backup or I would go to C:\Users\milo4\.VirtualBox and if VirtualBox.xml-prev isn't zero bytes copy that back to VirtualBox.xml. I would then look to try and understand the cause of why a file has got written as 0 bytes when it shouldn't have.

-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
andyp73
Volunteer
 
Posts: 1227
Joined: 25. May 2010, 23:48
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation

Re: Moving your VMs to a new VirtualBox. (or fixing a broken one)

Postby MiloTheDev » 15. Jan 2019, 02:32

andyp73 wrote:I would go to C:\Users\milo4\.VirtualBox and if VirtualBox.xml-prev isn't zero bytes copy that back to VirtualBox.xml.

Thanks! It worked perfectly!!!!
Also it worked for my broken Windows 7 VM!!! (w/ Windows 7.vbox-prev!)
From, MiloTheDev.
MiloTheDev
 
Posts: 25
Joined: 27. Dec 2018, 02:35
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Windows 7, Windows 8.1, Windows 10 1809,


Return to Using VirtualBox

Who is online

Users browsing this forum: No registered users and 13 guests