Partition State

Each partition can be in one of the following states:

Uninitialized

The state of the partition after a call to the HvCreatePartition function creates the partition.

A caller can only call the HvDepositMemory, HvGetMemoryBalance, HvGetNextChildPartition, and HvInitializePartition functions on uninitialized partitions.

Active

The state of the partition after a call to the HvInitializePartition function initializes the partition.

A caller can call all functions of the hypercall interface on active partitions, with the exception of HvDeletePartition.

Finalizing

The transitory state of the partition after a caller calls the HvFinalizePartition function but before the function completes.

A caller can only call the HvGetMemoryBalance, HvWithdrawMemory, HvGetNextChildPartition, and HvFinalizePartition functions on finalizing partitions.

Finalized

The state of the partition after a call to the HvFinalizePartition function successfully completes to finalize the partition.

A caller can only call the HvGetMemoryBalance, HvWithdrawMemory, HvGetNextChildPartition, and HvDeletePartition functions on finalized partitions.

The following figure shows the valid states and actions that can result in partition state transitions. All state transitions appear to be atomic from the perspective of hypervisor callers.

Send comments about this topic to Microsoft

Build date: 11/16/2013