From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57626) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr0XH-0003BY-T1 for qemu-devel@nongnu.org; Wed, 19 Nov 2014 03:22:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xr0XB-00089n-JL for qemu-devel@nongnu.org; Wed, 19 Nov 2014 03:22:47 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49001) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr0XB-00089U-Co for qemu-devel@nongnu.org; Wed, 19 Nov 2014 03:22:41 -0500 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sAJ8MdJB018350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 19 Nov 2014 03:22:40 -0500 Date: Wed, 19 Nov 2014 13:52:35 +0530 From: Amit Shah Message-ID: <20141119082235.GC6787@grmbl.mre> References: <1416254843-16859-1-git-send-email-mst@redhat.com> <20141119073114.GF9190@grmbl.mre> <20141119081516.GA24827@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141119081516.GA24827@redhat.com> Subject: Re: [Qemu-devel] [PATCH 0/5] pc: make ROMs resizeable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: pbonzini@redhat.com, Juan Quintela , qemu-devel@nongnu.org, dgilbert@redhat.com On (Wed) 19 Nov 2014 [10:15:16], Michael S. Tsirkin wrote: > On Wed, Nov 19, 2014 at 01:01:14PM +0530, Amit Shah wrote: > > On (Mon) 17 Nov 2014 [22:08:46], Michael S. Tsirkin wrote: > > > Note: migration stream is unaffected by these patches. > > > This makes it possible to enable this functionality > > > unconditionally, for all machine types. > > > > > > In the future, this might be handy for other things, > > > such as changing kernels loaded on command line > > > across migrations. > > > > I think that'll be too risky; unless we do S4 before / after > > migration to ensure the kernel realises things might be changing > > beneath its feet. > > Well - guest never sees the resizing. It happens before we start the VM. > So I don't see the issue - could you clarify please? Before we start the VM? That's a really odd corner case (ie not worth bothering about?). I took this to mean that the guest was running while migration happened. Amit