Hello, >> 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…
Ah, yes, you are right. My fault. >> 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'. OK, thank you, now the meaning of the blocked state is much clearer to me than before. Then, my following question is that, do we need the state? I wonder how the state is used in a real operation. It seems that the blocked state is a kind of temporal/short-lived state caused by the scheduling process of virtual machine entities running in a hypervisor. It is sure that we will have a blocked state, but it won't last long. Are we trying to catch that short-lived state using this VMM-MIB? Do we have any usage scenario of the blocked state? Regards, --- Keiichi SHIMA (島 慶一) WIDE project <[email protected]> Research Laboratory, IIJ Innovation Institute, Inc <[email protected]> On 2013/08/26, at 19:59, Juergen Schoenwaelder <[email protected]> wrote: > 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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
