Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 237895
Summary: | Fully virtualized FC6 guests hang at random times | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom Horsley <horsley1953> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | buckh, jonstanley |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-08 04:28:04 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: | |||
Bug Depends On: | |||
Bug Blocks: | 427887 |
Description
Tom Horsley
2007-04-25 21:49:13 UTC
Apparently more memory and newer kernel doesn't fix the hangs. Found it at 100% cpu and non-responsive on console or to ssh again this morning. I see the last thing in the cron log before I found it hung was: Apr 26 05:10:01 fc6-x86-64 crond[3039]: (root) CMD (/usr/lib64/sa/sa1 1 1) It did manage to get through a full yum update before it crashed though, so perhaps it isn't the same disk I/O related crash I see on rhel5 after all, but a new crash for some different reason. Found it hung again, but I have a comparison point this time. I also installed an i386 fc6 HVM, and it has never experienced this hang, so whatever is going on appears to be x86_64 specific (on the evidence so far, anyway). Anyone know of anything that always happens around 5 am? So far the last cron log entries have always shown the system was still alive around 5, and then stopped responding. 4-5AM is usually when cron jobs are running (makewhatis / prelink etc.) New data point: I'm trying to replace the fc6 guests with fedora 7 guests, and the hangs are infinitely more frequent with fc7 fully virtual guests. In fact, with the i386 guest, I can't even get it far enough to try installing. It has done the hang at 100% cpu on the scanning for packages step as well as the formatting disk step. So perhaps there is a simpler to reproduce example out there now (weird that now the i386 is the one with the big problems and x86_64 works better). These are both guest installs using the virt-manager in the FC6 dom0 host and the DVD iso's from the fedora 7 release to attempt the install. (This is a mass-update to all current FC6 kernel bugs in NEW state) Hello, I'm reviewing this bug list as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug, however this version of Fedora is no longer maintained. Please attempt to reproduce this bug with a current version of Fedora (presently Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a few days if there is no further information lodged. Thanks for using Fedora! Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA, since no information has been lodged for over 30 days. Please re-open this bug or file a new one if you can provide the requested data, and thanks for filing the original report! |