From owner-freebsd-emulation@FreeBSD.ORG Sun Jul 5 17:44:07 2009 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 282BB1065670 for ; Sun, 5 Jul 2009 17:44:07 +0000 (UTC) (envelope-from rondzierwa@comcast.net) Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by mx1.freebsd.org (Postfix) with ESMTP id BCCF18FC16 for ; Sun, 5 Jul 2009 17:44:06 +0000 (UTC) (envelope-from rondzierwa@comcast.net) Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA06.westchester.pa.mail.comcast.net with comcast id CGk71c0021HzFnQ56Hk7sL; Sun, 05 Jul 2009 17:44:07 +0000 Received: from sz0128.wc.mail.comcast.net ([76.96.58.192]) by OMTA14.westchester.pa.mail.comcast.net with comcast id CHk61c00C48qnZY3aHk6dY; Sun, 05 Jul 2009 17:44:06 +0000 Date: Sun, 5 Jul 2009 17:44:06 +0000 (UTC) From: rondzierwa@comcast.net To: Dan Nelson Message-ID: <1970692187.410191246815846780.JavaMail.root@sz0128a.westchester.pa.mail.comcast.net> In-Reply-To: <10109645.410031246815787615.JavaMail.root@sz0128a.westchester.pa.mail.comcast.net> MIME-Version: 1.0 X-Originating-IP: [76.111.0.24] X-Mailer: Zimbra 5.0.12_GA_2816.RHEL5_64 (ZimbraWebClient - FF3.0 (Win)/5.0.12_GA_2816.RHEL5_64) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-emulation@freebsd.org, Gary Jennejohn Subject: Re: vbox driver X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jul 2009 17:44:07 -0000 dmesg reveals the real problem: link_elf: symbol smp_rendezvous_cpus undefined I grep'ed the kernel sources (*.c, *.s, even *.h) and found no reference of this symbol. Is my kernel too old? phoenix% uname -a FreeBSD phoenix.hsd1.md.comcast.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Mar 8 04:04:40 EDT 2009 root@phoenix.hsd1.md.comcast.net:/usr/src/sys/i386/compile/PHOENIX i386 ----- Original Message ----- From: "Dan Nelson" To: "Gary Jennejohn" Cc: rondzierwa@comcast.net, freebsd-emulation@freebsd.org Sent: Sunday, July 5, 2009 12:40:25 PM (GMT-0500) Auto-Detected Subject: Re: vbox driver In the last episode (Jul 05), Gary Jennejohn said: > On Sat, 4 Jul 2009 17:09:33 +0000 (UTC) > rondzierwa@comcast.net wrote: > > I have installed the VirtualBox port my FreeBSD 7.0 system. I had to > > csup ports and download and install the virtualbox port manually, but > > eventually everything built and installed. > > > > kldload has a problem with the vboxdrv module: > > > > phoenix# kldload /boot/modules/vboxdrv.ko > > kldload: can't load /boot/modules/vboxdrv.ko: No such file or directory > > > > the file is there, and kldconfig is set up for the /boot/modules directory: > > > > phoenix# kldconfig -r > > /boot/kernel;/boot/modules > > phoenix# ls -l /boot/modules > > total 182 > > -r-xr-xr-x 1 root wheel 185300 Jul 4 12:57 vboxdrv.ko > > > > could it be that there is no vboxdrv.ko.symbols file? all the other > > modules are in the /boot/kernel directory, and they all have .symbols > > files. > > > > This error message is confusing and doesn't necessarily really have > anything to do with vboxdrv.ko being present. kldload(2) in the kernel > can return a number of errors, but they're all hidden behind the error > message "can't load..." > > kldload(8) should probably use perror(3) so the user can see exactly > what the error returned from the kernel was. kldload did use perror; the kernel returned ENOENT - "No such file or directory". The problem is that the 92 defined errno values are not enough to describe all possible ways a syscall can fail. When loading a module, the most likely cause of ENOENT is a missing symbol preventing the linker from loading the module. The kernel will print a more verbose message to the console, so run dmesg and see what it's complaining about. -- Dan Nelson dnelson@allantgroup.com