From owner-freebsd-current@freebsd.org Sun Aug 19 16:06:06 2018 Return-Path: Delivered-To: freebsd-current@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 8BFF3106E19A for ; Sun, 19 Aug 2018 16:06:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 208D67D29F for ; Sun, 19 Aug 2018 16:06:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id y12-v6so932374ioj.13 for ; Sun, 19 Aug 2018 09:06:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=xetQqMp/mrJ2E95wWjJHzH3DqHq+jTK/6JtDsQRYLwQ=; b=QJKEcCx07d2mXIg1w/zFkbGfFrWbJmWLlXUAT48MiBPSHc4SteVjTycybWrPV1T6NA 98sMRKxa0WQC+nOzSvU6tF9E9VJ6gmqGiKpsaqWeOPpfpmHUnxuOSiOB8hhoTSFr+NBU PAllKxgMLXbpyaEZgxdqZI9q3WtacO5cQ+cOktC1zk5qqF2M+P+GPsC3Ev90DBD4iHOu OxmO1ZUmvKImq6kjz475edsIOb8+ei0rAhSXfJaEUDJ+yWG0ec8RItxj+GWqo76tSpBz vWSI03j1EKv7atDI7j7kHvPJvJrwmkYke3MgVxRsOmFSq7kmvLhRywWNRpEJF6+M1rWW Lphw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=xetQqMp/mrJ2E95wWjJHzH3DqHq+jTK/6JtDsQRYLwQ=; b=NLzu7GhITeG9csLTamOHd8JSfiGa59OoeZGkJFD4BQXlsHHEgm9anZd3kxuhzqhvUn +oLGVamHcmF5ICjiCmnd01bo+2GeLED0tCTrdpae4jQ32On4mqAw3iZhhMJA9pndKfc+ 4X0fuqr+zeOiBLIOJBtdWqpT+kGonGwS//DQg+sm8Bx4NY4wCIbYH4J9yJiiHrIvHZBO ULhquAYcu7He3joO6X6Ajp0NUTHdp3Jqsf7EJAp3Sn4sLFac+iE7rBGYE+r8IaO0zz+k 11zWPHDDaUwGGBtMnqTeYiKqGKBC/8pUxnwn+DndTuyvmpQpblRCtziBxKlqevjX7tVL o+/g== X-Gm-Message-State: AOUpUlGHqr272E8LWG5HQPVYsl0PWaC/FdEYY/OIt3xCohApnB/SYjys 9FThP7U/VwdpRKWBKOWn19n+7zSrOGDv77o2EgFV0w== X-Google-Smtp-Source: AA+uWPxZGfbtjfhe07J856UbdL73hDPDGhR8g1wUkjrAyj8CzB+YJbUDZ317NCGI1dg8KShzxvnGV0wFDP2afTO8ZoY= X-Received: by 2002:a6b:3902:: with SMTP id g2-v6mr35862140ioa.168.1534694765296; Sun, 19 Aug 2018 09:06:05 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:2806:0:0:0:0:0 with HTTP; Sun, 19 Aug 2018 09:06:04 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180819160503.nlns5pz6rnt7afzo@ler-imac.local> References: <20180819152253.bbcrefdvynl7y5ka@ler-imac.local> <20180819153526.7ruovrpmdsimkmfj@ler-imac.local> <20180819160503.nlns5pz6rnt7afzo@ler-imac.local> From: Warner Losh Date: Sun, 19 Aug 2018 10:06:04 -0600 X-Google-Sender-Auth: XQlUPbElWb6Iy6rrmKUEzQwDk3M Message-ID: Subject: Re: LUA loader: bhyve now doesn't? To: Joe Maloney , Warner Losh , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2018 16:06:06 -0000 On Sun, Aug 19, 2018 at 10:05 AM, Larry Rosenman wrote: > On Sun, Aug 19, 2018 at 11:54:51AM -0400, Joe Maloney wrote: > > I ran into this as well months ago. To workaround it I extracted > > userboot.so for the VM's, and launched bhyve with the alternate > > userboot.so. You can use a flag as described in the manpage to start > > userboot.so from an alternate location. > > > > https://www.freebsd.org/cgi/man.cgi?query=bhyveload&sektion=8 > > > > Also support was recently added for vm-bhyve to specify alternate > > userboot.so location for one that is compatible with 4th. You just need > to > > extract that somewhere onto the host, and specify it to load when > starting > > the VM. > > > > https://github.com/churchers/vm-bhyve/blob/ > d4532f6da3e155a4430acbb9138e59c0d5abfc39/sample-templates/config.sample > > > > Alternatively you could just use UEFI, or UEFI-CSM firmware. > Ok, so pulling /boot/userboot.so from my non-upgraded 12 system and > putting it in /boot/userboot-4th.so on the host allows the VM's to boot > after changing the config files to point bhyveload_loader to it (yes, > I'm using vm-bhyve). > > This default change is a POLA violation for bhyve/vm-bhyve users. OK. We're on it. Thanks for the heads up. We were unaware of the issue when we flipped the switch. Warner