 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] Re: [PATCH] reset PV devices in crash kernel
| To: | Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] Re: [PATCH] reset PV devices in crash kernel |
| From: | Olaf Hering <olaf@xxxxxxxxx> |
| Date: | Mon, 7 Feb 2011 18:42:05 +0100 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Mon, 07 Feb 2011 09:42:52 -0800 |
| Dkim-signature: | v=1; a=rsa-sha1; c=relaxed/relaxed; t=1297100532; l=840; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:Cc:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=c4gqAbdVyKW68JlsWUHin014FM8=; b=UzMuFfd6JalG3nB9v6v0hgdl5gE0KiwLHpE1M+m6VF4kWylvFp281m5nZ+13Z7Ismi+ lfq6lk77c8flYg0/U64lwfnaHQAVPMZlR0X6HEKcskrocAW/Y3ze2M98wbEip1HhNABX0 BkvF/fEMu9WsWFuKEKmcMFQf+lwlu8NbPpg= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20110207171642.GB16937@xxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <20110204152850.GA8726@xxxxxxxxx> <20110204153012.GA9258@xxxxxxxxx> <20110207162809.GA23727@xxxxxxxxx> <20110207171642.GB16937@xxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
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 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH] xentrace: dynamic tracebuffer size allocation, George Dunlap |
|---|---|
| Next by Date: | Re: [Xen-devel] AMD_IOV: IO_PAGE_FALT trying to pass through Mellanox ConnectX HCA (debian testing), Ward Vandewege |
| Previous by Thread: | Re: [Xen-devel] Re: [PATCH] reset PV devices in crash kernel, Konrad Rzeszutek Wilk |
| Next by Thread: | [Xen-devel] [PATCH] xen: Change trace_var argument to void*, to match __trace_var, George Dunlap |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
