virtualbox.org

OK, I've actually got this working but I'm afraid there might be unforeseen consequences. Or in other words, am I just asking for trouble?
So I have dual boot laptop with three drives configured like so:
Drive A - SSD w/Win 10 Pro
Drive B - SSD w/Debian Jessie
Drive C - Hard drive formatted NTFS with VMs (and other data)
So far this actually seems to work. The VMs were created under Win10, but Debian Vbox will run them, though it will complain about missing ISO files.
Is there any reason to anticipate problems with this setup? I generally prefer Linux over Windows, but I like being able to play those AAA Windows games as well.

imrazor wrote:though it will complain about missing ISO files. Is there any reason to anticipate problems with this setup?

You've already seen the problems; paths. The way that paths (for mounted ISOs for example) are referenced is different between Windows and Linux. Other than that, if you kept the VM structure the default, you shouldn't see any problems.

Your VirtualBox preferences are going to be different of course.

Thanks for that. I guess I'm just worried about potential filesystem corruption or permission issues, with the data volume being NTFS and non-native to Linux. I've got the Data volume automounting with uid 1000, which will hopefully prevent any permission issues. I take it the config files are universal regardless of which host OS is running Vbox?

imrazor wrote:I take it the config files are universal

If you're talking about the .VBOX file, the "recipe" of the VM, then yes, they are (except maybe line endings). As I said the exception is the paths.

The VirtualBox config file itself is not the same. That contains the registry of the VMs, and your VirtualBox Manager preferences, your definitions/modifications of Internal, HostOnly, NAT and NATService networks. That's stored at each user's home directory and since users are different when you boot different OSes, these are going to differ.

A suggestion on the ISO files, untested:

Try putting the ISO files each guest needs to access in the guest folder along with the guest's .vbox file and virtual drive file(s). Maybe the path to the ISO would then also be relative instead of absolute?

No, actually it wouldn't because it also works its way on the VirtualBox.xml as in the Recent used files...

socratis wrote:

imrazor wrote:I take it the config files are universal

If you're talking about the .VBOX file, the "recipe" of the VM, then yes, they are (except maybe line endings). As I said the exception is the paths.

The VirtualBox config file itself is not the same. That contains the registry of the VMs, and your VirtualBox Manager preferences, your definitions/modifications of Internal, HostOnly, NAT and NATService networks. That's stored at each user's home directory and since users are different when you boot different OSes, these are going to differ.

That makes sense. I had to add my NAT network to both instances of VirtualBox separately (once on Linux, once on Windows.) It's a bit confusing trying to figure out what's in the .xml file and what's in the VM's .vbox file.

You just quoted me listing what's stored in VirtualBox.xml, why are you still confused? Have you tried peeking at it? Peeking, not poking.