ova file imported to VMware

Discussion:

(too old to reply)

pinnerite

2023-06-20 21:05:48 UTC

Virtualbox with Windows 10 over Linux Mint was so slow as to be useless
but I need it.

I decided to export the Windows 10 virtual machine to an ova file and
import into VMware player 17.0.2.

There were several slips but eventually it was imported.
BUT it would start and then exit after the Windows 10 virtual machine
was started.

Starting it from a terminal as /usr/bin/vmplayer caused it to start
then stop after producing the following warnings: (I have removed the
repetitive prefixes).

removable-device-0: missing action removable-device-0
removable-device-0-connect: missing action removable-device-0-connect
removable-device-0-nic-bridged: missing action
removable-device-0-nic-bridged removable-device-0-nic-nat: missing
action removable-device-0-nic-nat removable-device-0-nic-host-only:
missing action removable-device-0-nic-host-only
removable-device-0-edit: missing action removable-device-0-edit
removable-device-0: missing action removable-device-0
removable-device-0-connect: missing action removable-device-0-connect
removable-device-0-nic-bridged: missing action
removable-device-0-nic-bridged removable-device-0-nic-nat: missing
action removable-device-0-nic-nat removable-device-0-nic-host-only:
missing action removable-device-0-nic-host-only
removable-device-0-edit: missing action removable-device-0-edit

I have ensured all three virtual network connections (Bridged, Host
only and NAT) were enabled but that made no difference other than to
add additional ertor messages gfor device-1 and device-2.

Frustrating.

--
Linux Mint 21.1 kernel version 5.15.0-75-generic Cinnamon 5.6.8

Big Al

2023-06-20 22:01:41 UTC

Permalink

Post by pinnerite
Virtualbox with Windows 10 over Linux Mint was so slow as to be useless
but I need it.
I decided to export the Windows 10 virtual machine to an ova file and
import into VMware player 17.0.2.
There were several slips but eventually it was imported.
BUT it would start and then exit after the Windows 10 virtual machine
was started.
Starting it from a terminal as /usr/bin/vmplayer caused it to start
then stop after producing the following warnings: (I have removed the
repetitive prefixes).
removable-device-0: missing action removable-device-0
removable-device-0-connect: missing action removable-device-0-connect
removable-device-0-nic-bridged: missing action
removable-device-0-nic-bridged removable-device-0-nic-nat: missing
missing action removable-device-0-nic-host-only
removable-device-0-edit: missing action removable-device-0-edit
removable-device-0: missing action removable-device-0
removable-device-0-connect: missing action removable-device-0-connect
removable-device-0-nic-bridged: missing action
removable-device-0-nic-bridged removable-device-0-nic-nat: missing
missing action removable-device-0-nic-host-only
removable-device-0-edit: missing action removable-device-0-edit
I have ensured all three virtual network connections (Bridged, Host
only and NAT) were enabled but that made no difference other than to
add additional ertor messages gfor device-1 and device-2.
Frustrating.

How did you install vmware-player?
I downloaded a bundle, it installs, but won't run.

--
Linux Mint 21.1 Cinnamon 5.6.8
Al

Paul

2023-06-21 05:30:23 UTC

Permalink

Post by Big Al

How did you install vmware-player?
I downloaded a bundle, it installs, but won't run.

Name: VMware-Player-Full-17.0.2-21581411.x86_64.bundle
Size: 522,230,270 bytes (498 MiB)
SHA256: DD8DB47A80F08AD777BCFE6126EBFE12178AC520514774AE5A70818159EE5826

sudo sh VMware-Player-Full-17.0.2-21581411.x86_64.bundle # cannot use your TMPFS /tmp , as noexec

# These are shards found after install :-)
# The desktop file is located where it can be seen, which is good

/usr/lib/vmware/bin/vmplayer

/usr/local/share/applications/vmware-player.desktop ==>
/usr/share/applications/vmware-player.desktop

On Ubuntu 22.04 I launched from unity (the nine-dot icon) by typing vmware-player.

I was greeted first by a EULA.

X I accept the terms in the license agreement [personal usage only, one guest OS]

After that, an elevation step prompted for password, then the program
ran for the first time.

I'll update if I make any progress on making something useful
out of this wad of commercial-dough.

[Picture]

Loading Image...

Paul

pinnerite

2023-06-21 07:44:13 UTC

Permalink

Post by Big Al
How did you install vmware-player?
I downloaded a bundle, it installs, but won't run.
Linux Mint 21.1 Cinnamon 5.6.8
Al

I just downloaded the bundle,

VMware-Player-Full-17.0.2-21581411.x86_64.bundle

made it executable. I did that by right-clicking on the name in Nemo,
selecting Properties, peermissions and ticking exercutable.

As I write I am exporting a VBOX Windows XP virtual machine to an ova file.
Then see how that works out.

Everything crossed.

--
Linux Mint 21.1 kernel version 5.15.0-75-generic Cinnamon 5.6.8

pinnerite

2023-06-21 07:57:22 UTC

Permalink

On Wed, 21 Jun 2023 08:44:13 +0100

Post by pinnerite

Post by Big Al
How did you install vmware-player?
I downloaded a bundle, it installs, but won't run.
Linux Mint 21.1 Cinnamon 5.6.8
Al

