Our organization is running FreeBSD 13 and 14 as guests VM's both under bhyve and also AWS. Despite lots of trying, it seems like detecting expanded drives (nvme emulation) requires a reboot. Am I missing something?
I recently expanded the drive of a Ubuntu Linux guest machine, where FreeBSD was the host using bhyve. I simply expanded the host's drive file using
It'd sure be swell if FreeBSD as guest and host (using bhyve) could support expansion in this same elegant manner. I found an older post on stackexchange that suggested there is a disconnect between the nvmecontrol and gpart layer, but I'm not sure if that would still apply.
I've already experimented a good deal with forced rescan of devices inside the guest,
I recently expanded the drive of a Ubuntu Linux guest machine, where FreeBSD was the host using bhyve. I simply expanded the host's drive file using
truncate. Immediately inside the guest, the larger disk could be seen with lsblk, and then utilized with zpool online.It'd sure be swell if FreeBSD as guest and host (using bhyve) could support expansion in this same elegant manner. I found an older post on stackexchange that suggested there is a disconnect between the nvmecontrol and gpart layer, but I'm not sure if that would still apply.
I've already experimented a good deal with forced rescan of devices inside the guest,
devctl etc., with no luck. It seems like it could be within reach. nvmecontrol devlist shows the new size, but I haven't been able to grow into it without a reboot.