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
After importing owa, I get "bootable media not found" for multiple VMs
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: After importing owa, I get "bootable media not found" for multiple VMs
Start by updating your host to the latest and greatest VirtualBox.not-bob- wrote:How do I start to dig into this issue to find a resolution?
Now... since I see the following:
I have the suspicion that you might be running the Ubuntu fork. You can tell if that's the case by running:not-bob- wrote:VirtualBox 5.2.18 on an Ubuntu 18.04 LTS host
$ VBoxManage -version 5.2.18_Ubuntu r124319
Start from that and we take it from there...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: After importing owa, I get "bootable media not found" for multiple VMs
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
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
Re: After importing owa, I get "bootable media not found" for multiple VMs
Here is the vbox file in case that is useful
- Attachments
-
- POS-Server.vbox.txt
- Likley important?
- (3.19 KiB) Downloaded 82 times
Re: After importing owa, I get "bootable media not found" for multiple VMs
The logs are attached, again presuming they are useful
- Attachments
-
- logs.zip
- (26.31 KiB) Downloaded 128 times
Re: After importing owa, I get "bootable media not found" for multiple VMs
Anyone have any insights on this?
Re: After importing owa, I get "bootable media not found" for multiple VMs
I hate to pester, but any thoughts on this?
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: After importing owa, I get "bootable media not found" for multiple VMs
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".