From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: Re: [PATCH] reset PV devices in crash kernel Date: Mon, 7 Feb 2011 18:42:05 +0100 Message-ID: <20110207174205.GA9190@aepfle.de> References: <20110204152850.GA8726@aepfle.de> <20110204153012.GA9258@aepfle.de> <20110207162809.GA23727@aepfle.de> <20110207171642.GB16937@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20110207171642.GB16937@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, Feb 07, Konrad Rzeszutek Wilk wrote: > On Mon, Feb 07, 2011 at 05:28:09PM +0100, Olaf Hering wrote: > > > > After triggering a crash dump in a HVM guest, the PV backend drivers > > will remain in connected state. When the kdump kernel starts the PV > > drivers will skip such devices. As a result, no root device is found > > and the vmcore cant be saved. > > > > With this change all frontend devices with state XenbusStateConnected > > will be reset by changing the state file to Closing/Closed/Initializing. > > This will trigger a disconnect in the backend drivers. Now the frontend > > drivers will find the backend drivers in state Initwait and can connect. > > Do you have a similar patch for the pv-ops? No yet, due to lack of pv-ops kernel on my side. I will try to get one up and running soon. Olaf