Hi,
I have PVE environment running 2 VMs, Ubuntu and TrueNAS scale. The Scale VM had a LSI HBA passed through to it. I have since moved my disks over to the onboard SATA controller, so removed the HBA from the system and unmapped it, but the VM will no longer boot, and gives an "Internal Error".
Behaviour is:
When it boots correctly:
Any help would be much appreciated - is this a PVE error or a TrueNAS error?
Thanks!
I have PVE environment running 2 VMs, Ubuntu and TrueNAS scale. The Scale VM had a LSI HBA passed through to it. I have since moved my disks over to the onboard SATA controller, so removed the HBA from the system and unmapped it, but the VM will no longer boot, and gives an "Internal Error".
Behaviour is:
- No HBA installed - internal error
- LSI HBA installed and passed through - VM Boots
- Replacing HBA with an AsMedia SATA HBA - internal error
Code:
Jan 26 14:02:28 pve pvedaemon[2978]: VM 103 started with PID 2996.
Jan 26 14:02:28 pve pvedaemon[1697]: <root@pam> end task UPID:pve:00000BA2:000052BB:67964071:qmstart:103:root@pam: OK
Jan 26 14:02:29 pve QEMU[2996]: kvm: vfio-pci: Cannot read device rom at 0000:00:02.0
Jan 26 14:02:29 pve QEMU[2996]: Device option ROM contents are probably invalid (check dmesg).
Jan 26 14:02:29 pve QEMU[2996]: Skip option ROM probe with rombar=0, or load from file with romfile=
Jan 26 14:02:29 pve kernel: vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xcd82
Jan 26 14:02:45 pve QEMU[2996]: error: kvm run failed Bad address
Jan 26 14:02:45 pve QEMU[2996]: RAX=ffffa9068010ab60 RBX=ffff9bff520adf00 RCX=0000000000000018 RDX=ffff9bff501dee00
Jan 26 14:02:45 pve QEMU[2996]: RSI=ffff9bff68c1ca28 RDI=000000000000000b RBP=ffff9bff501deea4 RSP=ffffa90680108f58
Jan 26 14:02:45 pve QEMU[2996]: R8 =0000000000000000 R9 =0000000000000000 R10=0000000000000000 R11=ffffa90680108ff8
Jan 26 14:02:45 pve QEMU[2996]: R12=0000000000000000 R13=000000000000000b R14=ffff9bff501dee00 R15=0000000000000000
Jan 26 14:02:45 pve QEMU[2996]: RIP=ffffffffc04231c6 RFL=00010086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
Jan 26 14:02:45 pve QEMU[2996]: ES =0000 0000000000000000 ffffffff 00c00000
Jan 26 14:02:45 pve QEMU[2996]: CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
Jan 26 14:02:45 pve QEMU[2996]: SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
Jan 26 14:02:45 pve QEMU[2996]: DS =0000 0000000000000000 ffffffff 00c00000
Jan 26 14:02:45 pve QEMU[2996]: FS =0000 0000000000000000 ffffffff 00c00000
Jan 26 14:02:45 pve QEMU[2996]: GS =0000 ffff9c02afc40000 ffffffff 00c00000
Jan 26 14:02:45 pve QEMU[2996]: LDT=0000 0000000000000000 ffffffff 00c00000
Jan 26 14:02:45 pve QEMU[2996]: TR =0040 fffffe5b369e8000 00004087 00008b00 DPL=0 TSS64-busy
Jan 26 14:02:45 pve QEMU[2996]: GDT= fffffe5b369e6000 0000007f
Jan 26 14:02:45 pve QEMU[2996]: IDT= fffffe0000000000 00000fff
Jan 26 14:02:45 pve QEMU[2996]: CR0=80050033 CR2=00005620b7a26788 CR3=00000001683fa000 CR4=000006e0
Jan 26 14:02:45 pve QEMU[2996]: DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
Jan 26 14:02:45 pve QEMU[2996]: DR6=00000000ffff0ff0 DR7=0000000000000400
Jan 26 14:02:45 pve QEMU[2996]: EFER=0000000000000d01
Jan 26 14:02:45 pve QEMU[2996]: Code=1e fa 0f 1f 44 00 00 48 8b 86 80 01 00 00 48 05 60 03 00 00 <8b> 00 83 e8 01 83 f8 fd 0f 87 fd 00 00 00 41 57 49 89 f7 41 56 41 55 41 54 55 53 48 83 ecWhen it boots correctly:
Code:
Jan 26 13:42:17 pve pve-guests[1861]: VM 103 started with PID 1951.
Jan 26 13:42:18 pve QEMU[1951]: kvm: vfio-pci: Cannot read device rom at 0000:00:02.0
Jan 26 13:42:18 pve QEMU[1951]: Device option ROM contents are probably invalid (check dmesg).
Jan 26 13:42:18 pve QEMU[1951]: Skip option ROM probe with rombar=0, or load from file with romfile=
Jan 26 13:42:18 pve kernel: vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xcd82
Jan 26 13:42:21 pve pve-guests[1726]: <root@pam> end task UPID:pve:000006C2:00000667:67963BB1:startall::root@pam: OK
Jan 26 13:42:21 pve systemd[1]: Finished pve-guests.service - PVE guests.
Jan 26 13:42:21 pve systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler...
Jan 26 13:42:21 pve pvescheduler[2078]: starting server
Jan 26 13:42:21 pve systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.
Jan 26 13:42:21 pve systemd[1]: Reached target multi-user.target - Multi-User System.
Jan 26 13:42:21 pve systemd[1]: Reached target graphical.target - Graphical Interface.
Jan 26 13:42:21 pve systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
Jan 26 13:42:21 pve systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Jan 26 13:42:21 pve systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
Jan 26 13:42:21 pve systemd[1]: Startup finished in 27.660s (firmware) + 6.558s (loader) + 6.340s (kernel) + 22.572s (userspace) = 1min 3.132s.Any help would be much appreciated - is this a PVE error or a TrueNAS error?
Thanks!
Last edited:
