[Resolved] QNX 7 ?

[Cla]

Hi all,

did anybody manage to run QNX 7 on VirtualBox?

I tried using the Other -> QNX configuration choice, but the VM seems to crash at boottime.

It runs fine on QEMU on Linux, but I was hoping to be able to also run it on Windows using virtualbox.

Ciao,

Claudio

[andyp73]

the VM seems to crash at boottime

Is there a more descriptive error message as "crash" is a bit vague! It might also be helpful if you could post the VBox.log file from the guest so we can see if anything has gone on under the hood that causes the crash.

-Andy.

[Cla]

Hello Andy,

I attach the VBox.log, I did not see much actionable debugging information, but maybe the initial configuration information could be useful?

I build the image via the QNX BSP for generic X86_64, then converted the image from raw format to vdi format using qemu-img. Maybe there is a better way?

The output I get is:

Press F1-F4 to select drive or select partition 1? 
QNX v1.2b Boot Loader: x86_64-generic.bin ...

Then a virtualbox dialog box appears saying that the machine encountered a fatal error, without actionable detail,
the machine becomes unresponsive, the dialog is not usable, and I need to kill -9 virtualbox.

Thank you,

Claudio

[socratis]

Where

I build the image via the QNX BSP for generic X86_64, then converted the image from raw format to vdi format using qemu-img. Maybe there is a better way?

Where can we get that so that we can test it as well?

[andyp73]

VirtualBox VM 5.1.38_Ubuntu r122592 linux.amd64 (Jul 10 2018 10:40:22) release log

This is the Ubuntu tribute act (forked) version of VirtualBox it is also quite an old version. You should probably start by upgrading to the latest real version from the Linux Downloads page.

00:00:07.789732 !!         VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

This is the error that is causing the guest to terminate abruptly. These triple faults are extremely difficult to diagnose. I would start by simplifying the guest configuration to be a single CPU, etc. to turn the guest into as simple a computer as possible.

I haven't looked to see if there is any guidance about these parts on getting QNX 6.x to work. Much of that is probably still applicable.

-Andy.

[andyp73]

Where can we get that so that we can test it as well?

You can register for a 30day eval version of QNX on their website. It used to include an installation ISO image. I don't have anything more recent than 6.4.1 to hand.

-Andy.

[socratis]

You can register for a 30day eval version of QNX on their website

Not particularly fond of registering just to test it out. Maybe I'll use a throw-away email...

I don't have anything more recent than 6.4.1 to hand.

So, do I take it that you've tried running 6.4.1 inside a VM?

[andyp73]

So, do I take it that you've tried running 6.4.1 inside a VM?

Unfortunately not. I needed it for the application development tools and cross compilers rather than running QNX on a PC and now all my license keys have expired.

I'll talk to my local QNX contact and see if I can get a temporary license for QNX 7 to try it out.

-Andy.

[Cla]

VirtualBox VM 5.1.38_Ubuntu r122592 linux.amd64 (Jul 10 2018 10:40:22) release log

This is the Ubuntu tribute act (forked) version of VirtualBox it is also quite an old version. You should probably start by upgrading to the latest real version from the Linux Downloads page.

I am running Mint 18.3 64bit. I purged the xenial virtualbox packages, then installed the xenial package from your Downloads page.
This time it does not even start, I get two dialogs that open at the same time:

One says:

"Failed to open a session for the virtual machine QNX_x86_64"

The other, opening at the same time, and whose text is not copy/pastable, says:

RTR3InitEx failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox
[...]
where: supR3HardenedMainInitRuntime what: 4
VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

[socratis]

That's because you didn't completely uninstall the previous version, and you didn't pay attention to the installer's output, the error messages.

Clean your system from any traces of VirtualB*. Then install the official version, and pay attention to the installer output. Post the installer output actually, so we know what we're dealing with.

[Cla]

As I mentioned before, I purged the virtualbox packages before installing version 5.2 from the website. I ran:

