gyptazy.ch is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
I decided to run #NetBSD on my #OmniOS machine, using #bhyve. And so far, it works.
https://www.tumfatig.net/2024/running-netbsd-on-omnios-using-bhyve/#installation
Yeah, a run Debian with #Bhyve on #FreeBSD14
# vm list
NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE
debian default grub 1 512M - No Running (29647)
Thanks @vermaden for his tutorial: https://vermaden.wordpress.com/2023/08/18/freebsd-bhyve-virtualization/
The recording of the April 25th, 2024 #bhyve Production User Call is up:
https://youtube.com/watch?v=gGzpLLJTHS0
We discussed SR-IOV and GPU pass-through, DaVinci Resolve on #FreeBSD using Linux compatibility, FreeBSD at Netflix, and more!
Likey Subscriby!
Hey-o! A modern Mac Mini would sure help speed up this process!
Took me some time but finally nailed that one :]
To have working (a lot more accurate) mouse in #GhostBSD VM on #Bhyve - with xhci_mouse="yes" in 'vm-bhyve' config - You need to add these to /boot/loader.conf file:
hw.usb.usbhid.enable=1
usbhid_load=YES
Reference:
https://twitter.com/vermaden/status/1718862370930376847
Took me some time but finally nailed that one :]
To have working (a lot more accurate) mouse in #GhostBSD VM on #Bhyve - with xhci_mouse="yes" in 'vm-bhyve' config - You need to add these to /boot/loader.conf file:
hw.usb.usbhid.enable=1
usbhid_load=YES
Reference:
https://twitter.com/vermaden/status/1718862370930376847
Hey #BSD Fans!
We all share the same interests - #BSD based systems like #FreeBSD, #OpenBSD and #NetBSD.
We chat all day, sharing thoughts, questions and help. We talk on Matrix across different channels, we share on the #Fediverse. We have @vermaden@bsd.cafe's newsletter, we have @dexter@bsd.network's #FreeBSD #Jails and #bhyve calls and many other ones I can't list here.
Wondering if there would be and interests in the #BSDNetwork, #BSDCafe, etc., for a weekly smalltalk session like in a pub. Just a Jitsi based video/audio call where we can meet, discuss things from newsletter, trending things from the #Fediverse or just have off-topic and openminded discussions. This could result into the #BSDPub meeting.
I know, some people are shy - keep your cam off until you feel comfortable and feel free to join the discussions. Even this meetings should make fun and no pressure - so if someone is not in the mood or can't make it - no worries. No one will judge.
Would you be interested?
#helloSystem #DragonFlyBSD #HardenedBSD #GhostBSD #pfSense #illumos #tribblix #solaris #opensolaris #zfs #community #social
Yes: | 44 |
No: | 4 |
Closed
I spoke with Greg Wallace with @FreeBSDFoundation about GPU support. It's a thing. The #FreeBSD forums are full of folks asking about native driver support. That would be my preference. Just need to get enough developers complaining to convince the manufacturers to care.
There are threads of tinkerers getting pass-through working with #bhyve on CURRENT. I may go this route soon on a test bench.
I spoke with Greg Wallace with @FreeBSDFoundation about GPU support. It's a thing. The #FreeBSD forums are full of folks asking about native driver support. That would be my preference. Just need to get enough developers complaining to convince the manufacturers to care.
There are threads of tinkerers getting pass-through working with #bhyve on CURRENT. I may go this route soon on a test bench.
FreeBSD OpenJDK Contract
Various contracts, full- and part-time:
— bhyve hypervisor kernel improvements
— desktop usability
— developer tools such as LLD
— hardware support on new ARM and RISC-V devices
— installer
— jails – usability/orchestration/OCI-compatibility
— networking
— packaging – including package base (pkgbase)
— …
<https://freebsdfoundation.org/open-positions/>
#FreeBSD #OCI #JDK #OpenJDK #ARM #RISCV #bhyve #LLD #pkgbase #orchestration #Java
The recording of the April 4th, 2024 bhyve Production User Call
We discussed the #Fudo security appliance which is now available as a #bhyve VM, TPM Emulation, a VM framework for #NetBSD, AMD SEV and untrusted public VM providers, identifying tap/bridge performance bottlenecks, diagnosing PCI Pass-Through (PPT) issues, and the various FUD surrounding #TrueNAS CORE and other #FreeBSD-based appliances.
Several recordings are up!
https://YouTube.com/@callfortesting
Thank you @antranigv for co-hosting during #AsiaBSDCon!
#FreeBSD #illumos #OpenZFS #bhyve
Sorry to be offline during the Great bsd.network Outage of 2024.
@badgerops Can take it to the next level of nonsense with some #Windows server running in #bhyve 😂
I seriously didn't expect (web?!??) browsers go into *that* direction when I first installed some #Netscape 🤯
@dexter From the register article floating around, SCALE is all about NAS and Kubernetes. iXsystems is probably going to push for tighter ZFS and Kubernetes integration for on-prem customers. That's a saturated market, IMO. But there's probably money there.
It would be interesting if some upstart #BSD devs started a company that tightly integrated bhyve and #ZFS on #FreeBSD. Made a slick web-based GUI around managing #bhyve / ZFS storage. Maybe one that honors gitops; ArgoCD (without k8s).
@dexter From the register article floating around, SCALE is all about NAS and Kubernetes. iXsystems is probably going to push for tighter ZFS and Kubernetes integration for on-prem customers. That's a saturated market, IMO. But there's probably money there.
It would be interesting if some upstart #BSD devs started a company that tightly integrated bhyve and #ZFS on #FreeBSD. Made a slick web-based GUI around managing #bhyve / ZFS storage. Maybe one that honors gitops; ArgoCD (without k8s).
A quick bhyve/ARM64 demo based on experiments during the informal #bhyve Production User Call today:
I finally got PCI pass-through to work in bhyve so I can use a webcam in my windows vm. It took several hours of chasing my tail around so I submitted a patch for the vmm(4) manpage which will hopefully save someone else a bit of frustration.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277530
#freebsd #bhyve @dexter
Today's #bhyve Production User Call:
We discussed Chris' bhyve storage model benchmarking, SAS multipathing, Jan's UCL macro project, and more!
Today's #bhyve Production User Call:
We discussed Chris' bhyve storage model benchmarking, SAS multipathing, Jan's UCL macro project, and more!
Self-reflection time!
We had a very unique #bhyve Production User call where we discussed what defines a Production User, bhyve/ARM64, vmrun.sh, SR-IOV issues, Documentation, and much more!
Today's #bhyve Production User Call recording:
We discussed the slirp Review, resources for VMware users (or lack there of), Chris' work on the Handbook, the four fundamental types of documentation, more GRUB/UEFI-CSM/BIOS boot strategies such as booting a kernel directly with EFI, plus vmstated and Zelta updates and brainstorming.
Benchmarking on Ryzen vs other architectures for #bhyve hypervisor runs on #FreeBSD
#VMware is canceling the free ESXi that will mean the next generations will not be able to use it in their homelabs. This means other solutions like #Proxmox, #KVM or #Bhyve will educate the admins of the future. Citrix did the same thing with XEN server and killed an complete ecosystem even it was released for free again later people did not come back.
Did this not post?
The recording of yesterday's #bhyve call is up:
Lots of great discussions and yet more network buffer diagnostics!
Today's #bhyve Production User Call recording:
We discussed web UI strategies, UEFI-CSM/SeaBIOS... and a spicy topic you'll only see in the notes!
@david_chisnall Same. I use the #FreeBSD RE team's snapshots on vagrant cloud, also. At first just with vagrant (via VirtualBox), but am looking to do the same with #bhyve. I would like to see #AWS support deployment of FreeBSD containers on ECS, or Cloud Run on #GCP. That would make FreeBSD deployment into the cloud much easier. FreeBSD RE team, your work is greatly appreciated out in the wild. I promise.
[1] https://app.vagrantup.com/freebsd
[2] https://gist.github.com/bsdlme/14a46c568b2917206e9d84356e1a4303
Today's amazing #bhyve call is recorded but delayed.
@meka -- I was excited about this too. I think it's just the control plane for #kubernetes that is running on #FreeBSD. But it's also possible to bootstrap a node pool of #linux machines through #bhyve. With well-tunned Linux VMs, this could be a mighty on-prem compute cluster.
It's been an incredibly intense week, and it's only Wednesday. This morning, I had to drive 200 km through icy fog and heavy traffic. However, this afternoon was dedicated to setting up a FreeBSD server.
The client wanted to retain some of the features from their old Linux system. I came up with the idea of directly passing the two physical disks to bhyve and booting them. The boot was immediate, and there were no issues. The new FreeBSD server was up and running, and the 'old' Linux was now operating as a VM, working perfectly on the physical disks.
The client was pleased with the outcome and asked me to set up a native FreeBSD desktop, encrypted because they will store important data. I hadn't installed a FreeBSD desktop recently, but it turned out to be easier than expected (no wifi involved).
I installed xorg, the Nvidia drivers, nvidia-xconfig (which generated the configuration file perfectly), kde5, sddm, Firefox, LibreOffice, the Nextcloud client, and made a few small adjustments to get the keyboard audio buttons working. Even suspend/resume functionality worked flawlessly, which amazed the client.
I then created a jail on the server and set up zfs-autobackup to back up the client's PC on the server (of course, on an encrypted dataset). Time to go home, satisfied with the outcome.
Yes. Windows Server 2025 boots under #bhyve
A client's server (a Dell r630) began experiencing issues (originally due to a faulty switch, but it led to new hardware purchases). It was running Proxmox, which I installed about three years ago, featuring SSD drives and 128 GB of RAM. A new server was set up around four months ago, but a water leak from the floor above flooded the rack, rendering the new hardware unusable. In a rush yesterday morning, I quickly reconfigured the "old" r630, installing FreeBSD 14.0-RELEASE and transferring VMs from the latest backup using zfs-send/receive. After launching the VMs on bhyve with some minor adjustments, everything was back in production. Just got a call saying the performance has "drastically improved." Previously, a specific end-of-month process on the r630 with Proxmox took about 30 minutes, while the new (flooded) server cut that down to 15 minutes, much to their delight. This morning, the same process only took 8 minutes, to their great surprise. I'm curious to investigate, but can't quite pinpoint how this is possible: my suspicion is that the process is mainly I/O bound, and the nvme driver in bhyve is exceptionally efficient in this aspect. For once, I'm taking credit for something I never expected. :-)
#TechLife #DataRecovery #ServerManagement #ITChallenges #bhyve #Proxmox #FreeBSD
I find myself coming back to this paper / talk from Maciej Czekaj on using #freebsd for data science. For the uninitiated, a modern data science software stack is large and unwieldy. Running jupyterlab out of ports and jails can take you 90% of the way there. And do it in a way that is secure / stable. I use #linux VM's and #bhyve for some of the stuff he touches on. And not much on #ARM (which he goes into). But the discussion on #Python is spot-on.
https://papers.freebsd.org/2022/bsdcan/czekaj-data_science_on_freebsd_arm64/
The recording of today's #bhyve Production User Call is up!
Welcome Ivo!
The ad-free Production User Call and bhyvecon archive is about to hit 100 hours and 100 videos!
https://youtube.com/@callfortesting
Thank you everyone who has participated to date and we always welcome new participants!
Does any have a copy of VMS x86 and are willing to test it under #bhyve?
I tested a dozen or so guest operating systems with #bhyve in preparation for Friday's hackathon and have posted the successes to the Wiki along with some clean-up:
The recording of today's #bhyve PUC is up:
https://youtu.be/b9MWzMrrcEA?si=R8OX5qDA43EH0EhJ
You are welcome to join the #bhyve hackathon FRIDAY at 10AM Pacific.
Use the regular meeting link found at https://callfortesting.org
Topics:
1. Consolidate advanced networking documentation. (Yelling "Read the VALE paper!" has proven unhelpful)
2. UEFI, UEFI-CSM, GRUN, ChuckGRUB, SeaBIOS, rEFInd, rEFI, OpenCore, CoreBoot, etc. Bootathon
3. Your topic!
@brbennett @dexter @triton_dc ABI.am ’s host is #FreeBSD. The guess is #Linux, so we use #bhyve.
The Linux VM has 1.5TB of RAM and 240 vCPUs.
AFAIK not many hypervisors can do that ;)
Tomorrow morning, I'll need to migrate an Alpine Linux-based VPS from a physical host (Proxmox) to another one running FreeBSD.
My first instinct was to go with bhyve, but I'm considering a less conventional and perhaps more efficient approach. 😉
I hope to craft the perfect #OpenSource/FreeSoftware Event fundraising pitch!
9/???
I would not have spent over a dozen years with the #bhyve hypervisor if I hadn't stumbled into its unveiling at a @bsdcan DevSumnit.
The 20th Anniversary #BSDCan invites you to attend, present, and sponsor this amazing event!
Learn more at https://bsdcan.org
Links for the Production User Calls are (finally) consolidated at https://callfortesting.org
@crest and @antranigv have a mix of #bhyve process supervision goodies in the mix and helper scripts
Chris M has a bhyve process supervisor written in C
@bellhyve has a delicious #OpenZFS replication tool written in AWK with sh wrappers, meaning you can push to a system that only has AWK
Antranig appears to have cracked the secrets of NATIVE Collabora office on FreeBSD
@josephholsten Is doing the same with the 'realm' AD join command
And OMG @meka just announced that the has added SIGINFO A.K.A. CTRL-T for the 'find' command which I totally needed yesterday!
And many more!
The recording of today's #bhyve Production User call is up: