thanks, I was looking thru the logs and found this;
Found a thread in the forum on this warning.. but not sure its in the
same context as I'm following but it might. As far a memory, well guess
stranger things have happened.. I have upped memory allocation to my
each of my VMs.
(I'm thinking this is just errors from the underlying issue.)
Nov 23 18:31:45 proliant02 pmxcfs[3128]: [status] notice: received log
Nov 23 18:46:45 proliant02 pmxcfs[3128]: [status] notice: received log
Nov 23 19:01:45 proliant02 pmxcfs[3128]: [status] notice: received log
Nov 23 19:16:45 proliant02 pmxcfs[3128]: [status] notice: received log
Nov 23 19:17:01 proliant02 /USR/SBIN/CRON[261314]: (root) CMD ( cd /
&& run-parts --report /etc/cron.hourly)
Nov 23 19:17:24 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 124 socket - timeout after 31 retries
Nov 23 19:17:27 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 104 socket - timeout after 31 retries
Nov 23 19:17:30 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 142 socket - timeout after 31 retries
Nov 23 19:17:33 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 139 socket - timeout after 31 retries
Nov 23 19:17:36 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 107 socket - timeout after 31 retries
Nov 23 19:17:39 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 116 socket - timeout after 31 retries
Nov 23 19:17:42 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 154 socket - timeout after 31 retries
Nov 23 19:17:45 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 106 socket - timeout after 31 retries
Nov 23 19:17:48 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 100 socket - timeout after 31 retries
Nov 23 19:17:51 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 138 socket - timeout after 31 retries
Nov 23 19:17:54 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 111 socket - timeout after 31 retries
Nov 23 19:17:57 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 153 socket - timeout after 31 retries
Nov 23 19:18:00 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 109 socket - timeout after 31 retries
Nov 23 19:18:03 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 171 socket - timeout after 31 retries
Nov 23 19:18:06 proliant02 pvestatd[3666]: WARNING: unable to connect to
VM 113 socket - timeout after 31 retries
Nov 23 19:18:15 proliant02 kernel: BUG: soft lockup - CPU#22 stuck for
67s! [ksmd:265]
On 11/25/2014 11:07 AM, Michael Rasmussen wrote:> On Tue, 25 Nov 2014
10:55:17 -0500
> David Lawley <da...@upilab.com> wrote:
>
>>
>> Asking for a nudge in the right direction bad guest, bug in kvm, and
>> even read something about possible cpu voltage issue.
>>
> Bad memory could also be causing this.
>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
On 11/25/2014 11:07 AM, Michael Rasmussen wrote:
On Tue, 25 Nov 2014 10:55:17 -0500
David Lawley <da...@upilab.com> wrote:
Asking for a nudge in the right direction bad guest, bug in kvm, and
even read something about possible cpu voltage issue.
Bad memory could also be causing this.
_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
