Bug 1347172
| Summary: | 'info block' should not show backing file when reopen block after drive-mirror with 'sync=full' | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Qianqian Zhu <qizhu> |
| Component: | qemu-kvm-rhev | Assignee: | John Snow <jsnow> |
| Status: | CLOSED ERRATA | QA Contact: | Qianqian Zhu <qizhu> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 7.3 | CC: | chayang, juzhang, knoel, michen, mrezanin, qizhu, virt-bugs, virt-maint, xfu, xianwang |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.9.0-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 23:32:13 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: | |||
Too late in the 7.3 cycle to fix this for this release. Will investigate for 7.4. This bug also exists in ppc64le.test version is as follows: host is ppc64le, guest is ppc64 BE Host install tree: RHEL7.3-20161012.0 kernel: kernel-3.10.0-513.el7 qemu: qemu-kvm-rhev-2.6.0-27.el7 SLOF: SLOF-20160223-6.gitdbbfda4.el7 Guest: RHEL6.8 BE guest driveformat: virtio_blk nicmodel: spapr-vlan mem: 16G vcpu: 16 (In reply to xianwang from comment #3) > This bug also exists in ppc64le.test version is as follows: > host is ppc64le, guest is ppc64 BE > > Host install tree: RHEL7.3-20161012.0 > kernel: kernel-3.10.0-513.el7 > qemu: qemu-kvm-rhev-2.6.0-27.el7 > SLOF: SLOF-20160223-6.gitdbbfda4.el7 > > Guest: RHEL6.8 BE guest > driveformat: virtio_blk > nicmodel: spapr-vlan > mem: 16G > vcpu: 16 when check the info with"(qemu)info block" it will show backing file, but with command in terminal "#qemu-img info mirror_full",it will not show backing file No longer appears to reproduce under 2.9.0, try testing once more when convenient? Test on qemu-kvm-rhev-2.9.0-2.el7.x86_64: Steps same as comment 0. Result: as expected, block info has no backing file. So this is fixed in qemu-kvm-rhev-2.9.0-2.el7.x86_64. Great, moving to POST to indicate that we picked up a fix when we rebased to 2.9.0. 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 |
Description of problem: 'info block' should not show backing file when reopen block after drive-mirror with 'sync=full' Version-Release number of selected component (if applicable): kernel-3.10.0-425.el7.x86_64 qemu-kvm-rhev-2.6.0-6.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.launch guest with a snapshot: /usr/libexec/qemu-kvm -name avocado-vt-vm1 -sandbox off -machine pc -nodefaults -vga cirrus -drive id=drive-virtio-blk0,if=none,cache=none,snapshot=off,aio=native,format=qcow2,file=/root/sn1.qcow2 -device virtio-blk-pci,id=image1,drive=drive-virtio-blk0,bootindex=0,bus=pci.0,addr=03,disable-legacy=off,disable-modern=on -m 4096 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2 -cpu SandyBridge,+kvm_pv_unhalt -vnc :1 -boot order=cdn,once=c,menu=off,strict=off -monitor stdio -qmp tcp:0:5555,server,nowait 2.block mirror with 'sync=full' { "execute": "drive-mirror", "arguments": { "device": "drive-virtio-blk0", "target": "/root/sn2", "format": "qcow2", "mode": "absolute-paths", "sync": "full" } } 3.complete block mirror job, switch to target image: {"execute": "block-job-complete", "arguments": { "device": "drive-virtio-blk0" } } 4. query block info by 'info block' Actual results: (qemu) info block drive-virtio-blk0 (#block1048): /root/sn2 (qcow2) Cache mode: writeback, direct Backing file: /usr/share/avocado/data/avocado-vt/images/RHEL-Server-7.3-64-virtio.qcow2 (chain depth: 1) Expected results: target file sn2 should not have a backing file when 'sync=full' Additional info: qemu-img info give correct information for the target file sn2 # qemu-img info sn2 image: sn2 file format: qcow2 virtual size: 20G (21474836480 bytes) disk size: 4.8G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false