public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Andrey Utkin <andrey_utkin@fastmail.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] Enhance kvmconfig
Date: Sat, 23 Apr 2016 18:05:53 +0200	[thread overview]
Message-ID: <20160423160553.GA8568@pd.tnic> (raw)
In-Reply-To: <1461426709-24094-1-git-send-email-andrey_utkin@fastmail.com>

On Sat, Apr 23, 2016 at 06:51:49PM +0300, Andrey Utkin wrote:
> This was tested only on Hetzner CX10 VPS.
> I don't know how recent KVM server stuff they use.
> Tests & reports from anybody else are appreciated.
> I guess some of added options may be not strictly necessary or make not
> that lot of sense as enabled by default, feel free to ask me to drop some
> and test how it works.
> Thanks.
> ---8<---
> "make defconfig kvmconfig" is supposed to end up with usable kernel for
> KVM guest. In practice, it won't work for e.g. Hetzner VPS (KVM-based)
> unless you add these options.
> 
> Signed-off-by: Andrey Utkin <andrey_utkin@fastmail.com>
> ---
>  arch/x86/configs/kvm_guest.config | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/arch/x86/configs/kvm_guest.config b/arch/x86/configs/kvm_guest.config
> index f9affcc..ec35f28 100644
> --- a/arch/x86/configs/kvm_guest.config
> +++ b/arch/x86/configs/kvm_guest.config
> @@ -26,3 +26,11 @@ CONFIG_VIRTIO_NET=y
>  CONFIG_9P_FS=y
>  CONFIG_NET_9P=y
>  CONFIG_NET_9P_VIRTIO=y
> +CONFIG_MEMORY_BALLOON=y
> +CONFIG_BALLOON_COMPACTION=y

So why would a kvm guest need the ballooning thing? My guests work just
fine without it.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

      reply	other threads:[~2016-04-23 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-23 15:51 [PATCH] Enhance kvmconfig Andrey Utkin
2016-04-23 16:05 ` Borislav Petkov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160423160553.GA8568@pd.tnic \
    --to=bp@alien8.de \
    --cc=andrey_utkin@fastmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox