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, 2009
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
mccar...@clar
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 AR5007
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
--
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?
Thanks,
Matt
--
Mathew S. McCarrell
Clarkson University '10
mccar...@gmail.com
mccar...@clarkson.edu
On Wed, Apr 29, 2009 at 5:0
Just to make sure, you are using PAExen kernel on 12GB RAM Linux? 4GB is
max for regular kernel without PAE extensions.
Mathew S. McCarrell wrote:
> 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
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 Un
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
> Hey,
>
> I'm wo
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
en
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" co
On Sat, Apr 4, 2009 at 3:43 AM, Maros Timko wrote:
> 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
I've had to deal with issues like these in the past and I can say they
always suck. Normally, the whole OS freezes due to a hardware issue.
Isolating the cause is extremely time consuming. If it happens on a
regular basis, (I.E. every 60 or maybe 90 days) the most likely culprit
is the DRAC car
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
On Fri, Apr 3, 2009 at 4:18 PM, Maros TIMKO 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 me
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
15 matches
Mail list logo
