Kernel oops when passing through Adaptec ASR-72405 (aacraid) to VM on kernel 7.0+

exterrestris · Wednesday at 14:42

There looks to be a regression from kernel 6.17 in kernel 7 relating to aacraid passthrough - when Proxmox is running on kernel 7.0.14, I'm getting a kernel oops on one of my machines on VM startup when passing through an Adaptec ASR-72405 HBA:

Code:

Sep 01 11:01:12 starbase-375 kernel: BUG: unable to handle page fault for address: ffff8f4aedf8e018
Sep 01 11:01:12 starbase-375 kernel: #PF: supervisor write access in kernel mode
Sep 01 11:01:12 starbase-375 kernel: #PF: error_code(0x0002) - not-present page
Sep 01 11:01:12 starbase-375 kernel: PGD 296601067 P4D 296601067 PUD 0
Sep 01 11:01:12 starbase-375 kernel: Oops: Oops: 0002 [#1] SMP PTI
Sep 01 11:01:12 starbase-375 kernel: CPU: 5 UID: 0 PID: 2011 Comm: task UPID:starb Tainted: P           O        7.0.14-14-pve #1 PREEMPT(lazy)
Sep 01 11:01:12 starbase-375 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Sep 01 11:01:12 starbase-375 kernel: Hardware name: System manufacturer System Product Name/Z170-A, BIOS 3802 03/15/2018
Sep 01 11:01:12 starbase-375 kernel: RIP: 0010:__srcu_read_unlock+0x1a/0x30
Sep 01 11:01:12 starbase-375 kernel: Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 f0 83 44 24 fc 00 48 63 f6 48 c1 e6 04 48 03 77 08 <65> 48 ff 46 08 5d 31 f6 31 ff c3 cc cc cc cc 0f 1f 80 00 00 00 00
Sep 01 11:01:12 starbase-375 kernel: RSP: 0018:ffffd37387407a70 EFLAGS: 00010202
Sep 01 11:01:12 starbase-375 kernel: RAX: 0000000000000000 RBX: ffff8f475f230188 RCX: ffff8f475f2300e0
Sep 01 11:01:12 starbase-375 kernel: RDX: ffffd37387407b40 RSI: 0000000000000010 RDI: ffff8f475f230188
Sep 01 11:01:12 starbase-375 kernel: RBP: ffffd37387407a70 R08: 0000000000000000 R09: 0000000000000000
Sep 01 11:01:12 starbase-375 kernel: R10: 0000000000000000 R11: 0000000000000008 R12: 0000000000000000
Sep 01 11:01:12 starbase-375 kernel: R13: 0000000000000001 R14: ffffffffc063c8c8 R15: ffffffffc063c8c8
Sep 01 11:01:12 starbase-375 kernel: FS:  0000770845e52240(0000) GS:ffff8f4aedf8e000(0000) knlGS:0000000000000000
Sep 01 11:01:12 starbase-375 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 01 11:01:12 starbase-375 kernel: CR2: ffff8f4aedf8e018 CR3: 000000010a4be001 CR4: 00000000003726f0
Sep 01 11:01:12 starbase-375 kernel: Call Trace:
Sep 01 11:01:12 starbase-375 kernel:  <TASK>
Sep 01 11:01:12 starbase-375 kernel:  blk_mq_tagset_busy_iter+0x1c9/0x420
Sep 01 11:01:12 starbase-375 kernel:  ? schedule+0x27/0xb0
Sep 01 11:01:12 starbase-375 kernel:  ? schedule_timeout+0xcf/0x110
Sep 01 11:01:12 starbase-375 kernel:  ? __pfx___scsi_host_busy_iter_fn+0x10/0x10
Sep 01 11:01:12 starbase-375 kernel:  ? __wait_for_common+0x15c/0x1a0
Sep 01 11:01:12 starbase-375 kernel:  scsi_host_busy_iter+0x3a/0x60
Sep 01 11:01:12 starbase-375 kernel:  ? __pfx_wait_for_io_iter+0x10/0x10 [aacraid]
Sep 01 11:01:12 starbase-375 kernel:  aac_send_shutdown+0xb4/0x1a0 [aacraid]
Sep 01 11:01:12 starbase-375 kernel:  __aac_shutdown+0x70/0x1c0 [aacraid]
Sep 01 11:01:12 starbase-375 kernel:  aac_remove_one+0x47/0x170 [aacraid]
Sep 01 11:01:12 starbase-375 kernel:  pci_device_remove+0x41/0xb0
Sep 01 11:01:12 starbase-375 kernel:  device_remove+0x43/0x80
Sep 01 11:01:12 starbase-375 kernel:  device_release_driver_internal+0x206/0x270
Sep 01 11:01:12 starbase-375 kernel:  device_driver_detach+0x14/0x20
Sep 01 11:01:12 starbase-375 kernel:  unbind_store+0xac/0xc0
Sep 01 11:01:12 starbase-375 kernel:  drv_attr_store+0x24/0x50
Sep 01 11:01:12 starbase-375 kernel:  sysfs_kf_write+0x72/0x90
Sep 01 11:01:12 starbase-375 kernel:  kernfs_fop_write_iter+0x161/0x210
Sep 01 11:01:12 starbase-375 kernel:  vfs_write+0x274/0x490
Sep 01 11:01:12 starbase-375 kernel:  ksys_write+0x6f/0xf0
Sep 01 11:01:12 starbase-375 kernel:  __x64_sys_write+0x19/0x30
Sep 01 11:01:12 starbase-375 kernel:  x64_sys_call+0x22f/0x2390
Sep 01 11:01:12 starbase-375 kernel:  do_syscall_64+0x10b/0x14e0
Sep 01 11:01:12 starbase-375 kernel:  ? __x64_sys_openat+0x52/0xa0
Sep 01 11:01:12 starbase-375 kernel:  ? x64_sys_call+0x1f4c/0x2390
Sep 01 11:01:12 starbase-375 kernel:  ? do_syscall_64+0x148/0x14e0
Sep 01 11:01:12 starbase-375 kernel:  ? exc_page_fault+0x92/0x1c0
Sep 01 11:01:12 starbase-375 kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Sep 01 11:01:12 starbase-375 kernel: RIP: 0033:0x770845f1e687
Sep 01 11:01:12 starbase-375 kernel: Code: 48 89 fa 4c 89 df e8 58 b3 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff
Sep 01 11:01:12 starbase-375 kernel: RSP: 002b:00007fff33c14530 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Sep 01 11:01:12 starbase-375 kernel: RAX: ffffffffffffffda RBX: 0000770845e52240 RCX: 0000770845f1e687
Sep 01 11:01:12 starbase-375 kernel: RDX: 000000000000000c RSI: 000060d9f7d56a70 RDI: 000000000000000f
Sep 01 11:01:12 starbase-375 kernel: RBP: 0000000000000018 R08: 0000000000000000 R09: 0000000000000000
Sep 01 11:01:12 starbase-375 kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 000060d9f7d39fd8
Sep 01 11:01:12 starbase-375 kernel: R13: 000000000000000f R14: 0000000000000000 R15: 000060d9f7d39fc8
Sep 01 11:01:12 starbase-375 kernel:  </TASK>
Sep 01 11:01:12 starbase-375 kernel: Modules linked in: ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter nf_tables sunrpc binfmt_misc bonding tls nfnetlink_log intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel i915 mei_pxp mei_hdcp kvm drm_buddy ghash_clmulni_intel aesni_intel ttm rapl eeepc_wmi intel_wmi_thunderbolt wmi_bmof drm_display_helper mxm_wmi intel_cstate mei_me ee1004 pcspkr cec rc_core joydev intel_pmc_core mei i2c_algo_bit pmt_telemetry pmt_discovery pmt_class input_leds intel_pmc_ssram_telemetry intel_vsec acpi_pad mac_hid sch_fq_codel msr vhost_net vhost vhost_iotlb tap vfio_pci vfio_pci_core irqbypass vfio_iommu_type1 vfio nvme_fabrics iommufd nvme_core nvme_keyring nvme_auth hkdf efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 zfs(PO) spl(O) btrfs libblake2b xor raid6_pq hid_logitech_hidpp hid_logitech_dj hid_generic usbkbd usbmouse usbhid hid mfd_aaeon asus_wmi sparse_keymap platform_profile ixgbe libie_fwlog
Sep 01 11:01:12 starbase-375 kernel:  i2c_i801 psmouse xhci_pci xfrm_algo i2c_mux e1000e serio_raw video ahci i2c_smbus mdio aacraid dca libahci xhci_hcd wmi
Sep 01 11:01:12 starbase-375 kernel: CR2: ffff8f4aedf8e018
Sep 01 11:01:12 starbase-375 kernel: ---[ end trace 0000000000000000 ]---
Sep 01 11:01:12 starbase-375 kernel: RIP: 0010:__srcu_read_unlock+0x1a/0x30
Sep 01 11:01:12 starbase-375 kernel: Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 f0 83 44 24 fc 00 48 63 f6 48 c1 e6 04 48 03 77 08 <65> 48 ff 46 08 5d 31 f6 31 ff c3 cc cc cc cc 0f 1f 80 00 00 00 00
Sep 01 11:01:12 starbase-375 kernel: RSP: 0018:ffffd37387407a70 EFLAGS: 00010202
Sep 01 11:01:12 starbase-375 kernel: RAX: 0000000000000000 RBX: ffff8f475f230188 RCX: ffff8f475f2300e0
Sep 01 11:01:12 starbase-375 kernel: RDX: ffffd37387407b40 RSI: 0000000000000010 RDI: ffff8f475f230188
Sep 01 11:01:12 starbase-375 kernel: RBP: ffffd37387407a70 R08: 0000000000000000 R09: 0000000000000000
Sep 01 11:01:12 starbase-375 kernel: R10: 0000000000000000 R11: 0000000000000008 R12: 0000000000000000
Sep 01 11:01:12 starbase-375 kernel: R13: 0000000000000001 R14: ffffffffc063c8c8 R15: ffffffffc063c8c8
Sep 01 11:01:12 starbase-375 kernel: FS:  0000770845e52240(0000) GS:ffff8f4aedf8e000(0000) knlGS:0000000000000000
Sep 01 11:01:12 starbase-375 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 01 11:01:12 starbase-375 kernel: CR2: ffff8f4aedf8e018 CR3: 000000010a4be001 CR4: 00000000003726f0
Sep 01 11:01:12 starbase-375 kernel: note: task UPID:starb[2011] exited with irqs disabled
Sep 01 11:01:14 starbase-375 pvesh[2008]: Starting VM 100 failed: unexpected status

I've also replicated the same oops on that machine with earlier patches of 7.0.14 and with 7.0.6-2-pve. The bug can also be reliably triggered by manually unbinding the adapter from the host.

I've attempted some investigating with the assistance of ChatGPT, which has suggested that there has been a change in aacraid unbind behaviour in 7.0 - it flagged a patch `scsi: aacraid: Fix reply queue mapping to CPUs based on IRQ affinity` from June 2025 as a possible cause, but wasn't able to determine that definitively.

For now I have pinned the kernel to 6.17 on that machine as passthrough is working with that hardware/kernel combination. I do have another (much newer) machine which does passthrough an Adaptec ASR-72405 HBA under 7.0.14 successfully, so there does seem to be some additional factors that trigger this bug

driley · Wednesday at 17:13

hi,
to help get to the bottom of this kernel oops, could you please run a few commands on the Proxmox host and share the output?

Please provide the output of the following:

The VM configuration:
Code:
```
cat /etc/pve/qemu-server/<vmid>.conf
```
The current PCI hardware and driver mappings:
Code:
```
lspci -nnk
```
Check the system journal from around the time of the crash:
Code:
```
journalctl
```
and add the relevant snippet.

exterrestris · Thursday at 11:25

VM config:

Code:

root@starbase-375:~# cat /etc/pve/qemu-server/100.conf
agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
efidisk0: local-zfs:vm-100-disk-0,efitype=4m,ms-cert=2023k,pre-enrolled-keys=1,size=1M
hostpci0: 0000:01:00.0,pcie=1,rombar=0
ide2: none,media=cdrom
machine: q35
memory: 12288
meta: creation-qemu=8.1.5,ctime=1757395073
name: memory-beta
net0: virtio=76:37:a8:cb:28:a1,bridge=vmbr1,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: local-zfs:vm-100-disk-1,size=120G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=86b298d1-cf78-4472-a5fa-43b34c223e55
sockets: 1
vmgenid: 127959d6-312b-48ba-8f56-e406b770fcf7

PCI hardware (on 7.0.14):

Code:

root@starbase-375:~# lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
        Kernel driver in use: skl_uncore
        Kernel modules: ie31200_edac
00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) [8086:1905] (rev 07)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
        DeviceName:  Onboard IGD
        Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
        Kernel driver in use: i915
        Kernel modules: i915
00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
        Subsystem: ASUSTeK Computer Inc. H110I-PLUS Motherboard [1043:8694]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
        Subsystem: ASUSTeK Computer Inc. H110I-PLUS Motherboard [1043:8694]
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31)
        Subsystem: ASUSTeK Computer Inc. H110I-PLUS Motherboard [1043:8694]
        Kernel driver in use: ahci
        Kernel modules: ahci
00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 [8086:a167] (rev f1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 [8086:a110] (rev f1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 [8086:a112] (rev f1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 [8086:a118] (rev f1)
        Subsystem: ASUSTeK Computer Inc. H110I-PLUS Motherboard [1043:8694]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1f.0 ISA bridge [0601]: Intel Corporation Z170 Chipset LPC/eSPI Controller [8086:a145] (rev 31)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31)
        Subsystem: ASUSTeK Computer Inc. H110I-PLUS Motherboard [1043:8694]
00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31)
        Subsystem: ASUSTeK Computer Inc. H110I-PLUS Motherboard [1043:8694]
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8672]
        Kernel driver in use: e1000e
        Kernel modules: e1000e
01:00.0 RAID bus controller [0104]: Adaptec Series 7 6G SAS/PCIe 3 [9005:028c] (rev 01)
        Subsystem: Adaptec Series 7 - ASR-72405 - 24 internal 0 external 6G SAS Port/PCIe 3.0 [9005:0503]
        Kernel modules: aacraid
02:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)
        Subsystem: Intel Corporation Ethernet Server Adapter X520-2 [8086:7a11]
        Kernel driver in use: ixgbe
        Kernel modules: ixgbe
02:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)
        Subsystem: Intel Corporation Ethernet Server Adapter X520-2 [8086:7a11]
        Kernel driver in use: ixgbe
        Kernel modules: ixgbe
04:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
        Subsystem: ASUSTeK Computer Inc. Device [1043:8696]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
05:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 04)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8489]
        Kernel modules: shpchp

On kernel 6.17 `aacraid` unbinds successfully and `vfio-pci` takes over:

Code:

01:00.0 RAID bus controller [0104]: Adaptec Series 7 6G SAS/PCIe 3 [9005:028c] (rev 01)
        Subsystem: Adaptec Series 7 - ASR-72405 - 24 internal 0 external 6G SAS Port/PCIe 3.0 [9005:0503]
        Kernel driver in use: vfio-pci
        Kernel modules: aacraid

The relevant journal snippet was posted in the original message.

As stated, I've run through a number of troubleshooting steps with the assistance of ChatGPT - these steps have fairly conclusively identified a change in the aacraid driver in kernel 7.0 as the cause. The full chat history with all the steps I performed, including output from a variety of diagnostic commands, is available at https://chatgpt.com/share/6a98679d-0244-83ed-be21-47ad58b9674c (publicly available)

