On Sat, Aug 24, 2013 at 08:52:47PM +0900, Keiichi SHIMA wrote:
> Hi,
>
> Let me ask one question about vmAdminState values.
>
> In the latest VMM-MIB draft
> (http://www.ietf.org/id/draft-asai-vmm-mib-04.txt), the values for
> vmAdminState are defined as below.
You are actually asking a question about VirtualMachineOperState...
>
> INTEGER {
> unknown(1),
> other(2),
> preparing(3),
> running(4),
> blocked(5),
> suspending(6),
> suspended(7),
> resuming(8),
> paused(9),
> migrating(10),
> shuttingdown(11),
> shutdown(12),
> crashed(13)
> }
>
> Also, how the state transits is shown in Figure 2.
>
> However, in the above description, the 'blocked' state is quite unclear to me.
The current description is this:
blocked(5) The virtual machine is currently blocked.
> What precisely does the 'blocked' state mean? When does a virtual
> machine transit to the 'blocked' state? I think we need more text
> about the state, if we want to keep the state.
The blocked state covers situations where a virtual machine is blocked
because it waits for certain service requests to complete. For
example, if you use Xen, then a DomU delegates most of the low-level
input/output to Dom0 and while waiting for Dom0 to finish processing a
request, the DomU issuing the request is 'blocked'.
Would this clarification help:
blocked(5) The virtual machine is currently blocked
waiting for example for some action of
the hypervisor to finish.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
