ruby.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
If you are interested in the Ruby programming language, come join us! Tell us about yourself when signing up. If you just want to join Mastodon, another server will be a better place for you.

Administered by:

Server stats:

1.1K
active users

#bhyve

2 posts2 participants0 posts today

The recording of the April 3rd, 2025 #bhyve Production User Call is up:

youtu.be/CxxmoItWtvA

We discussed FreeBSD/GitHub CI VM images, Alexey's EDK2 port update that needs your testing, a new VLAN-related bridge Review for FreeBSD, Hans' CPUID work, virtualizing "mission-critical abandonware" at length, tips for fingerprinting systems, VXLAN networking, bhyve ARM64, and more!

"Don't forget to slam those Like and Subscribe buttons."

'Member how I was kinda bragging about my FreeBSD NAS's 21-day uptime? Well, I attempted to reboot, just for the heck of it (because why not)...and some shit happened.

The reboot process took a while to stop PIDs, and I saw there was a "naspool has been suspended (uncorrectable I/O failure)" error printed to the console. About 40 minutes later it's still stuck. It appears to have hanged, so I had to do a hard reboot. I searched around on the web for this error and found some forum posts, but none of them seemed to have any doable solution. I've gathered that the common thread in some of the forum posts of this error is that it has to do with USB storage, and my naspool is connected via USB.

It booted back up, and the naspool seems fine, but for some reason bhyve doesn't work anymore. I have my web services in a bhyve Debian VM, so those are now (still) down. Bhyve was working before the reboot. When I run the bhyve command to launch the VM, it appears to boot but then it just stops and returns to the shell. No bhyve processes are running.

I suppose I can try reinstalling Debian in a QEMU VM, but I feel like bhyve /ought/ to work.

#FreeBSD#bhyve#ZFS
Replied in thread

@swaggboi Late last year I fired vSphere from my homelab and replaced it with #bhyve via #FreeBSD. And since, I'm dabbling with FreeBSD/XFCE on a ThinkPad T490. Most of all, there are so many great, friendly, and helpful BSD people here, its been a great experience for me.

Continued thread

A fabulous amount of source notes pop up

{quote

scsi_all.h started out life as a work by Julian Elischer to add SCSI
support to CMU Mach 2.5. It was 373 lines. Julian ported this to 386BSD,
included in the 386BSD patch kit and incorported into FreeBSD at its
creation. Justin used this file when writing CAM, and imported it with
the initial CAM import, but only 30% (100 lines) of the original
remained. Justin moved from bitfields to bytes in structures, dropped
the complex unions, and renamed many structures to have their length
appended. Only about 30 structure names and about 40 #defines remained
from the original. The define names were taken directly from the SCSI
standard with spaces replaced by '_', so had no creativity. Apart from
the license comment, there were no comments retained (all the comments
in the CAM import were written by Justin and Ken). Even at that time,
Justin and Ken could have put their copyrights and names and moved to an
acknowledgement of Julian.

In the almost 30 years since that original import, this file has grown
to 4500 lines. Kenneth Merry, Alexander Motin and Justin Gibbs write
85% of the file's lines, if mechanical commits are omitted. Other
contributors contributed less than %5 each of the file.

Replace the original license (which lacked a copyright even and has been
criticized as ambiguous) with FreeBSD's standard 2-clause license. Add
copyrights for Justin, Ken and Alexander, with the date ranges they
contributed to the file. Add a note about the origin of the file to
acknowledge Julian's original work upon which all this was built, though
it's become a ship of Theseus in the mean time, built and rebuild many
times.

On an absolute scale, there's less than 1% of the current file with
lines from the original, and those are named after the names in the SCSI
standards and likely wouldn't qualify for copyright protection.

Sponsored by: Netflix
Reviewed by: mav, ken
Differential Revision: reviews.freebsd.org/D49016

End Quote}
^Z

How wonderful to have learned this now

#bash #csh #ksh #sh #freeBSD #SCSI #bhyve #jails #ZFS #programming #POSIX

codeberg.org/FreeBSD/freebsd-s

Summary card of repository FreeBSD/freebsd-src
Codeberg.orgcam: Update scsi_all.h to reflect 30 years of evolution · 1016b3c344 scsi_all.h started out life as a work by Julian Elischer to add SCSI support to CMU Mach 2.5. It was 373 lines. Julian ported this to 386BSD, included in the 386BSD patch kit and incorported into FreeBSD at its creation. Justin used this file when writing CAM, and imported it with the initial CA...