WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Win2003 got blue Screen when ballooning with serial out

To: "Paul Durrant" <Paul.Durrant@xxxxxxxxxx>, "tinnycloud" <tinnycloud@xxxxxxxxxxx>, "Steven Smith" <Steven.Smith@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Win2003 got blue Screen when ballooning with serial out put: "Iomem mapping not permitted"
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Fri, 17 Dec 2010 20:20:08 +1100
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, JBeulich@xxxxxxxxxx
Delivery-date: Fri, 17 Dec 2010 01:21:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <291EDFCB1E9E224A99088639C47620228CF938AAE0@xxxxxxxxxxxxxxxxxxxxxxxxx>
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: <SNT0-MC4-F15TlpsWqi0002f5ac@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <BLU157-ds1AEAC80753959EC959A12DA160@xxxxxxx> <291EDFCB1E9E224A99088639C47620228CF938AAE0@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcudjQT/1ru6fBA9Q+y8rx823coE9AACJPTwAAxzPMAAAQPzAA==
Thread-topic: [Xen-devel] Win2003 got blue Screen when ballooning with serial out put: "Iomem mapping not permitted"
> 
> If the frontend GPL PV storport driver is not ignoring block write
failures in
> crashdump mode then you are unlikely the get a good dump from the
ballooned
> down VM.

It does, because I had to balloon down a few pages for migration to work
(probably an old bug by now). I did put a limit as to how many failures
it was prepared to put up with though.

> As for the original crash, I guess the balloon driver is just not
handling the
> populate hypercall failure gracefully.
> 

Quite likely.

James

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