Try to export your VMware machines into OVF, and re-import them into VirtualBox. VirtualBox can read VMDKs, but it provides a different virtual hardware, so the transition experience may be painful. Windows VMs may require re-activation or refuse to load (BSOD), and Linux VMs may require re-configuration of Xorg and hardware. While it is possible to transfer VMs, it is not pain-free. I recommend install OSes from scratch, like you would, when migrating to new physical hardware. ____________________________________________________________________
So I understood than Virtual box cannot open VMWare VM without tweaking. Especially because the VM is a windows XP system.
Mmmmm... that is a good point, and good that someone pointed it out - especially with Windows. Windows7 is pretty robust with changing hardware and seems to recover reasonably well - other than reactivation silliness and proving you're not a pirate etc etc. But.. WinXP and previous versions will probably have a fit. I've only had any experience with Linux VMDKs and they switched over painlessly... but thatw as my particular experience/setup. Different installs may not go as smooth. Basically, it will work on a technical level... Windows may have a fit.. and freak out.. or it may not. I've not tested it. That's why I suggested you make a copy of your working VMDK and open that :-) If it works, then you're set... if not, you haven't trashed your working install. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org