Recent content by blackangus

Sorry for the delay on this, I've been dealing with an issue for a while that turned out to be related to this topic :( FWIW anyone seeing this thread or wondering if/how to use resizable bar: watch out using it (at least with AMD cards) for now...

Yes that's right. I have things mostly working, the only issue is resizing bar 2 to it's max size. I'm able to successfully boot and use the VM (Windows 11 FWIW) with the gpu passed through when bar 0 is set to its maximum size. I'll check the kernel log later this week when I get a chance to...

Thanks for the info. I've tried the args approach you mentioned a few days ago but it didn't have any effect. My educated guess was that the xmlns was not taking effect since it was not set anywhere. Sorry, I should have been more explicit in my post and said the xmlns attribute is the key part...

I've been trying to get resizable bar (SAM for me) enabled in a Windows guest using a passed-through 6950 XT. While this is mostly working (I think) there are some snags I'm running into. See https://github.com/qemu/qemu/commit/3412d8ec9810b819f8b79e8e0c6b87217c876e32#commitcomment-112438130...

I can confirm 5.15-17-1 breaks PCIe GPU passthrough due to resizeable bar issues. Dmesg is filled with a massive amount of errors about not being able to reserve addresses. I'd share the logs but I don't have them at the moment, I had to go back to 5.13 in order to get my stuff up and running...

Sorry, please ignore my previous post. I just found a bunch of corruption in my ZFS pool :) Will post back here if it still happens after recovering from that. I'm pretty sure there's no issue with PVE or PBS at this point.

I'm not sure if it's a coincidence or not, but since I've upgraded to this new version I am getting constant failures when trying to back up my VMs (scheduled or manually triggered). The failures are always due to "operation cancelled", but no one and/or nothing should be cancelling them. I just...

Any idea when the fix might get pushed out to the public?

I posted a bug I found but I'm pretty sure it has gotten lost in the sea of new threads from 7.1 coming out :) Figured I'd share it here so it doesn't get lost https://forum.proxmox.com/threads/bug-report-android-app-unable-to-work-with-vms-where-the-os-type-is-microsoft-windows-11-2022.99822/

Looks like a small/easy one to fix. As soon as you tap on a VM in the app which has this OS type it throws up an error about deserializing. The exact error message is: "failed due to: Deserializing 'win11' to 'OSType' failed due to: Invalid argument(s): win11

Ignore my comment about KSM. I didn't wait enough time for it to kick in and scan through the pages. Seems like it needed an hour or so. I still can't find the reason for guest CPU usage not being reported though...

Also, it looks like KSM is now off by default...?

I just moved to 5.11 and noticed that the CPU counter for "guest" has stopped working. I have a telegraf + grafana setup which is where I first saw this but looking at /proc/stat shows all the values for guest usage at 0. Does anyone else see the same behavior?

Thanks! That helps :)

Hey all, Wanted to see if anyone has run into this before: https://github.com/openzfs/zfs/issues/11787 I'm assuming it's purely a ZFS issue but wasn't totally sure since the ZFS version is very much tied to Proxmox (2.0.3-pve2) Could any moderators confirm what is different/special in the...