similar to: libata-core kernel errors

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

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

Hi Centos-virt, 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

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 decided to simplify every that I was doing. I noticed that I had begun to overthink things, and I decided that KISS, is still the best way to go. This has turned out to be something like this; *** File xenmaster.testdomain.com.pp node xenmaster.testdomain.com { include xen } Where xen has been defined as a class in File testdomain.classes.pp class xen { package { xen: ensure =>

Is serial port "passthrough" possible for the version of xen that ships with centos 5.2? I've disabled the xen hypervisor serial console, and can see the serial port in dom0. I've masked out the 8250, 8250_pnp and serial_core modules on dom0 and rebooted. xm create domain fails with the error that exactly 4 arguments are required and only 3 were given. Steps I followed: 1) I

Hi All, [I originally posted this message in the main CentOS users' list, but later found this list. So, I'm reposting it here since this is where it belongs.] I'm trying to install a Fedora 8 domU on a CentOS 5 dom0, but the following command fails: [root at xenmaster ~]# virt-install -p -n krs -r 512 -m 00:16:3E:66:94:5F -b xenbr0 --vnc --vncport=5910 -l

Hello, I have one cluster drbd8+ocfs2. If I mount ocfs2 partition on node1 it's work but when I mount partition on node 2 I receive in /var/log/messages this -Mar 5 18:10:04 suse4 kernel: (2857,0):o2hb_do_disk_heartbeat:665 ERROR: Device "drbd1": another node is heartbeating in our slot! -Mar 5 18:10:04 suse4 kernel: WARNING: at include/asm/dma-mapping.h:44 dma_map_sg() -Mar 5

Hi All, I'm trying to install a Fedora 8 domU on a CentOS 5 dom0, but the following command fails: [root at xenmaster ~]# virt-install -p -n krs -r 512 -m 00:16:3E:66:94:5F -b xenbr0 --vnc --vncport=5910 -l http://10.19.75.200/mirror/fedora/linux/releases/8 -f /dev/vg00/krs -d Starting install... Sat, 08 Mar 2008 12:27:56 DEBUG Fetching URI

Iam new to Xen and I am trying to FC4 and FC4 domains. I came across a problem when my newly created domain never gets a network. When I start the domain I get a fatal error that leads me to believe that thios might be the reason why I don''t have networking with the bridge: Checking for new hardwaremodprobe: FATAL: Could not load /lib/modules/2.6.12-1.1411_FC4xen0/modules.dep: No such

Thank you all for you replies! For anyone following the fedora xen quickstart guide here are the steps to follow to get your eth0 working. At rawhide mkdir /lib/modules/2.6.12-1.1411_FC4xen0 depmod -a At the domain0 (make sure rawhide is down) mount -o loop /root/fedora.img /mnt cd /mnt cp /etc/sysconfig/network-scripts/ifcfg-eth0 etc/sysconfig/network-scripts/ifcfg-eth0 cp

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

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:

On 14.05.20 08:44, teawater wrote: > Hi David, > > I got a kernel warning with v2 and v3. Hi Hui, thanks for playing with the latest versions. Surprisingly, I can reproduce even by hotplugging a DIMM instead as well - that's good, so it's not related to virtio-mem, lol. Seems to be some QEMU setup issue with older machine types. Can you switch to a newer qemu machine version,

Hello List, I'm hoping someone else out there has an Asus DSBF-DE server board, and can tell me if anything special needs to be done to get ports 5 and 6 of the onboard SATA to work under Centos 5.1 x64. I have drives on 1 through 4 that are detected and working properly, however, a drive on 5 is not detected, from what i can tell, the kernel doesn't even see phy's for ports 5 and 6.

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:

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a