<![CDATA[I've just upgraded my Proxmox Backup Server, running inside a bhyve VM on FreeBSD 15.0-RELEASE, and it now kernel panics as soon as it boots.]]>EDIT: it's not the virtio driver. This VM has 1G ram. If increased to 2G, it will boot. It seems it's the intramfs unable to decompress. And it's strange.

I've just upgraded my Proxmox Backup Server, running inside a bhyve VM on FreeBSD 15.0-RELEASE, and it now kernel panics as soon as it boots.

Setup:
- Host: FreeBSD 15.0-RELEASE
- Guest Kernel: Linux 7.0
- NIC: virtio-net

Workarounds tested:
- Removing the network device: boots successfully
- Changing the NIC to e1000: boots successfully

This seems to point to a virtio-net issue with this kernel under bhyve.

Has anyone else noticed this?

]]>https://board.circlewithadot.net/topic/9a09fcb8-757b-4bd1-8ef4-74103f48ead8/i-ve-just-upgraded-my-proxmox-backup-server-running-inside-a-bhyve-vm-on-freebsd-15.0-release-and-it-now-kernel-panics-as-soon-as-it-boots.RSS for NodeThu, 14 May 2026 20:51:23 GMTFri, 08 May 2026 16:17:19 GMT60<![CDATA[Reply to I've just upgraded my Proxmox Backup Server, running inside a bhyve VM on FreeBSD 15.0-RELEASE, and it now kernel panics as soon as it boots. on Fri, 08 May 2026 17:10:00 GMT]]>@meena this is what I can see:

[ 1.430932] Kernel panic - not syncing: System is deadlocked on memory
[ 1.431870] CPU: 0 UID: 0 PID: 12 Comm: kworker/u4:0 Not tainted 7.0.2-2-pve #1 PREEMPT(lazy)
[ 1.433132] Hardware name: FreeBSD BHYVE/BHYVE, BIOS 14.0 10/17/2021
[ 1.434068] Workqueue: async async_run_entry_fn
[ 1.434740] Call Trace:
[ 1.435111] <TASK>
[ 1.435435] dump_stack_lvl+0x5f/0x90
[ 1.436010] dump_stack+0x10/0x18
[ 1.436509] vpanic+0x227/0x460
[ 1.436981] panic+0x67/0x70
[ 1.437413] out_of_memory.cold+0x2d/0x8d
[ 1.437864] __alloc_frozen_pages_noprof+0x1529/0x1700
[ 1.438435] alloc_pages_mpol+0x80/0x180
[ 1.438875] folio_alloc_noprof+0x5b/0xc0
[ 1.439325] filemap_alloc_folio_noprof+0x61/0x80
[ 1.439848] __filemap_get_folio_mpol+0x201/0x340
[ 1.440372] simple_write_begin+0x37/0x110
[ 1.440830] generic_perform_write+0x137/0x2d0
[ 1.441326] ? current_time+0x3b/0x130
[ 1.441746] __generic_file_write_iter+0xab/0xd0
[ 1.442260] generic_file_write_iter+0x73/0x110
[ 1.442765] __kernel_write_iter+0x134/0x280
[ 1.443243] kernel_write+0xf9/0x1c0
[ 1.443654] xwrite.constprop.0+0x3f/0xd0
[ 1.444118] do_copy+0x4c/0x150
[ 1.444474] write_buffer+0x2e/0x50
[ 1.444864] flush_buffer+0x30/0xa0
[ 1.445257] ? __pfx_error+0x10/0x10
[ 1.445660] unzstd+0x3b9/0x4b0
[ 1.446016] ? __pfx_flush_buffer+0x10/0x10
[ 1.446488] ? __pfx_unzstd+0x10/0x10
[ 1.446900] unpack_to_rootfs+0x133/0x2d0
[ 1.447350] ? __pfx_error+0x10/0x10
[ 1.447786] do_populate_rootfs+0x6e/0x190
[ 1.448343] async_run_entry_fn+0x35/0x170
[ 1.448959] process_one_work+0x1a9/0x3c0
[ 1.449557] worker_thread+0x1b8/0x360
[ 1.450117] ? __pfx_worker_thread+0x10/0x10
[ 1.450753] kthread+0xf7/0x130
[ 1.451226] ? __pfx_kthread+0x10/0x10
[ 1.451787] ret_from_fork+0x2dc/0x3a0
[ 1.452348] ? __pfx_kthread+0x10/0x10
[ 1.452909] ret_from_fork_asm+0x1a/0x30
[ 1.453499] </TASK>
[ 1.453927] Kernel Offset: 0x26000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 1.455499] ---[ end Kernel panic - not syncing: System is deadlocked on memory ]---

]]>https://board.circlewithadot.net/post/https://mastodon.bsd.cafe/users/stefano/statuses/116540060513443896https://board.circlewithadot.net/post/https://mastodon.bsd.cafe/users/stefano/statuses/116540060513443896Fri, 08 May 2026 17:10:00 GMT