VirtualBox - new error.

[Doug Laidlaw]

An updated release of VirtualBox has just come down. It cannot start.
The error message is:

"Failed to open a session for the virtual machine Windows 8.1.

Failed to load R0 module /usr/lib64/virtualbox/VMMR0.r0: Unable to
locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0'
(VERR_SYMBOL_NOT_FOUND).

Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"

The "missing" file exists, and is not executable. I tried making it
executable, but there was no improvement I think it is time I tried kvm
or qemu.

[TJ]

Post by Doug Laidlaw
An updated release of VirtualBox has just come down. It cannot start.
"Failed to open a session for the virtual machine Windows 8.1.
Failed to load R0 module /usr/lib64/virtualbox/VMMR0.r0: Unable to
locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0'
(VERR_SYMBOL_NOT_FOUND).
Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"
The "missing" file exists, and is not executable. I tried making it
executable, but there was no improvement I think it is time I tried kvm
or qemu.

So it's not VirtualBox that won't start, but the Windows 8.1 guest. No
experience with it, but from what I've heard about Windows 8, that's not
necessarily a bad thing. ;)

I tested it before release with my Windows 7 Pro guest. No problems
noticed, except for the whining that my anti-malware database was out of
date because I hadn't run it in months.

TJ

[Doug Laidlaw]

Post by TJ

Post by Doug Laidlaw
An updated release of VirtualBox has just come down. It cannot start.
"Failed to open a session for the virtual machine Windows 8.1.
Failed to load R0 module /usr/lib64/virtualbox/VMMR0.r0: Unable to
locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0'
(VERR_SYMBOL_NOT_FOUND).
Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"
The "missing" file exists, and is not executable. I tried making it
executable, but there was no improvement I think it is time I tried
kvm or qemu.

So it's not VirtualBox that won't start, but the Windows 8.1 guest. No
experience with it, but from what I've heard about Windows 8, that's not
necessarily a bad thing. ;)
I tested it before release with my Windows 7 Pro guest. No problems
noticed, except for the whining that my anti-malware database was out of
date because I hadn't run it in months.
TJ

Thanks, but the Windows guest worked well before the update.

[Bit Twister]

Post by Doug Laidlaw
An updated release of VirtualBox has just come down. It cannot start.
"Failed to open a session for the virtual machine Windows 8.1.
Failed to load R0 module /usr/lib64/virtualbox/VMMR0.r0: Unable to
locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0'
(VERR_SYMBOL_NOT_FOUND).
Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"
The "missing" file exists, and is not executable. I tried making it
executable, but there was no improvement I think it is time I tried kvm
or qemu.

I have no experience with your error. But just now updated my VB mga8 guest
with latest kernel and using vendor VB install. Mga8 booted. In the past
I had problems starting VMs. Solution was to Close/boot the vm that would
not run that had been saved.

[Doug Laidlaw]

Post by Bit Twister
I have no experience with your error. But just now updated my VB mga8 guest
with latest kernel and using vendor VB install. Mga8 booted. In the past
I had problems starting VMs. Solution was to Close/boot the vm that would
not run that had been saved.

Than ks Bits. It is one that I have never seen before. At first, the
message looked like a missing library, but all the files are there.

[David W. Hodgins]

Post by Doug Laidlaw

Post by Bit Twister
I have no experience with your error. But just now updated my VB mga8 guest
with latest kernel and using vendor VB install. Mga8 booted. In the past
I had problems starting VMs. Solution was to Close/boot the vm that would
not run that had been saved.

Than ks Bits. It is one that I have never seen before. At first, the
message looked like a missing library, but all the files are there.

You are not the only one, however I have no idea at present why it's happening
to you and at least one other person.

I have the updates testing kernel running, and as with the prior kernel vb is
working ok on my systems.

$ rpm -qa|grep virtualbox|sort
dkms-virtualbox-6.1.34-1.5.mga8
virtualbox-6.1.34-1.5.mga8
virtualbox-kernel-5.15.46-server-1.mga8-6.1.34-1.14.mga8
virtualbox-kernel-server-latest-6.1.34-1.14.mga8
$ dkms status|grep virtualbox|sort
virtualbox, 6.1.34-1.5.mga8, 5.15.45-server-1.mga8, x86_64: installed
virtualbox, 6.1.34-1.5.mga8, 5.15.46-server-1.mga8, x86_64: installed
virtualbox, 6.1.34-1.5.mga8, 5.15.46-server-1.mga8, x86_64: installed-binary from 5.15.46-server-1.mga8

Regards, Dave Hodgins

[TJ]

Post by Bit Twister
I have no experience with your error. But just now updated my VB mga8 guest
with latest kernel and using vendor VB install. Mga8 booted. In the past
I had problems starting VMs. Solution was to Close/boot the vm that would
not run that had been saved.

Than ks Bits. It is one that I have never seen before.  At first, the
message looked like a missing library, but all the files are there.

The one other person that Dave and I mentioned has determined the cause
on his system. To learn if yours is the same, please let us know what
kernel your system is currently using.

TJ

[Doug Laidlaw]

Post by TJ

Post by Bit Twister
I have no experience with your error. But just now updated my VB mga8 guest
with latest kernel and using vendor VB install. Mga8 booted. In the past
I had problems starting VMs. Solution was to Close/boot the vm that would
not run that had been saved.

Than ks Bits. It is one that I have never seen before.  At first, the
message looked like a missing library, but all the files are there.

The one other person that Dave and I mentioned has determined the cause
on his system. To learn if yours is the same, please let us know what
kernel your system is currently using.
TJ

