[Bug 1070478] New: Virtualization with virt-manager shareable disks are imposible
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.
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478#c2
--- Comment #2 from Walddys Emmanuel Dorrejo Céspedes
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478#c3
--- Comment #3 from Walddys Emmanuel Dorrejo Céspedes
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478#c4
James Fehlig
<disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/home/wedc/VMs/crs.img'/> <target dev='vdb' bus='virtio'/> <shareable/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk>
This XML snippet of your disk device is correct. The <shareable> element should allow the disk to be shared. But as Fei noted, your libvirt is not passing 'share-rw=on' when invoking qemu. There is an upstream patch to fix it, which will be included in the upcoming libvirt 3.10.0 release. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478#c6
--- Comment #6 from Walddys Emmanuel Dorrejo Céspedes
(In reply to Walddys Emmanuel Dorrejo Céspedes from comment #2)
<disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/home/wedc/VMs/crs.img'/> <target dev='vdb' bus='virtio'/> <shareable/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk>
This XML snippet of your disk device is correct. The <shareable> element should allow the disk to be shared. But as Fei noted, your libvirt is not passing 'share-rw=on' when invoking qemu. There is an upstream patch to fix it, which will be included in the upcoming libvirt 3.10.0 release.
Ok thank you, but in the last kernel update i have problem with the network too, libnetcontrol and including virtualbox can't create a bridge network, i will change to leap 42.3 and hopefully that this stable version i not find this error. if you know that leap 42.3 is working all fine, tell me pls, that will be a great help. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478#c7
--- Comment #7 from James Fehlig
if you know that leap 42.3 is working all fine, tell me pls, that will be a great help.
Leap 42.3 is certainly more stable than bleeding-edge Tumbleweed, but that's not to say you wont encounter bugs in your environment/use-case. No software the size of a libvirt+qemu stack is bug free :-). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478#c8
--- Comment #8 from Walddys Emmanuel Dorrejo Céspedes
(In reply to Walddys Emmanuel Dorrejo Céspedes from comment #6)
if you know that leap 42.3 is working all fine, tell me pls, that will be a great help.
Leap 42.3 is certainly more stable than bleeding-edge Tumbleweed, but that's not to say you wont encounter bugs in your environment/use-case. No software the size of a libvirt+qemu stack is bug free :-).
ok, but actually in the net there is a crisis on the virtualization side with the new kernel, and last updates of the tools, i am looking is if on 42.3 is working virtualization without this problems, because i am on a clean install of TW, and the only package installed are the kvm patterns -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478#c9
--- Comment #9 from Walddys Emmanuel Dorrejo Céspedes
(In reply to Walddys Emmanuel Dorrejo Céspedes from comment #2)
<disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/home/wedc/VMs/crs.img'/> <target dev='vdb' bus='virtio'/> <shareable/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk>
This XML snippet of your disk device is correct. The <shareable> element should allow the disk to be shared. But as Fei noted, your libvirt is not passing 'share-rw=on' when invoking qemu. There is an upstream patch to fix it, which will be included in the upcoming libvirt 3.10.0 release.
where i put this code "-device virtio-blk-pci,drive=vda,share-rw=on # share-rw=on" on the xml file. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478#c10
--- Comment #10 from James Fehlig
where i put this code
"-device virtio-blk-pci,drive=vda,share-rw=on
You can't put that in the VM XML config. Fei was giving an example of how you would use the 'share-rw' option if invoking qemu directly. I suggest waiting until libvirt 3.10.0 is available early next week, where the bug you have encountered is already fixed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478
http://bugzilla.opensuse.org/show_bug.cgi?id=1070478#c11
--- Comment #11 from Walddys Emmanuel Dorrejo Céspedes
(In reply to Walddys Emmanuel Dorrejo Céspedes from comment #9)
where i put this code
"-device virtio-blk-pci,drive=vda,share-rw=on
You can't put that in the VM XML config. Fei was giving an example of how you would use the 'share-rw' option if invoking qemu directly.
I suggest waiting until libvirt 3.10.0 is available early next week, where the bug you have encountered is already fixed.
ok, thank you very much, i have recently update the TW system and fix all bugs/glitch/error for run and/or install a VMs with virt-manager, and too fix network bug with kvm/qemu and virtualbox. thank you for your attendance. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com