Yes, mem and disk check was also our first thing to do. But it happened on different machines (1950s and 2950s), different BIOS versions and number of NICs. The freeze situation is unrecoverable - machine replies to pings, but did not write anything to console. You cannot SSH to it, the only thing we could do is power down the machine. After that everything is fine. Thanks. 2009/4/3 Tim Verhoeven <tim.verhoeven.be at gmail.com> > On Fri, Apr 3, 2009 at 4:18 PM, Maros TIMKO <timko at pobox.sk> wrote: > > > > 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? > > > > The complete freezing of a machine like that sounds like a hardware > issue to me, most likely the memory. Does the machine unfreeze after a > while or do you have to power cycle the server when it happens ? I > would suggest running a memtest. > > Regards, > Tim > > -- > Tim Verhoeven - tim.verhoeven.be at gmail.com - 0479 / 88 11 83 > > Hoping the problem magically goes away by ignoring it is the > "microsoft approach to programming" and should never be allowed. > (Linus Torvalds) > _______________________________________________ > 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/20090403/dc2718ee/attachment-0005.html>