My VB kernel is VirtualBox VM 6.1.34_Mageia r150636 linux.amd64. I just
tried to create a new VB drive and when I tried to install 8.1 from the
DVD, I received the same error as before.

My system kernel is 5.17.11-desktop-1.mga8. That is what made me query
the installation in the first place. AFAIK, Kernel 6.1 is not available yet.

[David W. Hodgins]

Post by Doug Laidlaw
My VB kernel is VirtualBox VM 6.1.34_Mageia r150636 linux.amd64. I just
tried to create a new VB drive and when I tried to install 8.1 from the
DVD, I received the same error as before.
My system kernel is 5.17.11-desktop-1.mga8. That is what made me query
the installation in the first place. AFAIK, Kernel 6.1 is not available yet.

Kernel 6.1 is not available yet. The changes include modifications that will allow
vb to work when kernel 6.1 is released.

Please post the output of "rpm -qa|grep -e kernel -e virtualbox|sort".

Regards, Dave Hodgins

[Doug Laidlaw]

On Mon, 13 Jun 2022 08:08:55 -0400, Doug Laidlaw

My VB kernel is VirtualBox VM 6.1.34_Mageia r150636 linux.amd64.  I just
tried to create a new VB drive and when I tried to install 8.1 from the
DVD, I received the same error as before.
My system kernel is 5.17.11-desktop-1.mga8.  That is what made me query
the installation in the first place. AFAIK, Kernel 6.1 is not
available yet.

Kernel 6.1 is not available yet. The changes include modifications that will allow
vb to work when kernel 6.1 is released.
Please post the output of "rpm -qa|grep -e kernel -e virtualbox|sort".
Regards, Dave Hodgins

A new suite of kernels just came down. The problem is now solved.

Thanks all,

Doug.

[Doug Laidlaw]

A new suite of kernels just came down.  The problem is now solved.
Thanks all,
Doug.

Now, Windows 8.1 refuses to run without first making an irrecoverable
mess of itself, but that has nothing to do with Linux

[TJ]

Post by Doug Laidlaw

A new suite of kernels just came down.  The problem is now solved.
Thanks all,
Doug.

Now, Windows 8.1 refuses to run without first making an irrecoverable
mess of itself, but that has nothing to do with Linux

There appears to be a problem with at least some host hardware,
VirtualBox, and kernels greater than 5.15.43. It is being investigated.

So far, the issue only seems to affect VirtualBox, and seems to have a
"random" trigger, which will make it more difficult to track down.

At this time, the best workaround appears to be to boot into kernel
5.15.43 to use VirtualBox.

TJ

[Doug Laidlaw]

Post by TJ

Post by Doug Laidlaw

A new suite of kernels just came down.  The problem is now solved.
Thanks all,
Doug.

Now, Windows 8.1 refuses to run without first making an irrecoverable
mess of itself, but that has nothing to do with Linux

There appears to be a problem with at least some host hardware,
VirtualBox, and kernels greater than 5.15.43. It is being investigated.
So far, the issue only seems to affect VirtualBox, and seems to have a
"random" trigger, which will make it more difficult to track down.
At this time, the best workaround appears to be to boot into kernel
5.15.43 to use VirtualBox.
TJ

just had the same problem again with a clue: Worked immediately after
installation, but not after rebooting.

CAUSE: dkms-virtualbox was not installed. I installed the RPM and
rebooted to let dkms take over. A complete fix.

[David W. Hodgins]

Post by Doug Laidlaw
CAUSE: dkms-virtualbox was not installed. I installed the RPM and
rebooted to let dkms take over. A complete fix.

That means you did not have virtualbox-kernel-server-latest or
virtualbox-kernel-desktop-latest (whichever matches the kernel-*-latest)
package installed.

The package virtualbox-kernel-desktop-latest pulls in the pre-compiled
virtualbox kernel modules matching the kernel-desktop-latest package when
a kernel update is installed.

Using dkms-virtualbox, which compiles the virtualbox kernel module every time
a kernel update is installed should only be needed if you're using a kernel
which doesn't have the matching pre-compiled kernel modules (kmod updates)
available.

The kmod updates are not provided for interim kernel updates intended for
qa team use only, or for the kernel-linux packages.

Are you installing kernel updates from updates-testing?

Regards, Dave Hodgins

[TJ]

On Thu, 07 Jul 2022 10:11:09 -0400, Doug Laidlaw

Post by Doug Laidlaw
CAUSE: dkms-virtualbox was not installed. I installed the RPM and
rebooted to let dkms take over.  A complete fix.

That means you did not have virtualbox-kernel-server-latest or
virtualbox-kernel-desktop-latest (whichever matches the kernel-*-latest)
package installed.
The package virtualbox-kernel-desktop-latest pulls in the pre-compiled
virtualbox kernel modules matching the kernel-desktop-latest package when
a kernel update is installed.
Using dkms-virtualbox, which compiles the virtualbox kernel module every time
a kernel update is installed should only be needed if you're using a kernel
which doesn't have the matching pre-compiled kernel modules (kmod updates)
available.
The kmod updates are not provided for interim kernel updates intended for
qa team use only, or for the kernel-linux packages.
Are you installing kernel updates from updates-testing?

If I recall correctly from a previous thread, he's running a 5.17.x
kernel from backports, probably as a result of
https://bugs.mageia.org/show_bug.cgi?id=29830 when he installed
virtualbox in the first place.
If so, then the "latest" packages wouldn't trigger a regular update.

TJ