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

Re: [Xen-users] flexible memory management?

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Jerry Amundson" <jamundso@xxxxxxxxx>
  • Date: Thu, 8 Feb 2007 21:18:03 -0600
  • Delivery-date: Thu, 08 Feb 2007 19:17:56 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TT0xyZ0M+T4NdS94WBwRolUlOn910sd7p2w46ROIf1AEKn0NU7TbGQFxurebVZKbBMSudqUK9KmSXYDqnFRW75j/C59pAIkQhr7XDCXBy2a7Gz8xwHDcFrW7nZJXUo6OiaaQVIMpwlALO+OwBayaj7P3igpXiHYI1WNn0ZWOqnQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 2/8/07, Gary W. Smith <gary@xxxxxxxxxxxxxxx> wrote:
> So it works! memory is transferred from dom0 to domU on demand.
> But as i reduce the domU's size with "xm mem-set", the memory does not
> flow back to dom0 automatically.
> I wonder, if that's possible too.

That is correct, Dom0 doesn't seem to grow back.

An "old-school" type, like myself, is also reassured somewhat, by
allocating only what dom0 would only ever need - net services,
compiling, running programs, etc. is isolated to domu's. Then, in the
event dom0 is ever compromised (though very highly unlikely), or even
if I accidentally start something there, dom0 can't take memory away -
a DoS prevention, of sorts...


"Pay no attention to that man behind the curtain!"

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.