Search results

  1. A

    [SOLVED] Windows server 2019

    But there's no special 2k19 in 164 as well.
  2. A

    [SOLVED] Windows server 2019

    Confirmed here as well. Using virtio 1.160 and windows 2k16 drivers.
  3. A

    PVE 5.2: netlink: 'ovs-vswitchd': attribute type 5 has an invalid length.

    Any news on this one? I see the same error in Proxmox 5.2-2 (upgraded from 4.4). pve-manager/5.2-9/4b30e8f9 (running kernel: 4.15.18-5-pve) IDK if it is related, but after an upgrade I get terrible migration speed (28-40MB/s) over 10Gbps with openvswitch. Before that it was 400-500MB/s. And...
  4. A

    Expand VM disk on LVM (on ISCSI SAN multipath): error *FROM GUI*, OK from CLI

    Old thread, but came across this problem today. I just had to start the VM, because otherwise the LVM was not seen by my host. After a VM start, resize was possible.
  5. A

    LDAP authentication with non-anonymous bind

    Thanks! Will try it out in a couple of months, when upgrading to Proxmox 4.0!
  6. A

    LDAP authentication with non-anonymous bind

    Pvedaemon restart helps to re-read LDAP.pm file service pvedaemon restart And it does not affect VMs.
  7. A

    LDAP authentication with non-anonymous bind

    Hi! I can confirm that the bind patch is working. But getting authentication from LDAP requires node reboot. I tried restarting three services, but it did not help. service pve-cluster restart && service pve-manager restart && service pveproxy restart After a reboot, Proxmox binded LDAP...
  8. A

    LDAP authentication with non-anonymous bind

    Hi! I could use it too. Any news on submitting this to git? What services do I need to restart if I apply this patch manually? I restarted only pveproxy, but this did not help. I edited /etc/pve/domains.cfg file, added bind_dn and bind_pw.
Top Bottom