vbox-users-community Mailing List for Vbox add-ons
Scripts for Virtualbox
Status: Pre-Alpha
Brought to you by:
fcassia4oss
Menu
▾
▴
vbox-users-community — Unofficial Vbox-users mailing list
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
(179) |
Apr
(181) |
May
(235) |
Jun
(147) |
Jul
(132) |
Aug
(126) |
Sep
(205) |
Oct
(113) |
Nov
(103) |
Dec
(208) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(134) |
Feb
(86) |
Mar
(115) |
Apr
(106) |
May
(132) |
Jun
(147) |
Jul
(95) |
Aug
(160) |
Sep
(86) |
Oct
(100) |
Nov
(111) |
Dec
(92) |
| 2012 |
Jan
(73) |
Feb
(91) |
Mar
(176) |
Apr
(115) |
May
(87) |
Jun
(125) |
Jul
(91) |
Aug
(104) |
Sep
(151) |
Oct
(193) |
Nov
(64) |
Dec
(35) |
| 2013 |
Jan
(147) |
Feb
(106) |
Mar
(169) |
Apr
(100) |
May
(67) |
Jun
(114) |
Jul
(51) |
Aug
(85) |
Sep
(37) |
Oct
(38) |
Nov
(35) |
Dec
(45) |
| 2014 |
Jan
(16) |
Feb
(15) |
Mar
(58) |
Apr
(47) |
May
(45) |
Jun
(12) |
Jul
(43) |
Aug
(12) |
Sep
(45) |
Oct
(27) |
Nov
(43) |
Dec
(24) |
| 2015 |
Jan
(10) |
Feb
(17) |
Mar
(36) |
Apr
(40) |
May
(73) |
Jun
(35) |
Jul
(45) |
Aug
(36) |
Sep
(17) |
Oct
(32) |
Nov
(52) |
Dec
(35) |
| 2016 |
Jan
(34) |
Feb
(27) |
Mar
(48) |
Apr
(34) |
May
(37) |
Jun
(35) |
Jul
(30) |
Aug
(35) |
Sep
(28) |
Oct
(8) |
Nov
(32) |
Dec
(6) |
| 2017 |
Jan
(29) |
Feb
(34) |
Mar
(12) |
Apr
(30) |
May
(15) |
Jun
(13) |
Jul
(30) |
Aug
(29) |
Sep
(7) |
Oct
(51) |
Nov
(8) |
Dec
(1) |
| 2018 |
Jan
(6) |
Feb
(3) |
Mar
|
Apr
(6) |
May
(5) |
Jun
(8) |
Jul
(4) |
Aug
(16) |
Sep
(20) |
Oct
(2) |
Nov
(3) |
Dec
(4) |
| 2019 |
Jan
(26) |
Feb
|
Mar
|
Apr
(8) |
May
(19) |
Jun
(1) |
Jul
(5) |
Aug
(11) |
Sep
(26) |
Oct
(12) |
Nov
(22) |
Dec
(11) |
| 2020 |
Jan
(7) |
Feb
(15) |
Mar
(11) |
Apr
(18) |
May
(17) |
Jun
(9) |
Jul
(9) |
Aug
(11) |
Sep
(11) |
Oct
(16) |
Nov
(7) |
Dec
(34) |
| 2021 |
Jan
(12) |
Feb
(3) |
Mar
(2) |
Apr
(2) |
May
(1) |
Jun
(13) |
Jul
(9) |
Aug
(3) |
Sep
(11) |
Oct
(40) |
Nov
(32) |
Dec
(8) |
| 2022 |
Jan
(6) |
Feb
(1) |
Mar
(7) |
Apr
(3) |
May
(15) |
Jun
(9) |
Jul
(14) |
Aug
(6) |
Sep
(1) |
Oct
(9) |
Nov
(2) |
Dec
(4) |
| 2023 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
(7) |
May
(3) |
Jun
(6) |
Jul
(4) |
Aug
(12) |
Sep
|
Oct
(5) |
Nov
(5) |
Dec
|
| 2024 |
Jan
(9) |
Feb
(8) |
Mar
|
Apr
(5) |
May
(1) |
Jun
|
Jul
(4) |
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
(11) |
Dec
(5) |
| 2025 |
Jan
(7) |
Feb
(10) |
Mar
|
Apr
(1) |
May
(24) |
Jun
(8) |
Jul
(4) |
Aug
(1) |
Sep
(4) |
Oct
(2) |
Nov
(11) |
Dec
(16) |
| 2026 |
Jan
(14) |
Feb
(8) |
Mar
(5) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Vadim G. <vad...@or...> - 2026-04-21 12:40:28
|
Hello, Today Oracle released VirtualBox 7.2.8, a maintenance release of VirtualBox 7.2 which improves stability and fixes regressions. See the change log at https://www.virtualbox.org/wiki/Changelog-7.2 for a list of changes. VirtualBox source code is now also available on GitHub at https://github.com/VirtualBox/virtualbox. If you want to report issues needing tracking, use https://github.com/VirtualBox/virtualbox/issues. In addition, please feel free to post a feedback about the release to https://forums.virtualbox.org/viewtopic.php?t=114520. |
|
From: Gregory N. <gr...@gr...> - 2026-04-02 00:46:51
|
On Wed, Apr 01, 2026 at 02:12:18PM +0200, mattias jonsson wrote: > in the virtual machine window > > any shortcut to access the menu bar? > > i tryed hostkey+page up > > not work No surprise, it's hostkey+home. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc -- Free domains: http://www.eu.org/ or mail dns...@EU... |
|
From: mattias j. <mjo...@gm...> - 2026-04-01 12:12:26
|
in the virtual machine window any shortcut to access the menu bar? i tryed hostkey+page up not work |
|
From: Prentice B. <pre...@uc...> - 2026-03-31 19:05:26
|
I'm using 7.2.6 r172322 (Qt6.8.0 on cocoa) on a MacBook Pro running Sequoia 15.7.4 on an Apple M2 Pro processor. I've used VirtualBox for ~8 years to provide a Linux desktop on a Windows x86_64 laptop. On I set up DNS on the Linux guest to use the host for DNS so that moving between networks wouldn't break DNS lookups. I remember editing the SERVER line in /etc/resolv.conf to use the IP address of the host (10.0.2.1 or 10.0.2.2, or something like that - it's been a couple years). I can't seen seem to make that work in this new environment. What am I doing wrong? I suspect I might not have the guests on the right network type, or using the right address for the host.I do have 'hosts: files dns" in my /etc/nsswitch.conf file. I have checked the VBox documentation, but I've always found the documentation around networking to not be the easiest to understand and/or incomplete. Since MacOS/ARM processor support is still pretty new, I'm also not sure if this just an issue with MacOS/ARM not supporting that capability yet. I had a number of issues with earlier version of VBox that supported that platform, but a lot of them have been fixed now. I've tried setting both --natdnsproxy1 on and --natdnshostresolver1 on, but neither option worked for me, but I admit in both cases it could have been user error. Again, I was able to make this work pretty easily in the past on a Windows/x86_64 platform. My Linux desktop guest (and a few other servers I've set up in my virtual lab) are all on the same NAT Network. Prentice |
|
From: John L. <jl...@bl...> - 2026-03-26 16:35:21
|
I found these two changes were required in order to obtain successful kmk build with the newest gcc.
The first one is probably an ancient mistake (although presumably it makes no difference to the result).
The second one has me baffled because the code is correct - the return type of strrchr is char *.
Or is it? preprocessor output of this compilation shows this strange sequence - note the cast "(const char *) (strrchr (" - but where that itself came from I've no diea -- easiest to change the c file.
if (fname !=
# 592 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c" 3 4
((void *)0)
# 592 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c"
) {
if ((p =
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c" 3 4
_Generic (0 ? (
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c"
fname
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c" 3 4
) : (void *) 1, const void *: (const char *) (strrchr (
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c"
fname
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c" 3 4
,
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c"
'/'
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c" 3 4
)), default: strrchr (
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c"
fname
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c" 3 4
,
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c"
'/'
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c" 3 4
))
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c"
) !=
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c" 3 4
((void *)0)
# 593 "/opt/VirtualBox-rev112603/src/VBox/ExtPacks/VBoxDTrace/onnv/lib/libdtrace/common/dt_program.c"
|
|
From: Prentice B. <pre...@uc...> - 2026-03-09 20:46:28
|
I'm running VB 7.2.6 r172322 on MacOS 15.7.4 on an M2 Pro chip (MacBook Pro). Not exactly the same version as you. I just downloaded and installed CentOS 10 w/o any issues whatsoever. What hardware/OS is your host running on? VB on MacOS/Arm processors hasn't been very good in the past, but it's been getting a lot better recently. As far as choosing CentOS 10 from the "OS Distributions" list, I think that only affects the icon shown in the VBox Manager window to make it easier to identify your VMs, and maybe sent some appropriate/sane default settings for the OS (default RAM size, VM disk size, etc.) How much RAM are you specifying for CentOS? Even though the default is 2 GB, I find RHEL installs (including RHEL) will fail if you don't have at least 4 GB. If the VM is going to have a GUI interface and your host has a high resolution, set the video RAM to 128 MB. If you don't, you usually can't go full screen with the GUI with modern display with HD and better displays. I didn't have any issues with the storage settings dialog, either. I know we're not using the same exact version of VB, so take this report just as a data point that there is a version of VB that works with CentOS 10. Prentice On 3/9/26 3:10 PM, George R Goffe via VBox-users-community wrote: > Howdy, > > I"m using VB version "VirtualBox-7.2.97-173028-Linux_amd64.run". > > I just downloaded Centos Stream 10... Hoping to finally get one working. > > The console support STILL has show stopping problems... > > Like trying to poke the lower right hand button after selecting "English (us)" as the language. I could NOT get the cursor to the button. VB captured the mouse pointer but that was it... I also had trouble configuring the "new" VM. > > There's NO Centos in the list of "OS Distributions". Maybe Centos is "Red Hat"? I went with "other linux"... > > Additionally, the menu for partitioning had trouble with "enabling" items like, "reformat". It was greyed out... I had to back up and restart to get it to work. Sigh... > > After finishing the "New" VM entry, the "Finish" button was NOT enabled... Again, I had to stop, back up... fiddle with the UI to get it to "enable"... > > Has anyone gotten VB and Centos-10 (or Centos-9) to work? > > Best regards, > > George... > > > _______________________________________________ > VBox-users-community mailing list > VBo...@li... > https://lists.sourceforge.net/lists/listinfo/vbox-users-community > _______________________________________________ > Unsubscribe: mailto:vbo...@li...?subject=unsubscribe |
|
From: George R G. <gr...@ya...> - 2026-03-09 19:31:32
|
Howdy, I"m using VB version "VirtualBox-7.2.97-173028-Linux_amd64.run". I just downloaded Centos Stream 10... Hoping to finally get one working. The console support STILL has show stopping problems... Like trying to poke the lower right hand button after selecting "English (us)" as the language. I could NOT get the cursor to the button. VB captured the mouse pointer but that was it... I also had trouble configuring the "new" VM. There's NO Centos in the list of "OS Distributions". Maybe Centos is "Red Hat"? I went with "other linux"... Additionally, the menu for partitioning had trouble with "enabling" items like, "reformat". It was greyed out... I had to back up and restart to get it to work. Sigh... After finishing the "New" VM entry, the "Finish" button was NOT enabled... Again, I had to stop, back up... fiddle with the UI to get it to "enable"... Has anyone gotten VB and Centos-10 (or Centos-9) to work? Best regards, George... |
|
From: George R G. <gr...@ya...> - 2026-03-02 15:36:49
|
>Message: 2 >Date: Wed, 18 Feb 2026 11:42:00 -0700 >From: JD <jd...@gm...> >To: Community mailing list of VirtualBox users > <vbo...@li...> >Subject: Re: [VBox-users] VBox build problems. >Message-ID: > <CAN...@ma...> >Content-Type: text/plain; charset="utf-8" > >Hi G. R. Goff > >What do you mean by "this system" ??? Pardon me. Fedora 45 (rawhide) on a Vivobook S16. The problem seems to have gone away (for now) with newer versions of VB. Thanks for your response. George... > >Perhaps you can be more specific??? > >On Wed, Feb 18, 2026 at 9:42?AM George R Goffe via VBox-users-community < >vbo...@li...> wrote: > >> Howdy, >> >> I'm attempting to get VB running on this system and am seeing build >> problems after running vboxconfig. >> >> Has anyone seen this problem and HOW to resolve it? >> >> Best regards, >> >> George... >> >> 31 ld -m elf_x86_64 -z noexecstack --no-warn-rwx-segments -r -o >> vboxdrv.o @vboxdrv.mod ; /export/h >> 31 ome/kernels/linux-6.18.9/tools/objtool/objtool --hacks=jump_label >> --hacks=noinstr --hacks=skylake -- >> 31 ibt --orc --retpoline --rethunk --sls --static-call --uaccess >> --prefix=16 --Werror --link --module >> 31 vboxdrv.o >> 32 vboxdrv.o: error: objtool: supdrvTracerCommonDeregisterImpl+0x3d: >> relocation to !ENDBR: supdrvTracer 32 ProbeFireStub+0x0 >> 33 vboxdrv.o: error: objtool: g_aFunctions+0xea0: data relocation to >> !ENDBR: SUPR0TracerFireProbe+0x0 >> 34 vboxdrv.o: error: objtool: g_pfnSupdrvProbeFireKernel+0x0: data >> relocation to !ENDBR: supdrvTracerPr 34 obeFireStub+0x0 >> 35 vboxdrv.o: error: objtool: .export_symbol+0x518: data relocation >> to !ENDBR: SUPR0TracerFireProbe+0x0 >> 36 make[3]: *** >> [/export/home/kernels/linux-6.18.9/scripts/Makefile.build:503: vboxdrv.o] >> Error 1 >> 37 make[3]: *** Deleting file 'vboxdrv.o' >> 38 make[2]: *** [/export/home/kernels/linux-6.18.9/Makefile:2011: .] >> Error 2 >> 39 make[1]: *** [Makefile:248: __sub-make] Error 2 >> 40 make: *** [/tmp/vbox.0/Makefile-footer.gmk:146: vboxdrv] Error 2 >> > |
|
From: Fernando C. <fc...@gm...> - 2026-02-24 11:09:30
|
On Tue, Feb 24, 2026, 2:22 AM Alexey Eromenko <al...@gm...> wrote: > https://gemini.google.com/share/f6536d1dcd39 > > Gemini answers means it can reason, can understand, and passed the Turing > Test. > Absolutely amazing results, if you ask me. > —- > Some modifications and improvements to LLM would allow to develop system > software and Virtualization capabilities from scratch in real-time. > > -Alexey Eromenko "Technologov" > In my view Anthropic's Claude is god too. FC |
|
From: Alexey E. <al...@gm...> - 2026-02-24 05:21:00
|
https://gemini.google.com/share/f6536d1dcd39 Gemini answers means it can reason, can understand, and passed the Turing Test. Absolutely amazing results, if you ask me. —- Some modifications and improvements to LLM would allow to develop system software and Virtualization capabilities from scratch in real-time. -Alexey Eromenko "Technologov" |
|
From: JD <jd...@gm...> - 2026-02-18 18:42:44
|
Hi G. R. Goff What do you mean by "this system" ??? Perhaps you can be more specific??? On Wed, Feb 18, 2026 at 9:42 AM George R Goffe via VBox-users-community < vbo...@li...> wrote: > Howdy, > > I'm attempting to get VB running on this system and am seeing build > problems after running vboxconfig. > > Has anyone seen this problem and HOW to resolve it? > > Best regards, > > George... > > > > 31 ld -m elf_x86_64 -z noexecstack --no-warn-rwx-segments -r -o > vboxdrv.o @vboxdrv.mod ; /export/h > 31 ome/kernels/linux-6.18.9/tools/objtool/objtool --hacks=jump_label > --hacks=noinstr --hacks=skylake -- > 31 ibt --orc --retpoline --rethunk --sls --static-call --uaccess > --prefix=16 --Werror --link --module > 31 vboxdrv.o > 32 vboxdrv.o: error: objtool: supdrvTracerCommonDeregisterImpl+0x3d: > relocation to !ENDBR: supdrvTracer 32 ProbeFireStub+0x0 > 33 vboxdrv.o: error: objtool: g_aFunctions+0xea0: data relocation to > !ENDBR: SUPR0TracerFireProbe+0x0 > 34 vboxdrv.o: error: objtool: g_pfnSupdrvProbeFireKernel+0x0: data > relocation to !ENDBR: supdrvTracerPr 34 obeFireStub+0x0 > 35 vboxdrv.o: error: objtool: .export_symbol+0x518: data relocation > to !ENDBR: SUPR0TracerFireProbe+0x0 > 36 make[3]: *** > [/export/home/kernels/linux-6.18.9/scripts/Makefile.build:503: vboxdrv.o] > Error 1 > 37 make[3]: *** Deleting file 'vboxdrv.o' > 38 make[2]: *** [/export/home/kernels/linux-6.18.9/Makefile:2011: .] > Error 2 > 39 make[1]: *** [Makefile:248: __sub-make] Error 2 > 40 make: *** [/tmp/vbox.0/Makefile-footer.gmk:146: vboxdrv] Error 2 > > > > _______________________________________________ > VBox-users-community mailing list > VBo...@li... > https://lists.sourceforge.net/lists/listinfo/vbox-users-community > _______________________________________________ > Unsubscribe: mailto:vbo...@li... > ?subject=unsubscribe > |
|
From: George R G. <gr...@ya...> - 2026-02-18 16:41:54
|
Howdy, I'm attempting to get VB running on this system and am seeing build problems after running vboxconfig. Has anyone seen this problem and HOW to resolve it? Best regards, George... 31 ld -m elf_x86_64 -z noexecstack --no-warn-rwx-segments -r -o vboxdrv.o @vboxdrv.mod ; /export/h 31 ome/kernels/linux-6.18.9/tools/objtool/objtool --hacks=jump_label --hacks=noinstr --hacks=skylake -- 31 ibt --orc --retpoline --rethunk --sls --static-call --uaccess --prefix=16 --Werror --link --module 31 vboxdrv.o 32 vboxdrv.o: error: objtool: supdrvTracerCommonDeregisterImpl+0x3d: relocation to !ENDBR: supdrvTracer 32 ProbeFireStub+0x0 33 vboxdrv.o: error: objtool: g_aFunctions+0xea0: data relocation to !ENDBR: SUPR0TracerFireProbe+0x0 34 vboxdrv.o: error: objtool: g_pfnSupdrvProbeFireKernel+0x0: data relocation to !ENDBR: supdrvTracerPr 34 obeFireStub+0x0 35 vboxdrv.o: error: objtool: .export_symbol+0x518: data relocation to !ENDBR: SUPR0TracerFireProbe+0x0 36 make[3]: *** [/export/home/kernels/linux-6.18.9/scripts/Makefile.build:503: vboxdrv.o] Error 1 37 make[3]: *** Deleting file 'vboxdrv.o' 38 make[2]: *** [/export/home/kernels/linux-6.18.9/Makefile:2011: .] Error 2 39 make[1]: *** [Makefile:248: __sub-make] Error 2 40 make: *** [/tmp/vbox.0/Makefile-footer.gmk:146: vboxdrv] Error 2 |
|
From: Sérgio B. <se...@se...> - 2026-02-09 13:52:21
|
On Sun, 2026-02-08 at 22:08 +0000, George R Goffe via VBox-users- community wrote: > Howdy, > > Thanks for the response. > > I have already tried this. It didn't work. Some sort of packaging > problem. The messages I got contained "uname -r" as a string... which > seems to have come from somewhere in the rpm(s) themselves. I think > it should have been the execution of "uname -r" to create part of the > name. A typo. > > I got the kernel source I wanted from kernel.org and built it myself. > Works fine... VB works too... sort of. I tried two versions of VB > 7.2 (VirtualBox-7.2.97-172565-Linux_amd64.run VirtualBox-7.2.97- > 172124-Linux_amd64.run) but both seem to have console support > problems. I went to VirtualBox-7.1.15-172119-Linux_amd64.run which > worked as expected. > > Thanks for the response... > Please check and follow this bug report. https://github.com/VirtualBox/virtualbox/issues/467#issuecomment-3869541116 > > > Ofc you can install any previous kernel, by downloading it from > > Koji. > > Here is link to 6.18.0-fc44 : > > https://koji.fedoraproject.org/koji/buildinfo?buildID=2872145 > > > _______________________________________________ > VBox-users-community mailing list > VBo...@li... > https://lists.sourceforge.net/lists/listinfo/vbox-users-community > _______________________________________________ > Unsubscribe: > mailto:vbo...@li...?subject=uns > ubscribe -- Sérgio M. B. |
|
From: George R G. <gr...@ya...> - 2026-02-08 22:08:48
|
Howdy, Thanks for the response. I have already tried this. It didn't work. Some sort of packaging problem. The messages I got contained "uname -r" as a string... which seems to have come from somewhere in the rpm(s) themselves. I think it should have been the execution of "uname -r" to create part of the name. A typo. I got the kernel source I wanted from kernel.org and built it myself. Works fine... VB works too... sort of. I tried two versions of VB 7.2 (VirtualBox-7.2.97-172565-Linux_amd64.run VirtualBox-7.2.97-172124-Linux_amd64.run) but both seem to have console support problems. I went to VirtualBox-7.1.15-172119-Linux_amd64.run which worked as expected. Thanks for the response... >Ofc you can install any previous kernel, by downloading it from Koji. >Here is link to 6.18.0-fc44 : >https://koji.fedoraproject.org/koji/buildinfo?buildID=2872145 |
|
From: Allan <all...@wa...> - 2026-02-07 00:15:11
|
På Fri, 6 Feb 2026 20:49:01 +0000 (UTC) George R Goffe via VBox-users-community <vbo...@li...> skrev: > Howdy, > > Yes. I know. This system is running 6.19.0-0.rc8.54.fc44.x86_64 which > is a RC kernel. I know... Not supported... yet. Back leveling the > kernel seems to be impossible. Ofc you can install any previous kernel, by downloading it from Koji. Here is link to 6.18.0-fc44 : https://koji.fedoraproject.org/koji/buildinfo?buildID=2872145 |
|
From: George R G. <gr...@ya...> - 2026-02-06 20:49:14
|
Howdy, Yes. I know. This system is running 6.19.0-0.rc8.54.fc44.x86_64 which is a RC kernel. I know... Not supported... yet. Back leveling the kernel seems to be impossible. Is there any chance of a "patch" to VB for this being available? Best regards, George... Here;s what I'm seeing: 42 # MODPOST Module.symvers 43 /export/home/kernels/6.19.0-0.rc8.54.fc44.x86_64/scripts/mod/modpost -M 43 -o Module.symvers -T modules.order -i /export/home/kernels/6.19.0-0.rc8.54.fc44.x86_ 43 64/Module.symvers -e 44 ERROR: modpost: module vboxdrv uses symbol cr4_update_irqsoff from namespace module: 44 kvm,kvm-amd,kvm-intel, but does not import it. 45 ERROR: modpost: module vboxdrv uses symbol cr4_read_shadow from namespace module:kvm 45 ,kvm-amd,kvm-intel, but does not import it. 46 ERROR: modpost: module vboxdrv uses symbol __flush_tlb_all from namespace module:kvm 46 ,kvm-amd,kvm-intel, but does not import it. 47 make[3]: *** [/export/home/kernels/6.19.0-0.rc8.54.fc44.x86_64/scripts/Makefile.modp 47 ost:147: Module.symvers] Error 1 48 make[2]: *** [/export/home/kernels/6.19.0-0.rc8.54.fc44.x86_64/Makefile:2041: modpos 48 t] Error 2 49 make[1]: *** [Makefile:248: __sub-make] Error 2 50 make: *** [/tmp/vbox.0/Makefile-footer.gmk:146: vboxdrv] Error 2 |
|
From: Marco M. <mm...@do...> - 2026-01-29 15:23:16
|
Am 26.01.2026 um 19:03:35 Uhr schrieb Gregory Nowak: > On Mon, Jan 26, 2026 at 07:38:27AM +0100, Marco Moock wrote: > > I do have promiscuous mode enabled for all, but the issue is that > > the bridge doesn't behave like a real bridge, it doesn't learn the > > multiple MAC addresses from the VM, like a real bridge/switch. > > How are you attaching the guest network interface? Are you bridging it > to the host's physical ethernet adapter, or to a tap device? If you're > bridging to the physical interface, create a bridge on the host with > the physical network interface and a tap device, and bridge the guest > interface to the tap device. That might make a difference. I have the physical trunk interface and that is selected in the virtualbox settings. That works for Linux guests, as I tried with Fedora. The NIC was not in promiscuous mode, so I assume an issue with FreeBSD in that case. Thanks for your suggestions. Someone on the freebsd-net list told me to switch off vlanhwfilter (an option in FreeBSD to disable the VLAN filtering option in certain NICs). Does the virtio interface in VirtualBox support such a feature? -- Gruß Marco Send unsolicited bulk mail to 176...@ca... |
|
From: Marco M. <mm...@do...> - 2026-01-28 18:44:39
|
Am 26.01.2026 um 19:03:35 Uhr schrieb Gregory Nowak: > On Mon, Jan 26, 2026 at 07:38:27AM +0100, Marco Moock wrote: > > I do have promiscuous mode enabled for all, but the issue is that > > the bridge doesn't behave like a real bridge, it doesn't learn the > > multiple MAC addresses from the VM, like a real bridge/switch. > > How are you attaching the guest network interface? Are you bridging it > to the host's physical ethernet adapter, or to a tap device? If you're > bridging to the physical interface, create a bridge on the host with > the physical network interface and a tap device, and bridge the guest > interface to the tap device. That might make a difference. I have the physical trunk interface and that is selected in the virtualbox settings. That works for Linux guests, as I tried with Fedora. The NIC was not in promiscuous mode, so I assume an issue with FreeBSD in that case. Thanks for your suggestions. -- Gruß Marco Send unsolicited bulk mail to 176...@ca... |
|
From: Vadim G. <vad...@or...> - 2026-01-28 17:59:24
|
Hello, Today Oracle released VirtualBox 7.2.6, a maintenance release of VirtualBox 7.2 which improves stability and fixes regressions. See the change log at https://www.virtualbox.org/wiki/Changelog-7.2 for a list of changes. VirtualBox source code is now also available on GitHub at https://github.com/VirtualBox/virtualbox. If you want to report issues needing tracking, use https://github.com/VirtualBox/virtualbox/issues. In addition, please feel free to post a feedback about the release to https://forums.virtualbox.org/viewtopic.php?t=114387. Confidential- Oracle Internal |
|
From: Vadim G. <vad...@or...> - 2026-01-28 17:57:22
|
Hello, Today Oracle released VirtualBox 7.1.16, a maintenance release of VirtualBox 7.1 which improves stability and fixes regressions. See the change log at https://www.virtualbox.org/wiki/Changelog-7.1 for a list of changes. VirtualBox source code is now also available on GitHub at https://github.com/VirtualBox/virtualbox. If you want to report issues needing tracking, use https://github.com/VirtualBox/virtualbox/issues. In addition, please feel free to post a feedback about the release to https://forums.virtualbox.org/viewtopic.php?t=114385. Confidential- Oracle Internal |
|
From: Gregory N. <gr...@gr...> - 2026-01-27 02:04:04
|
On Mon, Jan 26, 2026 at 07:38:27AM +0100, Marco Moock wrote: > I do have promiscuous mode enabled for all, but the issue is that the > bridge doesn't behave like a real bridge, it doesn't learn the > multiple MAC addresses from the VM, like a real bridge/switch. How are you attaching the guest network interface? Are you bridging it to the host's physical ethernet adapter, or to a tap device? If you're bridging to the physical interface, create a bridge on the host with the physical network interface and a tap device, and bridge the guest interface to the tap device. That might make a difference. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc -- Free domains: http://www.eu.org/ or mail dns...@EU... |
|
From: Marco M. <mm...@do...> - 2026-01-26 06:38:46
|
On 25.01.2026 19:15 Gregory Nowak wrote: > Use vboxmanage, like: > > vboxmanage modifyvm vmname --nic-promisc1=allow-all > > I believe this is chapter 8 of the VirtualBox user guide. I do have promiscuous mode enabled for all, but the issue is that the bridge doesn't behave like a real bridge, it doesn't learn the multiple MAC addresses from the VM, like a real bridge/switch. |
|
From: Gregory N. <gr...@gr...> - 2026-01-26 02:15:49
|
On Sun, Jan 25, 2026 at 03:37:51PM +0100, Marco Moock wrote: > I run Virtualbox on Debian with a network bridge to a real ethernet > interface that is a trunk (transports multiple vlans with tags). > > My goal is to bring that trunk into the VM, so one bridge exists to the > trunk interface and the VM will create subinterfaces. Although, the > bridge doesn't detect that those subinterfaces have multiple MAC > addresses and doesn't forward ethernet traffic to them unless I enable > promiscuous mode in the VM (e.g. start sniffing using tcpdump). If I > disable promiscuous mode in the VM, the traffic with dst of the > subinterfaces with different MAC will stop. > > How do I configure that properly, so the bridge behaves like a real > bridge that ust learns which MAC addresses are connected to which port > and don't filter. Use vboxmanage, like: vboxmanage modifyvm vmname --nic-promisc1=allow-all I believe this is chapter 8 of the VirtualBox user guide. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc -- Free domains: http://www.eu.org/ or mail dns...@EU... |
|
From: Marco M. <mm...@do...> - 2026-01-25 14:38:12
|
Hello! I run Virtualbox on Debian with a network bridge to a real ethernet interface that is a trunk (transports multiple vlans with tags). My goal is to bring that trunk into the VM, so one bridge exists to the trunk interface and the VM will create subinterfaces. Although, the bridge doesn't detect that those subinterfaces have multiple MAC addresses and doesn't forward ethernet traffic to them unless I enable promiscuous mode in the VM (e.g. start sniffing using tcpdump). If I disable promiscuous mode in the VM, the traffic with dst of the subinterfaces with different MAC will stop. How do I configure that properly, so the bridge behaves like a real bridge that ust learns which MAC addresses are connected to which port and don't filter. -- kind regards Marco Send unsolicited bulk mail to 176...@st... |
|
From: Marco M. <mm...@do...> - 2026-01-02 16:23:44
|
Hello! I have VirtualBox 7.2.4 on Debian sid. I use VMSVGA and added a second monitor to the VM, but I cannot activate it via View in menu bar, greyed out. What can cause that? -- kind regards Marco Send unsolicited bulk mail to 176...@st... |
97 messages has been excluded from this view by a project administrator.
