http://bugzilla.opensuse.org/show_bug.cgi?id=1070478 Bug ID: 1070478 Summary: Virtualization with virt-manager shareable disks are imposible Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: KVM Assignee: kvm-bugs@forge.provo.novell.com Reporter: dev.dorrejo@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0 Build Identifier: Hello i am trying to create a RAC lab, with KVM/QEMU using libvirt and when i add the disk to both VMs and put the option shareable the app send the next alert when i run both VMs: rror starting domain: internal error: process exited while connecting to monitor: 2017-11-30T05:23:44.088281Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/3 (label charserial0) 2017-11-30T05:23:44.160652Z qemu-system-x86_64: -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0: Failed to get "write" lock Is another process using the image? Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1505, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1069, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: process exited while connecting to monitor: 2017-11-30T05:23:44.088281Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/3 (label charserial0) 2017-11-30T05:23:44.160652Z qemu-system-x86_64: -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0: Failed to get "write" lock Is another process using the image? I try with SCSI and VirtIO but only appear that alert when i try run, first turn on one, and when i try turn on the other one that message appear. Reproducible: Always Steps to Reproduce: 1.Create 2 VMs 2.Create a Raw image 3.add new disk on both VMs using the Raw image and putting the flag shareable. Actual Results: appear the next alert: Error starting domain: internal error: process exited while connecting to monitor: 2017-11-30T05:23:44.088281Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/3 (label charserial0) 2017-11-30T05:23:44.160652Z qemu-system-x86_64: -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0: Failed to get "write" lock Is another process using the image? Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1505, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1069, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: process exited while connecting to monitor: 2017-11-30T05:23:44.088281Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/3 (label charserial0) 2017-11-30T05:23:44.160652Z qemu-system-x86_64: -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0: Failed to get "write" lock Is another process using the image? Expected Results: Both machine boot up and can see the disks IO on live. Opensuse TW last snapshot 20171125 last kernel 4.14.1.1. -- You are receiving this mail because: You are on the CC list for the bug.