Code: Select all

$ apt purge "virtualbox*"
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'virtualbox-source' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-utils' for glob 'virtualbox*'
Note, selecting 'virtualbox-ose' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-modules' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-additions-iso' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-dkms' for glob 'virtualbox*'
Note, selecting 'virtualbox-dkms' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-dkms-hwe' for glob 'virtualbox*'
Note, selecting 'virtualbox-ext-pack' for glob 'virtualbox*'
Note, selecting 'virtualbox' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-modules-hwe' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-x11-hwe' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-source' for glob 'virtualbox*'
Note, selecting 'virtualbox-ose-fuse' for glob 'virtualbox*'
Note, selecting 'virtualbox-qt' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-source-hwe' for glob 'virtualbox*'
Note, selecting 'virtualbox-2.0' for glob 'virtualbox*'
Note, selecting 'virtualbox-2.1' for glob 'virtualbox*'
Note, selecting 'virtualbox-2.2' for glob 'virtualbox*'
Note, selecting 'virtualbox-modules' for glob 'virtualbox*'
Note, selecting 'virtualbox-3.0' for glob 'virtualbox*'
Note, selecting 'virtualbox-3.1' for glob 'virtualbox*'
Note, selecting 'virtualbox-3.2' for glob 'virtualbox*'
Note, selecting 'virtualbox-4.0' for glob 'virtualbox*'
Note, selecting 'virtualbox-4.1' for glob 'virtualbox*'
Note, selecting 'virtualbox-4.2' for glob 'virtualbox*'
Note, selecting 'virtualbox-4.3' for glob 'virtualbox*'
Note, selecting 'virtualbox-5.0' for glob 'virtualbox*'
Note, selecting 'virtualbox-5.1' for glob 'virtualbox*'
Note, selecting 'virtualbox-5.2' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-utils-hwe' for glob 'virtualbox*'
Note, selecting 'virtualbox-dbg' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-x11' for glob 'virtualbox*'
Note, selecting 'virtualbox-guest-additions' for glob 'virtualbox*'
Package 'virtualbox-ose' is not installed, so not removed
Package 'virtualbox-ose-fuse' is not installed, so not removed
Note, selecting 'virtualbox-dkms' instead of 'virtualbox-modules'
Package 'virtualbox-2.0' is not installed, so not removed
Package 'virtualbox-2.1' is not installed, so not removed
Package 'virtualbox-2.2' is not installed, so not removed
Package 'virtualbox-3.0' is not installed, so not removed
Package 'virtualbox-3.1' is not installed, so not removed
Package 'virtualbox-3.2' is not installed, so not removed
Package 'virtualbox-4.0' is not installed, so not removed
Package 'virtualbox-4.1' is not installed, so not removed
Package 'virtualbox-4.2' is not installed, so not removed
Package 'virtualbox-4.3' is not installed, so not removed
Package 'virtualbox-5.0' is not installed, so not removed
Package 'virtualbox-guest-additions' is not installed, so not removed
Package 'virtualbox-5.1' is not installed, so not removed
Package 'virtualbox-guest-modules-hwe' is not installed, so not removed
Package 'virtualbox' is not installed, so not removed
Package 'virtualbox-dbg' is not installed, so not removed
Package 'virtualbox-dkms' is not installed, so not removed
Package 'virtualbox-ext-pack' is not installed, so not removed
Package 'virtualbox-guest-additions-iso' is not installed, so not removed
Package 'virtualbox-guest-dkms' is not installed, so not removed
Package 'virtualbox-guest-dkms-hwe' is not installed, so not removed
Package 'virtualbox-guest-source' is not installed, so not removed
Package 'virtualbox-guest-source-hwe' is not installed, so not removed
Package 'virtualbox-guest-utils' is not installed, so not removed
Package 'virtualbox-guest-utils-hwe' is not installed, so not removed
Package 'virtualbox-guest-x11' is not installed, so not removed
Package 'virtualbox-guest-x11-hwe' is not installed, so not removed
Package 'virtualbox-qt' is not installed, so not removed
Package 'virtualbox-source' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  libgsoap8 libvncserver1
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  virtualbox-5.2*
0 upgraded, 0 newly installed, 1 to remove and 44 not upgraded.
After this operation, 187 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 342539 files and directories currently installed.)
Removing virtualbox-5.2 (5.2.18-124319~Ubuntu~xenial) ...
Purging configuration files for virtualbox-5.2 (5.2.18-124319~Ubuntu~xenial) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for desktop-file-utils (0.22+linuxmint1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.2) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...

