9 years ago
When I originally did a Windows 7 (and probably Vista), I had to install VirtualPC (http://www.microsoft.com/windows/virtual-pc/) and convert the image to a VPC first. The vmware converter will convert the VPC image to a vmx/vmdk format. Then ran steps 5-12, starting with VPC image instead of the "real" pc. I use VMPlayer to run my Windows guest, but VirtualBox should be able to run it, too.
VirtualBox runs vmdk files, which the VMWare Converter creates. You only have to re-create the machine description with VirtualBox, then point the new machine to the exisiting vmdk.
These instructions are 5 years old and certainly not accounting for new additions to LM since, ie. including VMBox in Software Mgr. As with bones Tdog's comment, my goal is to have a Virtual Windows program in order to run "strictly specific" Windows programs, such as accounting and finance proprietary programs within 17.3 Rosa and later versions.
It would only matter if your Windows was OEM or not. Virtualizing is like changing the hardware so you'll probably have to re-validate it.
Would love more information in this direction:
1. Using VirtualBox rather than VMWare
2. Installing using a restore image (if that is different)
3. A bit more in depth for us n00bs
I would love to take my dual-booted machine to 100% Linux with Windows running in VB when needed, but only have the restore disk and no original install iso. Not sure if that matters.