Vadim, I looked for what version is currently running 151573 although there a couple of files in the src directory with differing IDs (see below).
Log and config file for the VM have posted to this bug report. Regards, George... 00:00:02.362972 VirtualBox VM 6.1.35 r151573 linux.amd64 (May 25 2022 14:07:19) release log 00:00:02.362975 Log opened 2022-05-31T17:53:06.688291000Z 00:00:02.362977 Build Type: release 00:00:02.362985 OS Product: Linux 00:00:02.362989 OS Release: 5.18.0-0.rc7.20220519gitf993aed406ea.56.fc37.x86_64 00:00:02.362993 OS Version: #1 SMP PREEMPT_DYNAMIC Thu May 19 23:37:47 UTC 2022 00:00:02.363144 DMI Product Name: N53SN 00:00:02.363269 DMI Product Version: 1.0 00:00:02.363318 Firmware type: BIOS 00:00:02.363489 Host RAM: 7796MB (7.6GB) total, 1216MB available 00:00:02.363495 Executable: /opt/VirtualBox/VirtualBoxVM 00:00:02.363496 Process ID: 810871 00:00:02.363497 Package type: LINUX_64BITS_GENERIC 00:00:02.428584 Installed Extension Packs: 00:00:02.428649 None installed! 00:00:02.432260 Console: Machine state changed to 'Starting' 00:00:02.433038 Qt version: 5.6.1 00:00:02.433092 X11 Window Manager code: 0 00:00:02.600923 GUI: UIMediumEnumerator: Medium-enumeration finished! 00:00:02.607674 X Server details: vendor: The X.Org Foundation, release: 12014000, protocol version: 11.0, display string::0.0 00:00:02.607736 Using XKB for keycode to scan code conversion 00:00:02.612582 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x383 x 1368x5 00:00:02.640108 GUI: Machine-window #0 activated 00:00:02.640172 GUI: Machine-view #0 focused, reason=3 00:00:02.672955 SUP: seg #0: R X 0x00000000 LB 0x00001000 00:00:02.673007 SUP: seg #1: R 0x00001000 LB 0x0004c000 00:00:02.673022 SUP: seg #2: R X 0x0004d000 LB 0x00118000 00:00:02.673036 SUP: seg #3: R 0x00165000 LB 0x0025d000 00:00:02.673050 SUP: seg #4: RW 0x003c2000 LB 0x000340a8 00:00:04.456352 GUI: Machine-window #0 deactivated 00:00:04.456404 GUI: Releasing mouse on focus out 00:00:04.456425 GUI: Machine-view #0 unfocused, reason=3 search for version: grep -R 1515 * src/vboxhost/vboxnetflt/linux/VBoxNetFlt-linux.c:/* $Id: VBoxNetFlt-linux.c 151573 2022-05-25 11:56:48Z vgalitsy $ */ src/vboxhost/vboxnetflt/revision-generated.h:#define VBOX_SVN_REV 151573 src/vboxhost/vboxdrv/linux/SUPDrv-linux.c:/* $Id: SUPDrv-linux.c 151565 2022-05-25 09:53:36Z ramshankar $ */ src/vboxhost/vboxdrv/revision-generated.h:#define VBOX_SVN_REV 151573 src/vboxhost/vboxdrv/SUPDrv.c:/* $Id: SUPDrv.cpp 151571 2022-05-25 11:52:30Z vgalitsy $ */ src/vboxhost/vboxnetadp/revision-generated.h:#define VBOX_SVN_REV 151573 On Tuesday, May 31, 2022, 11:43:15 AM PDT, Vadim Galitsin <vadim.galit...@oracle.com> wrote: Hi George, > I have tried both the stable(?) and developer versions of VB with "my" > 5.18.0-0.rc7.20220519gitf993aed406ea.56.fc37.x86_64 kernel. Please note that the only https://www.virtualbox.org/download/testcase/VirtualBox-6.1.35-151573-Linux_amd64.run build is currently has support for kernel 5.18. The issue you are observing might be something new which is related to kernel 5.18 or something else as well. Could you please describe you setup and attach VBox.log to https://www.virtualbox.org/ticket/20914 ? Best regards, Vadim ________________________________________ From: George R Goffe via VBox-users-community <vbox-users-community@lists.sourceforge.net> Sent: Tuesday, May 31, 2022 8:04 PM To: Community mailing list of VirtualBox users; Alexey Eromenko Cc: George R Goffe Subject: [External] : Re: [VBox-users] VB and 5.18.0-0.rc7.20220519gitf993aed406ea.56.fc37.x86_64 support Alexey, Thanks for responding. I have tried both the stable(?) and developer versions of VB with "my" 5.18.0-0.rc7.20220519gitf993aed406ea.56.fc37.x86_64 kernel. Based on your writing, this is not supported. It certainly doesn't boot... just pops up a console for the VM and a small popup that says "Starting virtual machine ... (2/2)". I don't think FC37 has a stable kernel. The next kernel step up is 5.19.0-0.rc0.20220526gitbabf0bb978e3.4.fc37 which doesn't work for me. I don't know why but when trying to boot it starts thinking zfs thoughts and NEVER completes the boot. I'm about to submit a bug report on this. "normaly" I'd use VB to test this but for the two problems described above. I'm not sure where to turn. Your thoughts? Best regards, George... On Tuesday, May 31, 2022, 09:42:11 AM PDT, Alexey Eromenko <al4...@gmail.com> wrote: Current practice is to release stable builds of VirtualBox once a month. Only Linux stable kernels are supported, meaning that any -rc kernels are unsupported. For people running unstable Linux, they must run unstable VirtualBox too, and perhaps patch themselves. Or wait 1 month. On Tue, May 31, 2022 at 18:48 George R Goffe via VBox-users-community <vbox-users-community@lists.sourceforge.net> wrote: > Hi, > > I've been waiting for a new point release for VB and "supported" kernels. > Currently I'm at 5.18.0-0.rc7.20220519gitf993aed406ea.56.fc37.x86_64. The > next kernel for FC37 is 5.19.0-0.rc0.20220526gitbabf0bb978e3.4.fc37. > > I'm a little confused about when development upgrades to VB to add support > for the newer kernels will happen. > > Could someone please update me (again) on the "current" practice? > > I've been seeing the below enclosed messages for over a month... It feels > like forever. > > Best regards and STAY safe, > > George... > > > 18 /tmp/vbox.0/linux/VBoxNetFlt-linux.c: In function ‘vboxNetFltPortOsXmit’: > 19 /tmp/vbox.0/linux/VBoxNetFlt-linux.c:2314:23: error: implicit declaration > of function ‘netif_rx_ni’; did you mean 19 ‘netif_rx’? > [-Werror=implicit-function-declaration] > 20 2314 | err = netif_rx_ni(pBuf); > 21 | ^~~~~~~~~~~ > 22 | netif_rx > 23 cc1: some warnings being treated as errors > 24 make[2]: *** [scripts/Makefile.build:288: > /tmp/vbox.0/linux/VBoxNetFlt-linux.o] Error 1 > 25 make[1]: *** [Makefile:1844: /tmp/vbox.0] Error 2 > 26 make: *** [/tmp/vbox.0/Makefile-footer.gmk:117: vboxnetflt] Error 2 > > > > > _______________________________________________ > VBox-users-community mailing list > VBox-users-community@lists.sourceforge.net > https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/vbox-users-community__;!!ACWV5N9M2RV99hQ!K2LIy3-XEdTmKHY_nbkdkiKFr4PEuRzohDNrtGgX8KU49Ps3wV8EZvCf-tdBRYCVz9S-pP9Utml2NxwDq8W4R1JlDXyKMUCI6ck8n6Zr$ > _______________________________________________ > Unsubscribe: > mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe > -- -Alexey Eromenko "Technologov" _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/vbox-users-community__;!!ACWV5N9M2RV99hQ!K2LIy3-XEdTmKHY_nbkdkiKFr4PEuRzohDNrtGgX8KU49Ps3wV8EZvCf-tdBRYCVz9S-pP9Utml2NxwDq8W4R1JlDXyKMUCI6ck8n6Zr$ _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
