Yeah, the Dom0 should have plenty of memory left since only 2-3 GB of memory is being used out of 12 GB installed. The out of memory messages were from the domU that I xm consoled into prior to shutting down that particular VM because it was out of memory.<br>
<br>Matt<br clear="all"><br>--<br>Mathew S. McCarrell<br>Clarkson University '10<br><br><a href="mailto:mccarrms@gmail.com">mccarrms@gmail.com</a><br><a href="mailto:mccarrms@clarkson.edu">mccarrms@clarkson.edu</a><br>
<br><br><div class="gmail_quote">On Wed, Apr 29, 2009 at 3:09 PM, Maros Timko <span dir="ltr"><<a href="mailto:timkom@gmail.com">timkom@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Hi Mathew,</div><div><br></div>I would say no. Our system has freezed completely, it did not reboot. Our issue was caused by concurrent access to scheduler method that created a deadlock.<div>I can see some out of memory messages, do you still have enough memory for Dom0?<br>
<br><div class="gmail_quote">2009/4/29 Mathew S. McCarrell <span dir="ltr"><<a href="mailto:mccarrms@gmail.com" target="_blank">mccarrms@gmail.com</a>></span><div><div></div><div class="h5"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hey,<br><br>I'm wondering if it is possible that your problem is related to mine. Earlier today I had to restart one of our domUs on one of our systems. I used xm shutdown instead of xm destroy and then did xm list to determine if the domU had shutdown or not. Upon issuing xm list a second time, the entire server crashed and rebooted. <br>
<br>I've checked the logs and have yet to find anything. I've attached a transcript of the commands as I executed them on the server. The system is running CentOS 5.3 x64 w/Xen (kernel 2.6.18-128.1.6.el5xen).<br>
<br>Any thoughts?<br clear="all"><br>Thanks,<br>Matt<br><br>--<br>Mathew S. McCarrell<br>Clarkson University '10<br><br><a href="mailto:mccarrms@gmail.com" target="_blank">mccarrms@gmail.com</a><br><a href="mailto:mccarrms@clarkson.edu" target="_blank">mccarrms@clarkson.edu</a><br>
<br><br><div class="gmail_quote">2009/4/7 Maros Timko <span dir="ltr"><<a href="mailto:timkom@gmail.com" target="_blank">timkom@gmail.com</a>></span><div><div></div><div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Hi all,</div>
<div> </div>
<div>thanks to all for valuable replies.</div>
<div>It seems like we identified the issue. We assured that it is not HW related as it was already reproduced on different machines and platforms, with different BIOS versions.</div>
<div>We are running a system performance/statistics collector that executes "xentop" command on Dom0 regularly. This is causing issues. If we execute:</div>
<div><font face="MS Shell Dlg">xentop -b -d 0.1 > /dev/null</font></div>
<div><font face="MS Shell Dlg">in multiple instances, it will freeze the system.</font></div>
<div><font face="MS Shell Dlg">It was reproduced on CentOS 5.3 (kernel-xen-2.6.18-128.1.6.el5) system.</font></div>
<div>There is created a bug for this issue:</div>
<div><a href="http://bugs.centos.org/view.php?id=3454" target="_blank">http://bugs.centos.org/view.php?id=3454</a></div>
<div> </div>
<div>With regards,</div>
<div> </div>
<div>Tino</div>
<div><br><br></div>
<div class="gmail_quote">2009/4/3 Maros TIMKO <span dir="ltr"><<a href="mailto:timko@pobox.sk" target="_blank">timko@pobox.sk</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;"><div><div></div><div>
<p>Hi all,</p>
<p>we are running CentOS 5.2 Xen virtualization system with the latest CentOS packages with couple of VMs on DELL PowerEdge. "Sometimes" the whole machine freezes without anything in log files, anything on the console. "Sometimes" really means we cannot define why or when. Sometimes the machine was idle with just one VM, sometimes quite busy with couple of VMs.</p>
<p> Has anybody had the same experience? If yes, any hints on how to resolve it or how to trace the cause?</p>
<p> </p>
<p>Thanks. </p><br></div></div><div>_______________________________________________<br>CentOS-virt mailing list<br><a href="mailto:CentOS-virt@centos.org" target="_blank">CentOS-virt@centos.org</a><br><a href="http://lists.centos.org/mailman/listinfo/centos-virt" target="_blank">http://lists.centos.org/mailman/listinfo/centos-virt</a><br>
<br></div></blockquote></div><br>
<br>_______________________________________________<br>
CentOS-virt mailing list<br>
<a href="mailto:CentOS-virt@centos.org" target="_blank">CentOS-virt@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-virt" target="_blank">http://lists.centos.org/mailman/listinfo/centos-virt</a><br>
<br></blockquote></div></div></div><br>
<br>_______________________________________________<br>
CentOS-virt mailing list<br>
<a href="mailto:CentOS-virt@centos.org" target="_blank">CentOS-virt@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-virt" target="_blank">http://lists.centos.org/mailman/listinfo/centos-virt</a><br>
<br></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
CentOS-virt mailing list<br>
<a href="mailto:CentOS-virt@centos.org">CentOS-virt@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-virt" target="_blank">http://lists.centos.org/mailman/listinfo/centos-virt</a><br>
<br></blockquote></div><br>