From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: PATCH: 0/10: Merge xenfb & xenconsoled into qemu-dm Date: Thu, 16 Aug 2007 08:30:08 +0100 Message-ID: References: <20070815200056.GE22579@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070815200056.GE22579@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Daniel P. Berrange" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 15/8/07 21:00, "Daniel P. Berrange" wrote: > The only feature this re-factoring looses is the ability to have the paravirt > text console persistently logged to a file. QEMU allows us to specify that > a character device is either sent to a PTY, or a file, but not both at the > same time. I'm thinking about ways in which QEMU's character device config > syntax & drivers may be extended to allow use of a PTY & File concurrently. > > The patches should be applied in order - after each individual patch you > should still have a fully operational system for both FV & PV. Have you tested both HVM and PV guests with save/restore, migration, and *failed* save/restore (e.g., by forcing an error in xc_domain_save.c)? The last needs care because qemu-dm must be kept around until the last moment, in case the save or migration fails. Are these patches intended to be applied now, or are they RFC? -- Keir