On 4/8/13 1:39 PM, "Marcus Sorensen" <shadow...@gmail.com> wrote:
>Has anyone put together a suggestion for adding a 'paused' state to >virtual >machines? Or is anyone working on it? This seems fairly straightforward, >and I think we may need the functionality going forward. Even if people >rarely use it themselves, if storage solutions are going to offer >snapshots >they may want to pause the VM in order to get an atomic snapshot if the VM >has multiple disks. So at least internally it may be a useful utility. Pause VM itself can not ensure data integrity. True data integrity can't be ensured without participant of guest OS and related application (for example, Microsoft offers Volume Shadow Copy Service to orchestrate and allow applications to participate the process via a set of tools and API interaction to achieve that). When CloudStack takes a snapshot of volume, it already utilizes snapshot feature provided by hypervisor to allow taking point of time storage image in a safe manner from operating system point of view. The ability of pausing VM is not mandatory in this case, although pausing/resuming VM may be useful in certain use case, it does not seem to be in any urgency or fit naturally in general cloud-operations. -Kelven >
