# Bug with migration VMs that using volatile disks on LVM

**URL:** <https://forum.opennebula.io/t/bug-with-migration-vms-that-using-volatile-disks-on-lvm/7112>\
**Category:** Product Support\
**Created:** [April 5, 2019, 10:43am UTC](https://forum.opennebula.io/t/bug-with-migration-vms-that-using-volatile-disks-on-lvm/7112 "2019-04-05T10:43:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sergjack](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@sergjack](https://forum.opennebula.io/u/sergjack)\
**Post date:** [April 9, 2019, 6:27am UTC](https://forum.opennebula.io/t/bug-with-migration-vms-that-using-volatile-disks-on-lvm/7112/3 "2019-04-09T06:27:39Z")

</div>

Thanks.  
Can you tell something about this issue?

> [@IO hangs on LVM Datastore during new VM creation](https://forum.opennebula.io/t/io-hangs-on-lvm-datastore-during-new-vm-creation/7105/7):
>
> Is storage driver compatible with lvmlockd? I see that lv commands a little differs when lvmlockd is used. For example mounts should be exclusive and so on.

---

_[View the full topic](https://forum.opennebula.io/t/bug-with-migration-vms-that-using-volatile-disks-on-lvm/7112)._