Search results

  1. J

    a lvm global_filter related boot issue

    I changed the filter to: global_filter=["r|WDC|", "r|TOSHIBA|", "r|/dev/zd.*|", "r|/dev/mapper/.*|"] then it boots without issue, so this is a viable workaround. But I guess that's still a bug in lvm?
  2. J

    a lvm global_filter related boot issue

    I have a custom global_filter set in lvm.conf like this: global_filter=["a|M4-CT064M4SSD2|", "r|.*|"] Basically I have quite a lot of physical disks, and some of them were spun down most of the time, I don't want to accidentally wake them up by lvm, and white listing the only disk I have lvm on...
  3. J

    [SOLVED] GPU Passthrough with Ryzen

    Sorry to revive an old thread but I'd like to report vendor-reset did solve the code 43 issue with Vega56 here. One thing I'd like to add is that I didn't succeed in the 1st try, then I noticed this quote from vendor-reset: I had the vm set to start on boot, so it's already non-recoverable...
  4. J

    GPU Passthrough Not working in Proxmox VE 6

    I have two VMs, each with a 1070 pass-through, upgrading from 5.4 to 6 0 broke it, I've tried both workarounds, kernel_ireqchip=on or pc-q35-3.1, none of them works, it crashes as soon as the GPU driver gets loaded. update: I upgraded to 6.0-7 and pc-q35-3.1 works now.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!