Transfering a VM between PCs

[Nivovar]

Hi,

I've used Oracle VirtualBox for a number of years. I first installed a then current version on a dual core desktop Win7 machine. After a number of years I removed it. 1) During upgrades some VMs became corrupt. 2) It is too much of a CPU burden on a dual core machine. My happiness was impaired. Then I got this quad core Win10 notebook. Later I have upgraded my dual core desktop to quad core and have installed the latest version. On my notebook I had installed Version 5.0.0 (according to docs). My notebook has an odd multi-touch for which mistakes are easy. I have since purchased an optical USB mouse. With the multi-touch I had advertently dragged the cursor across a file system window and scrambled the file hierarchy for my WinXP VM. I had put a lot of work into it using all the DVD software I had for WinXP. So my WinXP VM would not open even though everything is still there but scrambled. Later, after a Microsoft upgrade of Win10, I could no longer open the VirtualBox GUI. Then I installed the latest version of VirtualBox on my now quad core Win7 machine. So far I have encountered no problems.

Over the years I have focussed on operating systems but I am kind of a newbie WRT VirtualBox. I could use some help to recover the work I put in the Win7 VM.

Please outline the proper file hierarchy. I would like to transfer three VMs from my quad core notebook to my quad core desktop. Recall that when VirtualBox opens it lists all the VMs. How is that done?

Thanks in advance.

[scottgus1]

See this tutorial Moving a VM

[socratis]

... During upgrades some VMs became corrupt ... I had advertently dragged the cursor across a file system window and scrambled the file hierarchy for my WinXP VM ... my WinXP VM would not open even though everything is still there but scrambled ... I could no longer open the VirtualBox GUI ... I would like to transfer three VMs ...

I think that you might have bigger problems than moving three VMs.

[Nivovar]

Can you tell me the file hierarchy for your VM?

Thanks in advance.

[socratis]

Can you tell me the file hierarchy for your VM?

I'm not sure I understand the question. The VM has a default hierarchy (everything in the VM folder) unless you messed up with it. What do you have?

Open up VirtualBox manager, right-click on the VM, select "Show in Finder/Explorer/Whatever", ZIP the .vbox file and attach it in your response.

[Nivovar]

It turns out transfer of a VM virtual disk image is far from trivial. Permissions? After I found a work around and transferred Pentoo.vdi into it correct place, Oracle VirtualBox was able to get further into booting. Then I encounter legitimate VirtualBox errors. The errors come with explanations. It looks like I have learned all I need. I have my work cut out for me. Thanks group.

[Nivovar]

Can you tell me the file hierarchy for your VM?

Thanks in advance.

At this time I can say more. I am curious (yellow). I often show hidden files and folders for inspection. They are hidden to protect them from damage by newbies. I cannot remember exactly but I'm sure that is what got scrambled. Then I could not open VM WinXP. Now that I have moved three VM folders to my Win7 machine I am in position to explain the damage that was created but I cannot say why. Now when I try to ADD WinXP VM I get the following error message from VirtualBox GUI:
"
Failed to open virtual machine located in C:/Users/David/VirtualBox VMs/WinXP/WinXP.vbox.

Cannot register the DVD image 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' {9e2d82b9-4a6d-4434-b407-18e3ea7df6b3} because a CD/DVD image 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' with UUID {a11ec904-da21-42e3-a559-46190baa8286} already exists.

Result Code: E_INVALIDARG (0x80070057)
Component: VirtualBoxWrap
Interface: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
"

Please, can anyone explain what I can do to repair the damage? Thanks in advance!

It is apparent that good practice dictates that one should back up important VM folders before any danger like an upgrade of Oracle VirtualBox. I have lost a lot of work that impairs my happiness.

Also, I have downloaded the latest VirtualBox-5.0.14-105127-Win for my Win10 machine. I think that good practice would dictate use of two machines and upgrade by rotation.

Again, thanks in advance to help.

Best

[mpack]

Use File|Virtual Media Manager to release (deattach) media files from VMs.

It is good practice to always eject the GAs ISO after installing the GAs in a VM. Otherwise you will have problems when VirtualBox is updated (i.e. the ISO is replaced by a different one), or when moving hosts (same thing).

[scottgus1]

danger like an upgrade of Oracle VirtualBox

There isn't any. Your guests will stay safe because they aren't touched by an upgrade.

With the multi-touch I had advertently dragged the cursor across a file system window and scrambled the file hierarchy for my WinXP VM

That is dangerous. As you have discovered. Knowing how to use the host PC is essential to proper operation of host and guest.

A guest (VM) consists of a .vbox file and a virtual disk. If you have used snapshots they also will be part of your guest. There is also a Logs folder that is not needed to run the guest but will get created and used as the guest is used.

You tried to register the guest using the .vbox file. If you post that file (in a zip folder, .vbox extensions aren't allowed on the forum) we might be able to tell you what files go in that guest.

In the future, see this tutorial Moving a VM and re-interpret it as "Backing Up a VM".

[Nivovar]

I applied the VirtualBox-5.0.14-105127-Win upgrade on my Win10 machine. There were interesting things happening during the upgrade that gave the impression of quality. I selected the WinXP VM (26GB compressed) and RUN. I got a message about low memory and then crisis. I lost the screen and had to scramble to reboot. I have 4GB RAM and maybe should upgrade to 8GB. After reboot I tried again and it worked. During upgrade any damage was repaired. This is the first time I have experienced VirtualBox repair a VM rather than destroy one. Promote this to your friends.

Thanks.