Bug 998065
Summary: | libguestfs kernel hang in RHEL 6.5 | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Colin Walters <walters> | |
Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.5 | CC: | bfan, leiwang, ptoscano, walters, wshi | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 998108 (view as bug list) | Environment: | ||
Last Closed: | 2014-05-20 11:05:16 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
Colin Walters
2013-08-16 22:46:40 UTC
With the -412 kernel, nested (ie. using TCG) I'm getting a slightly different problem. Lots of: [ 24.678207] Clocksource tsc unstable (delta = 75815452 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. [ 26.311900] Clocksource tsc unstable (delta = 78919174 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. [ 32.618435] Clocksource tsc unstable (delta = 197138175 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. [ 34.296502] Clocksource tsc unstable (delta = 167980713 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. [ 63.056573] Clocksource tsc unstable (delta = 71039379 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. [ 69.328987] Clocksource tsc unstable (delta = 226577207 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. [ 72.595910] Clocksource tsc unstable (delta = 267708526 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. [ 78.234690] Clocksource tsc unstable (delta = 85922093 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. [ 81.805477] Clocksource tsc unstable (delta = 71247525 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. [ 82.420955] Clocksource tsc unstable (delta = 115523027 ns). Enable clocksource failover by adding clocksource_failover kernel parameter. and not much progress being made. Upstream we switched over to using kvmclock (038ed0a08e & c53b459fdd) which we should probably do in RHEL too since it would avoid most of this trouble. I will test on baremetal next. It works OK for me on baremetal (with the -412 kernel). Is the error reproducible every time, or only occasionally? Are you using this on baremetal or nested (eg in a cloud VM)? (In reply to Richard W.M. Jones from comment #2) > It works OK for me on baremetal (with the -412 kernel). Hmm. So you're booting -412 on -412? I'm sadly stuck on 2.6.32-381.el6.x86_64 due to https://bugzilla.redhat.com/show_bug.cgi?id=987060 Although I haven't tested -412 yet as a host. Give me a bit to context switch and try it. > Is the error reproducible every time, or only occasionally? Hangs every time. > Are you using this on baremetal or nested (eg in a cloud VM)? Baremetal; Lenovo T420s laptop. Updates from IRC conversations and others: - Would be interesting to know if the kernel eventually prints out anything, or if nothing is printed before the libguestfs-test-tool timeout (10 mins). - I have tried the -412 kernel on 3 systems, 2 baremetal, 1 virtualized, and I can't reproduce it. Note the bug was reported on -410 so this is not necessarily indicative. Would be interesting to know if the -412 or -413 kernel also shows the bug. - Colin tried adding -cpu host,+kvmclock to the qemu command line, but that didn't make any difference. The bug still happened with kvmclock enabled (hence I'm removing the blocked bugs). This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Hello Colin Walters, May I know do you still meet this kernel hung in latest rhel6 kernel? I don't see this, and we'd have heard about it if it was happening in the released RHEL 6.5 kernel. My guess is it was a temporary blip in an unreleased kernel. |