From owner-freebsd-emulation@FreeBSD.ORG Wed May 28 06:51:22 2014 Return-Path: Delivered-To: vbox@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 021998E2 for ; Wed, 28 May 2014 06:51:22 +0000 (UTC) Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B96162258 for ; Wed, 28 May 2014 06:51:21 +0000 (UTC) Received: by mail-oa0-f49.google.com with SMTP id eb12so10654079oac.22 for ; Tue, 27 May 2014 23:51:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=74dGZHGvLdfC5zmKcJBqf7FeuJvV2FFTWZbt4eJzVfI=; b=HFSZSUyvULojaIJiNhowS625F4BRqc724TMXWd1wgJdmhWtRVqOCVK7O+ZBbxxFw46 vjBwftAumYoyjOElK5pRbvY9nvhhdbtn5+NCPcSF4k/My0Sk+dvaTdLpaTqtNjwHV51E V+u6+58x1L2suytZH8aiMSSHg7KB2vyWEKqlE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=74dGZHGvLdfC5zmKcJBqf7FeuJvV2FFTWZbt4eJzVfI=; b=M/EwTV0kTUJ9+08A3Ak5dJgtUA0NS6w+ws+Bjmq/kQ31v0Hme6szYe7XasoflfA58n wJFiaPpGi6kSlFsrXRcDyTX+z55H+iJAtsq0AZ2CkYvDBxycOBXKl2Gx77X7YZ1Dki2+ EejyMuFjhbaNPoMYFTRcCItsj0S9WVsCBxUjIVlze9DVFcWj9wZHX4gPEi39aKY0GGUp 92Rmtcq5H7xgYwmOKhk0pe40BeY3TR1QtnpfluUOwOOupbz1sp5JTpARXA9Ei8GdM7RD u3yUsbNYnS/2/4kmFroRqGHlrUM94zwFaoRZCegMnwQ51pdIRgcAC6G+AH1pRr+g2Dox 7QFA== X-Gm-Message-State: ALoCoQnNDnGzvegQrKF7tGoMknacCVWE/bDiKdTyMp9Q/Ctfu9RiHH7RIgnQM89sVKd3AElv0yaz MIME-Version: 1.0 X-Received: by 10.60.37.99 with SMTP id x3mr38815016oej.65.1401259880812; Tue, 27 May 2014 23:51:20 -0700 (PDT) Received: by 10.76.154.136 with HTTP; Tue, 27 May 2014 23:51:20 -0700 (PDT) X-Originating-IP: [2001:470:1f15:673::1000] In-Reply-To: References: <861tvh62ni.fsf@nine.des.no> Date: Wed, 28 May 2014 08:51:20 +0200 Message-ID: Subject: Re: virtualbox-ose-kmod rc scripts From: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= To: Warren Block Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 28 May 2014 11:40:20 +0000 Cc: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , vbox@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.18 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: Wed, 28 May 2014 06:51:22 -0000 On Mon, May 26, 2014 at 4:25 PM, Warren Block wrote: > On Mon, 26 May 2014, Bernhard Fr=C3=B6hlich wrote: > >> Am 26.05.2014 01:49 schrieb "Dag-Erling Sm=C3=B8rgrav" : >>> >>> >>> First of all, why is there a vboxnet rc script but not a vboxdrv rc >>> script? >>> >>> Second, there is already support in /etc/rc.subr for checking whether a >>> module is loaded, and loading it if it isn't. Search for load_kld. >>> There is no unload_kld, but IMHO you can just "kldunload" blindly. >> >> >> The vboxdrv module needs to be loaded via loader.conf or it can cause >> kernel panics. There are also some features that don't work properly if = I >> remember correctly because of the startup order of startscripts so we >> can't >> use a rc script. > > > Does it still do that? Or maybe only on i386? I've been reloading it af= ter > a rebuild for a long time now without problems, but maybe that was becaus= e > it was on amd64 or just luck. It's not quite as easy as that. We tried it two times already (back in the old vbox 3.x days and last time around 4.0 I guess) and with both tests we ran into = panic reports from various people that we could not reproduce on any of our machi= nes. I don't remember the exact details about it anymore but there was another i= ssue with network interfaces coming up before vboxdrv and it was unable to see/u= se the interface or so. So it might be time to give it another try and see if we still run into that issues. --=20 Bernhard Fr=C3=B6hlich http://www.bluelife.at/