From nobody Thu Oct 26 18:39:02 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SGZMS6WL4z4y8Dg for ; Thu, 26 Oct 2023 18:39:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SGZMS4XvGz3HqF for ; Thu, 26 Oct 2023 18:39:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52e.google.com with SMTP id 4fb4d7f45d1cf-5409bc907edso1898092a12.0 for ; Thu, 26 Oct 2023 11:39:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1698345554; x=1698950354; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=y+QFnorjO6TXIfKvr0Sd6pJQ3cUvc9Abw7Yfq7vcV1s=; b=YaRn/c+WIGFQwsJ1q2BpfvEk0cDDidnjS031I5lPo3vMZZ2Q3m3YIcD+WIvFI5+9DJ GE2OYg/Ltw4QtdAXrLJzgAlSWdYubeCLOAeSKFRzGEKVH4qSAmsl4rH2I3RhGZzC8SKD f5ZYpANYdIg9uRSU2JR28MLkMpWIWsH0aFI55x37FYInORLaa6MijDmX4a0ZD0KaB9PU yy+8tsBkKvYixmrY/G/isAWcbD4faTT2C7Ek98LxRRXqW5NG+pT22bdEmokickzuRhXP 8IdjyEsHAqgeG36ZMcE0StfBHp8ffInhGHnyOzBG64+N110kewrLdw0bky1Rkpvr9xFg 53GA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698345554; x=1698950354; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=y+QFnorjO6TXIfKvr0Sd6pJQ3cUvc9Abw7Yfq7vcV1s=; b=NJBFOTOjLtjN/qFV85BAvEEF9RbdEEgkptpJXRUMxY2Q1cVr0y8vYX+ggYEMwyFLAx 9y2uwR/5qbqkk/ikHH7EPYQOGZPfW9IETjCB7dUZHCQVC1E+fXtylTKDvxWh6ckbG3ML QRfIcMDQaAG1sPrICCO53RoyYbYZB6OPt35dqOLW/Mqzqxt+HdXYAD3tgWsNGpT1/0Zc V2BAjNCWt3+MccTL1oXFGWn1Ao1mkj5twmmTZdgOqOXuAf5SVxEW93oco1+n6i7g58UV XVvI0xCSb1wNf1yo3YCUFdaHKx0y2W1jOGx518TGuL9VY1rRQ0UA033jv7NX9f74NU8G XLJg== X-Gm-Message-State: AOJu0Yy42zzXwc2VbxMpcXDA++A+PUy1Owlnm1XKUy9dtlMiNdyFdqR4 AOWOxjQJbfjv+vZzNogiLVeHDFfnu6mOGFmGPXjMvw== X-Google-Smtp-Source: AGHT+IGacc2u+H30TilTf380S1vTd9vrV8Mlt7teCCKu9TsfQdhgFtJAnhM6FYBzgigei+oKgEh9n/tRqnm1mSe8P3U= X-Received: by 2002:aa7:c309:0:b0:53d:eca8:8775 with SMTP id l9-20020aa7c309000000b0053deca88775mr505074edq.26.1698345553785; Thu, 26 Oct 2023 11:39:13 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202310250103.39P13maS040503@gndrsh.dnsmgr.net> <93ae484b-0f67-4f8b-829d-f75162afd680@FreeBSD.org> In-Reply-To: From: Warner Losh Date: Thu, 26 Oct 2023 12:39:02 -0600 Message-ID: Subject: Re: Ventoy support To: Ed Maste Cc: Kyle Evans , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000708a650608a2e320" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4SGZMS4XvGz3HqF --000000000000708a650608a2e320 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Oct 26, 2023 at 11:22=E2=80=AFAM Ed Maste wrot= e: > On Tue, 24 Oct 2023 at 21:24, Kyle Evans wrote: > > > > On 10/24/23 20:03, Rodney W. Grimes wrote: > > > > > > What "modules" are being provied by Ventoy, I do not know > > > of any FreeBSD modules being provided by Ventoy, it is an > > > EFI shim that loads the FreeBSD loader, and the loader > > > does all the work. > > > > > > Again, perhaps I do not see this as I am only using ventoy > > > in EFI mode. > > > > There's an accompanying geom module as well, source available[0] for > > every version they support (except 14.x, apparently, despite having a > > built blob in the geom_ventoy_ko dir). It's a little annoying to try > > and understand the problems they're running into from version to > > version, IMO, since they just publish the entire module again for each > > version rather than maintaining some __FreeBSD_version shims or > something. > > In particular, the kernel does not use EFI services for the root > filesystem. > I've looked to pass the root filesystem into FreeBSD via a UEFI file path, which FreeBSD has most, but not quite all, of the infrastructure to do. I've been slowly adding pieces to round this out. For simple filesystems on simple devices, it can be made to work. ZFS can be made to work too, but requires fairly different code (also, for ZFS, we can cheat and pass in a name that the boot loader and the OS share). The Ventoy stuff is interesting as well... Ed has some good ideas here and we've also done some work to have a unified .mem and .iso image as well... Though, honestly, the .iso format is getting rather long-of-toot= h and we might be better off leaving it behind like others have done. Warner --000000000000708a650608a2e320 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Oct 26, 2023 at 11:22=E2=80= =AFAM Ed Maste <emaste@freebsd.org= > wrote:
= On Tue, 24 Oct 2023 at 21:24, Kyle Evans <kevans@freebsd.org> wrote:
>
> On 10/24/23 20:03, Rodney W. Grimes wrote:
> >
> > What "modules" are being provied by Ventoy, I do not kn= ow
> > of any FreeBSD modules being provided by Ventoy, it is an
> > EFI shim that loads the FreeBSD loader, and the loader
> > does all the work.
> >
> > Again, perhaps I do not see this as I am only using ventoy
> > in EFI mode.
>
> There's an accompanying geom module as well, source available[0] f= or
> every version they support (except 14.x, apparently, despite having a<= br> > built blob in the geom_ventoy_ko dir).=C2=A0 It's a little annoyin= g to try
> and understand the problems they're running into from version to > version, IMO, since they just publish the entire module again for each=
> version rather than maintaining some __FreeBSD_version shims or someth= ing.

In particular, the kernel does not use EFI services for the root filesystem= .

I've looked to pass the root file= system into FreeBSD via a UEFI file path,
which FreeBSD has most,= but not quite all, of the infrastructure to do.
I've been sl= owly adding pieces to round this out. For simple filesystems
on s= imple devices, it can be made to work. ZFS can be made to work too,
but requires fairly different code (also, for ZFS, we can cheat and pass=
in a name that the boot loader and the OS share).

=
The Ventoy stuff is interesting as well...=C2=A0 Ed has some goo= d ideas here
and we've also done some work to have a unified = .mem and .iso image
as well... Though, honestly, the .iso format = is getting rather long-of-tooth
and we might be better off leavin= g it behind like others have done.

Warner
--000000000000708a650608a2e320--