Bug #14038


OpenIndiana fails to migrate from VirtualBox to VMWare

Added by Denis Ovsienko 9 months ago. Updated 9 months ago.

Start date:
Due date:
% Done:


Estimated time:
Gerrit CR:


As discussed on IRC earlier, I am observing an unexpected fault with OI 2021.04 as follows:

  • OI installs from .iso and works fine in a VM with a SATA virtual disk inside VirtualBox 6.1.22 (/etc/path_to_inst attached).
  • OI installs from .iso and works fine in a VM with a "VMware PVSCSI" virtual disk inside VMWare (/etc/path_to_inst attached).
  • If I plug the working disk image from VirtualBox into VMWare (this can be done in a number of ways, and works as expected otherwise), OI starts to boot and crashes shortly thereafter.

In the latter case it makes little difference to rm /etc/path_to_inst or to touch /reconfigure or to boot -r. Let me know if you need any additional information. The VMWare VM is now running OI installed from scratch using a virtual DVD, but I can arrange a temporary reboot into an imported disk image if necessary and to collect diagnostics.


path_to_inst_virtualbox.txt (828 Bytes) path_to_inst_virtualbox.txt Denis Ovsienko, 2021-08-28 08:41 AM
path_to_inst_vmware.txt (2.33 KB) path_to_inst_vmware.txt Denis Ovsienko, 2021-08-28 08:41 AM
Screenshot_2021-09-02_15-07-55.png (52.1 KB) Screenshot_2021-09-02_15-07-55.png Denis Ovsienko, 2021-09-02 02:10 PM
Screenshot_2021-09-02_15-08-49.png (67.4 KB) Screenshot_2021-09-02_15-08-49.png Denis Ovsienko, 2021-09-02 02:10 PM
Screenshot_2021-09-02_15-16-42.png (69.2 KB) Screenshot_2021-09-02_15-16-42.png Denis Ovsienko, 2021-09-02 02:16 PM
Screenshot_2021-09-05_12-21-34.png (128 KB) Screenshot_2021-09-05_12-21-34.png set disable-mpt=true Denis Ovsienko, 2021-09-05 11:31 AM
Actions #1

Updated by Joshua M. Clulow 9 months ago

We'll need to know more about the crash you're seeing. Does the system panic? If so, what's the panic stack?

Actions #2

Updated by Denis Ovsienko 9 months ago

The system crashes (and resets the VM unless booted as boot -k), please see the attached screenshots from the virtual KVM console. If you need additional diagnostics, let me know how to extract it and I will assist.

Actions #3

Updated by Joshua M. Clulow 9 months ago

I see the old closed source mpt driver in the stack, which we likely cannot fix. I assume you've selected an LSI SCSI HBA for disk emulation from VMware.

I would recommend switching to NVMe or perhaps SATA instead and see if that helps!

Actions #4

Updated by Denis Ovsienko 9 months ago

It is odd that the MPT driver comes into scope at all, as neither VM has the virtual hardware for it. Would you like to ssh into the VM to confirm?

Actions #5

Updated by Joshua M. Clulow 9 months ago

It would probably help to look at the VMware configuration file. I believe they have the *.vmx extension, and are plain text. Can you locate and attach that file?

Actions #6

Updated by Denis Ovsienko 9 months ago

Please mind that on the VirtualBox side I am the administrator, but on the VMWare side I am a user of a hosting service, so getting the file might be difficult. Nevertheless, I have just placed a request with the tech support, if they provide the file, you will see it.

Actions #7

Updated by Joshua M. Clulow 9 months ago

So another thing you can try is, at the loader ok prompt, set disable-mpt true before you boot -k. It's possible that the VMware configuration has an LSI SCSI controller even if it doesn't attach any disks that way, and this should prevent the driver loading entirely. If you're sure you don't have any disks attached via mpt, this is probably ok to try.

Actions #8

Updated by Denis Ovsienko 9 months ago

The tech support claims they don't see my repeated attempts to contact them by e-mail, and by phone they neither accept nor seem to understand the request. Clearly, it is off their runbook. So please do not expect the .emx file or any other diagnostics from the hypervisor side of the VMWare VM.

Please mind once again that whatever virtual hardware is configured in VMWare, it does not block installing and running OI (see the problem description and the path_to_inst originally attached), and that you can ssh into the running system if you wish and see which drivers load for which virtual hardware.

Other than that, I have tried your latest suggestion, which changed the way the transplanted disk image fails to boot (console screenshot attached). Let me know what other assistance you need.


Also available in: Atom PDF