Bug 1248312
Summary: | "fdisk -l"can not output anything and the process status is D+ after migrating RHEL7.2 guest with virtio-1 virtio-scsi disk | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Yanhui Ma <yama> |
Component: | qemu-kvm-rhev | Assignee: | jason wang <jasowang> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.2 | CC: | dgilbert, huding, jasowang, juzhang, mrezanin, virt-maint, xfu, yama, zhengtli |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.3.0-18.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-04 16:52:55 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
Yanhui Ma
2015-07-30 05:19:31 UTC
Did upstream qemu.git work for this? Fix included in qemu-kvm-rhev-2.3.0-18.el7 reproduce the issue: source host: 3.10.0-303.el7.x86_64 qemu-kvm-rhev-2.3.0-17.el7.x86_64 destination host: 3.10.0-304.el7.x86_64 qemu-kvm-rhev-2.3.0-17.el7.x86_64 steps: the steps is the same as steps in description results: after "fdisk -l", no output, after "ps aux | grep fdisk" the process status is D+. ps aux | grep fdisk root 3109 0.0 0.0 112420 956 pts/0 D+ 11:16 0:00 fdisk -l root 3836 0.0 0.0 112640 928 pts/1 S+ 12:24 0:00 grep --color=auto fdisk ============================================================================ verify the issue: source host: 3.10.0-303.el7.x86_64 qemu-kvm-rhev-2.3.0-18.el7.x86_64 destination host: 3.10.0-304.el7.x86_64 qemu-kvm-rhev-2.3.0-18.el7.x86_64 steps: the steps is the same as steps in description results: run "fdisk -l" successfully Based on the above results, I think the bug is fixed. According to comment10, set this issue as verified. *** Bug 1247541 has been marked as a duplicate of this bug. *** 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 |