From: "James Harper" <james.harper@bendigoit.com.au>
To: Paul Durrant <Paul.Durrant@citrix.com>,
tinnycloud <tinnycloud@hotmail.com>,
Steven Smith <Steven.Smith@eu.citrix.com>,
xen-devel@lists.xensource.com
Cc: Keir Fraser <Keir.Fraser@eu.citrix.com>, JBeulich@novell.com
Subject: RE: Win2003 got blue Screen when ballooning with serial out put: "Iomem mapping not permitted"
Date: Fri, 17 Dec 2010 20:20:08 +1100 [thread overview]
Message-ID: <AEC6C66638C05B468B556EA548C1A77D01BB8BA7@trantor> (raw)
In-Reply-To: <291EDFCB1E9E224A99088639C47620228CF938AAE0@LONPMAILBOX01.citrite.net>
>
> 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
next prev parent reply other threads:[~2010-12-17 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SNT0-MC4-F15TlpsWqi0002f5ac@snt0-mc4-f15.Snt0.hotmail.com>
2010-12-17 3:24 ` Win2003 got blue Screen when ballooning with serial out put: "Iomem mapping not permitted" tinnycloud
2010-12-17 8:53 ` Paul Durrant
2010-12-17 9:20 ` James Harper [this message]
2010-12-20 2:06 ` tinnycloud
2011-01-05 13:11 ` Could the page sharing inside domain? (memory_sharing on xen) xiaoyun.maoxy
2011-02-25 5:56 ` TODO in windows balloon driver tinnycloud
2011-02-26 12:17 ` James Harper
2011-02-26 13:35 ` MaoXiaoyun
2011-02-27 1:43 ` James Harper
2011-02-27 3:35 ` James Harper
2011-02-26 11:20 ` blue screen " xiaoyun.maoxy
[not found] ` <000301cbd5a7$3245a1b0$96d0e510$@maoxy@aliyun-inc.com>
2011-02-26 11:59 ` James Harper
2010-12-17 9:39 ` Win2003 got blue Screen when ballooning with serial out put: "Iomem mapping not permitted" tinnycloud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AEC6C66638C05B468B556EA548C1A77D01BB8BA7@trantor \
--to=james.harper@bendigoit.com.au \
--cc=JBeulich@novell.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=Steven.Smith@eu.citrix.com \
--cc=tinnycloud@hotmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).