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/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH][HVM] fix VNIF restore failure on HVMguest wi

To: "Zhao, Fan" <fan.zhao@xxxxxxxxx>, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH][HVM] fix VNIF restore failure on HVMguest with heavy workload
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 11 Apr 2007 18:32:44 +0100
Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 11 Apr 2007 10:31:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <0E6B8CEB89DCFE40A52F80EB8F97D99D013F1FC0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acd8F1GxkEamROgKEduOGgAX8io7RQAPiQwwAAJ88t8=
Thread-topic: [Xen-devel] Re: [PATCH][HVM] fix VNIF restore failure on HVMguest with heavy workload
User-agent: Microsoft-Entourage/
On 11/4/07 17:24, "Zhao, Fan" <fan.zhao@xxxxxxxxx> 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

Xen-devel mailing list