driley · 2026-09-04T14:04:08+0200

Thanks for providing the additional information and yes you are right you have already provided the necessary snippet of the journal, sorry for that.

From the output of 'lspci -nnk' it seems like the 'aacraid' driver is currently only used by this RAID bus Controller, therefore I would like you to try the following:

Blacklist the driver so the host does not initialize it:
[CODE]vim.tiny /etc/modprobe.d/blacklist.conf[/CODE]
in this file add the following line:
Code:
```
blacklist aacraid
```
Update initramfs:
Code:
```
update-initramfs -u -k all
```
Reboot your host

After that please try to boot the virtual machine again and let me know if this resolved the issue for you.
Please also keep in mind that if you add another RAID Controller, which utilizes the same driver this workaround won't be feasible anymore if you are not planning on passing it through as well but rather would like to use it on the host.

Hope this helps.

exterrestris · 2026-09-04T19:18:08+0200

Blacklisting `aacraid` does not allow the VM to successfully start under `7.014.15-pve` - the VM is killed by oom-killer.

Code:

Sep 04 18:02:56 starbase-375 kernel: kvm invoked oom-killer: gfp_mask=0x140dc2(GFP_HIGHUSER|__GFP_ZERO|__GFP_COMP), order=0, oom_score_adj=0
Sep 04 18:02:56 starbase-375 kernel: CPU: 5 UID: 0 PID: 1592 Comm: kvm Tainted: P           O        7.0.14-15-pve #1 PREEMPT(lazy)
Sep 04 18:02:56 starbase-375 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
Sep 04 18:02:56 starbase-375 kernel: Hardware name: System manufacturer System Product Name/Z170-A, BIOS 3802 03/15/2018
Sep 04 18:02:56 starbase-375 kernel: Call Trace:
Sep 04 18:02:56 starbase-375 kernel:  <TASK>
Sep 04 18:02:56 starbase-375 kernel:  dump_stack_lvl+0x5f/0x90
Sep 04 18:02:56 starbase-375 kernel:  dump_stack+0x10/0x18
Sep 04 18:02:56 starbase-375 kernel:  dump_header+0x48/0x1c7
Sep 04 18:02:56 starbase-375 kernel:  oom_kill_process.cold+0x8/0x87
Sep 04 18:02:56 starbase-375 kernel:  out_of_memory+0x22f/0x4d0
Sep 04 18:02:56 starbase-375 kernel:  __alloc_frozen_pages_noprof+0x1529/0x1700
Sep 04 18:02:56 starbase-375 kernel:  alloc_pages_mpol+0x80/0x180
Sep 04 18:02:56 starbase-375 kernel:  vma_alloc_folio_noprof+0x6b/0xe0
Sep 04 18:02:56 starbase-375 kernel:  do_anonymous_page+0x36b/0x940
Sep 04 18:02:56 starbase-375 kernel:  ? __pte_offset_map+0x1c/0x130
Sep 04 18:02:56 starbase-375 kernel:  __handle_mm_fault+0xba4/0x1030
Sep 04 18:02:56 starbase-375 kernel:  handle_mm_fault+0x136/0x3a0
Sep 04 18:02:56 starbase-375 kernel:  __get_user_pages+0x7ef/0x1310
Sep 04 18:02:56 starbase-375 kernel:  __gup_longterm_locked+0x129/0x8c0
Sep 04 18:02:56 starbase-375 kernel:  ? vtdss_map_range+0x2a7/0x580
Sep 04 18:02:56 starbase-375 kernel:  pin_user_pages_remote+0x6a/0xe0
Sep 04 18:02:56 starbase-375 kernel:  vaddr_get_pfns+0xa2/0x2b0 [vfio_iommu_type1]
Sep 04 18:02:56 starbase-375 kernel:  vfio_pin_pages_remote+0xe4/0x540 [vfio_iommu_type1]
Sep 04 18:02:56 starbase-375 kernel:  vfio_iommu_type1_ioctl+0x14ec/0x1c20 [vfio_iommu_type1]
Sep 04 18:02:56 starbase-375 kernel:  vfio_fops_unl_ioctl+0x68/0x380 [vfio]
Sep 04 18:02:56 starbase-375 kernel:  __x64_sys_ioctl+0xa5/0x100
Sep 04 18:02:56 starbase-375 kernel:  x64_sys_call+0x103b/0x2390
Sep 04 18:02:56 starbase-375 kernel:  do_syscall_64+0x10b/0x14e0
Sep 04 18:02:56 starbase-375 kernel:  ? mod_memcg_lruvec_state+0xd7/0x1f0
Sep 04 18:02:56 starbase-375 kernel:  ? __x64_sys_ioctl+0xbf/0x100
Sep 04 18:02:56 starbase-375 kernel:  ? x64_sys_call+0x103b/0x2390
Sep 04 18:02:56 starbase-375 kernel:  ? do_syscall_64+0x148/0x14e0
Sep 04 18:02:56 starbase-375 kernel:  ? next_uptodate_folio+0x98/0x2d0
Sep 04 18:02:56 starbase-375 kernel:  ? filemap_map_pages+0x478/0x830
Sep 04 18:02:56 starbase-375 kernel:  ? do_fault+0x312/0x580
Sep 04 18:02:56 starbase-375 kernel:  ? __handle_mm_fault+0x9d5/0x1030
Sep 04 18:02:56 starbase-375 kernel:  ? count_memcg_events+0xeb/0x190
Sep 04 18:02:56 starbase-375 kernel:  ? handle_mm_fault+0x283/0x3a0
Sep 04 18:02:56 starbase-375 kernel:  ? do_user_addr_fault+0x1e7/0x820
Sep 04 18:02:56 starbase-375 kernel:  ? irqentry_exit+0xb2/0x710
Sep 04 18:02:56 starbase-375 kernel:  ? exc_page_fault+0x92/0x1c0
Sep 04 18:02:56 starbase-375 kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Sep 04 18:02:56 starbase-375 kernel: RIP: 0033:0x70f15926e91b
Sep 04 18:02:56 starbase-375 kernel: Code: Unable to access opcode bytes at 0x70f15926e8f1.
Sep 04 18:02:56 starbase-375 kernel: RSP: 002b:00007fff936aed00 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Sep 04 18:02:56 starbase-375 kernel: RAX: ffffffffffffffda RBX: 0000565aab0b2940 RCX: 000070f15926e91b
Sep 04 18:02:56 starbase-375 kernel: RDX: 00007fff936aed60 RSI: 0000000000003b71 RDI: 0000000000000026
Sep 04 18:02:56 starbase-375 kernel: RBP: 0000000100000000 R08: 0000000000000000 R09: 0000000000000000
Sep 04 18:02:56 starbase-375 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000280000000
Sep 04 18:02:56 starbase-375 kernel: R13: 0000565aab0b2940 R14: 0000000000000000 R15: 000070eec7e00000
Sep 04 18:02:56 starbase-375 kernel:  </TASK>
Sep 04 18:02:56 starbase-375 kernel: Mem-Info:
Sep 04 18:02:56 starbase-375 kernel: active_anon:166110 inactive_anon:3182270 isolated_anon:0
                                      active_file:81 inactive_file:45 isolated_file:0
                                      unevictable:8131 dirty:0 writeback:0
                                      slab_reclaimable:7310 slab_unreclaimable:39514
                                      mapped:4757 shmem:13114 pagetables:9591
                                      sec_pagetables:637 bounce:0
                                      kernel_misc_reclaimable:0
                                      free:488660 free_pcp:1456 free_cma:449338
