Guest machines crashing on migration to new OS

[Anakunda]

Hello, after moving to new Windows (and migrating VirtualBox) I can't run any of my guest OSs:

I get error: http://i.imgur.com/Fo08dmd.png

(VirtualBox crashes on clipboard copy)

Question: do I have to re-create virtual machines from zero or can I adjust the network adapters to new environment?

[mpack]

You shouldn't have to change anything unless you want to. The VMs should be 100% forward compatible.

In any case I (literally) don't understand your error report. Are you saying that the guest only crashes on a clipboard copy, i.e. when typing Ctrl+C ?

Post a VM log file: Right click the VM in the GUI. Select "Show Log". Save "VBox.log" to a file. Compress that file and attach it to a message here. Make sure the VM is fully shut down before taking a log.

[Anakunda]

No the VBox crash is secondary to initial VM crash (due to clipboard copy which is problem of self VBox). Primary error is something about network adapter.

I guess on new OS VBox instalation, it created new unique virtual network adapters which the guest VM can't access (supposedly it requests unique network adapters from old OS).

My question was if I can adjust new VBox install to match it's network adapters to old instance or I can adjust the VM definitions to request new virtual network adapters.

[mpack]

If you moved the entire VM to the new host (not just moved the VDI), then the virtual network adapters would move with the VM. If you are using Bridged Mode for networking then you have have select again which NIC you want to bridge to. Switching to NAT mode is also possible.

I asked you for a log file. Among other things that would tell me what the new host OS is ("new Windows" is not explicit), since you neglected to mention it already.

[Anakunda]

I copied all "%UserProfile%\VirtualBox VMs" dir so I suppose everything was copied.

[mpack]

As I suspected, "new Windows" means you're using Windows 10, an unsupported host OS. It would have been better if you mentioned that right away, as that explains why bridged networking is not working.

We already have a topic to discuss Window 10 as a host. See here: viewtopic.php?f=6&t=68590

I suggest you read the posts in that topic. In the meantime I will lock this one.