Search results

  1. K

    turned off VM still respond to ping and SSH

    thanks. is my fault. I moved 200.conf to 120.conf before.
  2. K

    turned off VM still respond to ping and SSH

    here it is: root@pve-1:~# ping 172.16.2.20 PING 172.16.2.20 (172.16.2.20) 56(84) bytes of data. 64 bytes from 172.16.2.20: icmp_seq=1 ttl=64 time=0.084 ms 64 bytes from 172.16.2.20: icmp_seq=2 ttl=64 time=0.098 ms 64 bytes from 172.16.2.20: icmp_seq=3 ttl=64 time=0.082 ms 64 bytes from...
  3. K

    turned off VM still respond to ping and SSH

    @spirit , both 2 nodes have no vm 120 running.
  4. K

    turned off VM still respond to ping and SSH

    I met this same issue, config: 2 pve node cluster (v7.2.4) the ip of vm (in node 1) is pingable even it's power off (conformed in shell), from switch and arp table confirmed the icmp respond is from node 1, and no other vm have same MAC address. no other vm is configured with the ip address...
  5. K

    Permssion denied (os error 13) on NFS share

    @sublightnova , need btrfs file system on nfs server.
  6. K

    Permssion denied (os error 13) on NFS share

    thank you, this is the real solution currently.
  7. K

    dead node could not be remove

    I've delete /etc/pve/nodes/pve-03 & restart pve-cluster/pvedaemon, still no luck. the dead node is still in the web console. and Votequorum vote still seeking the dead node 'pve-03'. root@pve-04:/etc/pve/nodes# pvecm nodes Membership information ---------------------- Nodeid Votes...
  8. K

    dead node could not be remove

    a new node just gone dead because of HDD corruption. (could not load pve OS after reboot) I can NOT find the node in terminal, (have NOT issue "pvecm delnode" command yet). but web admin console the dead node is still there. (pve-03 is dead) is there anything I can do? thanks. root@pve-01:~#...
  9. K

    create container all failed

    :oops: yes. which user should I add to the folder? thank you.
  10. K

    create container all failed

    Hi all, my pve can not create container from template now, it was ok before. have 2 proxmox , and mounted nfs share as container template / vm folder. have tried: 1. do dist-upgrade 2. reboot pve 3. check read/write permission (create txt file from proxmox terminal to nfs share folder...