cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8762) Check KVM disk files for activity before starting VM
Date Wed, 02 Sep 2015 09:25:46 GMT


ASF subversion and git services commented on CLOUDSTACK-8762:

Commit 047d759a73572476353dc47d0ce41e8443829a4a in cloudstack's branch refs/heads/4.5 from
[;h=047d759 ]

Merge pull request #754 from shapeblue/4.5-CLOUDSTACK-8762

CLOUDSTACK-8762: Check to confirm disk activity before starting a VMImplements 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
file, on per-host basis.

Signed-off-by: Rohit Yadav <>

* pr/754:
  CLOUDSTACK-8762: Confirm disk activity before starting a VM

Signed-off-by: Rohit Yadav <>

> Check KVM disk files for activity before starting VM
> ----------------------------------------------------
>                 Key: CLOUDSTACK-8762
>                 URL:
>             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

View raw message