Bug 1673014

Summary: Local VM and migrated VM on the same host can run with same RAW file as visual disk source while without shareable configured or lock manager enabled
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: Kevin Wolf <kwolf>
Component: qemu-kvmAssignee: Kevin Wolf <kwolf>
Status: CLOSED ERRATA QA Contact: CongLi <coli>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: chayang, ddepaula, juzhang, knoel, rbalakri, virt-bugs, virt-maint
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-3.1.0-13.module+el8+2783+15cec5ae Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1531888 Environment:
Last Closed: 2019-05-29 16:05:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1531888    
Bug Blocks: 1673010    

Comment 2 Danilo de Paula 2019-02-06 15:39:53 UTC
Hi Kevin,

Why not Internal Target Release == 8.0.0.0?

Comment 3 Danilo de Paula 2019-02-06 15:40:29 UTC
qa_ack+, please

Comment 4 Kevin Wolf 2019-02-06 16:58:39 UTC
(In reply to Danilo Cesar de Paula from comment #2)
> Why not Internal Target Release == 8.0.0.0?

Because I forgot to set it. :-)

Doing that now.

Comment 5 Danilo de Paula 2019-02-11 20:01:24 UTC
Fix included in qemu-kvm-3.1.0-13.module+el8+2783+15cec5ae

Comment 6 CongLi 2019-02-19 09:32:54 UTC
Reproduced this issue on qemu-kvm-3.1.0-5.module+el8+2708+fbd828c6 with steps in description:
Terminal 1:
(qemu) info status
VM status: running
Terminal 2:
(qemu) c
Failed to get "write" lock
Is another process using the image?
**after migration**
(qemu) info status
VM status: running
Terminal 3:
(qemu) info status
VM status: paused (postmigrate)

Verified this bug on qemu-kvm-3.1.0-15.module+el8+2792+e33e01a0.x86_64:
Terminal 1:
(qemu) info status
VM status: running
Terminal 2:
(qemu) c
Failed to get "write" lock
Is another process using the image [/home/kvm_autotest_root/images/rhel80-64-virtio-scsi.raw]?
**after migration**
(qemu) qemu-kvm: Failed to get "write" lock
Is another process using the image [/home/kvm_autotest_root/images/rhel80-64-virtio-scsi.raw]?
(qemu) info status
VM status: paused
(qemu) c
Failed to get "write" lock
Is another process using the image [/home/kvm_autotest_root/images/rhel80-64-virtio-scsi.raw]?
Terminal 3:
(qemu) info status
VM status: paused (postmigrate)

Thanks.

Comment 8 errata-xmlrpc 2019-05-29 16:05:30 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1293