From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: ANNOUNCE: Xen Transcendent Memory support now in stock Ubuntu and Fedora guest kernels Date: Wed, 28 Nov 2012 15:14:41 -0500 Message-ID: <20121128201439.GA3479@phenom.dumpdata.com> References: <990a88d4-f0f8-427a-bb66-3beda4641186@default> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <990a88d4-f0f8-427a-bb66-3beda4641186@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Dan Magenheimer Cc: Kurt Hackel , Konrad Wilk , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, Nov 27, 2012 at 01:24:33PM -0800, Dan Magenheimer wrote: > FYI, it has come to my attention that both the kernel in the > recently-released Ubuntu 12.10 (aka Quantal Quetzal) and the > kernel in Fedora 17 (after yum-update to a 3.5-or-later kernel) > are fully configured to support Transcendent Memory ("tmem"). Woohoo! > Oracle's "UEK2" kernel has also had tmem support since its release > in early 2012. > > To enable tmem support in Xen, it is necessary to specify > a Xen boot parameter ("tmem"). Specifying "dom0_mem=" There are some extra ones too - tmem_compress tmem_dedup right? > and disabling dom0 autoballooning in the toolstack is also > highly recommended. Then tmem must be explicitly enabled in > any tmem-capable guest kernel by specifying a boot parameter > (also "tmem") in each guest grub.conf. Note that use of > tmem in dom0 is not recommended, so "tmem" should not be > provided as a dom0 boot parameter. > > I'll try to write up a more complete current HOW-TO soon > since much of the Xen tmem documentation floating around > the web is a bit outdated. > > Note that some security issues were reported in the > Xen hypervisor tmem implementation last summer. Please > ensure your hypervisor is updated to patch XSA-15 before > enabling tmem on a Xen machine exposed to the internet! > > Thanks, > Dan > > P.S. If you build your own Linux guest kernels, a 3.5-or-later > kernel is required built with the following config variables: > > CONFIG_FRONTSWAP=y > CONFIG_CLEANCACHE=y > CONFIG_XEN_TMEM=y > CONFIG_XEN_SELFBALLOONING=y > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >