From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [ANNOUNCE] kvm-46 release Date: Wed, 10 Oct 2007 15:39:38 +0200 Message-ID: <470CD61A.4090103@qumranet.com> References: <470C8D28.2060408@qumranet.com> <20071010133912.GB1894@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: "Daniel P. Berrange" Return-path: In-Reply-To: <20071010133912.GB1894-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Daniel P. Berrange wrote: > On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote: > >> We've now switched to allocating guest memory in userspace rather than >> in the kernel. This is important if you have a mainframe, but also if >> you want to share memory between guests and implement nice features like >> swapping. >> > > Is the memory allocation swappable by default, or still pinned in RAM by > default ? > > It's still not swappable. That will come in a future release. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/