virtualbox.org

Hi,
I have an old PC with Ubuntu 14.04 as host and VirtualBox 4.3.12, inside Windows 7 as guest. I got a new PC today - I installed the same software Ubuntu 14.04 as host, VirtualBox 4.3.12 and I have copied "Windows 7" directory (vdi file and all of the files and both subfolders Logs and Snapshots - this two subfolders are empty). When I start virtual guest on new PC this happens:
a) VirtulaBox BIOS window opens
b) Windows is starting up with message: "Windows is loading" and progress bar displayed.
c) When progress bar gets to the end step a) appears and then endless looping between Windows is loading and VirtualBox BIOS window.

I am wondering if this is proper way of migrating from old PC to new PC (obviously they are not the same hardware - old having 2 CPU cores and 4 GB RAM and new has 4 CPU cores and 8 GB RAM etc).

Quetions:
1. Should I execute File | Export appliance on old PC and then after OVF file is created import applicance in new PC?
2. There is default setting of OVF 1.0. Should I use this or OVF 2.0?
3. When I import appliance will there be VDI disk or VMDK or something else?
Regards

loukingjr wrote:Moving a VM

Yes, I have done exactly as is described in this tutorial and I have run into a problem reported in first post. Just wondering should I uninstall VirtualBox Guest Addins from my Windows 7 virtual guest before coping virtual machine folder from old to new PC? (It is not described in tutorial).

The continuous loop sounds like a BSOD reboot. See Chapter 12 Troubleshooting Windows guests for how to record the information needed.

I have solved the problem.

I tried both options (from my two posts above) and both are working fine:
USING APPLIANCE
1. In old PC in Windows no changes, VirtualGuest are installed and not removed. Shut-down Windows guest if running.
2. File | Export Appliance
3. Selecting default OVF 1.0 data format.
4. Move OVF file to new PC.
5. On new PC: File | Import Appliance.
6. Start virtual machine.
7. Windows 7 started without a problem.

COPYING VIRTUAL MACHINE FOLDER
1. On old PC: Start Windows.
2. Uninstall "Oracle VM VirtualBox Guest Additions" --> Previously I didn't do this step so getting in endless loop restarting Windows before even they were started, so VERY IMPORTANT step, that should not be skipped.
3. Restart Windows --> It is important that you restart Windows after 'virtual guest addins' are removed, because Windows remove some components after restart is executed, because addins are modules (drivers) that are in use by Windows.
4. Shutdown Windows.
5. In command line program (terminal on Linux) move to directory where virtual machines are stored. Display content of that directory, in my case it is Windows_7 witch is a virtualbox directory of my Windows_7 virtual machine.
6. I have compressed Windows_7 directory (because I am moving this files over little bit slow local network), so in Linux host I did:
tar -zcf archive.tar.gz
7. I have moved compressed archive file over FTP to my new PC.
8. On new PC I have uncompressed archive in <virtual_box_virtual_machine_directory> --> the directory from File | Preferences | General tab | Default machine folder (but it can be any other path as well) using command:
tar -xf archive.tar.gz
Note: Steps 6, 7 and 8 can be skipped if you have some decent USB hard drive that can be used to transfer virtualbox virtual directory.
9. Started VirtualBox GUI and selected Machine | Add and pointed to the Windows_7 directory of my virtual machine ".vbox" file.
10. Started Windows. Windows started normally without a problem and requested to "Restart Windows" again, I restarted it (just in case).
11. After Windows restart I have installed back VirtualBox Guest Addins (removed in step 1).

That's it, problem solved. Ahhhh, yes, which solution did I finally accept as my solution: The second one. Why? If using first solution (export-appliance) the vmdk (default VMware file format) is created. I think this is solid solution, but I know VDI (second solution) is much much more tested in VirtualBox environment, so I prefer solution 2, to keep VDI file as storage file type.

Thanks a lot for tips and advices.
Regards

It sounds like your problem was caused by leaving the guest additions .iso mounted as you tried to move your guest. once you mount the .iso and install the guest additions, you should unmount the guest additions .iso whether you are moving a VM or not.