From: Andrey Utkin <andrey_utkin@fastmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
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 v2] Enhance kvmconfig
Date: Mon, 25 Apr 2016 03:49:04 +0300 [thread overview]
Message-ID: <20160425004904.GD22633@zver> (raw)
In-Reply-To: <20160424205129.GG3822@pd.tnic>
On Sun, Apr 24, 2016 at 10:51:29PM +0200, Borislav Petkov wrote:
> On Sun, Apr 24, 2016 at 11:35:53PM +0300, Andrey Utkin wrote:
> > Could you please test "make defconfig kvmconfig" how it boots?
> > The point of my patch is to enable user to end up with working kernel
> > for KVM guest without previously having any config,
>
> That doesn't work as you need to control the qemu options too.
Could you please point, which ones?
I haven't changed any, and yet my host is running fine.
> The purpose of kvmconfig is to give you the bare minimum and thus
> to save you a lot of time wasted searching for all those options in
> Kconfig. You'd still need to tweak your guest kernel .config after that.
IMO current kvmconfig doesn't fulfill this purpose, because trying
- "make defconfig kvmconfig"
- "make localmodconfig kvmconfig"
- "gunzip -c /proc/config.gz > .config && make olddefconfig" (rescue
system had way too old kernel I guess)
didn't save me a lot of hours wasted searching for all those options to
make it boot.
IMO "bare minimum" term makes sense if it boots. If it doesn't, then
"bare minimum" for what we are talking about?
Borislav, could you please tell, which options from this patch are you
using in your configs? Sorry to bother you.
Thank you for your interest.
next prev parent reply other threads:[~2016-04-25 0:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 17:26 [PATCH v2] Enhance kvmconfig Andrey Utkin
2016-04-24 16:30 ` Borislav Petkov
2016-04-24 19:57 ` Andrey Utkin
2016-04-24 20:18 ` Borislav Petkov
2016-04-24 20:35 ` Andrey Utkin
2016-04-24 20:51 ` Borislav Petkov
2016-04-25 0:49 ` Andrey Utkin [this message]
2016-04-25 10:52 ` Borislav Petkov
2016-05-09 12:16 ` Paolo Bonzini
2016-05-09 15:13 ` Andrey Utkin
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=20160425004904.GD22633@zver \
--to=andrey_utkin@fastmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@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