Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

293
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#bhyve

0 posts0 participants0 posts today
Public
hyperreal

'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
Public
Peter Wemm
Today's learnings:

1) #bhyve on #FreeBSD is a lot more interesting and capable than I realized.
2) There's lots of sharp edges and surprises.
3) use nvme rather than virtio-blk on bhyve if your guests support it. It seems to be a lot more performant.
4) Information about pci passthrough is wildly inconsistent when you compare docs vs what tooling does vs what people say.
5) Trying to mix multiple less-commonly-used tech features into one project can be quite an adventure. eg: SR-IOV splitting one ethernet card -> many VFs -> many VMs. And throw in vlans for more footgun potential.

I don't know why I'm tired today.
Public *
Just Dude

Just flashed into my mind, I spent hours less on system maintenance since I switched from Linux and Proxmox to #freebsd and #bhyve

It is easy to install, it is up and running…. No memory leaks, no package conflicts, no nothing except steady performance and user (sysadmin) joys

Remarkable effort. Thanks

Public
Michael Dexter

The recording of the January 9th, 2025 #bhyve Production User Call is up:

youtu.be/8PhuosvTqt0

We discussed SeaBIOS, Netgraph usability, PkgBase graphing, kern.geom.confdot graphing, libsys.so, bhyve documentation, error messages, global uniqueness, the need for a fast VLAN filtering bridge, and more!

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

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
Continued thread
Public *
Marcel Stritzelberger

It continues in my article series: "FreeBSD as a server"

An important milestone that deals with the topic of #FreeBSD virtualisation with #BHYVE . FreeBSD has a fully-fledged virtualization that is ideally suited to starting other operating systems.

bsdbox.de/en/blog/2024-12-22-f

This also marks the start of a parallel series of articles on how best to install the various VMs.

bsdbox.de/en/artikel/bhyve

Windows 11 Screenshot with Explorer and Terminal
Public
Sven Bookmeyer

I will get the chance to order an new Lenovo #ThinkPad notebook for my work. I would like to try #FreeBSD with #bhyve on it. What should my preferred components/manufactors (CPU, GPU, audio, LAN, WLAN, …)? I do not have a problem with an USB adapter for LAN and WLAN if the build-in component is not working. Any other things I should watch out for?

Public
D. Creemer

I’ve updated my usb-passthrough to #bhyve vm’s configuration on #FreeBSD. Recall bhyve does not support usb pass through, but #qemu does. I’ve created a super-lightweight Alpine #linux VM with qemu, passing through the usb devices I need elsewhere to that. Then I use USBIP to make the devices available via TCP to the bhyve VMs, which can then import them (at least on windows and Linux). The qemu VM uses little resources and is mostly invisible. It’s a hack - but a pretty nice one I think!

Replied in thread
Public
Kevin Karhan :verified:

@libreleah @ariadne the closest to it is like the way Microsoft basically implemented 2 independent systems with completely vietualized and abstracted access in the #XboxOne which is AFAIK still unhacked.

infosec.space/@kkarhan/1128436

But their intention in terms of #security is inherently anti-user and would only be acceptable in #CriticalInfrastructure like #Avionics where you'll have to prevent malicious users from ramming a plane into the ground!

As for mass-adopted systems, I'd say that #Android (aka. #toybox + #musl / #Linux + ART) with it's #Java-#VM is the best compromise after hardened Linux-distros, BSDs with #bhyve & #jails and "#KISS-principled" #OpenBSD which all buy security at the expense of control, modablility and portability.

Infosec.SpaceKevin Karhan :verified: (@kkarhan@infosec.space)@dalias@hachyderm.io @sam@trapped.genoq.org @ariadne@treehouse.systems potentially yes. I think it's safe to look at the way #Microsoft kept the #XboxOne watertight to this day: https://youtu.be/U7VwtOrwceo Nit everything of it is applicable tho and their implemebtation requires custom silicon and microcode but ideally any I/O would be restricted to hard-sandboxed ranges and thus denied access to anything outside it. I had lenghtly conversations with @stman@mastodon.social about this whole issue and any interface like #PCIe would've to be basically sandboxed on low level and denied random I/O access entirely outside of that "IO-mapped address space"...
#kiss
ExploreLive feeds
About