Date: Wed, 9 Nov 2022 13:53:59 -0700 From: Warner Losh <imp@bsdimp.com> To: Alexander Leidinger <Alexander@leidinger.net> Cc: marklmi@yahoo.com, tsoome@freebsd.org, Li-Wen Hsu <lwhsu@freebsd.org>, current@freebsd.org Subject: Re: changes to the zfs boot (was: Re: git: 72a1cb05cd23 - main - rc(8): Add a zpoolupgrade rc.d script) Message-ID: <CANCZdfpubReX8mK5wFDRnv6zOWPHgSeGZ=uy%2B3j61Z1ehbP1sw@mail.gmail.com> In-Reply-To: <20221109204736.Horde.u-t3-sSaTA023DA3Tib0oV4@webmail.leidinger.net> References: <202211070339.2A73dJlO027991@gitrepo.freebsd.org> <20221107121514.Horde.nulS9Wg1s3yzAsXXkuJRBa9@webmail.leidinger.net> <CANCZdfrdc%2BDbv6sDyDLcWNpXnWScEmpUsGu3q8%2BMbZRjDS8eig@mail.gmail.com> <20221108105053.Horde.eqgFiBJe2ngGAj6BkXcv5-Z@webmail.leidinger.net> <20221109134610.Horde.JB7ibQTWprHbmIUfhg7JY7f@webmail.leidinger.net> <CANCZdfptmipq%2BsS0AQ1%2B7EmLT-7YdKv8s%2BnCV7ON1Qy6-C6N9A@mail.gmail.com> <20221109204736.Horde.u-t3-sSaTA023DA3Tib0oV4@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Wed, Nov 9, 2022 at 12:47 PM Alexander Leidinger <Alexander@leidinger.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 (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
[-- Attachment #2 --]
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 9, 2022 at 12:47 PM Alexander Leidinger <<a href="mailto:Alexander@leidinger.net">Alexander@leidinger.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Quoting Warner Losh <<a href="mailto:imp@bsdimp.com" target="_blank">imp@bsdimp.com</a>> (from Wed, 9 Nov 2022 08:54:33 -0700):<br>
<br>
> as well. I'd settle for a good script that could be run as root (better<br>
> would be not as root) that would take a filesystem that was created<br>
> by makefs -t zfs and turn on these features after an zpool upgrade.<br>
> I have the vague outlines of a test suite for the boot loader that I<br>
> could see about integrating something like that into, but most of my<br>
> time these days is chasing after 'the last bug' in some kboot stuff I'm<br>
> working on (which includes issues with our ZFS in the boot loader<br>
> integration).<br>
<br>
How would you test a given image? bhyve/qemu/...?<br></blockquote><div><br></div><div>I have a script that creates a number of image files and a number of qemu scripts that look</div><div>like the following:</div><div><br></div>/home/imp/git/qemu/00-build/qemu-system-aarch64 -nographic -machine virt,gic-version=3 -m 512M -smp 4 \<br> -cpu cortex-a57 \<br> -drive file=/home/imp/stand-test-root/images/arm64-aarch64/linuxboot-arm64-aarch64-zfs.img,if=none,id=drive0,cache=writeback \<br> -device virtio-blk,drive=drive0,bootindex=0 \<br> -drive file=/home/imp/stand-test-root/bios/edk2-arm64-aarch64-code.fd,format=raw,if=pflash \<br> -drive file=/home/imp/stand-test-root/bios/edk2-arm64-aarch64-vars.fd,format=raw,if=pflash \<br> -monitor telnet::4444,server,nowait \<br><div> -serial stdio $*</div><div><br></div><div>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.</div><div><br></div><div>Warner</div></div></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpubReX8mK5wFDRnv6zOWPHgSeGZ=uy%2B3j61Z1ehbP1sw>