From: xuehai zhang <hai@cs.uchicago.edu>
To: aq <aquynh@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] balloon bugfix on -TESTING
Date: Tue, 19 Jul 2005 02:17:18 -0500 [thread overview]
Message-ID: <42DCA8FE.8060909@cs.uchicago.edu> (raw)
In-Reply-To: <9cde8bff050718005248622ca@mail.gmail.com>
Hi aq,
I tested the -testing tree by applying your patch and i can successfully balloon the domain's memory
above the initial allocation now. BTW, you can give either bytes, or m (mega bytes), or k (kilo
bytes) to the "mem=" kernel command line parameter in the "extra" option of the domain's config file.
Thanks!
Xuehai
aq wrote:
> On 7/18/05, aq <aquynh@gmail.com> wrote:
>
>>This patch is for -testing, to fix some wrong calculates of max_pages
>>and max_memkb. Now balloon problem goes away (on *testing*).
>>
>>Unfortunately i cannot confirm the similar fix to -unstable yesterday
>>is able to fix balloon problem, since i got some troubles creating
>>domU with the latest -unstable.
>>
>>Demonstration:
>>
>>$ xm list
>>Name Id Mem(MB) CPU State Time(s) Console
>>Domain-0 0 92 0 r---- 44.3
>>tty 1 40 0 -b--- 0.9 9601
>>
>>$ xm balloon tty 45
>>bun@dewey2:~/projects/myxen$ xm list
>>Name Id Mem(MB) CPU State Time(s) Console
>>Domain-0 0 92 0 r---- 45.3
>>tty 1 45 0 -b--- 0.9 9601
>>
>>bun@dewey2:~/projects/myxen$ xm balloon tty 35
>>bun@dewey2:~/projects/myxen$ xm list
>>Name Id Mem(MB) CPU State Time(s) Console
>>Domain-0 0 92 0 r---- 46.1
>>tty 1 35 0 -b--- 0.9 9601
>>
>
>
> i can confirm that now (on -testing) "xm maxmem" also works :-)
>
> bun@dewey2:~/projects/myxen$ xm list
> Name Id Mem(MB) CPU State Time(s) Console
> Domain-0 0 92 0 r---- 101.4
> tty 3 40 0 -b--- 0.7 9603
>
> bun@dewey2:~/projects/myxen$ xm balloon tty 62
> bun@dewey2:~/projects/myxen$ xm list
> Name Id Mem(MB) CPU State Time(s) Console
> Domain-0 0 92 0 r---- 102.1
> tty 3 60 0 -b--- 0.7 9603
>
> bun@dewey2:~/projects/myxen$ xm maxmem tty 62
> bun@dewey2:~/projects/myxen$ xm balloon tty 62
> bun@dewey2:~/projects/myxen$ xm list
> Name Id Mem(MB) CPU State Time(s) Console
> Domain-0 0 92 0 r---- 103.2
> tty 3 62 0 -b--- 0.7 9603
>
>
>
> regards,
> aq
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
prev parent reply other threads:[~2005-07-19 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 6:24 [PATCH] balloon bugfix on -TESTING aq
2005-07-18 7:52 ` aq
2005-07-19 7:17 ` xuehai zhang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42DCA8FE.8060909@cs.uchicago.edu \
--to=hai@cs.uchicago.edu \
--cc=aquynh@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.