Hi,
In:
http://www.ietf.org/internet-drafts/draft-asai-vmm-mib-02.txt
Think we need to clarify the concept of 'pause' in both admin
and operational states.
VirtualMachineAdminState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The administrative state of a virtual machine:
on(1) The administrative power state of the
virtual machine is off.
off(2) The administrative power state of the
virtual machine is on.
pause(3) The administrative power state of the
virtual machine is hibernated or
suspended."
SYNTAX INTEGER {
on(1),
off(2),
pause(3)
}
A virtual machine is a OS process. An operator can suspend it in memory (pkill
-HUP ${myvm}).
HOST-RESOURCES-MIB (rfc 2790) would report the VM process in hrSWRunTable
as state notRunnable.
hrSWRunStatus OBJECT-TYPE
SYNTAX INTEGER {
running(1),
runnable(2), -- waiting for resource
-- (i.e., CPU, memory, IO)
notRunnable(3), -- loaded but waiting for event
invalid(4) -- not loaded
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The status of this running piece of software.
Setting this value to invalid(4) shall cause this
software to stop running and to be unloaded. Sets to
other values are not valid."
::= { hrSWRunEntry 7 }
That's how I naturally think of what 'pause' as opposed to 'suspend or
hibernate'
which takes the process out of memory deep-freeze's running state (for a given
CPU hardware) to
persistent storage.
Thanks,
Mike MacFaden
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
