[package - head-i386-default][emulators/virtualbox-ose-additions] Failed for virtualbox-ose-additions-5.2.26_4 in build

2019-04-02 Thread pkg-fallout
You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: v...@freebsd.org Last committer: j...@freebsd.org Ident: $FreeBSD:

[Bug 236616] emulators/virtualbox-ose: Unable to create a new machine due to "Unexpected exception: cxxrt::bad_alloc [St9bad_alloc]"

2019-04-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236616 --- Comment #7 from Dimitry Andric --- (In reply to Mateusz Piotrowski from comment #2) > Here are some additional error messages I get when running "vagrant up" to > create a new machine: > > > There was an error while executing

[package - head-i386-default][emulators/virtualbox-ose] Failed for virtualbox-ose-5.2.26_3 in build

2019-04-02 Thread pkg-fallout
You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: v...@freebsd.org Last committer: j...@freebsd.org Ident: $FreeBSD:

[Bug 236616] emulators/virtualbox-ose: Unable to create a new machine due to "Unexpected exception: cxxrt::bad_alloc [St9bad_alloc]"

2019-04-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236616 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added Status|New |Open ---

Re: starting virtual box VM instantly crashes FreeBSD after upgrade from 11 to 12

2019-04-02 Thread Graham Menhennitt
Thanks for replying. Yes I rebuilt and installed virtualbox-ose and virtualbox-ose-kmod. The files in /boot/modules are the newly built ones. I have rebooted after installing them. Thanks,     Graham On 2/4/19 4:46 pm, Koichiro Iwao wrote: Hi, did you rebuild virtualbox-ose-kmod? On Tue,

Re: starting virtual box VM instantly crashes FreeBSD after upgrade from 11 to 12

2019-04-02 Thread Ivo Karabojkov
I had the same problem. It occurs when a virtual machine has bridged adapter and VirtualBox is compiled without VIMAGE support on FreeBSD 12.0. More details you can find here: https://forums.freebsd.org/threads/virtualbox-5-2-22-causes-kernel-panic-with-bridged-adapter.68787/#post-411096 On