Sep 04 18:02:56 starbase-375 kernel: Node 0 active_anon:664440kB inactive_anon:12729080kB active_file:324kB inactive_file:180kB unevictable:32524kB isolated(anon):0kB isolated(file):0kB mapped:19028kB dirty:0kB writeback:0kB shmem:52456kB shmem_thp:30720kB shmem_pmdmapped:0kB anon_thp:12374016kB kernel_stack:5824kB pagetables:38364kB sec_pagetables:2548kB all_unreclaimable? no Balloon:0kB
Sep 04 18:02:56 starbase-375 kernel: Node 0 DMA free:13308kB boost:0kB min:72kB low:88kB high:104kB reserved_highatomic:0KB free_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB zspages:0kB present:15980kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Sep 04 18:02:56 starbase-375 kernel: lowmem_reserve[]: 0 2103 15839 15839 15839
Sep 04 18:02:56 starbase-375 kernel: Node 0 DMA32 free:368256kB boost:0kB min:8312kB low:10388kB high:12464kB reserved_highatomic:0KB free_highatomic:0KB active_anon:332kB inactive_anon:1779740kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB zspages:0kB present:2221056kB managed:2154284kB mlocked:0kB bounce:0kB free_pcp:248kB local_pcp:248kB free_cma:305152kB
Sep 04 18:02:56 starbase-375 kernel: lowmem_reserve[]: 0 0 13735 13735 13735
Sep 04 18:02:56 starbase-375 kernel: Node 0 Normal free:1573076kB boost:26624kB min:85820kB low:100616kB high:115412kB reserved_highatomic:0KB free_highatomic:0KB active_anon:664104kB inactive_anon:10949340kB active_file:324kB inactive_file:180kB unevictable:32524kB writepending:0kB zspages:0kB present:14401536kB managed:14065180kB mlocked:0kB bounce:0kB free_pcp:5576kB local_pcp:500kB free_cma:1492200kB
Sep 04 18:02:56 starbase-375 kernel: lowmem_reserve[]: 0 0 0 0 0
Sep 04 18:02:56 starbase-375 kernel: Node 0 DMA: 1*4kB (U) 1*8kB (U) 1*16kB (U) 1*32kB (U) 1*64kB (U) 1*128kB (U) 1*256kB (U) 1*512kB (U) 0*1024kB 2*2048kB (UM) 2*4096kB (M) = 13308kB
Sep 04 18:02:56 starbase-375 kernel: Node 0 DMA32: 8*4kB (UM) 7*8kB (UME) 7*16kB (UME) 5*32kB (ME) 7*64kB (UME) 8*128kB (UME) 5*256kB (M) 5*512kB (ME) 6*1024kB (ME) 8*2048kB (MEC) 83*4096kB (UMC) = 368168kB
Sep 04 18:02:56 starbase-375 kernel: Node 0 Normal: 3*4kB (EC) 3*8kB (UE) 166*16kB (UME) 326*32kB (ME) 184*64kB (UME) 163*128kB (UMEC) 83*256kB (UMEC) 29*512kB (MEC) 0*1024kB 2*2048kB (C) 363*4096kB (C) = 1572804kB
Sep 04 18:02:56 starbase-375 kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Sep 04 18:02:56 starbase-375 kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Sep 04 18:02:56 starbase-375 kernel: 13233 total pagecache pages
Sep 04 18:02:56 starbase-375 kernel: 0 pages in swap cache
Sep 04 18:02:56 starbase-375 kernel: Free swap  = 0kB
Sep 04 18:02:56 starbase-375 kernel: Total swap = 0kB
Sep 04 18:02:56 starbase-375 kernel: 4159643 pages RAM
Sep 04 18:02:56 starbase-375 kernel: 0 pages HighMem/MovableOnly
Sep 04 18:02:56 starbase-375 kernel: 100937 pages reserved
Sep 04 18:02:56 starbase-375 kernel: 0 pages cma reserved
Sep 04 18:02:56 starbase-375 kernel: 0 pages hwpoisoned
Sep 04 18:02:56 starbase-375 kernel: Memory cgroup min protection 0kB -- low protection 0kB
Sep 04 18:02:56 starbase-375 kernel: Tasks state (memory values in pages):
...
Sep 04 18:02:56 starbase-375 kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=qemu.slice,mems_allowed=0,global_oom,task_memcg=/qemu.slice/100.scope,task=kvm,pid=1592,uid=0
Sep 04 18:02:56 starbase-375 kernel: Out of memory: Killed process 1592 (kvm) total-vm:13186016kB, anon-rss:12573872kB, file-rss:40kB, shmem-rss:0kB, UID:0 pgtables:24900kB oom_score_adj:0
Sep 04 18:02:56 starbase-375 systemd[1]: 100.scope: A process of this unit has been killed by the OOM killer.
Sep 04 18:02:56 starbase-375 systemd[1]: 100.scope: Failed with result 'oom-kill'.
Sep 04 18:02:56 starbase-375 systemd[1]: 100.scope: Consumed 1.539s CPU time, 12G memory peak.
Sep 04 18:02:56 starbase-375 systemd[1]: qemu.slice: A process of this unit has been killed by the OOM killer.
Sep 04 18:02:56 starbase-375 pve-guests[1561]: start failed: QEMU exited with code 1

