From owner-freebsd-emulation@freebsd.org Mon Dec 24 00:50:18 2018 Return-Path: Delivered-To: freebsd-emulation@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85CFF1351261 for ; Mon, 24 Dec 2018 00:50:18 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DFAF096BB1 for ; Mon, 24 Dec 2018 00:50:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id A32BE135125D; Mon, 24 Dec 2018 00:50:17 +0000 (UTC) Delivered-To: emulation@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DDD3135125A for ; Mon, 24 Dec 2018 00:50:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0FC0D96BAD for ; Mon, 24 Dec 2018 00:50:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x336.google.com with SMTP id t5so9866043otk.1 for ; Sun, 23 Dec 2018 16:50:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=l0w1A2inUR47C67ldpV/jtcGUW87QzEQoloYooBE+So=; b=CcwIFtzSR6gyDU2rEn7ai/NSGXyZrK4ghSbW0DmmdxjRPoxtASYaNss+SBZltiNv8y zbKuobEL9HQwykvbwoTgVp5g0VeRN/sECaaUK33VEgVkd2vc+osjbCmwh6aukO8UC9vv 9l5ty/AwMWP7EBE1VbauQWkWyhLh/MVIf/RL2jzffBrpuLAT3c+iouVGogoz0kZ19lwv 4hTMnkD+Wgy8IXfB19vNzPlsoskt033aURA4evxdpvXAa28Cw03fZGc1o5KIcMrAxpUO F5b/6ziBu2I0UOXqA5vTnc2tpt7DmqSgkWKeyB7nfwwXjXZQFzO0AJHfGM1PlUycnGJ5 iheA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=l0w1A2inUR47C67ldpV/jtcGUW87QzEQoloYooBE+So=; b=uHccVvJlTrqN55ZDcc3eky3BJuaqlRivMT4+veMPIIutMeu4xtJZ38vRy4IS9K3rnH K0XnIap6E1vDdhw7TdndByuxpK39YguJ4RCUlInamOO74X+cEiFRa9VmQnU2ho6Lu+/o BU57aK3S2SXzidNEZV/fgCW92f8R3JSO40r3m2hKLdwvXaYeYdLc4KvhI1XvG1c1WRAu CoNu0KCPs6KEN1aWpiOPJuvZWBN+2ISITXjTxs1SRj7QRw/O22idLxbvL5EQwqLCHcYN 1UJht04N4M4RZcdf0liVtalszWPdLud/vcheM65Mc/R6unqk3mv0853bZeknhGvOus/B t4Ow== X-Gm-Message-State: AJcUukeqfm3jVYYjDrgrLIUB7ArShEiJkapjXfp2oFvvWhPjyxsc5p7T N1qVCcAQkiXbgTJRcICN2dqUtBk5CHdbAQqUfdHUhwZ+ X-Google-Smtp-Source: ALg8bN6Efb+WYglUBLueC0KuIoIOZ6I/ykbz0vC+enIs5eOMBEj2c1g1lig1mpOC1o2UKKkZT1RPGBK2lqcXfrVCxAE= X-Received: by 2002:a9d:4f0c:: with SMTP id d12mr7864281otl.302.1545612615980; Sun, 23 Dec 2018 16:50:15 -0800 (PST) MIME-Version: 1.0 References: <401db2b8-9831-7419-a675-357e41bf24f9@hedeland.org> <24b03c02-d7d0-6344-c26c-8e6a5eadc179@hedeland.org> In-Reply-To: <24b03c02-d7d0-6344-c26c-8e6a5eadc179@hedeland.org> From: Kevin Oberman Date: Sun, 23 Dec 2018 16:49:59 -0800 Message-ID: Subject: Re: Instant crash starting VBox on 12.0-Stable To: Per Hedeland Cc: "freebsd-emulation@freebsd.org" X-Rspamd-Queue-Id: 0FC0D96BAD X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.970,0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 24 Dec 2018 00:50:18 -0000 On Sun, Dec 23, 2018 at 2:21 AM Per Hedeland wrote: > On 2018-12-23 06:13, Kevin Oberman wrote: > > On Sat, Dec 22, 2018 at 3:58 PM Per Hedeland per@hedeland.org>> wrote: > > > > On 2018-12-22 19:19, Kevin Oberman wrote: > > > > > > Can anyone confirm running VirtualBox on head after 11.0-Release? > > > > Apparently you meant to ask "after 12.0-RELEASE", though I'm not sure > > about the "after" - anyway *on* 12.0-RELEASE, I'm running > > virtualbox-ose-5.2.18_1 (from package) with > > virtualbox-ose-kmod-5.2.22_1 (from port) without problems. Pretty > > light usage though, a single VM running Linux, started "directly" > with > > "VirtualBox --startvm xxx" and only access via ssh. Starting the > > "manager application" i.e. plain "VirtualBox", works fine too, > though. > > > > But, I'm not loading any vboxnet* modules (seems to be more than one > > these days), only vboxdrv - and that via kld_list in rc.conf, i.e. I > > have no vbox* variables set there. After fighting with the networking > > setup (in more complex cases, that I don't currently use) with first > > vmware and then qemu I decided to do as little as possible of that > > with VirtualBox itself - only bridge to a tapN device, and do the > rest > > ("actual" bridging/routing) with the standard FreeBSD functionality. > > > > --Per Hedeland > > > > > > No, I actually meant "be4fore", but I guess it depends on your point of > view.. The issue was first reported on RC2, and I have now tested to before > the branch of 12 from head. I am about to test on > > head from August. It has worked on 11.2 all the way through Dec. 17, so > it is something that changed some time ago. Your experience tells me that, > as I had suspected, that the issue is with the > > network module which you do not use. So I am just hoping that someone > who was testing head and used VirtualBox with networking. > > Well, I do use "VirtualBox with networking" - as I wrote, bridged to a > tapN device, which doesn't require the vboxnet* modules. (I then, with > a bit of overkill for this setup, have created a standard FreeBSD > "bridge" interface to which I "addm" both the tapN (via a devd action) > and my physical ethernet interface.) I am not aware of any > functionality that the "builtin" VirtualBox networking provides that I > can't achieve without it. But of course if you are specifically > interested in using it, I don't have any relevant info. > > --Per > > > Thanks for the report. It certainly help a bit. Now to boot the August > 2018 kernel and see what happens. > Problem resolved. Turns out that VIMAGE is now required for 12.0. If you install the package, it is built with VIMAGE, but, if you build the port and had the old default , it didn't change and you got no indication that the default has changed. The default was changed 4 days after head made VIMAGE the default, so it looks like having VIMAGE selected when the kernel is buiit without it is not an issue. It works with VIMAGE detected on 11.2 where the kernel does not default to VIMAGE. It looks like the appropriate choice is to eliminate the option if there is no reason for it. Thanks to Ivo Karabojkov for reporting the solution! -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683