Can an XP Virtual Box VM created on Win 7 plug into Win 10

[corcky]

I have an XP VM created with Virtual Box on a Win 7 host.

I want to upgrade the host using the existing hardware, to run Win 10 pro.

Can I simply run the XP VM (created under Win 7), and run it on a Win 10 pro host?

Any help would be appreciated.

I want to avoid rebuilding the XP VM as the applications running are highly bespoke and not a vanilla install.

Thank you

[towo2099]

Can I simply run the XP VM (created under Win 7), and run it on a Win 10 pro host?

Yes.

[corcky]

Can I simply run the XP VM (created under Win 7), and run it on a Win 10 pro host?

Yes.

So for instance -

I save the XP VM for restoring later.

I remove the current SSD (250 gig) with the Win 7 Host

Insert a new SSD (250 gig)

Install Win 10 pro

Install Virtual Box on Win 10 pro host

restore the XP VM

Is that roughly what needs to be done?

Many thanks

[BillG]

Your original post said "existing hardware". Your next post talks about replacing the SSD.

Are you replacing the SSD? That changes what you need to do.

[corcky]

Your original post said "existing hardware". Your next post talks about replacing the SSD.

Are you replacing the SSD? That changes what you need to do.

I would like to learn what changes need to be done if I replace the ssd? Thank you for noticing that.

The only reason to change the ssd was to keep the Win 7 host with out the need to make a backup image.

Having said that, I don't need to keep the Win 7 host. Therefore if it is much simpler to do a fresh install of Win 10 & Virtual Box on the original ssd, then that is also perfectly acceptable.

[socratis]

I want to upgrade the host using the existing hardware, to run Win 10 pro.

Insert a new SSD (250 gig). Install Win 10 pro.

Do you see the difference between your two statements? The one is using your existing VMs after an upgrade of the host OS, the other is moving your VMs to a "new" computer. In the first case you shouldn't have to do anything. In the second case, you would need to think of the operation according to the Moving a VM guide. Key phrase in there is "Perhaps you have a new PC and you want to move all your VMs there".

[corcky]

I want to upgrade the host using the existing hardware, to run Win 10 pro.

Insert a new SSD (250 gig). Install Win 10 pro.

Do you see the difference between your two statements? The one is using your existing VMs after an upgrade of the host OS, the other is moving your VMs to a "new" computer. In the first case you shouldn't have to do anything. In the second case, you would need to think of the operation according to the 'Move VM guide' guide. Key phrase in there is "Perhaps you have a new PC and you want to move all your VMs there".

Thanks Socratis - yes I do see the difference, thank you for pointing that out. I am just starting to get a grip on the terms used and the flexibility of using VMs.

'The basic procedure for moving VMs created by VirtualBox v4.0.0 or later is to copy the VM folder (with contents) to your preferred location, then use the GUI's Machine|Add menu item to register the .vbox file (found in the VM folder) from its new location.'

So if I replace the ssd - these are the instructions:-

My procedure would be to copy the XP VM folder.

Fresh install Win10 & the appropriate Virtual Box for Win 10 on the replaced ssd

then Machine|Add to the copy of XP VM folder

Wow - that's incredibly simple.

[Rootman]

To cut to the chase, YES, it SHOULD work. I've done it many times. I am using guests I created back in the Windows XP days to this day on Windows 10, and they all went through Windows 7 hosts too.

As you stated, get your OS setup, install VBox, COPY the guests folders to the new OS's drive. Start Vbox and ADD the Vm's to the new OS's instance of VBox. You would then need to go into the Guests VBox setup and perhaps tweak the NICs to point to the correct physical NIC. Although it's the same physical hardware, the OS may show it as a different name, so you need to make sure the guest's virtual NIC is bound to the right host physical NIC.

The Windows guest should run fine. It should not trip an activation in the guest as the processor is the same, but this is always a crap shoot with MS. So be prepared and have the guests Windows activation code handy just in case.

If it all fails, put the original OS back into the machine, fire up the VM and use some sort of P2V software to make an image of the guest OS and try using that. Even though you are really to a Virtual to Virtual a P2V software does the same thing regardless of the source or destination. My bet is that you won't have to do this, but I've been wrong before .

[corcky]

To cut to the chase, YES, it SHOULD work. I've done it many times. I am using guests I created back in the Windows XP days to this day on Windows 10, and they all went through Windows 7 hosts too.

As you stated, get your OS setup, install VBox, COPY the guests folders to the new OS's drive. Start Vbox and ADD the Vm's to the new OS's instance of VBox. You would then need to go into the Guests VBox setup and perhaps tweak the NICs to point to the correct physical NIC. Although it's the same physical hardware, the OS may show it as a different name, so you need to make sure the guest's virtual NIC is bound to the right host physical NIC.

Thanks Rootman

[corcky]

Just as an update if any other noobies are considering moving their VMs -

Rather than use the existing hardware I used a new Laptop running win 10 in the end! By way of a test run before messing with the current set up.
I tried the copy Virtual Box folder route, realised there are dependencies that can be set up in the preferences; storage, Networks, USB and shared folders. Tidied those up or switched them off.
Got a bit further after I cloned the VM I wanted. That worked but Windows objected as the change of hardware environment triggered the software verification alarm.
But the easiest way was with an OVA (appliance) exported then imported to the laptop.

Everything except for Outlook 2010 worked first time. I think that Outlook in cached mode produces an unresolved file location- either way it dd not seem to be anything to do with Virtual Box. No need to re-verify the Windows XP environment.

[socratis]

You advice is not the best way to do things. Let's see why.

I tried the copy Virtual Box folder route, realised there are dependencies that can be set up in the preferences; storage, Networks, USB and shared folders. Tidied those up or switched them off.

If you had followed the Moving a VM guide there should be no need for that. The preferences are stored in the VM folder, so, if you copied the whole VM folder, there would be no need for you to either change the settings or "switch them off". So, something in there does not make sense.

Got a bit further after I cloned the VM I wanted. That worked but Windows objected as the change of hardware environment triggered the software verification alarm.

Of course it would. A clone is not a copy. The identification (UUID) of the VM changes, the UUID of the HD changes. And if you copied the clone to another laptop with a different CPU, well, the CPU changes too. So, Windows thinks that this is not a small change, but a change that requires activation.

But the easiest way was with an OVA (appliance) exported then imported to the laptop.

Again, an export is not a copy. The export should be primarily used only as a means of transferring your VM to another virtualization program, not between VirtualBox installations. The exported VM has a different UUID, the HD has a different UUID and the format of the HD in the disk changes from VDI (native to VirtualBox) to VMDK.

[corcky]

You advice is not the best way to do things. Let's see why..

The theory and the practice are both difficult to piece together when the terms are unfamiliar.

Ill keep practicing! I am appreciative of the advice people have given, despite how frustrating it may be to see someone like my self stumbling about:)

[socratis]

The theory and the practice are both difficult to piece together when the terms are unfamiliar.

That's why we're here as a community, to help each other learn. I just felt the need to correct some of your points for two reasons; a) that you would understand a little bit more on what you were doing, and b) so that future users understand better by reading your post.