virtualbox crash with kernel 5.13

Discussions related to using VirtualBox on Linux hosts.
fth0
Volunteer
Posts: 5661
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: virtualbox crash with kernel 5.13

Post by fth0 »

Schade, das nohugevmalloc deaktiviert eine Neuerung im Speichermanagement des 5.13er Kernels, und da die Abstürze im Speichermanagement von VirtualBox auftreten, wäre das ein guter Kandidat gewesen. Könnte ich von beiden Versuchen auch VBox.log Dateien bekommen, um sicher zu gehen, dass nicht ein anderes Problem aufgetreten ist?
fth0
Volunteer
Posts: 5661
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: virtualbox crash with kernel 5.13

Post by fth0 »

Die VirtualBox-Entwickler können das Problem bisher nicht nachstellen. Es ist aber ein weitere potentielle Ursache entdeckt worden. Kannst Du bitte einmal testen, ob der Kernel-Parameter no5lvl hilft? Wenn Du keine Zeit (oder Lust) für weitere Tests hast, bitte auch kurz Bescheid geben.

Edit:
Der Kernel-Parameter no5lvl scheint nur für Intel-CPUs sinnvoll zu sein.
Last edited by fth0 on 13. Jul 2021, 19:44, edited 1 time in total.
klaus
Oracle Corporation
Posts: 1101
Joined: 10. May 2007, 14:57

Re: virtualbox crash with kernel 5.13

Post by klaus »

The 5 level page table support should play no role for illulix's system. The log files show pretty clearly that the CPU is a 1st gen Ryzen, and AMD isn't selling any CPUs yet which have 5 level page table support. Reportedly it will become available with Zen 4 generation AMD CPUs.
bird
Oracle Corporation
Posts: 127
Joined: 10. May 2007, 10:27

Re: virtualbox crash with kernel 5.13

Post by bird »

illulix: Try try adding

Code: Select all

randomize_kstack_offset=0
to the linux kernel command line and see if it helps. Made the problem go away for me here.

It is related to the CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT kernel config option. So, if the problem persist, please upload your kernel config.

Cheers,
bird.
Knut St. Osmundsen
Oracle Corporation
gliderpilot
Posts: 1
Joined: 14. Jul 2021, 14:40

Re: virtualbox crash with kernel 5.13

Post by gliderpilot »

I had the same problem here, and can confirm that adding

Code: Select all

randomize_kstack_offset=0

has solved the problem.

Tx for your support.

Peter
illulix
Posts: 10
Joined: 7. Jul 2021, 17:10

Re: virtualbox crash with kernel 5.13

Post by illulix »

bird wrote:illulix: Try try adding

Code: Select all

randomize_kstack_offset=0
to the linux kernel command line and see if it helps. Made the problem go away for me here.

It is related to the CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT kernel config option. So, if the problem persist, please upload your kernel config.

Cheers,
bird.
Ok, Thank you :)
Added randomize_kstack_offset=0 to the linux kernel command line

All VM's are starting now, except the Windows XP VM.
there is only a black screen :(

bernd
Attachments
21-07-14_16-53-illulix-VBox.log.zip
VBox.log
(34.93 KiB) Downloaded 3 times
21-07-14_16-27-illulix-kernel.zip
kernelconfig
(59.06 KiB) Downloaded 4 times
Last edited by illulix on 14. Jul 2021, 17:01, edited 1 time in total.
illulix
Posts: 10
Joined: 7. Jul 2021, 17:10

Re: virtualbox crash with kernel 5.13

Post by illulix »

fth0 wrote:Die VirtualBox-Entwickler können das Problem bisher nicht nachstellen. Es ist aber ein weitere potentielle Ursache entdeckt worden. Kannst Du bitte einmal testen, ob der Kernel-Parameter no5lvl hilft? Wenn Du keine Zeit (oder Lust) für weitere Tests hast, bitte auch kurz Bescheid geben.

Edit:
Der Kernel-Parameter no5lvl scheint nur für Intel-CPUs sinnvoll zu sein.

Danke für Deine Mühe !

Nach dem post von bird scheint sich ja eine Lösung anzubahnen :)
So werde ich auf die restlichen, von Dir vorgeschlagenen Test erstmal verzichten ;)
fth0
Volunteer
Posts: 5661
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: virtualbox crash with kernel 5.13