Full boot log attached

exterrestris · 2026-09-04T19:38:19+0200

The host machine has 16 GB RAM, with 12 GB allocated to the VM, and there are no other VMs or any LXCs on this machine. As previously noted, this configuration works without issue under kernel 6.17.

Given the out-of-memory warning, I then tried reducing the VM allocation to 8 GiB which allowed the VM to start successfully. I was then able to increase the VM allocation to 10 GiB and still have the VM start successfully.

Wondering if the aacraid oops is related to this apparent memory issue under kernel 7.0, I then tried reducing the VM allocation to 8 GiB and removing the `aacraid` driver blacklist entry. This resulted in the same oops as previously reported.

As such, I have reverted to kernel 6.17 as this does not require the driver blacklist and allows for allocating 12 GiB of RAM to the VM.

Given this, it appears that not is there definitely a regression regarding `aacraid` in kernel 7.0, but that there are either higher minimum requirements for PVE9 with kernel 7.0 or another memory related regression in kernel 7.0

Kernel oops when passing through Adaptec ASR-72405 (aacraid) to VM on kernel 7.0+

exterrestris

New Member

driley

Proxmox Staff Member

exterrestris

New Member

driley

Proxmox Staff Member

exterrestris

New Member

Attachments

exterrestris

New Member

We value your privacy