Date: Tue, 27 Aug 2019 14:45:54 -0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: [Bug 234878] emulators/virtualbox-ose: Update to 6.0 Message-ID: <bug-234878-26505-TyW88zcKXQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234878-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-234878-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234878 Mikhail Teterin <mi@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mi@FreeBSD.org --- Comment #35 from Mikhail Teterin <mi@FreeBSD.org> --- I too would like the VirtualBox ports upgraded (the current latest from upstream is 6.0.10) -- at least, the ose-guest-additions, because that's al= l I use. The one point, that all of the virtualbox ports have omitted so far is addi= ng -DPAE to the compiler command lines building kernel modules. I'm trying to = deal with this myself currently with things like this: .if ${.CURDIR:M*/ports/*virtualbox-ose*} CFLAGS+=3D -DPAE COPTFLAGS+=3D -DPAE CXXFLAGS+=3D -DPAE .endif but I'm never certain, if they have the proper effect every time or if my vboxguest.ko is subtly miscompiled :( This may be less important to the server port, as VM-hosting servers these = days tend to be 64bit anyway, but it is perfectly normal for a guest VM to be 32= -bit -- using PAE to have more than 4GB of total memory, while limiting each pro= cess to 4GB. I'm not sure, if PAE should be a "flavor" or an option... Given that it only affects kernel-modules (both for the host- and the guest- ports), maybe, the vboxguest.ko needs a port of its own (like the already-existing virtualbox-ose-kmod). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234878-26505-TyW88zcKXQ>