Bug 1179555
Summary: | qemu-kvm Segmentation fault when switch runlevel 5 to runlevel 3 inside RHEL6 guest | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | FuXiangChun <xfu> |
Component: | qemu-kvm-rhev | Assignee: | Gerd Hoffmann <kraxel> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.1 | CC: | juzhang, mazhang, michen, mrezanin, virt-maint, xfu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu 2.3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-04 16:25:06 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: |
Description
FuXiangChun
2015-01-07 05:21:56 UTC
RHEL6.6 64 bit guest also hit the same issue(send key ctrl-alt-F2 via spice). But 7.1 guest works well. Doesn't reproduce. Please retest with qemu 2.3. (In reply to Gerd Hoffmann from comment #7) > Doesn't reproduce. Please retest with qemu 2.3. Gerd, As this bug is found on 160 vcpus guest. I need to reserve a host of 160 processors. Anyway, I will update test result to bz asap. The bug can not be reproduced with qemu-kvm-rhev-2.3.0-1.el7.x86_64. QE tested two hosts. still can not reproduce it. Seems the rebase picked up a fix then. 1. Test this bug on qemu-kvm-rhev-2.1.2-16.el7.x86_64 with rhel6.4 and rhel6.7 guest, can't reproduce it. 2. Also test on latest qemu-kvm version qemu-kvm-rhev-2.3.0-12.el7.x86_64 with rhel6.4 rhel6.7 guest and rhel7.2 guest. a) For rhel6.4 and rhel6.7 guest, qemu-kvm and guest works well. b) For rhel7.2 guest test, try switch runlevel from 5 to 3 got black screen, see bug 1245551 Base on above, set this bug as verified, if any problem please let me know. Thanks, Mazhang. 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://rhn.redhat.com/errata/RHBA-2015-2546.html |