On 2018-05-09 16:00, Carlos E. R. wrote:
On 2018-05-08 12:55, David Haller wrote:
Hello,
On Mon, 07 May 2018, Carlos E. R. wrote:
On 2018-05-07 06:12, Andrei Borzenkov wrote:
You need to export VM in VMware into OVF file.
How? The tool refuses and gives an error.
Usage: ovftool [options] <source> <source>: Source URL locator to an OVF package, VMX file, <target>: Target URL locator which specifies either a file location
See also ovftool --help examples:
ovftool /vms/my_vm.vmx /ovfs/my_vapp.ovf (.vmx file to .ovf file. Result is put in /ovfs/my_vapp.[ovf|vmdk])
Just try: ovftool foo.vmx foo.ovf
Thanks! This worked instantly :-)
elcontar:~ # ovftool /data/vmware/Virtual\ Machines/openSUSE\ Tumbleweed/OpenSUSE\ Tumbleweed.vmx /data/vmware/OVF/openSUSE\ Tumbleweed/OpenSUSE\ Tumbleweed.ovf Opening VMX source: /data/vmware/Virtual Machines/openSUSE Tumbleweed/OpenSUSE Tumbleweed.vmx Opening OVF target: /data/vmware/OVF/openSUSE Tumbleweed/OpenSUSE Tumbleweed.ovf Writing OVF package: /data/vmware/OVF/openSUSE Tumbleweed/OpenSUSE Tumbleweed.ovf Transfer Completed Completed successfully Telcontar:~ #
This created several files:
Telcontar:/data/vmware/OVF/openSUSE Tumbleweed # l total 11603336 drwxr-sr-x 2 root vmware 4096 May 8 14:08 ./ drwxr-sr-x 3 root vmware 40 May 6 20:40 ../ -rw-r--r-- 1 root vmware 229 May 8 14:08 OpenSUSE Tumbleweed.mf -rw-r--r-- 1 root vmware 7391 May 8 14:08 OpenSUSE Tumbleweed.ovf -rw-r--r-- 1 root vmware 7257579520 May 8 14:07 OpenSUSE_Tumbleweed-disk1.vmdk -rw-r--r-- 1 root vmware 4624220160 May 8 14:08 OpenSUSE_Tumbleweed-file1.iso Telcontar:/data/vmware/OVF/openSUSE Tumbleweed #
Interestingly, the "OpenSUSE_Tumbleweed-file1.iso" is indeed the Tumbleweed installation iso! Yes, the virtual machine was still connected to it, and it was converted in full.
The next hurdle is importing in VB. The importer does not ask what directory to use as destination, uses my home, and aborts because of full disk. Easily solved, I hope:
cer@Telcontar:~> l VirtualBox\ VMs lrwxrwxrwx 1 cer users 23 May 9 15:01 VirtualBox VMs -> /data/vmware/VirtualBox/
It doesn't even ask for the name of the destination virtual machine, it gets called "vm". I hope to be able to change it later.
Ok, name change done. This is trivial in Virtual Box, it is not so much in Vmware Player.
But it does not boot: "FATAL: No bootable medium found! System halted"
I found the issue: that particular machine hard disk is GPT and is meant to boot using EFI partition. Now it boots :-) ovftool forgot to migrate that little detail. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)