VM dont start after Update 4.1.0.RLQ1

VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2.

Moderator: Lillian.W@AST

baguss
Posts: 2
youtube meble na wymiar Warszawa
Joined: Tue Oct 04, 2022 9:38 am

Re: VM dont start after Update 4.1.0.RLQ1

Post by baguss »

Confirmed..my AS6302T also got updated virtualbox too.
Now my VM running well with bridged network again.
Thx
giostark
Posts: 16
Joined: Mon Feb 05, 2018 11:22 pm

Re: VM dont start after Update 4.1.0.RLQ1

Post by giostark »

5104T ADM 4.0.6.RCR1 (the last available version for my series)
Problem still here:

Code: Select all

Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND). One of the kernel modules was not successfully loaded. Make sure that VirtualBox is correctly installed, and if you are using EFI Secure Boot that the modules are signed if necessary in the right way for your host system. Then try to recompile and reload the kernel modules by executing '/sbin/vboxconfig' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND)
Should be more modules active?

Code: Select all

$ lsmod | grep vbox
vboxdrv 413696 0 - Live 0x0000000000000000 (O)
User avatar
father.mande
Posts: 1807
Joined: Sat Sep 12, 2015 2:55 am
Location: La Rochelle (France)

Re: VM dont start after Update 4.1.0.RLQ1

Post by father.mande »

Hi,

Kernel have been changed (not version but internal builtin modules), so as for 4.1 RLQ1 ... some modules (external) are not compatible.

A the moment of the problem ... run dmesg and look for "unknow symbol" or "disagrees about version of symbol "
if it is a problem when one module is loaded, you can see it.

Don't consider having module in lsmod list ... because if error is during init phase (calling internal entry point ex. for another module : xt_register_match changed in kernel but not compatible with external modules) , the module is already in memory and loaded BUT not functional. (even if module is provide by Asustor it's difficult to understand, but current for modules provide by users (APKG) because kernel source is not yet updated ... the delay is abnormal (G.P.L. constraints) even understandable..

open a ticket on support web site ...

Philippe.
AS6602T / AS5202T /AS5002T / AS1002T / FS6706T
Post Reply

Return to “VirtualBox”