https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221275

Fabian Keil <f...@fabiankeil.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |f...@fabiankeil.de

--- Comment #1 from Fabian Keil <f...@fabiankeil.de> ---
zfsbootcfg actually checks for kenv(1) variables (which sysctl(8) doesn't
show).

Having said that, I can reproduce the problem that the variables aren't
set when running in bhyve.

They are set on all the physical systems I checked, though.

You can still set them manually with kenv(1) using the values from the
vdev label:

[fk@test-vm ~]sudo zdb -l /dev/gpt/bpool-vtbd1
[...]
    name: 'bpool'                                                               
[...]
    pool_guid: 14860026282992656750                                             
[...]
    guid: 6160965258301852628                                                   
[...]
[fk@test-vm ~]sudo kenv vfs.zfs.boot.primary_pool=14860026282992656750
vfs.zfs.boot.primary_pool="14860026282992656750"
[fk@test-vm ~]sudo kenv vfs.zfs.boot.primary_vdev=6160965258301852628
vfs.zfs.boot.primary_vdev="6160965258301852628"

At least for me this resulted in zfsbootcfg reporting success:

[fk@test-vm ~]$ sudo zfsbootcfg zfs:rpool
zfs next boot options are successfully written

As I currently don't use boot environments (not yet supported by cloudiatr),
I couldn't easily test if this has any effect in bhyve, though.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Reply via email to