[
https://issues.apache.org/jira/browse/CLOUDSTACK-8762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727065#comment-14727065
]
ASF subversion and git services commented on CLOUDSTACK-8762:
-------------------------------------------------------------
Commit 711acfa93dd8fcf1083062753464901c171f4d6f in cloudstack's branch
refs/heads/4.5 from [~rohit.ya...@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=711acfa ]
CLOUDSTACK-8762: Confirm disk activity before starting a VM
Implements a VM volume/disk file activity checker that checks if QCOW2 file
has been changed before starting the VM. This is useful as a pessimistic
approach to save VMs that were running on faulty hosts that CloudStack could
try to launch on other hosts while the host was not cleanly fenced. This is
optional and available only if you enable the settings in agent.properties
file, on per-host basis.
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
> Check KVM disk files for activity before starting VM
> ----------------------------------------------------
>
> Key: CLOUDSTACK-8762
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8762
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.5.3, 4.6.0
>
>
> KVM hosts have real issue with fencing when storage are accessible by
> multiple hosts such as in the case of NFS, in which case there is a
> possibility of qcow2 disks being accessed by multiple hosts causing disk
> corruptions. The aim of this ticket is to explore ways to delay starting a VM
> if the qcow2 disks/files are still being accessed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
