src icon indicating copy to clipboard operation
src copied to clipboard

Kernel panic when run in a VM with i350 VF.

Open Phreeman33 opened this issue 1 year ago • 7 comments

Same issue with this.

Environment: VM System: Proxmox VE 8.1.10 (Linux 6.5.13-5-pve) OPNsense: 24.1.5_3 CPU: Intel i5-3340 NIC: intel i350-t4

Phreeman33 avatar Apr 12 '24 04:04 Phreeman33

Closing due to switch to FreeBSD 14.x

fichtner avatar Feb 05 '25 11:02 fichtner

I'm not sure if this has been closed because it's believed fixed in FreeBSD 14.x? But I can confirm this is still an issue in OPNsense 25.1 when using Virtual Functions with an Intel i350 NIC.

Image

Also, I'm not sure if I'm looking in the right place, but I checked the FreeBSD Bugzilla with the keyword IntelNetworking (https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=IntelNetworking), and I can't find any reports of this.

Indeed, there are reports (such as this one) that suggests FreeBSD does basically work with i350 VFs. So it's possible this might not be an upstream issue, but I haven't yet tried booting FreeBSD with an i350 VF passed through to see if it gets past the kernel panic that happens in OPNsense.

abirkill avatar Feb 06 '25 01:02 abirkill

I don’t mind reopening, but that won’t change much if this does not get reported to FreeBSD with a full panic or better yet a core dump (we do have a debug kernel for this purpose).

Intel may have something say about the behaviour on FreeBSD too. Some bugs are known, but not widely reported.

Cheers, Franco

fichtner avatar Feb 06 '25 05:02 fichtner

That's fair enough. I've been slightly less lazy than in my previous comment and actually tried FreeBSD 14.2, and can confirm it also fails with a very similar kernel panic.

When I get a bit more time I'll try and figure out how to collect the diagnostics required to usefully open a FreeBSD issue.

Thanks for your help!

abirkill avatar Feb 06 '25 07:02 abirkill

@abirkill thanks, I'll reopen and if you need help let me know

fichtner avatar Feb 06 '25 07:02 fichtner

A new method I just tried:

Hardware: Ryzen 3900X + X470-F Platform: Proxmox 8.4.1 Kernel: 6.5.13-6-pve

VM setting: CPU: host, 4-core RAM: 8G assigned 2 i350-VF DON'T USE UEFI BOOT!

New edit: just add args: -cpu Skylake-Server,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi in vmid.conf or as qemu args

it boot and work fine.

Actually I'm accently found this way. So I don't know why it work for OPNsense 25.1 lol

sunsky131221 avatar Jun 14 '25 06:06 sunsky131221

Here the full VM.conf

agent: 1 args: -cpu Skylake-Server,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi balloon: 0 boot: order=virtio0;ide2 cores: 4 cpu: host hostpci0: 0000:04:10.3,pcie=1 hostpci1: 0000:04:10.2,pcie=1 hotplug: 0 ide2: local:iso/OPNsense-25.1-dvd-amd64.iso,media=cdrom,size=2165500K localtime: 0 machine: q35 memory: 8192 meta: creation-qemu=9.2.0,ctime=1742896978 name: OPNSENSE numa: 0 onboot: 1 ostype: other scsihw: virtio-scsi-single smbios1: uuid=0660bfbc-b189-407a-a015-1fe87135a215 sockets: 1 startup: order=0 tablet: 0 virtio0: local:101/vm-101-disk-0.qcow2,discard=on,iothread=1,size=64G vmgenid: a6b8fa50-6efa-4d92-8388-e3c6e324070c

sunsky131221 avatar Jun 14 '25 07:06 sunsky131221

I'm going to close this. We're not going to work on upstream issues anymore.

fichtner avatar Sep 11 '25 06:09 fichtner