I just downloaded the bundle,
VMware-Player-Full-17.0.2-21581411.x86_64.bundle
made it executable. I did that by right-clicking on the name in Nemo,
selecting Properties, peermissions and ticking exercutable.
As I write I am exporting a VBOX Windows XP virtual machine to an ova file.
Then see how that works out.
Everything crossed.

The XP ova file was reasd by VMware Player but when i attempted to
execute it, it just returned to the desktop. :(

--
Linux Mint 21.1 kernel version 5.15.0-75-generic Cinnamon 5.6.8

Paul

2023-06-21 14:02:27 UTC

Permalink

Post by pinnerite
On Wed, 21 Jun 2023 08:44:13 +0100

Post by pinnerite

Post by Big Al
How did you install vmware-player?
I downloaded a bundle, it installs, but won't run.
Linux Mint 21.1 Cinnamon 5.6.8
Al

I just downloaded the bundle,
VMware-Player-Full-17.0.2-21581411.x86_64.bundle
made it executable. I did that by right-clicking on the name in Nemo,
selecting Properties, peermissions and ticking exercutable.
As I write I am exporting a VBOX Windows XP virtual machine to an ova file.
Then see how that works out.
Everything crossed.

The XP ova file was reasd by VMware Player but when i attempted to
execute it, it just returned to the desktop. :(

The warning text in the terminal (from a terminal start), those
were possibly GTK warnings. If I do a clean Win10 install in Linux VMWare Player 17,
I get the warning text, but it still installs. I did this, because I wanted
some metadata that was "working", and then see if I could trick it into accepting
imported materials.

I tried a pretty standard technique, of cloning over the C: partition
from the .vhd container to where the C: partition was on the .vmdk .
I did a boot repair on the .vmdk (under VBox) and then tried to
start the .vmdk back on the Linux machine. And it seemed to be
complaining about something UEFI related. I'm trying to figure out
just how restrictive the thing is, to changes.

But it is not going well so far. I am not trying to use an OVA on purpose.
Some of these tools, can't even make an OVA and read their own OVA. In an
ideal world, I would definitely have tried that, but the track record here
to date is so poor, I'd rather do stupid stuff instead :-)

Paul

2023-06-21 14:04:31 UTC

Permalink

I've never used VMware, so I really know nothing about it, but at a
guess I would think the trouble might be that the Windows VM is set up
to use the VirtualBox simulated devices, and is confused because VMware
is using different ones.

I would think it would be like pulling a Windows hard drive from one
machine and plugging it into another with different hardware. Linux
might work, but Windows won't. The installed drivers are all wrong.

TJ

Chris Elvidge

2023-06-21 14:34:53 UTC

Permalink

As this seems to be nic-relevant, perhaps try removing all networking
from the vbox machine before exporting and then (if it starts) put back
the networking in vmware.

--
Chris Elvidge, England

THIS PUNISHMENT IS NOT BORING AND POINTLESS

Paul

2023-06-22 22:58:29 UTC

Permalink

As this seems to be nic-relevant, perhaps try removing all networking from the vbox machine before exporting and then (if it starts) put back the networking in vmware.

At the moment, it's not getting to the point where networking would matter.

The warning messages come from GTK.

Still thinking positive here.

My setup is booting, so I got that far, but the screen goes black.
And I'm working on it. I'm moving these VMs between two boxes (.vmdk file),
and the second box is running Ubuntu 22.04 with VMWare Player 17 in it.

Every operation takes its own sweet time.

******* Two days pass... *****************

OK, I'll try and summarize and cut out some of the fat.

When I bring over a container manually, I get

1) Can ping the Guest. Network working at ping level.
2) Can use nbtscan (NetBIOS working). This means at least
two Services with the word "Function" in their name must
be running.
3) Can't remote in and use Terminal Server. Could be Firewall,
could be something else.

Screen remains black. Even Safe Mode doesn't work.

Machine rails on cores, and leaving it for extended periods of time
does not help.

This was an attempt to transplant a VM, by simply overwriting
the C: partition with "dd". (Take an install that was working
on VMWare Player, and replace the C: partition with the
mature C: image.)

*******

So I was forced to try it the same way as Alan (OVF appliance).

1) OVF 1.0 format on the source VirtualBox end.

2) VMWare player whines about "not OVF 1.0 compatible",
and then you click a button to try again, and it does it.
It does this, by throwing away lots of config info (metadata).

3) Your HDD corresponding to .vmdk container is present.
The SATA DVD, the sound card, the USB hub have to be added manually.
There is an "Add" button to add them.

4) Very important. In the Options part of the machine settings,
the Guest operating system has been set to "Other" by the automation.
This is bad. Set it back to Windows. Hosting softwares need to know
the OS, so they can "inject" stuff properly and mess around when you
are not looking.

The sound subsys doesn't always behave itself. The "Auto" setting
seems to work, but only sometimes.

[Picture]

Loading Image...

My Win10.vmx file, has this for sound. I've seen other wacky
lines in place of this. Third time lucky.

sound.pciSlotNumber = "34"
sound.present = "TRUE"
sound.autoDetect = "TRUE"
sound.virtualDev = "hdaudio"
sound.fileName = "-1"

Paul