Recent content by czechsys

Hi, currently are our VMs network dualstack mainly. Only very small number of them is ipv6 only. The problem is currently detected on the dualstack VMs on the PVE 8.4. When doing manual offline migration (gui or ha-manager), some migrated VM's ipv6 doesn't work after boot. When doing automatic...

Busy database with huge number of the cpu cores? Solution: 1] disable HT or 2] don't overallocate nonHT cores to VM+PVE The HT cores aren't for busy/fast/etc workloads, but for idle/low workloads mainly (so you can overallocate low power VMs).

Test it with live iso (debian, ubuntu),

Apples and oranges. You are comparing PRODUCT (based on the debian + ubuntu) with pure OS (debian).

PVE (9.1.1): domains.cfg: ad: SUB.EXAMPLE.ORG comment AD authentication domain sub.example.org server1 fqdn1 base_dn DC=sub,DC=example,DC=org case-sensitive 1 default 1 mode ldaps server2 fqdn2 user.cfg...

AD realm is created manually in domains.cfg. This works Editing via gui "Sync options" failing. "Sync" via gui Realms failing - unedited error message: 2025-12-10T10:53:48+01:00: this is a DRY RUN - changes will not be persisted 2025-12-10T10:53:48+01:00: TASK ERROR: LDAP operation result: rc=1...

Any option to have "cluster name" or alias for cluster in remotes? Having cluster hidden under hostname is little confusing...

With manual "base-dn" configuration and any change in the "Sync Options" api error (status = 400: Could not search LDAP realm, base_dn could be incorrect: LDAP operation result: rc=1 (operationsError), dn: "", text: "00002020: Operation unavailable without authentication": rc=1...

Adding domains.cfg with "base-dn" works. But with "base_dn" don't: api error (status = 400: parsing "/etc/proxmox-datacenter-manager/access/domains.cfg" failed: line 2 - unknown property 'base_dn') The returned error in the first post use "base_dn". Next, in the "Sync options", when trying...

Hi, those bars are bad readable. Can you please think about better coloring schema to differentiate usage? I am not blind but in the first two it hardly to see some orange spikes or so. is

Hi, trying to add AD realm with anonymous search (without bind user): api error (status = 400: Could not search LDAP realm, base_dn could be incorrect: LDAP operation result: rc=1 (operationsError), dn: "", text: "00002020: Operation unavailable without authentication": rc=1 (operationsError)...

Why PDM use by default nicX variant as network interface name instead ensX as PMG, pve VMs etc? When trying to add AD server, it doesn't work in anonymous mode - but almost the same PVE gui configuration is working, only one difference is a field for base_dn.

Your SAN and iscsi_* are on the same vlan, so if you can't ping, your L2 doesn't work. Check tcpdump for arp and fix firewall/network config.

It looks as https://forum.proxmox.com/threads/test-migration-stuck.168776/

Really HP G6 (super old server) and SSD? DId you even tested disk performance on the host?