From: Keir Fraser <keir@xensource.com>
To: "Zhao, Fan" <fan.zhao@intel.com>, "Zhai, Edwin" <edwin.zhai@intel.com>
Cc: Tim Deegan <Tim.Deegan@xensource.com>,
Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.xensource.com
Subject: Re: Re: [PATCH][HVM] fix VNIF restore failure on HVMguest with heavy workload
Date: Wed, 11 Apr 2007 18:32:44 +0100 [thread overview]
Message-ID: <C242DA4C.D2A4%keir@xensource.com> (raw)
In-Reply-To: <0E6B8CEB89DCFE40A52F80EB8F97D99D013F1FC0@pdsmsx413.ccr.corp.intel.com>
On 11/4/07 17:24, "Zhao, Fan" <fan.zhao@intel.com> wrote:
> I noticed that with cset 14773, if I use xm mem-set to adjust the memory of
> hvm guest with balloon driver by xm mem-set, and then save the guest, the xm
> save will fail, so does xm migrate. A white window will pop up, and the guest
> still exists through xm li. So will your great fixes also include the fixing
> for this issue? Thanks!
It works for me (Linux guest, initial alloc 256MB, ballooned to 128MB).
Is it definitely the save that fails for you? Is there any interesting
output in xend.log?
-- Keir
next prev parent reply other threads:[~2007-04-11 17:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 16:47 [PATCH][HVM] fix VNIF restore failure on HVM guest with heavy workload Zhai, Edwin
2007-04-10 19:16 ` Keir Fraser
2007-04-11 7:20 ` Zhai, Edwin
2007-04-11 7:41 ` Keir Fraser
2007-04-11 8:56 ` Keir Fraser
2007-04-11 16:24 ` Re: [PATCH][HVM] fix VNIF restore failure on HVMguest " Zhao, Fan
2007-04-11 16:54 ` Re: [PATCH][HVM] fix VNIF restore failure on HVMguestwith " Steven Hand
2007-04-12 18:46 ` Mark Williamson
2007-04-12 18:51 ` Steven Hand
2007-04-13 9:42 ` Keir Fraser
2007-04-11 17:32 ` Keir Fraser [this message]
2007-04-12 2:47 ` Re: [PATCH][HVM] fix VNIF restore failure on HVMguest with " Zhao, Fan
2007-04-12 7:06 ` Keir Fraser
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=C242DA4C.D2A4%keir@xensource.com \
--to=keir@xensource.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Tim.Deegan@xensource.com \
--cc=edwin.zhai@intel.com \
--cc=fan.zhao@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.