similar to: Xen crash

Hi, I'm new to this list and joined since I am volunteering as a tech admin for a non profit organization called CouchSurfing (.com) where we tried to move the web servers to Xen zones and this has proven quite unstable since the our defined zones tends to crash on a daily basis with the latest CentOS 5 Xen updates. The physical boxes have 2 quad core 1.6GHz Xeon CPU's and 4 GB RAM, there

This is a repost of sorts, and for that I am sorry; I do not think my original posting subject was very clear, and I have more data about the problem. I'm experiencing lots of kernel errors when reading or writing to a disk that is part of an mdadm softraid-5 array. Since originally detecting this problem, I have isolated it to one disk, but I'm not sure what the cause of the error is. I

This error is not 100% reproducible. However, kernel panic has been occurred many times for last two months. It usually happens when multi VMs (in our case, 14 VMs) are booting together. After we made three big changes to gain more availibility, it began to happen. Changes are : 1. Use *NAS* as vm storage for migration from local disk 2. Use *two bondings* for switch HA (with 4 nics) from

I've been experiencing delays access data off my file server since I upgraded to 5.3... either I hosed something, have bad hardware or very unlikely, found a bug. When reading or writing data, the stream to the hdd's stops every 5-10 min and %iowait goes through the roof. I checked the logs and they are filled with this diagnostic data that I can't readily decipher. my setup

I have an IBM System x 3250 that successfully boots using the standard kernel (2.6.18-8.1.10.el5) but fails to boot with the xen kernel. The kernel appears to fail when it attempts to initialize the driver for the onboard SAS controller (LSI Logic / Symbios Logic SAS1064E PCI-Express Fusion-MPT SAS). Can anyone provide any advice? Here's the relevant info. Please let me know if any other

CentOS Errata and Security Advisory 2007:0323 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-0323.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 513cbea0fee3d2e0b2c7731c081b4cdc xen-3.0.3-25.0.4.el5.x86_64.rpm 0dcb7c88433bfa0a0bf8560c50ab60e6 xen-devel-3.0.3-25.0.4.el5.i386.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

My kernel crashes every time I shut down dom0 This crash was not happening before I installed the Xen hypervisor Any ideas? (XEN) Xen version 3.2-1 (Debian 3.2.1-2) (waldi at debian.org) (gcc version 4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008 (XEN) Command line: com1=9600,8n1 console=com1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods:

CentOS Errata and Security Advisory 2007:0323 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-0323.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 5accaf1077cd46d0f54acf22ad011ba0 xen-3.0.3-25.0.4.el5.i386.rpm 0dcb7c88433bfa0a0bf8560c50ab60e6 xen-devel-3.0.3-25.0.4.el5.i386.rpm

Summary Many Thanks to Bill Campbell, Nicolas Sahlqvist and Barry Brimer The problem turned out to be one of disk had software errors (message attached), I used ubuntu live cd to fix this issue Cheers Harry ________________________________________________________________________ ____________ From: centos-bounces at centos.org [mailto:centos-bounces at centos.org]

Hello All, My name is Gaurav, and I am tasked with configuring a linux box with NTP. I am having a problem that I hope you can help me with. We have installed CentOS V5 on 1 processor down in the lab. The rest of the processors on the network are AIX boxes versions 3.2.5 and 5.2. I worked through the entire initial NTP configuration; setup the /etc/ntp.conf file to point to the server, etc.

After a yum update my two guests that had been shutdown do not start any more. I have two other guests running that seem to work okay but I am now afraid that they won't come up again if I restart them. I am running CentOS5 with kernel 2.6.18-8.1.8.el5xen. Previously I had following xen versions installed: Oct 14 23:45:10 Updated: xen-libs.i386 3.0.3-25.0.4.el5 Oct 14 23:46:05 Updated:

Sent from my GoodLink synchronized handheld (www.good.com) -----Original Message----- From: Nicolas Sahlqvist [mailto:nicco77 at gmail.com] Sent: Friday, November 23, 2007 05:10 AM Pacific Standard Time To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] xen dom0/domU network speed I have not had the opportunity to test, but it sounds like expected behavior due how

Found an error or two from my logwatch report from yesterday, thought I would share this in hopes this is just first time run of the problem I noticed in the Kernel report section... Also not sure why there's an issue with automount either.... but I guess I could ask on that issue as well. I am not worried about the NAMED error, this is something that happens due to one of the services that

Since upgrading my server from CentOS 4.5 to 4.6 I've been getting the following error from amanda backups: mutilate /home lev 1 FAILED [compress got signal 11, /bin/tar got signal 13] I was away from the house for most of the end of December and had a couple of other issues that came up that could have been related but apparently weren't (why is it that several things all go wrong

On Monday, 19 November 2007, Ross S. W. Walker rwalker at medallion.com wrote: <snip> > You can fix it all from CentOS. Ross: In addition to coming up with another slick way to fix this box, which I truly appreciate, you came up with the below: >You need to run some kind of rootkit detection and cleaner on the >system before it reboots or else it will just reinstall itself.

Hi, I am trying to install Windows 2003 server as a guest OS in Centos 5 Xen and installation is freeze , i am attaching screen shot, here is xend log file details [2007-10-29 17:04:11 xend.XendDomainInfo 3413] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'testwin'], ['memory', '1024'], ['maxmem', '1024'],

Hi all, This is my first post to the list, I hope someone out there can help! I am running xen 3.0.3, with CentOS 5.2 based Dom0 (kernel-xen-2.6.18-92.1.22.el5) Recently I have noticed some complete system lockups on a few different servers. Neither Dom0 or any of the guests respond to pings, connecting a keyboard and monitor to the system only shows a blank screen. Nothing is written to logs

Recently our automated testing system has caught a curious assertion while testing Xen 4.1.5 on a HaswellDT system. (XEN) Assertion ''(sp == 0) || (peoi[sp-1].vector < vector)'' failed at irq.c:1030 (XEN) ----[ Xen-4.1.5 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82c48016b2b4>] do_IRQ+0x514/0x750 (XEN) RFLAGS: 0000000000010093 CONTEXT: