On May 6, 2018 11:45:36 AM PDT, "Carlos E. R." <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Maybe I understood wrong, but I thought that Virtualbox could load directly vmware virtual machines. But it does not seem to be so.
First I copied the virtual machine. It contains these files - none is VDI:
Telcontar:/data/vmware/VirtualBox/openSUSE Tumbleweed # l -h total 15G drwxr-sr-x 2 cer vmware 4.0K May 6 20:28 ./ drwxrws--- 4 cer vboxusers 57 May 6 19:57 ../ - -rw-r--r-- 1 cer vmware 130 Aug 5 2015 Notas - -rw-r--r-- 1 cer vmware 15G May 6 20:21 OpenSUSE Tumbleweed-0.vmdk - -rw------- 1 cer vmware 73K May 6 20:21 OpenSUSE Tumbleweed.nvram - -rw------- 1 cer vmware 2.6M Aug 5 2015 OpenSUSE Tumbleweed.vmdk - -rw-r--r-- 1 cer vmware 0 Aug 5 2015 OpenSUSE Tumbleweed.vmsd - -rwxr-xr-x 1 cer vmware 2.8K May 6 20:21 OpenSUSE Tumbleweed.vmx* - -rw-r--r-- 1 cer vmware 274 Aug 6 2015 OpenSUSE Tumbleweed.vmxf - -rw-r--r-- 1 cer vmware 242K Apr 17 11:46 vmware-0.log - -rw-r--r-- 1 cer vmware 301K Feb 18 03:15 vmware-1.log - -rw-r--r-- 1 cer vmware 443K Feb 7 01:12 vmware-2.log - -rw-r--r-- 1 cer vmware 254K May 6 20:21 vmware.log
One guide says that I have first to convert the machine to a Virtual Appliance first, using something called "OVFTool", "/usr/bin/ovftool" I
guess.
<https://www.admfactory.com/how-to-convert-vmware-to-virtualbox-virtual-machine/>
But the instructions are for Windows, and I don't seem to get anywhere,
but to an error I don't understand:
Telcontar:/data/vmware # ovftool "Virtual Machines/openSUSE Tumbleweed/" "OVF/openSUSE Tumbleweed/" Opening OVF source: Virtual Machines/openSUSE Tumbleweed/openSUSE Tumbleweed.ovf Error: Failed to open OVF descriptor Completed with errors Telcontar:/data/vmware #
It seems to want to open file "openSUSE Tumbleweed.ovf" which of course
does not exist. That's what it is about, creating the appliance for migration.
Another: <https://blogs.oracle.com/oswald/importing-a-vdi-in-virtualbox> says that I first have to create a new virtual machine in virtual box, but importing the "hard disk", which is supposed to be .vdi, but mine are .vmdk. Anyway, some links say vmdk works - but this method would not migrate the "hardware" of the machine, so to speak, only the hard disks.
I'm confused.
- -- Cheers
Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iEYEARECAAYFAlrvTVcACgkQtTMYHG2NR9VN2QCggEv2Scmy8laWmeffFxCZvC1t 2awAn3B21reydmNE0iIL/hEPEk90t8+M =3lJ7 -----END PGP SIGNATURE-----
Carlos, all you need to copy from the VMware machine is the .vmdk files. In Virtualbox, create a new machine, but use the do not create a virtual disk. That will set up the Virtualbox directory. Copy all your .vmdk files directly from your VMware directory to the newly created Virtualbox vm subdirectory created by step above. Then go back to the Virtualbox app, edit settings to the vbox machine, and select the copied vmdk, just the one with no number suffix. That's all there is to it. Note: You could just point it to the .vmdk files in VMware directory, but copying is the safe way. I've not tried to use the same set of files in Virtualbox and VMware alternatingly. Seems unlikely to be successful. The only files Virtualbox needs is those .vmdkx files. It will use these without convesion., As if they were native Virtualbox files. No conversation necessary! -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org