Virtualbox kernel version mismatch kernel 4.19

:: Synchronizing package databases...
core 149,5 KiB 1092K/s 00:00 [####################################] 100%
extra 1840,7 KiB 2,77M/s 00:01 [####################################] 100%
community 5,2 MiB 2,95M/s 00:02 [####################################] 100%
multilib 184,4 KiB 1254K/s 00:00 [####################################] 100%
:: Starting full system upgrade...
warning: faba-icon-theme: local (1:4.3-1) is newer than community (4.3-1)
there is nothing to do

Hm... interestingly enough, I do not have the newer modules here either despite refreshing mirrors.
You could dkms but that's bound to create more problems.

all the modules are still to 6.0.0.
I don't know for the host modules. but it does not seems to caused problem on my MJ guest on windows host.
it has been released yesterday.. so we need to give philm some times.. :wink:

That shouldn't happen though... :frowning:

Thanks a lot for the quick replies and support!

what should not happen?
virtualbox come from arch.. then phil need time to build the kernels module.
or I missunderstood you?

It looks like you installed for Kernel 4.9 and 4.4. the guest modules, but for Kernel 4.19 the host modules.

is your Manjaro system a host or a guest?

Extramodules need rebuild in unstable.

It's host

I'm writing this from Manjaro guest on OSX host 6.0.2, while I do get a warning that modules mismatch, it still works. But it's OSX...

Module mismatch. I know that philm needs time to update, no disrepect.

How do I do that?
Thanks
Best

Wait.

Phil needs to build them.

1 Like

Ok. We'll do that then.
Thanks!
Best,

Hi guys,
I just received the update.
I'm still getting a pgm error.
Any clues?
Thanks!

Did you reboot?

Yeah, I'm running a clone of the windows 10 machine I have saved. Seems to be working for now. But it would be nice to use the saved one.
Have you had any luck?
Best,

Isn't working still:
image

I only have Linux VMs and they are starting now.

This seems particular to your specific Windows VM, I think you will have to discard your saved state.

I have had issues with virtualbox saved states in the past, they were prone to corruption for me, so I no longer use them.

Yeah, just started a new one and it's working fine.
Thanks!

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by