Bug 490080

Summary:	kernel-2.6.29-0.218 does not boot on an x86_64 VM
Product:	[Fedora] Fedora	Reporter:	Debarshi Ray <debarshir>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	11	CC:	kernel-maint
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:	2009-08-06 19:43:03 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:

Description Debarshi Ray 2009-03-13 05:14:24 UTC

Description of problem:
The two most recent Rawhide kernels fail to boot on a x86_64 KVM based virtual machine created by a Fedora 10 Virt Manager.

Version-Release number of selected component (if applicable):
kernel-2.6.29-0.218.rc7.git2.fc11.x86_64
kernel-2.6.29-0.237.rc7.git4.fc11.x86_64

Comment 1 Chuck Ebbert 2009-03-14 01:44:59 UTC

What kernel version is the f10 machine running? You might need the latest 2.6.27.19 kernel...

Comment 2 Debarshi Ray 2009-03-14 06:18:55 UTC

I am running kernel-2.6.27.19-170.2.35.fc10.x86_64 on Fedora 10 x86_64 host.

Comment 3 Debarshi Ray 2009-03-14 06:46:18 UTC

I updated the hosts libvirt and virt-manager to the latest versions from Fedora 10's update-testing without any luck. They fail, as before, with the following messages seen if 'Esc' was hit immediately after hitting 'Enter' in Grub:
+ kernel-2.6.29-0.237.rc7.git4.fc11.x86_64:
    Clocksource tsc unstable (delta = -153867381 ns)
+ kernel-2.6.29-0.218.rc7.git2.fc11.x86_64:
    Clocksource tsc unstable (delta = -275552273 ns)

Since I had updated the Rawhide VM from a Fedora 10 x86_64 preview release, I have kernel-2.6.27.4-68.fc10 on it and it does boot.

Not sure if this is related or not, but I have some SELinux related problems probably due to the messy upgrade from Fedora 10 preview to post Fedora 11 alpha Rawhide -- RPM, OpenSSL, Python 2.6, etc -- and I am using 'enforcing=0'.

Comment 4 Bug Zapper 2009-06-09 12:12:51 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Debarshi Ray 2009-07-27 16:39:44 UTC

I can boot Fedora 11 x86_64 on a Fedora 10 x86_64 VM now. So can this be closed?

Comment 6 Mike Gahagan 2009-08-06 19:43:03 UTC

Thanks for the feedback, I think we can close this now if its working ok for you with current updates.