Bug 212500

Summary: The Xen is in panic when specifying "maxmem =" in domVTI-config.
Product: [Fedora] Fedora Reporter: yoshiro fujita <yo.fujita>
Component: xenAssignee: Steven Rostedt <srostedt>
Status: CLOSED WONTFIX QA Contact: Martin Jenner <mjenner>
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: bstein, katzj, mattdm, sakaia, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-26 18:34:54 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description yoshiro fujita 2006-10-26 21:52:09 EDT
Description of problem:
The Xen kept outputting a trace log when specifying "maxmem = " in domVTI-
( This problem did not happen when specifying same or less value of "memory 
= " for "memmax =".)

In domU's case, the following message was displayed.
# xm create -c domU-config
Using config file "./domU-config
Xend has probably crashed!  Invalid or missing HTTP status

I met same issue in the Xen-ia64-unstable.

My domVTI's config is the below.
kernel = "/boot/Flash.fd"
builder = "hvm"
memory = 256
maxmem = 1024
vcpus = 2
vif = [ 'type=ioemu, bridge=xenbr2' ]
name = "vm1"
disk = [ 'file:/xen/xen-test/image/rhel4_vti1.img,ioemu:hda,w' 
device_model = "/usr/lib/xen/bin/qemu-dm"
memmap = "/usr/lib/xen/boot/mem-map.sxp"
sdl = 0
vnc = 0
vncviewer = 0
nographic = 1
serial = "pty"

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

How reproducible:

Steps to Reproduce:
1. create VTI-domain with maxmem = value (not same as memory =).
Actual results:
Xen is in panic.

Expected results:
domVTI normaly start without Xen panic.

Additional info:
Comment 1 Akio Takebe 2006-11-06 05:23:48 EST
I fix this issue.
Comment 3 Matthew Miller 2007-04-06 12:03:08 EDT
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.

[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
Comment 4 Red Hat Bugzilla 2007-07-24 20:01:23 EDT
change QA contact
Comment 5 Chris Lalancette 2008-02-26 18:34:54 EST
This report targets FC6, which is now end-of-life.

Please re-test against Fedora 7 or later, and if the issue persists, open a new bug.