[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#423084: marked as done (maxmem parameter apparently ignored)

Your message dated Sun, 26 Jul 2009 11:56:18 +0200
with message-id <20090726095618.GA22727@galadriel.inutil.org>
and subject line Re: maxmem parameter apparently ignored
has caused the Debian Bug report #423084,
regarding maxmem parameter apparently ignored
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
423084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423084
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xen-linux-system-2.6.20-1-xen-amd64
Version: 2.6.20-3

The maxmem parameter in Xen config files does not work, that is,
regardless of the use of that setting, domU can never be ballooned to a
value greater than the value set in the memory field.

--
Tom Allen                       Email: tallen@10east.com
Senior Open Systems Engineer    Phone: 904-220-3627
10East Corp                     FAX: 904-384-1038

--- End Message ---
--- Begin Message --- 
On Sat, Nov 29, 2008 at 02:32:19AM +0100, Moritz Muehlenhoff wrote:
> On Wed, May 09, 2007 at 12:45:43PM -0400, Tom Allen wrote:
> > Package: xen-linux-system-2.6.20-1-xen-amd64
> > Version: 2.6.20-3
> >
> > The maxmem parameter in Xen config files does not work, that is,
> > regardless of the use of that setting, domU can never be ballooned to a
> > value greater than the value set in the memory field.
> 
> Does this error still occur with more recent kernel/Xen versions, such
> as the ones from Lenny?

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz

--- End Message ---
Reply to: