Recent content by CRCinAU

Thanks @fabian and the Proxmox team for these. These problems have been coming so thick and fast that its getting harder and harder to just keep up with what's happening. It's at the point now that if you have a server with an uptime of a week, it has several vulnerabilities.... Things are...

https://app.opencve.io/cve/CVE-2026-53359 This won't get fixed in the 7.0.x kernel tree, but is fixed in kernel versions: * 6.1.177 * 6.6.144 * 6.12.95 * 6.18.38 * 7.1.3 * 7.2-rc1 Reference: https://lore.kernel.org/linux-cve-announce/2026070403-CVE-2026-53359-4f57@gregkh/T Wondering what the...

Just to follow this up, things have been 100% stable since adding `iommu=pt` to the kernel command line.

Ah, I didn't see that at all. That being said, I'm struggling to get my head around how it would actually function. I can see how to represent the information I already have - but I'm not sure how I would discover how to create this if I hadn't already used Claude to give me a custom...

I was messing around today with the CPU types that I'm telling QEMU to use. My home lab is a couple of repurposed Ryzen CPUs: 1 x AMD Ryzen 7 3700X 8-Core Processor (1 Socket) 1 x AMD Ryzen 7 5700G with Radeon Graphics (1 Socket) I've been looking at the CPU flags available across both CPUs...

Hi @fabian , Thanks for the reply. I'm actually starting to think that it was the removal of the `iommu=pt` from the kernel command line that was causing the failure. This system has been built for quite some time - and that was in there for a while - and I don't know why. I don't recall what /...

Thanks - this mainboard is an MSI X570-A PRO (MS-7C37) with BIOS version H.P1. Looking here, it seems to be a couple of versions out of date: https://www.msi.com/Motherboard/X570-A-PRO/support I have another system with only an NVMe drive, that's a Gigabyte mainboard, and that seems to run...

I'm in the middle of troubleshooting this. I was doing a smart test on my nvme drive (Seagate FireCuda 510 SSD ZP500GM30001) when the drive went unresponsive. dmesg showed errors like: [ 337.272885] nvme nvme0: I/O tag 757 (12f5) opcode 0x2 (I/O Cmd) QID 2 timeout, aborting req_op:READ(0)...

Ah - I should note that when I unblocked the IPv6 access to the master DNS server, everything worked as it should - so this issue is purely around the fallback to IPv4 address.

Trying to get a Let's Encrypt cert via the ACME nsupdate plugin and it's failing with FORMERR. TSIG key works fine if I run nsupdate by hand against the same server, so it's not an auth or ACL issue. Versions: libproxmox-acme-perl 1.7.1 libproxmox-acme-plugins 1.7.1 Proxmox...

Understood. Added: https://bugzilla.proxmox.com/show_bug.cgi?id=7436 fwiw, the bugzilla has a current issue: Software error: Insecure directory in $ENV{PATH} while running with -T switch at /usr/share/perl5/Sys/Hostname/Long.pm line 82. For help, please send mail to the webmaster...

Is it possible to add to the roadmap to have a single, static, unpackaged binary for both x86_64 and aarch64 architectures for download? This would allow the client to be used much easier on a much wider set of systems.

Hi all, I haven't been able to find any information on backing up a machine that is not a VM to the PBS installation. I'm trying to back up everything from an embedded board that is aarch64 running Fedora 43. Is there a static binary download somewhere that is distributed for these cases?

Interesting. I'll consider it a false alarm then hahaha... I was kinda looking forward to tinkering.

I have a Ryzen 7 3700X - which seems to say it supports SEV: flags : ..... sev sev_es $ cat /run/qemu-server/host-hw-capabilities.json { "amd-sev": { "cbitpos": 47, "reduced-phys-bits": 5, "sev-support": true, "sev-support-es": true, "sev-support-snp": false } } When I try to...