Hi Mathew, 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.I can see some out of memory messages, do you still have enough memory for Dom0? 2009/4/29 Mathew S. McCarrell <mccarrms at gmail.com> > Hey, > > 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. > > 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). > > Any thoughts? > > Thanks, > Matt > > -- > Mathew S. McCarrell > Clarkson University '10 > > mccarrms at gmail.com > mccarrms at clarkson.edu > > > 2009/4/7 Maros Timko <timkom at gmail.com> > > Hi all, >> >> thanks to all for valuable replies. >> 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. >> We are running a system performance/statistics collector that executes >> "xentop" command on Dom0 regularly. This is causing issues. If we execute: >> xentop -b -d 0.1 > /dev/null >> in multiple instances, it will freeze the system. >> It was reproduced on CentOS 5.3 (kernel-xen-2.6.18-128.1.6.el5) system. >> There is created a bug for this issue: >> http://bugs.centos.org/view.php?id=3454 >> >> With regards, >> >> Tino >> >> >> 2009/4/3 Maros TIMKO <timko at pobox.sk> >> >>> Hi all, >>> >>> 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. >>> >>> Has anybody had the same experience? If yes, any hints on how to resolve >>> it or how to trace the cause? >>> >>> >>> >>> Thanks. >>> >>> _______________________________________________ >>> CentOS-virt mailing list >>> CentOS-virt at centos.org >>> http://lists.centos.org/mailman/listinfo/centos-virt >>> >>> >> >> _______________________________________________ >> CentOS-virt mailing list >> CentOS-virt at centos.org >> http://lists.centos.org/mailman/listinfo/centos-virt >> >> > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20090429/88b7f8fe/attachment-0004.html>