Hi all,
we have a problem on one of our VMs. This VM was not reachable on this moment. Thirst after stop and start it works back fine.
In node log we found only the entrys:
KVM VM has 16 GB RAM and 3 sockets with 4 cores.
Any idea? Best reagrds
we have a problem on one of our VMs. This VM was not reachable on this moment. Thirst after stop and start it works back fine.
In node log we found only the entrys:
Code:
Oct 18 12:25:18 titan pvedaemon[3358]: WARNING: unable to connect to VM 5134 socket - timeout after 31 retries
Oct 18 12:25:19 titan pvestatd[3380]: WARNING: unable to connect to VM 5134 socket - timeout after 31 retries
Oct 18 12:25:28 titan pvedaemon[3360]: WARNING: unable to connect to VM 5134 socket - timeout after 31 retries
Oct 18 12:25:29 titan pvestatd[3380]: WARNING: unable to connect to VM 5134 socket - timeout after 31 retries
Oct 18 12:25:34 titan pvedaemon[297689]: WARNING: VM still running - terminating now with SIGTERM
Oct 18 12:25:39 titan pvedaemon[3359]: WARNING: unable to connect to VM 5134 socket - timeout after 31 retries
Oct 18 12:25:39 titan pvestatd[3380]: WARNING: unable to connect to VM 5134 socket - timeout after 31 retries
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu0 unhandled rdmsr: 0xc001100d
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu0 unhandled rdmsr: 0xc0010112
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu0 unhandled rdmsr: 0xc0010001
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu1 unhandled rdmsr: 0xc001100d
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu2 unhandled rdmsr: 0xc001100d
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu3 unhandled rdmsr: 0xc001100d
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu4 unhandled rdmsr: 0xc001100d
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu5 unhandled rdmsr: 0xc001100d
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu6 unhandled rdmsr: 0xc001100d
Oct 18 12:26:13 titan kernel: kvm: 297839: cpu7 unhandled rdmsr: 0xc001100d
KVM VM has 16 GB RAM and 3 sockets with 4 cores.
Any idea? Best reagrds