AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Qemu img11/25/2023 ![]() ![]() qemu-img create -f qcow2 /mnt/tmp/foo.qcow2 64Mįormatting '/mnt/tmp/foo.qcow2', fmt=qcow2 size=67108864 cluster_size=65536 lazy_refcounts=off refcount_bits=16 I don’t think the problem is locking support, because if I deliberately break all file locking calls in qemu, this is the result: not the Linux NFS server), I wonder whether this is a duplicate of BZ 1817640 (where a Dell/EMC NFS server was used). ![]() Seeing that this is about a Windows-based NFS server (i.e. If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization that will result in a timely resolution.įor information on how to contact the Red Hat production support team, please visit: That said, we're not able to guarantee the timeliness or suitability of a resolution for issues entered here because this is not a mechanism for requesting support. We use reports like yours to keep improving the quality of our products and releases. How is this handled in recent QEMU versions? If things are OK in RHEL-8, we can close this BZ, as support for locking in the NFS server is a requirement to have this working. * Any additional hints or advice for what to enable in the NFS server to enable locking? > # qemu-img info /home/win_nfs_test/test.raw > qemu-img: /home/win_nfs_test/test.raw: Failed to get "resize" lock > # qemu-img create -f raw /home/win_nfs_test/test.raw 1G > Tested with raw format, also hit this issue. I wonder if there's a way to differentiate between fail if locking is not supported vs fail when the lock is held. > qemu-img: /home/win_nfs_test/test.qcow2: Failed to get "resize" lock > # qemu-img info /home/win_nfs_test/test.qcow2Īpparently the image was created, but empty. "Image is not in qcow2 format" doesn't seem to be right. > qemu-img: /home/win_nfs_test/test.qcow2: Image is not in qcow2 format > cluster_size=65536 lazy_refcounts=off refcount_bits=16 > # qemu-img create -f qcow2 /home/win_nfs_test/test.qcow2 1G (In reply to Xueqiang Wei from comment #2) Max: the error message is confusing though, see inline comments: This happens because QEMU introduced support for locking in qcow2 (to prevent an image from being open by multiple apps or users) and this server doesn't seem to have locking support or it's not enabled. # qemu-img info /home/win_nfs_test/test.raw Qemu-img: /home/win_nfs_test/test.raw: Failed to get "resize" lock # qemu-img create -f raw /home/win_nfs_test/test.raw 1Gįormatting '/home/win_nfs_test/test.raw', fmt=raw size=1073741824 Tested with raw format, also hit this issue. Qemu-img: /home/win_nfs_test/test.qcow2: Failed to get "resize" lock Qemu-img: /home/win_nfs_test/test.qcow2: Image is not in qcow2 format # qemu-img info /home/win_nfs_test/test.qcow2 ![]() # qemu-img create -f qcow2 /home/win_nfs_test/test.qcow2 1Gįormatting '/home/win_nfs_test/test.qcow2', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16 Tested with qemu-kvm-rhev-2.9.0-16.el7_4.14, not hit this issue. ![]()
0 Comments
Read More
Leave a Reply. |