Segfault with unknown acronym

Discussions related to using VirtualBox on Linux hosts.
Post Reply
shprdchris
Posts: 7
Joined: 7. Oct 2022, 10:21

Segfault with unknown acronym

Post by shprdchris »

Hi all, first time posting to plz be gentle :)

After updating virtualbox on my Arch host, I'm getting a segfault on all my VMs - even ones I create from fresh, across various ISOs (win10, ubuntu). The relevant final lines of the logs (regardless of the choice of ISO) are:

Code: Select all

00:00:03.837427 Audio:   Flags           = DEFAULT_IN
00:00:03.837427 Audio:   Input channels  = 2
00:00:03.837427 Audio:   Output channels = 0
00:00:03.837771 HDA: Codec reset
00:00:03.837780 HDA: Reset
00:00:03.838116 SUP: seg #0: R X 0x00000000 LB 0x00001000
00:00:03.838123 SUP: seg #1: R X 0x00001000 LB 0x00002000
00:00:03.838125 SUP: seg #2: R   0x00003000 LB 0x00101000
00:00:03.838128 SUP: seg #3: RW  0x00104000 LB 0x00000820
00:00:03.838695 SUP: Loaded VBoxEhciR0.r0 (/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxEhciR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX
I'm not sure what the SUP acronym refers to, so am struggling to trace the issue back. The only solution so far is to revert to my initially-installed virtualbox release, which isn't ideal for obvious reasons.

Can someone please shed some light on either the source of the issue or the meaning of the acronym? I'm running a pretty vanilla version of Arch, nothing fancy going on.

Thanks in advance from a very frustrated user!
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Segfault with unknown acronym

Post by mpack »

Provide one VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
shprdchris
Posts: 7
Joined: 7. Oct 2022, 10:21

Re: Segfault with unknown acronym

Post by shprdchris »

Hey mpack, thanks for the reply!

I've attached the log to this message, plz let me know if you spot anything :)
Attachments
ubuntu-2022-10-07-09-13-24.log
(37.48 KiB) Downloaded 2 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Segfault with unknown acronym

Post by mpack »

Is this the complete log? It is only 700 lines.

1GB RAM, 16MB graphics RAM, 1 core - is not a lot to give to a modern OS. You can give the VM 2048MB RAM and 128MB graphics RAM. Unfortunately with a truncated log I don't know the capabilities of your CPU, but 2 cores is usually ok.
shprdchris
Posts: 7
Joined: 7. Oct 2022, 10:21

Re: Segfault with unknown acronym

Post by shprdchris »

This is the log for a fresh Ubuntu machine, using all the default options. I haven't deleted anything from the log so presumably this is the whole thing.
shprdchris
Posts: 7
Joined: 7. Oct 2022, 10:21

Re: Segfault with unknown acronym

Post by shprdchris »

I've just adjusted the memory to your recommendations and resaved the log, which is attached to this reply.
Attachments
ubuntu-2022-10-07-10-52-54.log
(37.69 KiB) Downloaded 5 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Segfault with unknown acronym

Post by mpack »

It is only the complete log if the VM aborted, which would be very unusual. Even if an error occurs, VirtualBox is expected to finish up the log.
shprdchris
Posts: 7
Joined: 7. Oct 2022, 10:21

Re: Segfault with unknown acronym

Post by shprdchris »

It is aborting :'(

Code: Select all

Failed to open a session for the virtual machine ubuntu.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Segfault with unknown acronym

Post by mpack »

That is not what I mean - coincidental terminology. The fact that the error dialog is showing any message proves that it has not aborted. Aborting means going back to the host OS shell without warning, without error messages etc. If it's still capable of showing error dialogs then (a) it is still running so logs should not be copied yet, (b) it has not aborted.
shprdchris
Posts: 7
Joined: 7. Oct 2022, 10:21

Re: Segfault with unknown acronym

Post by shprdchris »

OK, I understand. Regardless, this is the full log. If there were more info, I'd definitely be using it.
shprdchris
Posts: 7
Joined: 7. Oct 2022, 10:21

Re: Segfault with unknown acronym

Post by shprdchris »

Is there anything we can do at this point?
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Segfault with unknown acronym

Post by mpack »

Well, the only other thing I see, and apologies for not noticing last time, is that you have a version conflict with the Extension Pack.
00:00:03.069836 VirtualBox VM 6.1.38 r153438 linux.amd64 (Sep 1 2022 19:47:47) release log
00:00:03.069838 Log opened 2022-10-07T09:52:54.011694000Z
...
00:00:03.072689 Installed Extension Packs:
00:00:03.072710 Oracle VM VirtualBox Extension Pack (Version: 6.1.34 r150636; VRDE Module: VBoxVRDP)
I don't know why this would cause a segfault on the host, but it won't be helping either.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Segfault with unknown acronym

Post by fth0 »

mpack wrote:I don't know why this would cause a segfault on the host
Linux kernel 5.19 (on the OP's host) is only supported by VirtualBox 6.1.36 and newer, and the added Linux kernel support has usually to do with having to use Linux kernel interfaces differently. IMO (*) this is the main reason for the requirement to combine the same version of VirtualBox and the Extension Pack.

(*) OTOH, when the interface between VirtualBox and the Extension Pack changes, VirtualBox also changes an internal version number and rejects to load the Extension Pack, thereby preventing crashes based on those interface changes.
Post Reply