What would be the #freebsd equivalent to "kpartx -a" on linux?
Asking because #bhyve is currently broken on 15.0 and i'd like to access the data in a zvol which is the disk of a bhyve vm.
Currently FreeBSD doesn't see (and doesn't care about) the partitions inside said zvol. I'd like to make it care temporarily :-)
On Thursday, @gyptazy provided a talk about #BoxyBSD at the "Virtualization Gathering" at @credativde.
@gyptazy provided some more information about the BoxyBSD project, but also about the history and infrastructure including the switches of #FreeBSD #Jails, #bhyve and #Proxmox ( #kvm). Afterwards, additional information about the #Sylve project were shared and why this is so important and interesting and could make BoxyBSD return to bhyve based #virtualization.
Slides: https://cdn.gyptazy.com/talks/BoxyBSD_Virtualization_Hypervisor_bhyve_Proxmox_credativ_gyptazy.pdf
Recording: https://peertube.gyptazy.com/w/2HtUv9HFBNEU4sEw52bD8H
On Thursday, @gyptazy provided a talk about #BoxyBSD at the "Virtualization Gathering" at @credativde.
@gyptazy provided some more information about the BoxyBSD project, but also about the history and infrastructure including the switches of #FreeBSD #Jails, #bhyve and #Proxmox ( #kvm). Afterwards, additional information about the #Sylve project were shared and why this is so important and interesting and could make BoxyBSD return to bhyve based #virtualization.
Slides: https://cdn.gyptazy.com/talks/BoxyBSD_Virtualization_Hypervisor_bhyve_Proxmox_credativ_gyptazy.pdf
Recording: https://peertube.gyptazy.com/w/2HtUv9HFBNEU4sEw52bD8H
The recording of the December 11th, 2025 #bhyve Production User Call is up:
We discussed Sylve/ARM64 progress, LibVirt issues, an OpenZFS wrapper in Go, bhyve configuration formats, libzfs, active and inactive bhyve management projects, vmnet bridged and routed networking, and more!
"Don't forget to slam those Like and Subscribe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
I can install Haiku (r1beta5-x86_64) in a bhyve VM on FreeBSD but the installed OS won鈥檛 boot.
I use vm-bhyve, and the config file haiku/haiku.conf looks like this:
loader="uefi"
cpu="2"
memory="1G"
graphics="yes"
graphics_port="5998"
graphics_res="1280x1024"
xhci_mouse="yes"
network0_type="virtio-net"
network0_switch="interne"
disk0_type="virtio-blk"
#disk0_type="nvme"
disk0_name="disk0.img"
uuid="blah-blah"
network0_mac="blah"
I tried both virtio-blk and nvme as disk type, no luck.
The boot error with virtio-blk is:
BdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot (0x0) /Pci (0脳4,0x0): Not Found
Any idea?
The last new #Linux #kernel for 2025 was just released and there are some really cool changes all around. One of the new additions is detection for FreeBSD's #bhyve #hypervisor. Wicked cool!
From the article:
"In what might be a sign of the quiet continued spread of FreeBSD, the kernel can now detect and handle that it is running under FreeBSD's built-in bhyve hypervisor. Coincidentally, FreeBSD 15.0 just appeared as well, and in this release bhyve supports over 255 virtual processors [PDF] in a VM. Now Linux can handle that configuration."
The juicy details are here:
The recording of the December 11th, 2025 #bhyve Production User Call is up:
We discussed Sylve/ARM64 progress, LibVirt issues, an OpenZFS wrapper in Go, bhyve configuration formats, libzfs, active and inactive bhyve management projects, vmnet bridged and routed networking, and more!
"Don't forget to slam those Like and Subscribe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
A potentially-awesome #bhyve surprise is in the works.
This #GivingTuesday we invite you to support all Call For Testing activities via https://bsdfund.org
Weekly #FreeBSD build option regressing tests
The Weekly Jails/Zones Production User Call
The Weekly #OpenZFS Production User Call
The Weekly #bhyve Production User Call
bhyvecon
The OpenZFS User and Developer Summit
BSDCan Fundraising
#BSDTV A/V package fundraising
Way too many conference talks
鉂わ笍
I can install Haiku (r1beta5-x86_64) in a bhyve VM on FreeBSD but the installed OS won鈥檛 boot.
I use vm-bhyve, and the config file haiku/haiku.conf looks like this:
loader="uefi"
cpu="2"
memory="1G"
graphics="yes"
graphics_port="5998"
graphics_res="1280x1024"
xhci_mouse="yes"
network0_type="virtio-net"
network0_switch="interne"
disk0_type="virtio-blk"
#disk0_type="nvme"
disk0_name="disk0.img"
uuid="blah-blah"
network0_mac="blah"
I tried both virtio-blk and nvme as disk type, no luck.
The boot error with virtio-blk is:
BdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot (0x0) /Pci (0脳4,0x0): Not Found
Any idea?
A potentially-awesome #bhyve surprise is in the works.
馃獰
馃槀