recentpopularlog in


« earlier   
Random Bhyve rant - The FreeBSD Forums
VMM are reality whether I like it or not. I tried them and they feel very much Xen Dom0 like. For me that is a good thing. Xen Dom0 (Alpine Linux) is my favourite hypervisor. I think that one of developers motivation was that Qemu even without kernel acceleration is moving into Linux only direction.

I am very familiar with VirtualBox and KVM. VirtualBox is desktop virtualization. KVM is more classical level 2 type Hypervisor. I would not run a server in the VirtualBox but I concur that it is very useful for a web developer who must test his product on multiple OSs and browsers. VirtualBox and Xen are as far apart as it gets so VMM are not really useful for somebody who needs VirtualBox. FreeBSD is not officially supported host for VirtualBox and my personal experience confirms that. I would not run VirtualBox on FreeBSD.

KVM is ok for server deployment but lacks hot migration comparing to Xen and even more think like block device provisioning where you can directly pass not just HDD but also other things like GPU computing cards directly to Xen host. I think that Red Hat requires now subscription for KVM Windows hosts (please see 7.4 below the release announcement) which means that I Xen will soon be my only option for Windows server as a virtual host.

Why am I taking so much about ZFS when the topic is bhyve. Because just like with Jails, Bhyve are infinitely more useful combined with ZFS underneath even with all network limitations you pointed. Personally I have not given a Bhyve try as I am experimenting with various DomU options on Alpine Linux. As adverse as Linux is to the third party kernel modules ZFS kernel modules do exist for ZFS and Alpine Linux does support DomU installation on the top of ZFS pool. That seems to be winner for me.

Also speaking from my extensive experience with Jails. Jails by itself even combined with ZFS are not really practically useful without a tool like sysutils/iocell
which is on another hand maintained outside of FreeBSD proper (in the ports three) by a single developer.

In retrospect I think that all BSDs were way to late for Virtualization party. FreeBSD was too late in part due to interesting Jail concept so much championed by Solaris zones and poorly imitated with Linux containers (docker is another laughable "brake trough" of Linux community. Maybe only NetBSD got it right by porting mature Xen technology instead of developing its own hypervisor but due to the current sorry state of the BSD (the headline for the incoming 8.0 release is support for USB 3.0) I am not sure how well maintained is Xen on NetBSD. One thing for sure I would not use NetBSD in production for anything at this time when the future of the project is so uncertain.

I compare Bhyve to KVM/QEMU and VirtualBox here. On them You just put any ISO (QNX/Linux/Windows/ReactOS/...), you start the process with several cores and memory and it just starts to boot this other OS, with graphical screen, without need for VNC, You can try it, install it or just close the window and kill that vm. With Bhyve graphical console is only for UEFI, so even if You load quite new system like Ubuntu Linux after install it fails to boot, You need to mess with grub-bhyve or other things and without UEFI there is no graphical console. Its just PITA.

Yes, Jails are also great, the only thing I miss in them is 'live migration' to other FreeBSD hosts. This is where Solaris Zones shine, also SmartOS (Illumos distribution) has nice (free) Solaris Zones implementation with CPU Overbursting and other features described here in real world usage:

KVM does support live migration, for RHV there is open source project called OVIRT and its totally free, its another 'open source VMware ESXi' product. You can also use KVM in OpenStack solution, but that also takes ages to jump in to (as a big project).
virtualization  freebsd  openbsd  bsd  networking  sysadmin  zfs 
3 days ago by dusko
bhyve - FreeBSD Wiki
bhyve, pronounced "beehive" is a hypervisor/virtual machine manager for FreeBSD that supports most Intel and AMD processors that report the "POPCNT" (POPulation Count) processor feature in dmesg(8).

Most Intel Atom C2000, Celeron, Core i3, i5, i7 and related Xeon processors support bhyve but early "Core" processors may only support one virtual machine.

Most "Barcelona" class and newer AMD processors support bhyve but some, notably the "Kuma" core processors include POPCNT but lack the required "NRIPS" (Next RIP Save) feature.
bhyve  freebsd  hypervisor  virtualization  bsd 
6 days ago by dusko
The EdgeBSD Project
EdgeBSD is a new member of the family of BSD-based Operating Systems, starting development with the current NetBSD codebase with Git for Source Code Management. Package management is based on pkgsrc.

The primary goal of EdgeBSD is to provide an ambitious environment for working as a bigger community together on the NetBSD Project. This is being achieved thanks to a modern development infrastructure, while taking an aggressive stance on integrating and enabling features.

Ultimately, EdgeBSD aims at being fun and attractive as a Research & Development platform while remaining a modern, robust, and industrial-grade system for all ranges of computer devices.
6 days ago by dusko
macos - Case-insensitive ls sorting in Mac OSX - Ask Different |
I needed sort's '-V' (version string sort) option, and here's how I got that:
Install the GNU Coreutils package:

sudo port install coreutils
sorting  textprocessing  bsd  mac  osx  shellscripting  workaround  solution 
10 days ago by kme
OpenBSD : why and how | Derek Sivers
Derek writes about why he likes OpenBSD; 2018-04-20.
unix  OpenBSD  BSD  DerekSilvers 
10 days ago by amoore
SUpraudit - An actually useful praudit(1) for MacOS
You may or may not be familiar with BSM auditing. A legacy of the dearly departed Solaris OS, which lives on in FreeBSD, Linux and - of course - MacOS. Auditing is detailed in my *OS Internals::Security & Insecurity's Chapter 2, and is one of the diamonds in the rough as far as system monitoring is concerned. Though not as powerful as the MAC Framework (and unable to proact, only react to operations), no other framework combines the ease of live monitoring with the advantages of pure user mode. The kernel is still very much involved - but you neither can nor should modify its auditing logic, which is enabled by default.

Apple took the set of default Solaris tools (namely, praudit(1), auditreduce and audit(8), and hasn't really invested in them. At all. Notably, praudit(1), which is used to print audit records from files in /var/audit and the /dev/auditpipe, is a pretty terrible tool that is not grep(1) friendly even when used with -l (single line output). And its XML output (-x) isn't that shabby either.
bsd  security  sun  osx  utility  openbsm 
11 days ago by horshacktest
OpenBSD on a Laptop
A guide to a secure and streamlined installation of OpenBSD 6.4 on a laptop.
bsd  computers  desktop  hardware  openbsd  Howto  IFTTT  laptop  laptops  linux 
12 days ago by xer0x

Copy this bookmark:

to read