From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Tripathy Subject: Re: RAM security Date: Mon, 06 Dec 2010 17:17:28 +0000 Message-ID: <4CFD1AA8.2020600@abpni.co.uk> References: <4CFD0FF5.1010808@abpni.co.uk> <4CFD25F702000078000262DB@vpn.id2.novell.com> <4CFD196E.2080403@abpni.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4CFD196E.2080403@abpni.co.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 06/12/10 17:12, Jonathan Tripathy wrote: > 3) If the physical server was shutdown (e.g. plug pulled), I'm guessing >>>>>> this will presetn a problem? >>>>> Xen scrubs all memory during boot, unless told not to via a boot >>>>> parameter. >>>>> >>>> Now this bit of code makes me happy! >>>> >>>> Just wondering, if Xen scrubs all memory during boot, why is >>>> booting the >>>> Hypervisor so fast? My machine has 8GB of RAM and starts nice and >>>> snappy.. >>> It probably takes just a couple of seconds to scrub 8GB. >> Plus it doesn't scrub the memory assigned to Dom0. >> > Doesn't this mean that if Dom0 releases some memory back to Xen, then > Xen gives it to another domain, data leakage could occur? > > Would one way to prevent this be to disable ballooning? Silly me, Dom0 should scrub the RAM before releasing it back to Xen, as mentioned in previous post!