From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hongyang Yang Subject: Re: [PATCH 1/1] xc_domain_restore: Allow QEMU to increase memory Date: Wed, 15 Apr 2015 19:15:43 +0800 Message-ID: <552E485F.5090805@cn.fujitsu.com> References: <1428941353-18673-1-git-send-email-dslutz@verizon.com> <552BEDF1.7070209@citrix.com> <552C5683.1040903@one.verizon.com> <20150414085304.GM17670@zion.uk.xensource.com> <552D4FB3.9060109@one.verizon.com> <1429092570.15516.172.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1429092570.15516.172.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Stefano Stabellini Cc: Wei Liu , Andrew Cooper , Ian Jackson , Don Slutz , "xen-devel@lists.xen.org" , Shriram Rajagopalan List-Id: xen-devel@lists.xenproject.org On 04/15/2015 06:09 PM, Ian Campbell wrote: > On Wed, 2015-04-15 at 10:46 +0100, Stefano Stabellini wrote: >> On Tue, 14 Apr 2015, Don Slutz wrote: >>> On 04/14/15 04:53, Wei Liu wrote: >>>> Is there a way to know how much more memory each option rom needs? If >>>> so, you can correctly account for the extra memory you need. This would >>>> be an ideal fix to this problem. >>> >>> I do not know of a way to get this info. It can change based on the >>> QEMU version. >> >> Indeed it would be fragile to rely on a fixed size for each option rom, >> given that they come out of the QEMU tree and can change at any time. > > Only having dipped into this thread so far it seems to me we need some > way for qemu to communicate the result of its manipulations of maxmem > into the migration stream explicitly to be picked up by the other end. Totally agreed. > > Ian > > . > -- Thanks, Yang.