Upstream is EOLng VirtualBox 6.x in December <URL:https://www.virtualbox.org/wiki/Downloads> VirtualBox 7.x includes several enhancements <URL:https://www.virtualbox.org/wiki/Changelog> John groenveld@acm.org
As discussed in bug #266907 "Devices: The EHCI and XHCI USB controller devices are now part of the open source base package" John groenveld@acm.org
Triage: * aim to make a cross-reference from bug 266907 * reuse the 'see also' field for a full URL with the same bug report number * begin the summary line with emulators/virtualbox-ose * adapted slightly, as koobs@ did for 266907 on 2022-10-12 * set the assignee that would have been automated by beginning with emulators/virtualbox-ose * keyword … and thank you :-)
My bug-271146 branch in GitHub <https://github.com/grahamperrin/freebsd-ports/tree/bug-271146> is a bare-bones beginning, two ports alone (virtualbox-ose, virtualbox-ose-kmod), build of which I'll test first in a 1400089 amd64 jail. If it does build and install, in any host environment, testers should take the usual precautions before proceeding with changes to any guest machine: * have verifiably good backups of all relevant guest data * and so on. Hint: .diff at <https://github.com/freebsd/freebsd-ports/compare/main...grahamperrin:freebsd-ports:bug-271146.diff>
Re: comment 3 Bare-bones was wishful thinking :-) =======================<phase: patch >============================ ===== env: DEVELOPER_MODE=yes DEVELOPER=1 STRICT_DEPENDS=yes USER=root UID=0 GID=0 ===> Patching for virtualbox-ose-kmod-7.0.8 ===> Applying FreeBSD patches for virtualbox-ose-kmod-7.0.8 from /usr/ports/emulators/virtualbox-ose-kmod/../virtualbox-ose/files 15 out of 21 hunks failed--saving rejects to Config.kmk.rej ===> FAILED Applying FreeBSD patch-Config.kmk ===> FAILED to apply cleanly FreeBSD patch(es) patch-Config.kmk *** Error code 1
(In reply to Graham Perrin from comment #4) Hello Graham, When patches doesn't apply we need to check if it was applied upstream or just adapt it to new code, e.g. vi files/patch-src-A work/portname/src/A and check it for differences. When done, make makepatch. For quick check you can disable patches renaming files -> files.off Cheers
VirtualBox 7.0.12 (released October 17 2023)
Virtualbox.org indicates 6.x goes end-of-life in December 2023
(In reply to Brian Roper from comment #7) > Virtualbox.org indicates 6.x goes end-of-life in December 2023 6.1.50 just released: https://www.virtualbox.org/wiki/Changelog-6.1#v50 I created a patch, testing the new version on 2 of my servers now and I'll create review (https://reviews.freebsd.org) tomorrow. 7.0.14 released too: https://www.virtualbox.org/wiki/Changelog-7.0#v14
Oracle support for VirtualBox 6.1 has ended. See https://www.virtualbox.org/wiki/Download_Old_Builds
(In reply to Brian Roper from comment #9) > Oracle support for VirtualBox 6.1 has ended. Thanks, that overlaps with 2023 bug 274270, >> 5.1.38 is more than five years old, support for Oracle VM VirtualBox >> 5.x ended more than three years ago.
(In reply to Vladimir Druzenko from comment #8) > 7.0.14 <https://www.virtualbox.org/wiki/Changelog-7.0#v16> > VirtualBox 7.0.16 (released April 16 2024)
(In reply to Graham Perrin from comment #11) > ATTENTION: PLEASE REFRAIN FROM UPGRADING TO 7.0.16 FOR NOW. THIS RELEASE HAS AN ISSUE WHICH MIGHT CAUSE HOST OS CRASH WHEN VM IS CONFIGURED TO USE BRIDGED OR HOST-ONLY NETWORKING. WE WILL SEND AN ANNOUNCEMENT TO MAILING LISTS WHEN FIX WILL BE AVAILABLE FOR DOWNLOAD. https://www.virtualbox.org/ I started updating the port, but then I read this and stopped.
Looks like 7.0.18 was released on 5/3/24. I'd be happy to help test if someone could point me to a ports src tree to build from.
(In reply to Roger Fujii from comment #13) Yes, I know. The sources have changed a lot - our patches need significant work: 89 patches with 7811 lines total. Is anyone else ready to take on updating some of our patches? If I do it alone, it could take weeks, or even months.
I originally tried applying the v6.x patches to 7 and realized there is a lot of files that required mods, so I figured someone must have already started this, so just waited. I'm happy to step up on this, but don't want to do all this work and then being told "oh, we already did that". If there is no current v7 patches, I can re-start the effort I started before. Just trying to efficiently use time/resources.