Re: r358503 breaks reroot

From: Mateusz Guzik <mjguzik_at_gmail.com>
Date: Mon, 27 Apr 2020 12:33:58 +0200
Thanks for bisecting, I'll look into it.

On 4/27/20, Ross Gohlke <ross_at_bisd.ro> wrote:
> As of r358503, *reboot -r* no longer works for me.
> This is only tested on amd64.
>
> I produced a vanilla mini-memstick image each for r358502 and r358503.
> I booted each in bhyve in single user mode and ran *reboot -r*.
> The first works as expected, the second halts with:
>
> kern_symlink /dev -> / returns 20
>
> Images (to be deleted when this is resolved):
> * https://club.bisd.ro/site/uv/FreeBSD-13.0-CURRENT-amd64-r358502.img
> * https://club.bisd.ro/site/uv/FreeBSD-13.0-CURRENT-amd64-r358503.img
>
> SHA1 checksums (via https://club.bisd.ro/site/uvlist):
> * r358502 - c968c4a71c270561c1b0a02e2b2281cbbf8787d7
> * r358503 - b5d1abd6b3f3e009c2b54198d76d71a8640807a6
>
> External bhyve commands:
> * sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 1024M -d
> /mnt/FreeBSD-13.0-CURRENT-amd64-r358502.img reroot
> * sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 1024M -d
> /mnt/FreeBSD-13.0-CURRENT-amd64-r358503.img reroot
>
> Internal bhyve commands:
> 1. Press 2 for single user mode.
> 2. When prompted, press Return.
> 3. Issue command: reboot -r
>
> To exit the first case:
> 1. Press Return.
> 2. Select Shell.
> 3. Issue command: shutdown -p now
>
> To exit the second case, issue the following command in a second terminal:
> bhyvectl --destroy --vm=reroot
>
> Any suggested workarounds besides reverting to r358502?
>
> Any help appreciated,
> Ross
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>


-- 
Mateusz Guzik <mjguzik gmail.com>
Received on Mon Apr 27 2020 - 08:34:01 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:23 UTC