Search results

  1. R

    WARNING: unable to connect to VM 100 socket - timeout after 31 retries

    Yes there is no permanent fix for this issue till now in 5 version..only reboot will fix this issue.
  2. R

    WARNING: unable to connect to VM 100 socket - timeout after 31 retries

    Just reboot/shutdown base node on which this VM resides & it will automatically fix this issue.
  3. R

    100VMs 4VCPUs/8GB/500G required on premises

    Thanks a lot Mr. ozdjh for such valuable information. It helped me a lot.
  4. R

    100VMs 4VCPUs/8GB/500G required on premises

    Can any one suggest (complete HA cluster with pveceph) hardware/network requirement to get 100 VMs with configuration 4VCPUs/8GB/500G.
  5. R

    Feature suggestion: Option to set "auto live migration"

    If you are going to implement this feature, it would be great & fantastic move for gaining more popularity among VMware/Citrix lovers & they will definitely migrate to Proxmox.
  6. R

    help needed to enable multicast

    I have resolved my issue. echo 0 > /sys/class/net/vmbr0/bridge/multicast_snooping Disabled multicast-snooping & Voillaaa its automatically joined cluster without restarting corosync service. it is stable in cluster now.
  7. R

    help needed to enable multicast

    I have 11 node cluster, with one of them is connected to trunk port of cisco switch igmp enabled. All nodes remain in quorum but only one node connected to trunk port of cisco switch get out of quorum after 2-5 mins. I have to restart corosync service then it again comes in cluster quorum...
  8. R

    node restart and automatically migrate VM's (HA)

    Hello Proxmoxians:) +1 from my side as well surely there is no mean of HA if vms get rebooted:oops:
Top Bottom