On 2018-12-22 19:19, Kevin Oberman wrote:
Can anyone confirm running VirtualBox on head after 11.0-Release?
Apparently you meant to ask "after 12.0-RELEASE", though I'm not sure
about the "after" - anyway *on* 12.0-RELEASE, I'm running
virtualbox-ose-5.2.18_1 (from package) with
virtualbox-ose
[I found my E-mail records reporting successful builds using
qemu-user-static from ports head -r484783 under FreeBSD
head -r340287.]
On 2018-Dec-22, at 00:10, Mark Millard wrote:
> [I messed up the freebsd-emulation email address the first time I sent
> this. I also forgot to indicate the qemu-u
Thanks for the info, but it has never been a problem on 11. I am running it
on 11.2-Stable of last week. The problem pops up only on 12. I will next
try something in mid-September, but I fear that the change that triggers
the crash goes back much further. It may take a while.
On Sat, Dec 22, 2018,
Fwiw, I am running virtualbox-ose-nox11-5.2.22 on FreeBSD 11.2 with (almost)
no issues. I installed virtualbox-ose-nox11 using pkg, then compiled
virtualbox-ose-kmod from ports (compiling kmod on the box was required about
a year ago or the system would crash at boot, and I follow the same
procedur
On Wed, Dec 19, 2018 at 10:26 PM Kevin Oberman wrote:
> After updating my system to 12 and re-installing all ports, the system is
> panicing when I try to run VirtualBox. There have been several bugs opened
> where VBox crashes the system instantly when started. Not the virtual
> system, but the
[I messed up the freebsd-emulation email address the first time I sent
this. I also forgot to indicate the qemu-user-static vintage relationship.]
I had been reporting intermittent hang-ups for my amd64->{aarch64,armv7} port
cross
builds in another message sequence. But it turns out that one thin
