Bug 1425151
Summary: | qemu zeroes the first byte of NVDIMM on initialization | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Michal Privoznik <mprivozn> |
Component: | qemu-kvm-rhev | Assignee: | Stefan Hajnoczi <stefanha> |
Status: | CLOSED ERRATA | QA Contact: | Yumei Huang <yuhuang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.4 | CC: | chayang, jinzhao, juzhang, knoel, michen, mrezanin, stefanha, virt-maint, yuhuang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
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:44:45 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: | 1270403 |
Description
Michal Privoznik
2017-02-20 16:36:35 UTC
Fixed by the following upstream patch in QEMU 2.9.0-rc1: commit 9dc44aa5829eb3131a01378a738dee28a382bbc1 Author: Daniel P. Berrange <berrange> Date: Fri Mar 3 11:32:55 2017 +0000 os: don't corrupt pre-existing memory-backend data with prealloc Reproduce: qemu-kvm-rhev-2.8.0-6.el7 kernel-3.10.0-655.el7.x86_64 Steps: 1. # echo -n 'A' > /tmp/nvdimm.dat 2. # truncate -s 10M /tmp/nvdimm.dat 3. # hexdump -C /tmp/nvdimm.dat 00000000 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |A...............| 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00a00000 4. # /usr/libexec/qemu-kvm -m 4G,slots=40,maxmem=40G \ -drive file=rhel74.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \ -netdev tap,id=idinWyYp -device virtio-net-pci,mac=42:ce:a9:d2:4d:d7,id=idlbq7eA,netdev=idinWyYp \ -vnc :0 -monitor stdio -machine pc,nvdimm \ -object memory-backend-file,id=mem1,share=on,mem-path=/tmp/nvdimm.dat,size=$((10 * 1024 * 1024)) -device nvdimm,id=nvdimm1,memdev=mem1 \ -mem-prealloc 5. # hexdump -C /tmp/nvdimm.dat 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00a00000 Verify: qemu-kvm-rhev-2.9.0-1.el7 kernel-3.10.0-655.el7.x86_64 With same steps as above, after step5, # hexdump -C /tmp/nvdimm.dat 00000000 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |A...............| 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00a00000 The first byte of the file is not changed. So the bug is fixed. 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 |