From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D0343C433EF for ; Wed, 20 Apr 2022 02:42:00 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.308664.524467 (Exim 4.92) (envelope-from ) id 1nh0Ht-0005MX-L4; Wed, 20 Apr 2022 02:41:49 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 308664.524467; Wed, 20 Apr 2022 02:41:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1nh0Ht-0005MH-Fz; Wed, 20 Apr 2022 02:41:49 +0000 Received: by outflank-mailman (input) for mailman id 308664; Wed, 20 Apr 2022 02:41:48 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1nh0Bd-0000eu-1j for xen-devel@lists.xenproject.org; Wed, 20 Apr 2022 02:35:21 +0000 Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 85040090-c052-11ec-a405-831a346695d4; Wed, 20 Apr 2022 04:35:20 +0200 (CEST) Received: from m5p.com (mailhost.m5p.com [IPv6:2001:470:1f07:15ff:0:0:0:f7]) by mailhost.m5p.com (8.16.1/8.15.2) with ESMTPS id 23K2ZB2W092991 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 19 Apr 2022 22:35:16 -0400 (EDT) (envelope-from ehem@m5p.com) Received: (from ehem@localhost) by m5p.com (8.16.1/8.15.2/Submit) id 23K2ZBk1092990; Tue, 19 Apr 2022 19:35:11 -0700 (PDT) (envelope-from ehem) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: 85040090-c052-11ec-a405-831a346695d4 Message-Id: In-Reply-To: References: From: Elliott Mitchell Cc: Wei Liu Cc: Anthony PERARD Date: Sat, 9 Jan 2021 14:44:07 -0800 Subject: [PATCH 05/10] docs: xlexample.hvm: Fix maxmem value To: xen-devel@lists.xenproject.org HVM doesn't balloon and so it makes no sense to specify maxmem. Signed-off-by: Elliott Mitchell --- tools/examples/xlexample.hvm | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/examples/xlexample.hvm b/tools/examples/xlexample.hvm index 26ae1c2fb4..a6cafcbf9f 100644 --- a/tools/examples/xlexample.hvm +++ b/tools/examples/xlexample.hvm @@ -25,9 +25,9 @@ name = "example.hvm" memory = 384 # Maximum memory (MB) -# If this is greater than `memory' then the slack will start ballooned -# (this assumes guest kernel support for ballooning) -#maxmem = 512 +# Unlike PV or PVH, HVM cannot balloon memory and hence this should match +# `memory' or simply be left unset. +#maxmem = # Number of VCPUS vcpus = 3 -- 2.30.2