From owner-freebsd-emulation@FreeBSD.ORG Tue Dec 22 22:40:34 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 DF66C106566C; Tue, 22 Dec 2009 22:40:34 +0000 (UTC) (envelope-from paul@fletchermoorland.co.uk) Received: from hydra.fletchermoorland.co.uk (hydra.fletchermoorland.co.uk [78.33.209.59]) by mx1.freebsd.org (Postfix) with ESMTP id 4E6498FC17; Tue, 22 Dec 2009 22:40:33 +0000 (UTC) Received: from demophon.fletchermoorland.co.uk (demophon.fletchermoorland.co.uk [192.168.0.154]) by hydra.fletchermoorland.co.uk (8.14.3/8.14.3) with ESMTP id nBMMJYaN091648; Tue, 22 Dec 2009 22:19:35 GMT (envelope-from paul@fletchermoorland.co.uk) Message-ID: <4B314586.1030301@fletchermoorland.co.uk> Date: Tue, 22 Dec 2009 22:17:42 +0000 From: Paul Wootton User-Agent: Thunderbird 2.0.0.23 (X11/20091217) MIME-Version: 1.0 To: dougb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=10.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on hydra.fletchermoorland.co.uk Cc: freebsd-emulation@freebsd.org Subject: VirtualBox error if kernel module loader in /boot/loader.conf (WAS Re: Loading kernel modules for virtualbox via script) 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: Tue, 22 Dec 2009 22:40:35 -0000 Doug Barton wrote: > Leslie Jensen wrote: > >> On 2009-12-22 21:22, Doug Barton wrote: >> >>> The appropriate way to do this is to add them to /boot/loader.conf, >>> like this: >>> >>> vboxdrv_load="yes" >>> vboxnetflt_load="yes" >>> vboxnetadp_load="yes" >> Thanks for your answer. >> >> I did test to load the modules as you suggest. They do load but >> virtualbox produces an error when starting a virtual machine. >> > > If what you're saying is that you tried loading the modules in > /boot/loader.conf and that produced an error, then you need to start a > NEW thread on this list and describe what you did, and what the > results are in detail. This method worked fine for me in 9-current, so > if it's not working for you then we need to find out why. > > >> I've tried to load vboxdrv and vboxnetflt via loader.conf and then load >> vboxnetadp manually before starting virtualbox. That also produces the >> error when starting a VM. >> I too get an error on starting a VM if I try to load the modules from /boot/loader.conf. For me, the loading of vboxnetflt does not seem to work correctly. I dont load vboxnetadp, so I cant comment on that. /boot/loader.conf zfs_load="YES" vboxdrv_load="YES" vboxnetflt_load="YES" If I try to start a VM that is using the "Bridged Ethernet" adapter, the error I get is "Failed to start the virtual machine Win Vista Failed to open/create the internal network 'HostInterfaceNetworking-re0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND). Unknown eror creating VM (VERR_SUPDRV_COMPONENT_NOT_FOUND). Details Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}" I know the module got loaded. [paul@demophon /usr/home/paul]$ kldstat Id Refs Address Size Name 1 25 0xffffffff80100000 e7c540 kernel 2 1 0xffffffff80f7d000 18a788 zfs.ko 3 2 0xffffffff81108000 3778 opensolaris.ko 4 2 0xffffffff8110d000 41e88 vboxdrv.ko 5 1 0xffffffff8114f000 6960 vboxnetflt.ko 6 1 0xffffffff81223000 38fc linprocfs.ko 7 1 0xffffffff81227000 1bcc4 linux.ko If I then do a kldunload vboxnetflt followed by kldload vboxnetflt, I can now start and stop my VMs to my heart's content. Im using 9 CURRENT and I only started using /boot/loader.conf for the vbox modules about a month back. The vboxnetflt module has never worked correctly for me this way Paul