So, I guess this wasn't just a hardware issue. I actually had another
system crash.
This only appears to happen when I'm issuing xm commands over and over.
Any thoughts?
Thanks,
Matt
--
Mathew S. McCarrell
Clarkson University '10
mccar...@gmail.com
mccar...@clarkson.edu
On Thu, Apr 30,
Mathew S. McCarrell wrote:
Well, I'm actually not using a PAExen kernel but I don't believe that I
need to be since I'm running the 64-bit version of CentOS. Am I
mistaken in that assumption?
Matthew, you are right.
Also, the idea of running a PAE kernel on CentOS is non relevant
--
Karanbir, can you please, in short, explain to me current status of
64-bit CentOS compared to i386? Is it's maturity same as of i386?
I started to actively use CentOS when 4.2 was last version. My decision
to use i386-only was based on issues with some (or many?) drivers like
madwifi for
I've discovered what the issue is.
The machine is rebooting when a sector error occurs on one of the drives
that is part of a software RAID where the VMs are currently being stored.
Thanks for the help though.
Matt
--
Mathew S. McCarrell
Clarkson University '10
mccar...@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
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 mccar...@gmail.com
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.
Matt
--
Mathew S. McCarrell
Clarkson
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
