From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=37922 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q4U4Q-0000FF-J7 for qemu-devel@nongnu.org; Tue, 29 Mar 2011 04:14:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q4U4O-000450-B8 for qemu-devel@nongnu.org; Tue, 29 Mar 2011 04:14:34 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44282) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q4U4N-00044r-T8 for qemu-devel@nongnu.org; Tue, 29 Mar 2011 04:14:32 -0400 Message-ID: <4D9194E2.80405@redhat.com> Date: Tue, 29 Mar 2011 10:14:26 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <4D9037EE.8000808@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 3/4] Introduce machine state List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel On 03/28/2011 07:21 PM, Blue Swirl wrote: >> > >> > What's the distinction between vm state and machine state? > > VM state should be invisible (except for PV devices). Got it. That's why I called it "emulator state" (a bit generic, but more precise than vm state: vm_clock for example is guest-visible). > About 'machine', I was thinking about -M switch to specify > the emulated machine type. Yes, makes sense. I actually like the name machine state, as long as you rename what you called "virtual machine state". Paolo