Bug 1175502
| Summary: | qemu instances started by nova fail to boot | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Lars Kellogg-Stedman <lars> |
| Component: | qemu-kvm-rhev | Assignee: | Virtualization Maintenance <virt-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | yeylon <yeylon> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0 (Juno) | CC: | kchamart, knoel, lersek, mrezanin, rjones, srevivo, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 6.0 (Juno) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-16 15:31:49 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
Lars Kellogg-Stedman
2014-12-17 21:26:52 UTC
The bug you specifically mention looks a lot like one which you could solve by adding no_timer_check to the kernel command line (this is the default in modern kernels, but you don't mention what kernel version this is). I'd also like to pimp qemu-sanity-check: http://people.redhat.com/~rjones/qemu-sanity-check/ It only has very minimal dependencies (just gcc, glibc-static and bash) and can test if a kernel is compatible with a qemu. Ah, the no_timer_check was discussed here https://bugs.launchpad.net/cirros/+bug/1312199 Speaking of no_timer_check, Daniel Berrnage once pointed me to this commit[1] in upstream Nova): commit 6b86a61fee15ce1237303fab2f7896f8c3bcad47 Author: Attila Fazekas <afazekas> Date: Wed May 28 09:19:29 2014 +0200 Use no_timer_check with soft-qemu The Linux kernel timer check not working properly when the hypervisor's thread preempted by the host CPU scheduler. The timer check is automatically disabled with other types of hypervisors including the hardware accelerated kvm, but timer_check is not disabled when qemu used without hardware acceleration. This issue is frequently mischaracterized as an SSH connectivity issue and causes rechecks and occasional boot failures. This change adds no_timer_check kernel parameter when we are using uec images with qemu. Closes-Bug: #1312199 Change-Id: I3cfdfe9048fe219fc12cdac8a399b496f237e55e [1] https://review.openstack.org/#/c/96090/ There are already bugs open against our guest images to add the no_timer_check parameter: - https://bugzilla.redhat.com/show_bug.cgi?id=1144155 - https://bugzilla.redhat.com/show_bug.cgi?id=1147035 So maybe this is CLOSE NOTABUG, but there is a difference in behavior with these two qemu versions. Miroslav, do you know if there were any changes that might account for this? I don't see anything obvious in the package changelog. Changelog contains all changes done in qemu-kvm-rhev between -7 and -10 version. I suspect the vmstate_xhci_event patches to be the culprit but I do not know how they can cause this? Any idea Laszlo? Nothing seems relevant. I suggest trying each official build in the interval, and then bisecting the "culprit build" patch for patch. |