Bug 1189998
Summary: | Active commit does not support on rbd based disk | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Yang Yang <yanyang> | |
Component: | qemu-kvm-rhev | Assignee: | Jeff Cody <jcody> | |
Status: | CLOSED ERRATA | QA Contact: | Suqin Huang <shuang> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 7.1 | CC: | chayang, coli, dyuan, hhuang, huding, jcody, juzhang, michen, mzhan, rhbug, ruben, shuang, virt-maint, xuzhang | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | qemu-kvm-rhev-2.9.0-3.el7 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1200726 (view as bug list) | Environment: | ||
Last Closed: | 2017-08-01 23:27:12 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: | ||||
Bug Blocks: | 1200726 |
Description
Yang Yang
2015-02-06 03:16:59 UTC
Is there currently any progress on it? Could you provide us an update, when it could possibly be fixed? (In reply to rhbug from comment #2) > Is there currently any progress on it? Could you provide us an update, when > it could possibly be fixed? Thanks for taking the time to enter a bug report with us. We use reports like yours to keep improving the quality of our products and releases. 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. 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. For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto Patches submitted upstream, for QEMU 2.10: https://lists.nongnu.org/archive/html/qemu-devel/2017-04/msg00729.html Patches applied to my block branch: https://lists.nongnu.org/archive/html/qemu-devel/2017-04/msg03374.html Fix included in qemu-kvm-rhev-2.9.0-3.el7 Hi Jeff, Package: qemu-kvm-rhev-2.9.0-6.el7.x86_64 Could you check if something wrong in my syntax? { "execute": "block-commit", "arguments": { "device": "drive_image1", "base": "rbd:kvm-test/rhel74-64-virtio.raw:mon_host=10.73.199.64", "top": "/root/sn3", "speed": 1000000000 } } {"error": {"class": "GenericError", "desc": "Base 'rbd:kvm-test/rhel74-64-virtio.raw:mon_host=10.73.199.64' not found"}} Hi Suqin, What does your block chain and qemu command look like? The error indicates that we are not able to find the image with that filename. Can you show the output of the QMP command { "execute": "query-block" }? { "execute": "query-block" } {"return": [{"io-status": "ok", "device": "drive_image1", "locked": false, "removable": false, "inserted": {"iops_rd": 0, "detect_zeroes": "off", "image": {"backing-image": {"backing-image": {"backing-image": {"virtual-size": 42212254720, "filename": "json:{\"driver\": \"raw\", \"file\": {\"pool\": \"kvm-test\", \"image\": \"rhel74-64-virtio.raw\", \"driver\": \"rbd\", \"=keyvalue-pairs\": \"[\\\"mon_host\\\", \\\"10.73.199.64\\\"]\"}}", "cluster-size": 4194304, "format": "raw", "dirty-flag": false}, "backing-filename-format": "raw", "virtual-size": 42212254720, "filename": "/root/sn1", "cluster-size": 65536, "format": "qcow2", "actual-size": 9187328, "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false}}, "full-backing-filename": "json:{\"driver\": \"raw\", \"file\": {\"pool\": \"kvm-test\", \"image\": \"rhel74-64-virtio.raw\", \"driver\": \"rbd\", \"=keyvalue-pairs\": \"[\\\"mon_host\\\", \\\"10.73.199.64\\\"]\"}}", "backing-filename": "json:{\"driver\": \"raw\", \"file\": {\"pool\": \"kvm-test\", \"image\": \"rhel74-64-virtio.raw\", \"driver\": \"rbd\", \"=keyvalue-pairs\": \"[\\\"mon_host\\\", \\\"10.73.199.64\\\"]\"}}", "dirty-flag": false}, "backing-filename-format": "qcow2", "virtual-size": 42212254720, "filename": "/root/sn2", "cluster-size": 65536, "format": "qcow2", "actual-size": 7680000, "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false}}, "full-backing-filename": "/root/sn1", "backing-filename": "/root/sn1", "dirty-flag": false}, "backing-filename-format": "qcow2", "virtual-size": 42212254720, "filename": "/root/sn3", "cluster-size": 65536, "format": "qcow2", "actual-size": 58859520, "format-specific": {"type": "qcow2", "data": {"compat": "1.1", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false}}, "full-backing-filename": "/root/sn2", "backing-filename": "/root/sn2", "dirty-flag": false}, "iops_wr": 0, "ro": false, "node-name": "#block2249", "backing_file_depth": 3, "drv": "qcow2", "iops": 0, "bps_wr": 0, "write_threshold": 0, "backing_file": "/root/sn2", "encrypted": false, "bps": 0, "bps_rd": 0, "cache": {"no-flush": false, "direct": true, "writeback": true}, "file": "/root/sn3", "encryption_key_missing": false}, "type": "unknown"}]} Steps: 1. { "execute": "qmp_capabilities" } 2. Create sn1 ~ sn3 { "execute": "blockdev-snapshot-sync", "arguments": { "device": "drive_image1", "snapshot-file": "/root/sn1", "format": "qcow2" } } { "execute": "blockdev-snapshot-sync", "arguments": { "device": "drive_image1", "snapshot-file": "/root/sn2", "format": "qcow2" } } { "execute": "blockdev-snapshot-sync", "arguments": { "device": "drive_image1", "snapshot-file": "/root/sn3", "format": "qcow2" } } 3. do block commit { "execute": "block-commit", "arguments": { "device": "drive_image1", "base": "", "top": "/root/sn3, "speed": 1000000000 } } cmd: /usr/libexec/qemu-kvm \ -S \ -name 'avocado-vt-vm1' \ -sandbox off \ -machine pc \ -nodefaults \ -vga std \ -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/src,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=serial_id_serial0,path=/tmp/serial-src0,server,nowait \ -device isa-serial,chardev=serial_id_serial0 \ -device ich9-usb-ehci1,id=usb1,addr=1d.7,multifunction=on,bus=pci.0 \ -device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=1d.0,firstport=0,bus=pci.0 \ -device ich9-usb-uhci2,id=usb1.1,multifunction=on,masterbus=usb1.0,addr=1d.2,firstport=2,bus=pci.0 \ -device ich9-usb-uhci3,id=usb1.2,multifunction=on,masterbus=usb1.0,addr=1d.4,firstport=4,bus=pci.0 \ -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,format=raw,file=rbd:kvm-test/rhel74-64-virtio.raw:mon_host=10.73.199.64 \ -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=03 \ -device virtio-net-pci,mac=9a:04:0e:0f:10:59,id=idKK4Mdq,vectors=4,netdev=idgjGCvt,bus=pci.0,addr=05 \ -netdev tap,id=idgjGCvt,vhost=on,script=/etc/qemu-ifup \ -m 2048 \ -smp 4,maxcpus=4,cores=2,threads=1,sockets=2 \ -cpu Opteron_G3 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :0 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off,strict=off \ -enable-kvm \ -monitor stdio The backing file created from the snapshots is in json format, which is likely the reason it is not being found from the the filename URI. In this particular test case, you could omit the base name, as it will commit to the deepest layer by default. Reproduce with qemu-kvm-rhev-2.9.0-2.el7.x86_64 {"error": {"class": "GenericError", "desc": "Block format 'rbd' used by node '#block089' does not support reopening files"}} Fixed on qemu-kvm-rhev-2.9.0-9.el7.x86_64 { "execute": "block-commit", "arguments": { "device": "drive_image1", "top": "/root/sn3", "speed": 1000000000 } } {"return": {}} (qemu) info block-jobs Type commit, device drive_image1: Completed 19595264 of 19595264 bytes, speed limit 1000000000 bytes/s Steps: { "execute": "qmp_capabilities" } { "execute": "blockdev-snapshot-sync", "arguments": { "device": "drive_image1", "snapshot-file": "/root/sn1", "format": "qcow2" } } {"return": {}} { "execute": "blockdev-snapshot-sync", "arguments": { "device": "drive_image1", "snapshot-file": "/root/sn2", "format": "qcow2" } } {"return": {}} { "execute": "blockdev-snapshot-sync", "arguments": { "device": "drive_image1", "snapshot-file": "/root/sn3", "format": "qcow2" } } {"return": {}} { "execute": "block-commit", "arguments": { "device": "drive_image1", "top": "/root/sn3", "speed": 1000000000 } } {"return": {}} { "execute": "block-job-complete", "arguments": { "device": "drive_image1" } } {"return": {}} According to comment14, update bug status to VERIFIED 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 |