Date: Tue, 08 Jun 2010 09:44:42 +0900 From: Daichi GOTO <daichi@freebsd.org> To: freebsd-emulation@freebsd.org Subject: Re: VirtualBox 3.2.2 on -current Message-ID: <4C0D927A.7060700@freebsd.org> In-Reply-To: <4C07FCC4.7010901@protected-networks.net> References: <4C07FCC4.7010901@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I rolled back my current system to r207841(900011) and checked
follow guest os with VirtualBox 3.2.2.
GuestOS:
Ubuntu 10.04 (64bit)
Windows 7 (64bit)
Windows Vista (64bit)
Windows XP SP3 (32bit)
Windows Server 2008 (64bit)
sysctl kern.osreldate
kern.osreldate: 900011
uname -a
FreeBSD parancell.ongs.co.jp 9.0-CURRENT FreeBSD 9.0-CURRENT #0
r207841: Tue Jun 8 07:03:35 JST 2010
root@parancell.ongs.co.jp:/usr/obj/usr/src/sys/PARANCELL amd64
It looks working well. No memory leaks. Thanks vbox team!
addition...
It looks like that nvidia driver cannot run on fresh current
system, hm? Does anyone use nvidia driver on fresh current
kernel?
On 2010/06/04 04:04, Michael Butler wrote:
> Two patches are required to get VirtualBox 3.2.2 to compile on -current
> SVN r208788 (and, likely, before).
>
> One has to do with the introduction of memchr() to the kernel include
> files and the other is a (superfluous) include file issue which causes
> all manner of QT-related type problems.
>
> Unofficial fixes for both attached,
>
> imb
--
Daichi GOTO
81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp
LinkedIn: http://linkedin.com/in/daichigoto
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C0D927A.7060700>