This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] over-allocation of memory

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] over-allocation of memory
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Fri, 22 Oct 2010 01:17:46 +0400
Delivery-date: Thu, 21 Oct 2010 14:18:46 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:in-reply-to :references:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=j0F7UyHceVJoOx0pTIqZnB8I1OCpDGbAEIRt2++n7xw=; b=Zr6eL9TmYzS0rAzFfgKi3AXbVfr2Aj3y/P9nFRNHpVFA9J0rR1SICiLXYY3Qtt6H3N 0kkDgbsKSrvWxZyQV7als/3nIScqwUpHMzkWamG1QLmPPGOZwL23ec/lmknLxRaTp/Rv pDAMlIt2aQOLwOoTqvAqeaCzMUDK7ChLyAEiE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=ZUnwPXG3qyyCZncuAZUFJz+oCXbUO9aqYncaiTHjuUNXILWiYY9sQknfkjWRCIGk4i ta50e59webLVMC03rOqvZDmaHGS9LZb7nR6ZhMID2LWQrByZKX72XxHl2qDPBVTPDz0i nl630dpgy9n7rfgj5vu/jBNqlfG0avBKGPvIY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1287694844.2510.278.camel@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1287694844.2510.278.camel@xxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
This can not be happen. There is no oversell in Xen. Ever. All
technology used by all experiments still coming to single conclusion: no

The Xen is driven by idea of page allocation. So, if we allocate page to
some VM we can not allocate it to other machine. 

All Xen memory controls works around idea of xenballoon - special
service (part of guest kernel) wich take memory from guest and returns
to hypervisor. And vice versa. 

Xen works with idea 'max memory' (theoretical limit to take memory from
hypervisor and return it to certain DomU). If maxmem is more than
available free memory for Xen, that means 'no more memory for DomU', and
this means 'ok, this is end line', MemoryErorr, OOM, etc as if domU was
normal comuter with non-rubber silicon DRAM modules with limited

All Xen can do: xen summ of maxmem > real_mem_for_host. But it could not
give more real pages (physical memory) to guests than have.

So, asked condition can not occur.

В Чтв, 21/10/2010 в 15:00 -0600, Greg Woods пишет:
> This is probably a really stupid question, but what happens if you have
> more memory allocated to domU's than your physical RAM? Will that cause
> dom0 to crash? DomU's to crash? Or just slow performance due to swap use
> on dom0?
> I ask this because we've got high availability clusters running domU's,
> and I want to know how much memory is safe to allocate to domU's given
> that a failure of one server could suddenly cause twice as many domU's
> to be started on the other server. I'd like to know if I really have to
> keep half the RAM reserved for a fairly rare occurrence.
> --Greg
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>