Search results

@Richard Isted Thanks for confirming my hypothesis. In fact neither option is a proper fix, but workarounds. I was hoping someone would confirm the reserve works before I jumped to conclusions. My findings A recent patch introduced by 6.2 tries to reclaim memory back from bios at the early...

@Richard Isted are you sure you ran update-grub after that change and then rebooted the host? Looking at the second line of your dmesg shows that the boot params aren't present at all.

@Richard Isted I'm not sure if you need both lines, but regardless, could you attach your dmesg again?

Can you try adding reserve=0x80000000,0xfffffff to your GRUB_CMDLINE_LINUX and removing the pci=realloc=off and let me know if it works?

For those who are still having this issue under 6.2 and 6.5, can you post your full `dmesg`? I was having this issue and the fix had nothing to do with the driver, and it appears to be a memory reservation issue.

I also don't get output past `Loading initial ramdisk ...` message, although it seems to boot fine if I connect to it using SSH. A new (since 5.13) suspicious (and probably the culprit) message is also showing up: [ 12.307308] mgag200 0000:0e:01.0: vgaarb: deactivate vga console [...

Sorry for the necrobump, but I think this is relevant for the discussion. taskset will bond that process to the specified CPUs so they don't get executed by different threads. But that doesn't necessarily mean that those CPUs will be dedicated to that process (i.e. other VMs that haven't been...

I used to virtualize an instance of FreeNAS and passing through a SAS adapter is the only way to access the raw hard drives because ZFS doesn't work well with virtualization or RAID. Now I just installed FreeNAS on bare metal and virtualized my appliances with bhyve. Not perfect but it works.

@alexxedo Yes, unfortunately you either upgrade your hardware or give up on Proxmox with 5.4+ kernels. I even ended up automating the build process for 5.3 so you wouldn't need to recompile it manually every time - but then unfortunately 5.4 came and I had to give up on Proxmox. Here's the...

Sure, boot: c bootdisk: ide0 cores: 8 cpu: host hostpci0: 05:00.0 ide0: local-lvm:vm-100-disk-0,size=8G memory: 10240 name: FreeNAS net0: virtio=CA:1C:4D:69:1F:0E,bridge=vmbr0,firewall=1 numa: 0 onboot: 1 ostype: other scsihw: virtio-scsi-pci smbios1: uuid=f67b4b42-110a-4c07-9fb5-c101ea37a230...

HI @t.lamprecht , Thanks for the support. I've tried both solutions you suggested, but none has effectively worked. I've also opened a new thread here: https://forum.proxmox.com/threads/kernel-5-4-error-when-attempting-to-start-a-vm-with-passthrough.67579/

On the new 5.4 kernel, launching an instance with a PCI passthrough device fails with the following error: kvm: -device vfio-pci,host=0000:05:00.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: VFIO_MAP_DMA: -22 kvm: -device vfio-pci,host=0000:05:00.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0...

Hello, I'm using a HP Microserver Gen8 and I'm facing this issue when I upgraded to 5.4. These are the logs I get when I try to start a VM with a passed through device: kvm: -device vfio-pci,host=0000:05:00.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: VFIO_MAP_DMA: -22 kvm: -device...