similar to: Bug#603727: xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver)

Hi, If you are getting tired of being teased about updating your syncmail script to the new CVS loginfo syntax, this mail is for you. If you have opted to use the CIA script, you have already switched to the new loginfo format. If not, you need to do now. For that you need to add UseNewInfoFmtStrings=yes to the CVS config file. Then if you have script using the old format you can escape it

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=62 Summary: I patched the iptables-restore and liblptulog for string included "," " Product: iptables userspace Version: 1.2.7a Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2

Package: xen Version: 4.3.0-3+b1 When trying to migrate from a 4.3 host to a 4.1 host (which should fail of course, but gracefully), the PV guest on the sending host crashes. To be honest, I have no idea which component to file this bug against. The sending host has been upgraded to jessie. Here're the relevant package versions: ii libxen-4.3 4.3.0-3+b1

Every few hours we get the following in /var/log/messages: Oct 19 20:56:20 wltracp1a kernel: mptscsi: ioc0: bus reset: SUCCESS (sc=0000010190c56080) Oct 19 20:56:20 wltracp1a kernel: mptscsi: ioc0: attempting task abort! (sc=0000010190c56080) Oct 19 20:56:20 wltracp1a kernel: scsi4 : destination target 2, lun 0 Oct 19 20:56:20 wltracp1a kernel: command = Test Unit Ready 00 00 00 00 00 Oct

Hi, i'm trying to relay local post from Postfix to Dovecot-lda. It's running on opensuse11.3-64bit with postfix V2.7.1 and dovecot V2.01. sending local message like: echo foo | /usr/sbin/sendmail -f root root gets no logdata in dovecot.err, -.info,-.debug. but the postfix-logfile tells: Sep 11 10:56:12 server postfix/cleanup[3027]: 94027A65BC: message-id=<20100911085612.94027A65BC at

On Debian Squeeze (2.6.32-5) running Xen 4.0, I have created 2 Ubuntu Lucid Lynx (Ubuntu 10.04) vms. The vms, in a stress test, pass a large file between them via nfs file sharing. A previous entry in this forum helped to establish that some ethernet cards improve VM IO performance. However, our box installed with better intel nics is still rebooting under heavy VM IO loads. The kernel call

hi, i setup a samba-3.0.0-2 server under redhat 9. i added this server to a win nt 4.0 domain controller. the nt domaincontroller only runs the following services: wins, dhcp & pdc. nothing more. /etc/samba/smb.conf: [global] workgroup = SCHLICK-ROTO server string = Server - File hosts allow = 172.24. 127. printcap name = /etc/printcap load printers = yes log file =

Dear all, actually I installed CentOS 5.4 x86_64 on 11 new Dell R710 servers. It is required to use 5.4 to be covered by the NetApp Interoperability Matrix for use of Snapdrive. All systems spit out the error message mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:4637/_scsih_add_device()! at boot time. In dmesg the complete SCSI initialization logging appears as follows: SCSI

I have a couple development servers running centos 6.3 64bit that have LSI 9211-8i SAS2 controllers connected to a SAS2 backplane. these work fine with SATA hard disks (populated with a bunch of 3TB SATA drives)... I'm trying to install a OCZ Vertex3 SSD on each of the two servers to do some ssd caching tests... system sees the drive, so I do the following... # parted -a min

Hi I am attempting to setup Xen 4.10 with kernel 4.9.86-30 ( virt7-xen-410-testing, virt7-common-testing ) on CentOS7 After installing everything, the machine was unable to boot and hung in dracut stating it could not find its root device. The testsystem I use is a somewhat aged Dell M915 Blade (Quad opteron 61xx), using an MPT SAS controller for it's SAS boot drives. Stock CentOS 7

<20100926154324.GD21843 at redhat.com>; from Michael S. Tsirkin on Sun, Sep 26, 2010 at 17:43:24 +0200 > > > >It's vanilla 2.6.32.22, but I also reproduced this on Debian's 2.6.32-23 > > > >(based on 2.6.32.21). > > > > > > > >If offload is the only difference, I'll play with different offload > > > >options and check

<20100926154324.GD21843 at redhat.com>; from Michael S. Tsirkin on Sun, Sep 26, 2010 at 17:43:24 +0200 > > > >It's vanilla 2.6.32.22, but I also reproduced this on Debian's 2.6.32-23 > > > >(based on 2.6.32.21). > > > > > > > >If offload is the only difference, I'll play with different offload > > > >options and check

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: normal My 32Bit Dom0-crashes with error "Out of SW-IOMMU space for 65536 bytes" after doing moderate I/O on the local storage, which is a software-raid1 over 3 harddrives, connected to the builtin Perc H200 controller with ext3-fs. The error is reproduceable with "dd if=/dev/zero of=bigfile bs=1024 count=1000000"

Processing commands for control at bugs.debian.org: > reassign 603727 linux-2.6 Bug #603727 [xen-hypervisor-4.0-amd64] xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver) Bug reassigned from package 'xen-hypervisor-4.0-amd64' to 'linux-2.6'. No longer marked as found in versions xen/4.0.1-1.

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hey all, I was watching some logs on a domU today and i suddenly noticed that the timestamps were off by something on the order of 47 seconds. I was surprised because *I don''t* run independent wall clocks. I checked some other domUs and the "drift" was also very close to that of the first domU. I also checked another dom0, Here the domUs were "only" out of sync by