RE: [Xen-devel] xm mem-set causes kernel panic

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

> We did run using unstable. We installed sles10 beta11 but we 
> pulled and built xen-unstable changeset 9903 from xensource 
> repository.  We have not tried with PAE hypervisor.  It is 
> not our focus.  How desperately would you need us to try PAE?

Interesting. If you boot with dom0_mem=512 and then start a 15GB guest,
do you see problems shrinking the guest's memory?

I'd certainly be interested in hearing whether the problem exists on
PAE.

Ian

> -----Original Message-----
> From: Ian Pratt [mailto:m+Ian.Pratt@xxxxxxxxxxxx]
> Sent: Wednesday, May 03, 2006 4:19 PM
> To: Krysan, Susan; xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: Subrahmanian, Raj; Vessey, Bruce A; Puthiyaparambil, 
> Aravindh; Carb, Brian A; ian.pratt@xxxxxxxxxxxx
> Subject: RE: [Xen-devel] xm mem-set causes kernel panic
> 
> 
> > When I boot the ES7000 with 32 GB of RAM, dom0 is allocated 
> almost all 
> > of it.  I issued an xm mem-set 0 512 command to decrease 
> dom0's memory 
> > to 512 MB.  Using xentop, I see the amount of memory 
> allocated to dom0 
> > slowly decrease.  The kernel panic occurs when dom0's 
> memory is around 
> > 1 GB.  The serial console output is attached.  Using SLES10 Beta 11 
> > upgraded to xen changeset 9903.
> 
> Can you repro this on -unstable? What about with a PAE hypervisor?
> 
> Thanks,
> Ian
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel