linux-kernel - Re: [PATCH v2] Enhance kvmconfig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 24 Apr 2016 18:30:46 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Andrey Utkin <andrey_utkin@...tmail.com>,
	Paolo Bonzini <pbonzini@...hat.com>
Cc:	linux-kernel@...r.kernel.org, x86@...nel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH v2] Enhance kvmconfig

On Sat, Apr 23, 2016 at 08:26:48PM +0300, Andrey Utkin wrote:
> Dropped BALLOON entries as suggested by Borislav Petkov. Tested.
> 
> 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@...tmail.com>
> ---
>  arch/x86/configs/kvm_guest.config | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/arch/x86/configs/kvm_guest.config b/arch/x86/configs/kvm_guest.config
> index f9affcc..9c78145 100644
> --- a/arch/x86/configs/kvm_guest.config
> +++ b/arch/x86/configs/kvm_guest.config
> @@ -26,3 +26,8 @@ CONFIG_VIRTIO_NET=y
>  CONFIG_9P_FS=y
>  CONFIG_NET_9P=y
>  CONFIG_NET_9P_VIRTIO=y
> +CONFIG_SCSI_LOWLEVEL=y
> +CONFIG_SCSI_VIRTIO=y
> +CONFIG_VIRTIO_INPUT=y
> +CONFIG_VIRTIO_MMIO=y
> +CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
> --

Frankly, I'm still not sure we want to do this. Apparently, virtio is
the way to go on kvm but it is not absolutely necessary to get a booting
guest.

Paolo, what do you think?

-- 
Regards/Gruss,
    Boris.

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