Recent content by FingerlessGloves

I'll take a look at those profiles when I get some time to do some indepth testing :)

Detected nodes: virt-1 | 10.11.17.11 | x86-64-v4 virt-2 | 10.11.17.12 | x86-64-v4 virt-3 | 10.11.17.13 | x86-64-v4 Cluster CPU type: x86-64-v4 Good point with the nested virt but that would probably break the VBS security stuff sadly, I think it needs those instruction sets

I have a Gold 6248R, which if I run `/usr/lib64/ld-linux-x86-64.so.2 --help` returns supported for x86-64-v4, but when I tried using it in 2025 and I think 2022, it crashes lockups. Not sure if there's a upcoming fix for the issue from qemu or not, for now I'm setting all VMs to x86-64-v3, so...

It's EL9 I'm trying to network boot and then use kickstart to build the VM. I think the fix it to temporarily disable hotplug and add it back, which is fine because I'm using ansible to full automate the VM deployment. But it would be nice to be able to specify the base memory. It's the initial...

I've been trying to workout why with Memory Hotplug enabled, I can not PXE boot a distro installer, even if I have 16GB of memory set with no ballooning. Soon as I turn off hotplug it works no problem. I've tried adding `memhp_default_state=online` to the kernel line of installer which uses...

I can connect using anonymous bind to the same server in Proxmox VE, with no bind user required. I'm trying to connect PDM to the same AD servers specified in PVE. I have users logging in using the Windows AD realm just fine too on PVE Screenshots from PVE

I've just tried to add a Windows AD Realm via the UI and using Anonymous Search, getting an API error. Are we still waiting a bug fix for this? I also see someone mentioned about supporting non Case-Sensitive? I have done an apt dist-upgrade just now to make sure I'm up to date

Hi Shanreich, It's the issue was a mixure of two issues, the cards and the Mikrotik Switches. On Proxmox I have to do add a postup for the vlan offload, otherwise I've found sometimes the VLANs on a bridge don't work at all, it's not very consistent but turning off the offload fixes it...

Just had this problem on my Proxmox Cluster also using HP Gen 10, x86‑64‑v4 to x86‑64‑v3 fixed it.

Did you create a enhancement request? I commented on one but just realised it was for OVA, not the ESXi guest importer https://bugzilla.proxmox.com/show_bug.cgi?id=6113 Not having a pool option also means you need someone with full permissions to create VMs outside of pool to migrate a ESXi...

The management interface is working on each host and that's never had a problem. No firewall are configured on the Proxmox hosts. VM is configured as `virtio=00:1a:4a:4c:72:72,bridge=vmbr0,tag=103` as I wanted to rule out the sdn bridges being the issue. What I have noticed, is using the VM...

Working system https://paste.n9.uk/?3f742395b8606f43#2JkUfxBhEpEviBK3gD9SbEahNK6YWEfE4oHxCJHKm8Re Non working https://paste.n9.uk/?d068f772f5c37401#HUzenbr8oJXLGApxEQr1XEqsmbeSjteFMpbFBZEGHnrn Text was too long to post here I can't see any differences bar the ones you'd expect like IPs and MACs

I've got a BCM57504 connected to two upstream switches using a 802.3ad bond and then off that bond I have vmbr0. Then I have vmbr0.108 for the management interface and then I have SDN configured, to create bridges on top of that bridge for each network I want to use in VMs. I have 3 identical...

Where did you get too with this, I'm wondering if my i226 dual port card is causing the C3 being max state. I wonder if the card in have is using a PCIe switch chip perhaps which is why it can't reach other states. Little hard to debug when the server is in a colocation.

https://bugzilla.proxmox.com/show_bug.cgi?id=7312