xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: tinnycloud <tinnycloud@hotmail.com>
To: steven.smith@citrix.com, xen-devel@lists.xensource.com
Cc: james.harper@bendigoit.com.au, keir.fraser@eu.citrix.com,
	JBeulich@novell.com
Subject: Win2003 got blue Screen when ballooning with serial out put: "Iomem mapping not permitted"
Date: Fri, 17 Dec 2010 11:24:22 +0800	[thread overview]
Message-ID: <BLU157-ds1AEAC80753959EC959A12DA160@phx.gbl> (raw)
In-Reply-To: <SNT0-MC4-F15TlpsWqi0002f5ac@snt0-mc4-f15.Snt0.hotmail.com>

Hi Steven:

	I was trying to make use of balloon driver on my win2003 HVM Guests,
but confront a Guest crash problem with blue screen.
	The serial output is much like 
	(XEN)grant_table.c:555:d0 Iomem mapping not permitted
ffffffffffffffff

	My pvdriver changeset is 823. From
http://xenbits.xensource.com/ext/win-pvdrivers.hg
	Xen is 4.0.0

	I've done quite a lot experiments to locate the crash, and finally
make it easy to reproduce.
	Here is the situation:

	1) Start several Win2003 Guest with 2G memory to occupy host memory
till from xm info | grep free to see xen has only almost 3G memory
	2) Start another Guest with 2G memory, say domain X, and set its
target to be 512M, after balloon, dom X will has only 512M, and xen has 2.5G
memory
	3) Start another Guest with 2G memory, then xen will have only 0.5G
memory left
	4) At this time, I set the domain X target to 2G (use xenstore-write
/local/domain/x/memory/target 2097152)
    5) domain X got blue screen at once. With code says 0x0000007f
(0x0000000d, 0x00000000, 0x00000000, 0x00000000)"

	So, in short, when a domain wants more memory, it deflates its
balloon, but if Xen doesn't enough memory, the domain will crash.

	I've go through
http://lists.xensource.com/archives/html/xen-devel/2010-01/msg01230.html
	
http://lists.xensource.com/archives/html/xen-devel/2010-02/msg00074.html

	it looks like the crash is because windows crash dumper go through
those balloon out pages
	and from the discuss it would be harmless, but why I got this crash?
	
	Could you kindly offer me some help, thanks.

	

       reply	other threads:[~2010-12-17  3:24 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 ` tinnycloud [this message]
2010-12-17  8:53   ` Win2003 got blue Screen when ballooning with serial out put: "Iomem mapping not permitted" Paul Durrant
2010-12-17  9:20     ` James Harper
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=BLU157-ds1AEAC80753959EC959A12DA160@phx.gbl \
    --to=tinnycloud@hotmail.com \
    --cc=JBeulich@novell.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=keir.fraser@eu.citrix.com \
    --cc=steven.smith@citrix.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).