Bug 714497

Summary:	Linux 3.0-rc2+ and on broke 64bit guest detection in VirtualBox
Product:	[Fedora] Fedora	Reporter:	Shawn Starr <shawn.starr>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	aquini, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
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:	2011-06-26 02:24:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Shawn Starr 2011-06-19 17:15:59 UTC

Description of problem:
While upgrading to latest kernel -rc2, and then -rc3 in Fedora rawhide. I cannot boot a Windows 64bit Guest, it says the CPU cannot support 64bit and fails to boot the VM guest.

Version-Release number of selected component (if applicable):

Fails
====
kernel-3.0-0.rc2.git0.2.fc16.x86_64
kernel-3.0-0.rc3.git5.1.fc16.x86_64

Works
=====
3.0.0-0.rc1.git0.1.fc16.x86_64

How reproducible: 100%


Steps to Reproduce:
1. Boot host with newer kernel than -rc1
2. Start VirtualBox , VM will abort on very initiation of bootloader loading windows components.
  
Actual results:
VM guest aborts loading with message

Expected results:
VM loads, no issues.

Additional info:

I am going to be trying vanilla kernel.org -rc3 and use fedora's .config from RPM to confirm if this is a Fedora patch that broke something or if a .config option we are using turns off something that is required.

Comment 1 Shawn Starr 2011-06-26 02:24:21 UTC

This is VirtualBox bug, I found their code does not properly deal with '3.0' from 'x.y.z' format. Close it!