On Thu, Apr 03, 2014 at 09:47:02AM +0200, Torbjorn Granlund wrote: > Glen Barber <g...@freebsd.org> writes: > > It is not a doc problem. > > The issue is specific to certain hardware configurations, and unless > anyone has made any breakthroughs that I am unaware of, the cause is > still unknown. > > It happens on: > > AMD piledriver running Linux+KVM > AMD piledriver running Linux+Xen > Intel Nehalem running NetBSD+Xen > Intel Sandybridge running NetBSD+Xen > Intel Haswell running NetBSD+Xen > AMD K10 Barcelona running NetBSD+Xen > AMD Bulldozer running NetBSD+Xen >
We need more specifics. > I've seen the laughable claim that this is a "bug in Virtualbox", and now > the major downplay at http://www.freebsd.org/releases/10.0R/errata.html, > where this is a minor hardware specific problem. > > I have not found one piece of PC hardware where it does not happen under > virtualisation. Please let me know some configuration where FreeBSD/i386 > works under a type 1 virtualiser? Perhaps Bhyve is FreeBSD-compatible? > Does not happen on my VirtualBox host. Glen
pgp_Ld3672Hdp.pgp
Description: PGP signature
