[opensuse] How convert a Wmware Player machine into a VirtualBox virtual machine?
-----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----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 2018-05-07 06:01, John Andersen wrote:
On May 6, 2018 11:45:36 AM PDT, "Carlos E. R." <> wrote:
Carlos, all you need to copy from the VMware machine is the .vmdk files.
But this does not copy the hardware of the original machine. It is like moving the hard disk from one computer to another computer, boot it, and hope it works. For Linux VMs, it probably does. For Windows VMs, it might void the license. Memory size, peripherals present, type of hard disks (pata, sata, scsi...), etc, are not migrated that way. It is what I may finally do, but I'll have to carefully go over the hardware details manually and try to reproduce. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/07/2018 04:44 AM, Carlos E. R. wrote:
On 2018-05-07 06:01, John Andersen wrote:
On May 6, 2018 11:45:36 AM PDT, "Carlos E. R." <> wrote:
Carlos, all you need to copy from the VMware machine is the .vmdk files.
But this does not copy the hardware of the original machine. It is like moving the hard disk from one computer to another computer, boot it, and hope it works. For Linux VMs, it probably does. For Windows VMs, it might void the license.
Of course not. And neither would any convoluted conversion from one VM format to another. Different drivers are used by Vmware and Virtualbox. You are allowed to replace nics, processors, and essentially move your entire license to a new machine. Worst case is windows wants to re-validate, but since it finds everything is in place on the EXACT same hard drive, it does so without you even having to key in a license.
Memory size, peripherals present, type of hard disks (pata, sata, scsi...), etc, are not migrated that way.
Not an issue. (Do you seriously think all these things remain unchanged when you migrate via some double conversion process?)
It is what I may finally do, but I'll have to carefully go over the hardware details manually and try to reproduce.
You don't need to worry about this. I've had one installation ask to re-validate, (Win10, or Win7, I can't remember) I clicked ok, and it did so with no other input from me. This is the preferred way to make this migration. https://techathlon.com/how-to-run-a-vmdk-file-in-oracle-virtualbox/ But you're going to do it your way no matter what anybody tells you so I've said all I'm going to say on this issue. One last thing: Virtualbox has no official support for Windows 98, which I still test some software on for my day job. (Makes tiny VMs that you can run many of in very little memory, and valid licenses are easy to find in your junk drawer). You can still make it work if you need to. -- After all is said and done, more is said than done.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2018-05-07 at 10:42 -0700, John Andersen wrote:
On 05/07/2018 04:44 AM, Carlos E. R. wrote:
On 2018-05-07 06:01, John Andersen wrote:
On May 6, 2018 11:45:36 AM PDT, "Carlos E. R." <> wrote:
This is the preferred way to make this migration. https://techathlon.com/how-to-run-a-vmdk-file-in-oracle-virtualbox/
But you're going to do it your way no matter what anybody tells you so I've said all I'm going to say on this issue.
I tried your way, and it does not work: "FATAL: No bootable medium found! System halted" - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlrzRjEACgkQtTMYHG2NR9WjQwCfWxInHsA0MIvG/UEIebr+POeQ MXcAni7tUl71DC5oTCe34vWnHPWHECgq =diAe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On May 9, 2018 12:04:17 PM PDT, "Carlos E. R." <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2018-05-07 at 10:42 -0700, John Andersen wrote:
On 05/07/2018 04:44 AM, Carlos E. R. wrote:
On 2018-05-07 06:01, John Andersen wrote:
On May 6, 2018 11:45:36 AM PDT, "Carlos E. R." <> wrote:
This is the preferred way to make this migration. https://techathlon.com/how-to-run-a-vmdk-file-in-oracle-virtualbox/
But you're going to do it your way no matter what anybody tells you so I've said all I'm going to say on this issue.
I tried your way, and it does not work:
"FATAL: No bootable medium found! System halted"
It has worked for me over a dozen times. Linux vms, windows vms and even one OpenBSD vm all created under VMware Workstation of various vintages. Your problems seems to be mostly PEBCAK problems. I must admit I never attempted to use my method with a machine suspended with a mounted DVD iso. -- 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
On 10/05/18 06:01, John Andersen wrote:
It has worked for me over a dozen times. Linux vms, windows vms and even one OpenBSD vm all created under VMware Workstation of various vintages.
I can confirm this. I have done the same, moving VMs to and from VirtualBox, VMware and VirtualPC. It *does* work. I have even published an article about it: https://www.theregister.co.uk/2014/04/10/how_to_run_xp_on_new_windows/ -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-10 06:01, John Andersen wrote:
On May 9, 2018 12:04:17 PM PDT, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Monday, 2018-05-07 at 10:42 -0700, John Andersen wrote:
On 05/07/2018 04:44 AM, Carlos E. R. wrote:
On 2018-05-07 06:01, John Andersen wrote:
On May 6, 2018 11:45:36 AM PDT, "Carlos E. R." <> wrote:
This is the preferred way to make this migration. https://techathlon.com/how-to-run-a-vmdk-file-in-oracle-virtualbox/
But you're going to do it your way no matter what anybody tells you so I've said all I'm going to say on this issue.
I tried your way, and it does not work:
"FATAL: No bootable medium found! System halted"
It has worked for me over a dozen times. Linux vms, windows vms and even one OpenBSD vm all created under VMware Workstation of various vintages.
Your problems seems to be mostly PEBCAK problems.
No, it wasn't. Check the thread.
I must admit I never attempted to use my method with a machine suspended with a mounted DVD iso.
It was not suspended. And it is working now. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
06.05.2018 21:45, Carlos E. R. пишет:
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.
You need to export VM in VMware into OVF file.
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 would not hold my breath - in any non-trivial case I am aware of conversion either failed outright or required manual editing of OVF properties.
On May 6, 2018 9:12:50 PM PDT, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
06.05.2018 21:45, Carlos E. R. пишет:
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.
You need to export VM in VMware into OVF file.
NO YOU DO NOT. .vmdk files can be used directly. Use a copy of them out of an abundance of caution. This is specifically covered in the rather well written Virtualbox manual (PDF). -- 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
On May 6, 2018 9:12:50 PM PDT, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
06.05.2018 21:45, Carlos E. R. пишет:
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.
You need to export VM in VMware into OVF file.
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 would not hold my breath - in any non-trivial case I am aware of conversion either failed outright or required manual editing of OVF properties.
See this page https://websiteforstudents.com/import-vmware-workstation-guest-machines-virt... -- 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
Отправлено с iPhone
7 мая 2018 г., в 8:14, John Andersen <jsamyth@gmail.com> написал(а):
See this page https://websiteforstudents.com/import-vmware-workstation-guest-machines-virt...
“convert the .vmdk disk into .ova of .ovf file” I stopped reading after that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On May 6, 2018 10:43:02 PM PDT, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
Отправлено с iPhone
7 мая 2018 г., в 8:14, John Andersen <jsamyth@gmail.com> написал(а):
See this page https://websiteforstudents.com/import-vmware-workstation-guest-machines-virt...
“convert the .vmdk disk into .ova of .ovf file”
I stopped reading after that.
Too bad you didn't read both sentences in that paragraph. Clue it said its NOT necessary. Come-on Andre. -- 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
On May 6, 2018 10:52:17 PM PDT, John Andersen <jsamyth@gmail.com> wrote:
On May 6, 2018 10:43:02 PM PDT, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
Отправлено с iPhone
7 мая 2018 г., в 8:14, John Andersen <jsamyth@gmail.com> написал(а):
See this page https://websiteforstudents.com/import-vmware-workstation-guest-machines-virt...
“convert the .vmdk disk into .ova of .ovf file”
I stopped reading after that.
Too bad you didn't read both sentences in that paragraph.
Clue it said its NOT necessary.
Come-on Andre.
Another newer guide https://techathlon.com/how-to-run-a-vmdk-file-in-oracle-virtualbox/ -- 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
On 2018-05-07 06:12, Andrei Borzenkov wrote:
06.05.2018 21:45, Carlos E. R. пишет:
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.
You need to export VM in VMware into OVF file.
How? The tool refuses and gives an error. The instructions I found are for Windows where the tool is a GUI. In Linux, it is a CLI, and the help page gives about three screenfulls of options.
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 would not hold my breath - in any non-trivial case I am aware of conversion either failed outright or required manual editing of OVF properties.
:-( -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
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 -dnh --
if anybody who broke a nightly build should pay on beer, the whole development department would be drunk I guess ;-) [...] over the last 2 weeks we would have been *very* drunk. -- > Ulrich Windl and Marcus Meissner
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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 deleted the disk, copied directly the one from vmware, added it, same result. I then created a new machine, and told it to use an existing hard disk, and copied the one from vmware. Well, it refuses: "Failed to open the disk image file /home/cer/VirtualBox VMs/openSUSE Tumbleweed VB/OpenSUSE Tumbleweed VB-0.vmdk." Cannot register the hard disk '/home/cer/VirtualBox VMs/openSUSE Tumbleweed VB/OpenSUSE Tumbleweed VB-0.vmdk' {d510107c-158b-4023-b892-fd74225f2a3f} because a hard disk '/home/cer/VirtualBox VMs/openSUSE Tumbleweed/OpenSUSE Tumbleweed-0.vmdk' with UUID {d510107c-158b-4023-b892-fd74225f2a3f} already exists. Result Code: NS_ERROR_INVALID_ARG (0x80070057) Component: VirtualBoxWrap Interface: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945} Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) Oh, for Penguin shake! What the **** does it matter that the uuid is repeated? Can't I have the the same machine replicated a dozen times? If the uuid is such a huge problem, it should offer to change it! Even deleting from the database the other virtualbox and it still insists it is registered! Anyway, I finally got it by deleting the machines and directories and starting over. Anyway, same error: "FATAL: No bootable medium found! System halted" (this is creating new machine and using existing hard disk file, copied over from vmware) Well, I'll have to try a rescue system on it next :-( -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
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)
On 2018-05-09 23:17, Carlos E. R. wrote:
On 2018-05-09 16:00, Carlos E. R. wrote:
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.
There are more hurdles on the road. Network did not start. I had to go to YaST, remove the existing and configured (virtual) network card, and configure the other network card that appeared. But this is not all: via dhcp it does not get a DNS resolver. The resolv.conf file still points to 192.168.74.2, the one I suppose it got from vmware virtualization system, and it is unpingable, obviously. The address it gets is 10.0.2.15, and happens to be the same one as another virtual machine that is currently hibernated! This is chaos. And of course, till I get network I can not install the proper guest tools. Copy-paste across to/from the host does not work. I'll write a DNS address of my own for the moment. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
David Haller -
John Andersen -
Liam Proven