Bug 585951
| Summary: | A process using kvm can enter a non-killable state | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Naphtali Sprei <nsprei> | ||||
| Component: | kvm | Assignee: | Virtualization Maintenance <virt-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 5.4 | CC: | mtosatti, virt-maint, ykaul | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-05-04 07:38:59 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 409187 [details]
test-case for the bug
*** This bug has been marked as a duplicate of bug 588251 *** |
Description of problem: While running one of the qemu-kvm unit test (called access), the qemu process gets to a state that it cannot be killed. When killed, the process get's zombied but continue to consume resources. Version-Release number of selected component (if applicable): kvm-83-143.el5 How reproducible: Consistently, every time. Steps to Reproduce: 1. qemu-kvm -kernel access.flat (the attached test-case) This test-case was/can be built from qemu-kvm unit tests. clone an upstream qemu-kvm git repo, go to its subdir kvm/user and type make test-cases are created in test/x86 subdir, including access.flat Intended test runs with following parameters to produce output: "-kernel access.flat -device testdev,chardev=testlog -chardev file,id=testlog,path=access.log", where access.log is an example of an output file 2. wait about 5 minutes Actually, the test-case runs lots of sub-test-cases until it reaches the problematic sub-test-case that causes this problem. You can follow the output to see when it's stuck. 3. try to kill qemu-kvm process Actual results: qemu-kvm process keeps running Expected results: qemu-kvm process killed and disappear Additional info: