virtualbox.org

I have a collection of VMs exported from VMWare to owa format.

I'm using VirtualBox 5.2.18 on an Ubuntu 18.04 LTS host and the guest OS on the VMs are Windows 10

There is no obvious error when importing to VirtualBox, but at least 5 different VMs behave the same way.

When I use the VMWare Workstation Player, they import and start fine. Because of the licensing requirements, the VMWare product is not something I can use.

How do I start to dig into this issue to find a resolution?

Thanks

not-bob- wrote:How do I start to dig into this issue to find a resolution?

Start by updating your host to the latest and greatest VirtualBox.

Now... since I see the following:

not-bob- wrote:VirtualBox 5.2.18 on an Ubuntu 18.04 LTS host

I have the suspicion that you might be running the Ubuntu fork. You can tell if that's the case by running:

• 
  $ VBoxManage -version
  5.2.18_Ubuntu r124319

If it comes back with that "_Ubuntu", well that's the forked VirtualBox. You can either ask in their forums/channels for help, or completely remove/uninstall/delete/purge their version and install the official version from the Linux Downloads section of VirtualBox.

Start from that and we take it from there...

Thanks for the reply

Your suspicion was right, I did have the forked version. After upgrading (and signing kernel drivers), I re-imported with version 6.0.6 r130049 and still have the same issue.

the first thing I see is something like the following before the 'FATAL: No bootable medium found! System halted.

ata2 master unknown device
ata2 slave unknown device
ata3 master unknown device
ata3 slave unknown device

Here is the vbox file in case that is useful

The logs are attached, again presuming they are useful

Anyone have any insights on this?

I hate to pester, but any thoughts on this?

Can you show an example of problems with a supported guest OS? I.e "POS" and a guest OS template of "Other" usually translates to "not supported".