Description of problem:
The Xen kept outputting a trace log when specifying "maxmem = " in domVTI-
config.
( 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):
xen-3.0.2-44
kernel-xen-2.6.18-1.2784.fc6

How reproducible:
Always

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

Expected results:
domVTI normaly start without Xen panic.

Additional info: