[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Any common reasons for segfaults apart from tls being enabled?

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: George Styles <ripnetuk@xxxxxxxxx>
  • Date: Wed, 18 May 2005 15:01:04 +0100
  • Delivery-date: Wed, 18 May 2005 14:00:34 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Mr7deW4yDs2JxiBXVJdVJUIC++BdRxvWrPyKsx0ry0chSrLRj8ERHjJprYvoKjvOnGWq/f+z/B7oXVdzHKlabUtC0mpLjZwWYC3/v1kthmoPKy741RxFdtJ/XgisAxfTtU5JhBfmSZJszLF94numw0zGbMZscQvEUce3D1cbJsw=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


I have a Xen machine running on Suse 9.3 with default everything. One
of my domains keeps getting Signal 11's to its processes (seg faults)
- its affecting mythbackend (part of mythtv) and mysqld. The other 4
domains are all working perfectly.

Is there a common reason for this apart from the tls libs still being
enabled (they arent). Is this a known issue with the non-test release
of Xen?

Any 'hidden' logs that I have missed? (tried dmesg on both domain 0
and domain X)



Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.