On Tue, Mar 29, 2011 at 11:14 AM, Paolo Bonzini wrote:
> 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 gen
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-visib
On Mon, Mar 28, 2011 at 10:25 AM, Paolo Bonzini wrote:
> On 03/26/2011 11:28 PM, Blue Swirl wrote:
>>
>> Move generic machine state to machine-state.h, adjust
>> users.
>
> What's the distinction between vm state and machine state?
Machine state or configuration is visible to guest, for example n
On 03/26/2011 11:28 PM, Blue Swirl wrote:
Move generic machine state to machine-state.h, adjust
users.
What's the distinction between vm state and machine state?
Perhaps your vm state is more appropriately called "emulator state"
(i.e. sits between host and vm), and machine state is actually
