From nobody Wed Nov 9 20:53:59 2022 X-Original-To: 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 4N6xz86rg3z4XPQy for ; Wed, 9 Nov 2022 20:54:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (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 4N6xz84vfNz4CYT for ; Wed, 9 Nov 2022 20:54:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62e.google.com with SMTP id q9so73634ejd.0 for ; Wed, 09 Nov 2022 12:54:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=jLlHNwUfPkmnxSuv8+MVAk+F+oi1fJdnTkJm/Qi58Ss=; b=XFgUw6K2kwiWOuAI7u9V/97VtKuNvdOTkBjB7arL2/dBh1OOSl/HKeWHTJo4tnWwJq Gw6WDPPkUbIP7+E6RVN7+em9hlUjnWYX80MDw4EDhVBqsQWgr2GxsKwHoY8o/q+nrIdd oc5XObVFGbnbcWRBns/c0Nw0k0FhNhq3QKx8bIr6zv+thrkp8j4Xx1fYPYHYP8qUyiBe CxTtzvoHleQh9UiRlc4CTe2UBrMmaMC26wrSa70pG8wJduGOXMAyvb78B/VDc/kNKSG4 Y9m3nEks+jjlW3izXkTXpMOVrQ8AxxKIoc5h6RzK9DZ+xst6vP/IwAokN5E3dZmi3Yjz DzHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=jLlHNwUfPkmnxSuv8+MVAk+F+oi1fJdnTkJm/Qi58Ss=; b=v5U3/kV71MAjcNL5mhYhuwBtNWiF5wXLdVrZcatcN28RhccyEgYUFHnFICazEFmbD6 lrNM0z9/e+tmzqEUA+ynTLL2vs57jSuNhTLdqU2I9UWYhacb6gb3NEHrhf3ga4OU95IW SZaDvaWqlyeXSlyw9Wd+vkSgCb9oQ3haf2KK+rmPN8T6iMSbrRnhi8haEatETJ1kHLey U1mrbWh/ntQPxKMI4xMJq7bXTqrNuXXUt4//Uau8nTfUz/kFZjxmEcwkunCqTASMT0eY KBBImVaVIoZSTL0aIoQHSkY6VVSUW6/hkcYoSRrGFt5cuoX+/xxsxxvvVFDufNo9fi1H HjIQ== X-Gm-Message-State: ACrzQf1ImPkfEc0/ALoaOtOmJqTnhTLl2EeD4w2S0np9rslhPWwStpNz 35RoBcBf1ZkVvmWRCMz2Z05LsjDwKjPATrob2cLg2g== X-Google-Smtp-Source: AMsMyM6jjzLwcBk47VcOYeEhqKxKhNmyuOnJhk37KkUVipW0sFuz2hqPIDj5rLuAUjwsmDQvfm8wvwPI9l/u+SPqZJI= X-Received: by 2002:a17:906:3b17:b0:7ad:b645:9e3e with SMTP id g23-20020a1709063b1700b007adb6459e3emr53927931ejf.140.1668027250632; Wed, 09 Nov 2022 12:54:10 -0800 (PST) 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: <202211070339.2A73dJlO027991@gitrepo.freebsd.org> <20221107121514.Horde.nulS9Wg1s3yzAsXXkuJRBa9@webmail.leidinger.net> <20221108105053.Horde.eqgFiBJe2ngGAj6BkXcv5-Z@webmail.leidinger.net> <20221109134610.Horde.JB7ibQTWprHbmIUfhg7JY7f@webmail.leidinger.net> <20221109204736.Horde.u-t3-sSaTA023DA3Tib0oV4@webmail.leidinger.net> In-Reply-To: <20221109204736.Horde.u-t3-sSaTA023DA3Tib0oV4@webmail.leidinger.net> From: Warner Losh Date: Wed, 9 Nov 2022 13:53:59 -0700 Message-ID: Subject: Re: changes to the zfs boot (was: Re: git: 72a1cb05cd23 - main - rc(8): Add a zpoolupgrade rc.d script) To: Alexander Leidinger Cc: marklmi@yahoo.com, tsoome@freebsd.org, Li-Wen Hsu , current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c008da05ed0fdb68" X-Rspamd-Queue-Id: 4N6xz84vfNz4CYT 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-ThisMailContainsUnwantedMimeParts: N --000000000000c008da05ed0fdb68 Content-Type: text/plain; charset="UTF-8" On Wed, Nov 9, 2022 at 12:47 PM Alexander Leidinger wrote: > Quoting Warner Losh (from Wed, 9 Nov 2022 08:54:33 > -0700): > > > as well. I'd settle for a good script that could be run as root (better > > would be not as root) that would take a filesystem that was created > > by makefs -t zfs and turn on these features after an zpool upgrade. > > I have the vague outlines of a test suite for the boot loader that I > > could see about integrating something like that into, but most of my > > time these days is chasing after 'the last bug' in some kboot stuff I'm > > working on (which includes issues with our ZFS in the boot loader > > integration). > > How would you test a given image? bhyve/qemu/...? > I have a script that creates a number of image files and a number of qemu scripts that look like the following: /home/imp/git/qemu/00-build/qemu-system-aarch64 -nographic -machine virt,gic-version=3 -m 512M -smp 4 \ -cpu cortex-a57 \ -drive file=/home/imp/stand-test-root/images/arm64-aarch64/linuxboot-arm64-aarch64-zfs.img,if=none,id=drive0,cache=writeback \ -device virtio-blk,drive=drive0,bootindex=0 \ -drive file=/home/imp/stand-test-root/bios/edk2-arm64-aarch64-code.fd,format=raw,if=pflash \ -drive file=/home/imp/stand-test-root/bios/edk2-arm64-aarch64-vars.fd,format=raw,if=pflash \ -monitor telnet::4444,server,nowait \ -serial stdio $* There's a list of these files that's generated and looks to see if it gets to the 'success' echo in the minimal root I have for them. Warner --000000000000c008da05ed0fdb68 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Nov 9, 2022 at 12:47 PM Alexa= nder Leidinger <Alexander@lei= dinger.net> wrote:
Quoting Warner Losh <imp@bsdimp.com> (from Wed, 9 Nov 2022 08:54:33 -0700):
> as well. I'd settle for a good script that could be run as root (b= etter
> would be not as root) that would take a filesystem that was created > by makefs -t zfs and turn on these features after an zpool upgrade. > I have the vague outlines of a test suite for the boot loader that I > could see about integrating something like that into, but most of my > time these days is chasing after 'the last bug' in some kboot = stuff I'm
> working on (which includes issues with our ZFS in the boot loader
> integration).

How would you test a given image? bhyve/qemu/...?

=
I have a script that creates a number of image files and a numbe= r of qemu scripts that look
like the following:

/home/imp/git/qemu/00-build/qemu-system-aarch64 -nographic -machine virt= ,gic-version=3D3 -m 512M -smp 4 \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -cpu corte= x-a57 \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -drive file=3D/home/imp/stand-test-r= oot/images/arm64-aarch64/linuxboot-arm64-aarch64-zfs.img,if=3Dnone,id=3Ddri= ve0,cache=3Dwriteback \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -device virtio-blk,d= rive=3Ddrive0,bootindex=3D0 \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -drive file=3D= /home/imp/stand-test-root/bios/edk2-arm64-aarch64-code.fd,format=3Draw,if= =3Dpflash \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -drive file=3D/home/imp/stand-te= st-root/bios/edk2-arm64-aarch64-vars.fd,format=3Draw,if=3Dpflash \
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 -monitor telnet::4444,server,nowait \
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 -serial stdio $*

There= 9;s a list of these files that's generated and looks to see if it gets = to the 'success' echo in the minimal root I have for them.

Warner
--000000000000c008da05ed0fdb68--