If there is something else I should remove, let me know.

Then I install the package for Xenial:

Code: Select all

$ apt install ./virtualbox-5.2_5.2.18-124319~Ubuntu~xenial_amd64.deb
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'virtualbox-5.2' instead of './virtualbox-5.2_5.2.18-124319~Ubuntu~xenial_amd64.deb'
The following packages were automatically installed and are no longer required:
  libgsoap8 libvncserver1
Use 'sudo apt autoremove' to remove them.
Recommended packages:
  libsdl-ttf2.0-0
The following NEW packages will be installed:
  virtualbox-5.2
0 upgraded, 1 newly installed, 0 to remove and 44 not upgraded.
Need to get 0 B/73,5 MB of archives.
After this operation, 187 MB of additional disk space will be used.
Get:1 /home/claudio/Downloads/virtualbox-5.2_5.2.18-124319~Ubuntu~xenial_amd64.deb virtualbox-5.2 amd64 5.2.18-124319~Ubuntu~xenial [73,5 MB]
Preconfiguring packages ...
Selecting previously unselected package virtualbox-5.2.
(Reading database ... 341706 files and directories currently installed.)
Preparing to unpack .../virtualbox-5.2_5.2.18-124319~Ubuntu~xenial_amd64.deb ...
Unpacking virtualbox-5.2 (5.2.18-124319~Ubuntu~xenial) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for systemd (229-4ubuntu21.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.2) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for desktop-file-utils (0.22+linuxmint1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Setting up virtualbox-5.2 (5.2.18-124319~Ubuntu~xenial) ...
Adding group `vboxusers' (GID 138) ...
Done.
Processing triggers for libc-bin (2.23-0ubuntu9) ...

Then I reboot, and finally I run "virtualbox".

Same result,

"Failed to open a session for the virtual machine QNX_x86_64"

Are there some other logs I should post?

Thanks,

Claudio

[socratis]

Are there some other logs I should post?

You should post the complete error message. "Failed to open a session" for a VM is *the* classical error message. The "why" part (the rest of the error message) is the most interesting part. In the previous error message you were getting a:

VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

which was clearly a mismatch between the fork and the official versions of VirtualBox.

Is the error message the same this time? It shouldn't be, as it seems that you've completely uninstalled all VirtualBox related packages before doing a fresh official install.

[Cla]

The error message in the second dialog box is still the same:

VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

[socratis]

Still the same error. An installation problem. I don't know at this point, the only option is to clean the system, even manually if you have to. Don't ask me how, I'm not on Ubuntu...

[Cla]

Still the same error. An installation problem. I don't know at this point, the only option is to clean the system, even manually if you have to. Don't ask me how, I'm not on Ubuntu...

Hi, I have very good news!

I spent some time hunting for possible files left over from the uninstallation of virtualbox, and I found many files related to virtualbox, including left-over kernel modules. Apparently the apt purge does not clean correctly the Ubuntu package of virtualbox.

After doing this manual clean up, not only does virtualbox-5.2 start, but it runs QNX 7 without the triple fault exception!

I am now testing other features (networking, console, etc.) but this is already a huge step

So from virtualbox-5.2 on, QNX7 works!

Ciao and thanks,

Claudio