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

[Xen-users] openSuSE kernel-xen bug (netback deadlock issue)


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Mark Pryor <tlviewer@xxxxxxxxx>
  • Date: Tue, 3 Aug 2010 14:28:40 -0700 (PDT)
  • Delivery-date: Tue, 03 Aug 2010 14:31:02 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=pGj4DFj1bprchyUCZ6ASfvrS+1qULiIf2w0Z6M8PC2y7+FbHWKvE5nf153zg35NkvmXtrRnpi9E7ZC4gTXkXyJ1F4TSTXZYYUtbR3+GPKFOE7QFc7ZcQRYrxabHSfzGD/biCGnKLS9TaHa0MAe5ZdwhHtgSRfPlnzZI5JwM0dts=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,

As mentioned by Boris here
http://lists.xensource.com/archives/html/xen-users/2010-07/msg00817.html

there is a serious bug in kernel-xen 2.6.34-12, which is the default dom0 
kernel for the latest 11.3 release.

Good news is the bugzilla.novell.com has covered it and a fix is available in 
KOTD (also noted by Boris).

https://bugzilla.novell.com/show_bug.cgi?id=623286#c12

I wasted considerable time struggling with my 11.3 dom0 install, until 
realizing that I was up against the same bug. The KOTD solved it, but the 
factory kernel (2.6.34-14.x) didn't. Don't waste your time importing the 
factory repo and installing kernel-xen from there.

I ran my 11.3 dom0 for weeks before a path typo in disk=[] triggered this bug. 
Everything worked great: old VM's and new PV installs too. Only a vbd path 
error brought the deadlock. When a vbd error stopped 'xm create', the vifx.0 
was not released and was stranded after the domU closed.

-- 
Mark


      

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

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