Bug 233043 - emulators/virtualbox-ose results in FreeBSD virtual machines that quickly crash under load
Summary: emulators/virtualbox-ose results in FreeBSD virtual machines that quickly cra...
Status: Closed Unable to Reproduce
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: vbox
Depends on:
Reported: 2018-11-06 21:34 UTC by Dennis Clarke
Modified: 2019-07-16 11:16 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (vbox)


Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Clarke 2018-11-06 21:34:26 UTC
I have been working with a small team testing VirtualBox on FreeBSD 11.2 as
well as the 12.0beta3 and in both cases we see curious problems. In the case
of vbox on 11.2 we can create a FreeBSD 11.2 virtual guest and then even 
install the extension pack from the pkg repo.  However any real cpu load 
will result in the virtual machine to crash for reasons unknown. We tested
this with some trivial scp of a set of 1GB files and within 60 secs the 
virtual machine would crash. 

In the case of 12.0b3 we used an ovf export from the 11.2 system and the 
import process went smoothly. The vnc connection will not work at all so
there is no way to "see" a virtual machine console. Regardless we could
boot the virtual machine and try the same sort of tests only to get the
same result : a FreeBSD 11.2 virtual machine crashes within 60 to 90 secs
of any cpu load. 

The hardware is fairly top of the line Xeon based server hardware with 
Adaptec(MicroSemi) 8000 series SAS controllers and 128G of memory on
the host systems. No amount of tweaking of the virtual machine conf 
would bring stability. 

Not sure how to proceed but there is a multitude of bugs here.
Comment 1 Steve Wills freebsd_committer 2018-11-07 19:19:54 UTC
(In reply to Dennis Clarke from comment #0)
Did you tweak the AIO options? See the pkg-message for vbox:


Also, you should check system logs and vbox logs in the virtual machine dirs. If you can, post the vbox logs.
Comment 2 Dennis Clarke 2019-07-16 11:16:51 UTC
I want to close this as "can not reproduce" in a reliable manner.