Bug 855700

Summary:	kernel 3.5.3-1 and an iPXE network boot results in a KVM crash
Product:	[Fedora] Fedora	Reporter:	Patrick <rh_bugzilla>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	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:	2012-09-10 17:36:40 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 Patrick 2012-09-10 04:10:25 UTC

Description of problem:
With kernel 3.5.3-1 doing an iPXE network boot results in a KVM crash. Kernel 3.5.2 works

Version-Release number of selected component (if applicable):
Kernel 3.5.3-1.fc17.x86_64

How reproducible:
Boot F17 x86_64 box with kernel-3.5.3-1 and try to iPXE network boot a new VM. The process hangs during the iPXE phase and a crash in KVM is reported in the log file.

Steps to Reproduce:
1. boot F17 x86_64 box with kernel-3.5.3-1
2. iPXE network boot a new VM
3. error: KVM: entry failed, hardware error 0x80000021
  
Actual results:
error: KVM: entry failed, hardware error 0x80000021

Expected results:
a succesful iPXE network boot

Additional info:
This bug has also been reported and discussed here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1045027

Comment 1 Patrick 2012-09-10 04:12:54 UTC

The suggestion in the Ubuntu bugreport to load the kvm_intel module with emulate_invalid_guest_state=y did *not* result in a working iPXE boot when running kernel 3.5.3-1.

Comment 2 Patrick 2012-09-10 17:36:40 UTC


*** This bug has been marked as a duplicate of bug 854983 ***