Search results

a node (pve-3,172.16.2.3) is marked as questioned in web UI. what is found: 1. ssh to the node is ok, and vm is not dead, can be migrate to other node with [qm migrate --live] command. 2. restart pveproxy service did not fix the problem. 3. access to the node's ui(https://172.16.2.3:8006) is ok...

when our pve nodes expanded from 3 to 5, the IO issue on target pbs goes much worse. (sometimes a small mount of VMs backup will failed)

just migrate a windows 2003 server from esxi to pve, using this article to prepare. (other methods I found all leads to 0x0000007b bsod) https://backdrift.org/converting-windows-guests-from-vmware-esx-to-kvm-with-virtio-drivers

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

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...

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

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...

@sublightnova , need btrfs file system on nfs server.

thank you, this is the real solution currently.

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...

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:~#...

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

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...