Bug 236111

Summary:	Fatal opcode error when booting with dom0_mem >= 2GB
Product:	Red Hat Enterprise Linux 5	Reporter:	Joseph Szczypek <joseph.szczypek>
Component:	kernel-xen	Assignee:	Keiichiro Tokunaga <ktokunag>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Jenner <mjenner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0	CC:	lwang, martine.silbermann, xen-maint
Target Milestone:	---
Target Release:	---
Hardware:	ia64
OS:	Linux
Whiteboard:
Fixed In Version:	5.1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-08-06 18:23:18 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:
Bug Depends On:
Bug Blocks:	223107

Description Joseph Szczypek 2007-04-11 22:53:53 UTC

Description of problem:
When Domain0 is booted with dom0_mem set to 2G or greater, a fatal opcode error
occurs.

Version-Release number of selected component (if applicable):
2.6.18-8.1.1.el5xen

How reproducible:
Easily

Steps to Reproduce:
1. Add dom0_mem to elilo.conf's "append" line for the Xen elilo.conf entry
2. Set dom0_mem to 2G or greater
3. Boot Domian 0.
  
Actual results:
Fatal opcode

Expected results:
Domain 0 boots

Additional info:
This error was produced on an rx6600 equipped with 8 cores and 96GB of memory. 
It has 3 dual-port Fibre Channel PCI-X cards installed, each port connected to
an MSA1000.

Comment 1 Red Hat Bugzilla 2007-07-25 00:45:01 UTC

change QA contact

Comment 2 Brian Stein 2007-08-03 15:13:56 UTC

Please confirm this behavior with the current 5.1 beta.

Comment 3 Joseph Szczypek 2007-08-06 17:35:08 UTC

(In reply to comment #2)
> Please confirm this behavior with the current 5.1 beta.

I booted with dom0_mem set to 2G, 4G, 8G, 16G, 32G, 64G with 5.1 beta.  I did
not get the 'fatal opcode' error.   Dom0 boots and I can log in.

FYI, there is a difference in the system configuration I was able to use to do
these tests.   I was only able to run with one MSA1000, connected to one FC port.

Comment 4 Brian Stein 2007-08-06 18:23:18 UTC

Marking as resolved in 5.1.  Please reopen this issue or create a new BZ if this
is reproduced during testing.