Post by fth0 »

Danke für die Rückmeldung! Du könntest jetzt den Graphics Controller wieder hinzufügen. ;)
fth0
Volunteer
Posts: 5661
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: virtualbox crash with kernel 5.13

Post by fth0 »

Please try the VirtualBox test builds 6.1.23r145697 (or newer) that are supposed to fix VirtualBox issues on hosts with Linux kernel 5.13.
illulix
Posts: 10
Joined: 7. Jul 2021, 17:10

Re: virtualbox crash with kernel 5.13

Post by illulix »

fth0 wrote:Danke für die Rückmeldung! Du könntest jetzt den Graphics Controller wieder hinzufügen. ;)
Hi,
Danke, daran hab ich garnicht mehr gedacht.
Das hat noch gefehlt, jetzt rennt auch die Windows XP VM wieder :) :) :)

Vielen Dank nochmal!
bernd


Hi,
Thanks, I haven't thought about that.
That's all I needed, now the Windows XP VM is running again :) :) :)

Version 6.1.23 r145681 (Qt5.6.1)
Version 6.1.23 r145697 (Qt5.6.1) also works.

Thanks @ALL, for solving my problem!
bernd
trekfan1
Posts: 98
Joined: 13. May 2007, 07:22
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux
Location: Italy

Re: virtualbox crash with kernel 5.13

Post by trekfan1 »

I'm install the latest test build but nothing changed, virtual machine not start

Code: Select all

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
Sorry for my English, i'm Italian
klaus
Oracle Corporation
Posts: 1101
Joined: 10. May 2007, 14:57

Re: virtualbox crash with kernel 5.13

Post by klaus »

trekfan1 wrote:

Code: Select all

vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.
This hints that something is going wrong with building the guest additions kernel modules in general. Can you please attach the mentioned log file? We can't tell otherwise what's going wrong. And if the log file is mainly empty and points to another log file, please attach that one.
trekfan1
Posts: 98
Joined: 13. May 2007, 07:22
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux
Location: Italy

Re: virtualbox crash with kernel 5.13

Post by trekfan1 »

The problem is with the xanmod kernel not for standard kernel
Attachments
vbox-setup.log
(20.63 KiB) Downloaded 7 times
Sorry for my English, i'm Italian
klaus
Oracle Corporation
Posts: 1101
Joined: 10. May 2007, 14:57

Re: virtualbox crash with kernel 5.13

Post by klaus »

Sorry, I don't think I can help with such unusual modified kernels. All complaints are about gcc command line parameter issues:

Code: Select all

gcc: error: unrecognized command-line option ‘-Qunused-arguments’
gcc: error: unrecognized command-line option ‘-mno-global-merge’
gcc: error: unrecognized command-line option ‘-fsplit-lto-unit’
Those options must come from the modified kernel, because VirtualBox's kernel module build recipes do not specify either of them. In fact this kernel assumes to be built with clang (and not gcc), because the unrecognized options are all valid for clang but not gcc. This seems to be an error in your setup, because the VirtualBox kernel module build process does not specify any particular compiler. It relies on the Linux kernel module build infrastructure which should know what to use.
trekfan1
Posts: 98
Joined: 13. May 2007, 07:22
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux
Location: Italy

Re: virtualbox crash with kernel 5.13

Post by trekfan1 »

Until 5.12 it was also working with the Xanmod kernel but the problem occurred at the time of passage to 5.13, ok.... i'm waiting .....
Sorry for my English, i'm Italian
Post Reply