[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
From what I recall, that wasn't the problem - the issue I had was starting Win2K on what's effectively different underlying hardware -as if I'd taken my disk out of the Dell and put it in an HP box (for exmaple) I have the original Win2K disk but it didn't help me then as it couldn't see the CD rom drive... I was just wondering if anything had improved at the hardware emulation stage to make this sort of migration easier... Cheers, Gordon > That, I'm afraid, I don't know. > > However, if you still have the Dell box to hand, you could try booting > it up and then running the "SysPrep" tool. Once it's done, shut down, > remove harddrive, take image, add into VM and away you go. When it > boots up in the VM it will go looking for new hardware, find it and ask > for drivers (if necessary). Note though, after SysPrepping it you > shouldn't boot it on the old hardware again or you'll have to > re-SysPrep it. > > Grant. > This is correct, sysprep is one way to handle windows P2V migration. However, a much easier and cheatier way is to simply download the VMware Converter from here: http://www.vmware.com/products/converter/ (warning, free registration required, definitely not open-source software) Install and run on your physical target - windows 2000 is supported, as long as it's SP4 - and drop the finished image off to a USB drive or network storage. The new VM will be in VMware's format, but VirtualBox can deal with importing and running that fine, or if you can be bothered, convert it with VBoxManage. Major advantage of doing it this way is you usually avoid broken driver disasters and having to reactivate licenses as well, they all get transferred across. Install the guest additions and you're good to go. Watch out for network connections though, they'll be modified which can be bad when P2V'ing servers - windows will create "new wired connection 2/3/4/whatever" type interfaces silently, hiding the originals, and linux will need udev net-persistent rules modified so it's new virtualized interfaces match your original eth0/1/2/etc physical interfaces. Obviously especially important for linux P2V with iptables and friends and services bound to specific interfaces, etc. Cheers, Mat -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq