Bug 1393698
| Summary: | Correctly set host bits for guests to go beyond 1TB | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Miroslav Rezanina <mrezanin> |
| Component: | qemu-kvm-rhev | Assignee: | Dr. David Alan Gilbert <dgilbert> |
| Status: | CLOSED ERRATA | QA Contact: | Yumei Huang <yuhuang> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | chayang, hhuang, jinzhao, juzhang, mtessun, virt-maint, yuhuang |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | 7.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 23:39: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: | 1392328, 1395265, 1401400 | ||
|
Description
Miroslav Rezanina
2016-11-10 07:58:05 UTC
We dont need to do anything for 7.4 because we've already picked up the 'Enable host-phys-bits on RHEL' patch (0e8ab1be) from RHEV-7.3, that should be enough. See the setting of host-phys-bits in PC_RHEL_COMPAT. QA: Please verify in same way as bz 1339196 comment 14, also check big VMs (>128GB) work OK. (Marking as ON-QA since it doesn't need any code doing but we still need it checking) Verify: qemu-kvm-rhev-2.8.0-3.el7 kernel-3.10.0-558.el7.x86_64 Steps: 1. Boot guest on AMD host, and migrate to a file # /usr/libexec/qemu-kvm -m 4G -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off,vmport=off -cpu cpu64-rhel6,+rdtscp,+ht,+vme \ -smp 4,sockets=4,cores=1,threads=1 -monitor stdio \ -drive file=rhel73-64-virtio.qcow2,if=none,id=drive-virtio-blk0,format=qcow2,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=drive-virtio-blk0,bootindex=0 \ -spice port=5930,disable-ticketing \ -vga qxl -global qxl-vga.vram_size=33554432 -nodefaults (qemu) migrate "exec:cat > /tmp/mig-test-file" 2. Copy the file to an Intel host, and boot guest from the file # /usr/libexec/qemu-kvm -m 4G -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off,vmport=off -cpu cpu64-rhel6,+rdtscp,+ht,+vme \ -smp 4,sockets=4,cores=1,threads=1 -monitor stdio \ -drive file=rhel73-64-virtio.qcow2,if=none,id=drive-virtio-blk0,format=qcow2,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=drive-virtio-blk0,bootindex=0 \ -spice port=5930,disable-ticketing \ -vga qxl -global qxl-vga.vram_size=33554432 -nodefaults \ -incoming "exec:cat /tmp/mig-test-file" Guest works well on Intel host. QE also test big vm with 200GB memory, and use dd to allocate memory in guest. Guest works well, and no error in dmesg. 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 |