/bugzilla3/ Bug 800 – The Xen is in panic when specifying "maxmem =" in domVTI-config.
First Last Prev Next    No search results available
Bug 800 - The Xen is in panic when specifying "maxmem =" in domVTI-config.
: The Xen is in panic when specifying "maxmem =" in domVTI-config.
Status: RESOLVED FIXED
Product: Xen
HVM
: unstable
: IA64 All
: P2 critical
Assigned To: Xen Bug List
:
:
:
  Show dependency tree / graph
 
Reported: 2006-10-26 18:44 CDT by yoshiro fujita
Modified: 2006-10-31 22:45 CST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description yoshiro fujita 2006-10-26 18:44:14 CDT 
The Xen kept outputting a trace log when specifying "maxmem = " in
domVTI-config.
( This problem did not happen when specifying same 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 tested cset 11930 and 11961.

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"
---------------------------------------------------------------------------
Comment 1 Yongkang You 2006-10-30 22:06:37 CST 
Interesting bug.
As VTI domain doesn't support ballon memory, so max_mem should not be set to
VTI.
But it will crash Xen, anyway it is bug.
Comment 2 Akio Takebe 2006-10-31 22:45:16 CST 
fix changeset 12011
First Last Prev Next    No search results available