Move Windows VM from FreeBSD to OSX, ERRORS

[bluegroper]

Hi forum
My current host is Intel i5, FreeBSD 13.3 with VirtualBox 6.1.
My guest is Win10.
I'm trying to move the Win10 guest to OSX host (Intel not Apple silicon) with VirtualBox 7.0.18
I've tried doing the export to .ova, copy the file to OSX, then import into Virtualbox.
Keeps getting the windows BSOD with message "Your device ran into problems and needs to restart. Yadda yadda".
And the VM then just freezes.
So I deleted the guest, and then copied the entire directory from FreeBSD to OSX.
Directory containing the .vbox file, .vdi file and logs
Then in VirtualBox on OSX, Add the machine just copied.
Startup gives exact same error message as the export, import routine above.
Please, any clues for how to get this working in OSX ?

[multiOS]

Hopefully, the external 'drive' you used to transfer the VM between the two computers was not formatted as FAT32?

The Windows 'Blue Screen' as I'm sure you know means a problem within the Windows Operating System. The error code should give a better indication of the actual problem.

[bluegroper]

I didn't use any external 'drive'.
Files copied to OSX using ethernet connection to smb server on FreeBSD.
Underlying partition scheme and filesystem should not be an issue.
Thanks for any further suggestions to get this VM guest working on OSX host.

[multiOS]

One possibility is that some incompatibly is being introduced because of the different VirtualBox versions on the BSD and the macOS systems. Newer macOS versions which deny the installation of third-party kexts (kernel extensions) are not compatible with VirtualBox 6.1.xx, so the only equalisation option may be to upgrade the VirtualBox installation on the BSD system, if that is possible. If that can be done you could also then upgrade any VM's Guest Additions installation prior to the transfer. Then after confirming you still have a working VM, try re-copying the VirtualBox VM Folder across to the Mac. (Don't bother with the OVA approach as that can introduce further complications, including the loss of Windows activation)

Once you've confirmed that the VM still runs normally on the BSD Host; and ruled out any possibility of file 'corruption' during the movement of the VM files across the network, hopefully you will be able to re-add the VM to the Mac's VirtualBox installation and run it normally. However, if you still get a BSOD (Blue Screen of Death) there are well over 100 BSOD Stop Codes, so it's impossible to even begin diagnosing the actual cause without the specific code. When such problems are experienced, which is not uncommon in Windows, it's usually still possible to log in to the Windows installation in 'Safe Mode' on both hardware and virtual installations, to perform further investigation and determine what user action is needed, which inevitably means some form of Windows system 'repair' action.

https://support.microsoft.com/en-us/win ... 45a66ae3c6