From: Borislav Petkov <bp@alien8.de>
To: Andrey Utkin <andrey_utkin@fastmail.com>
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 12:52:44 +0200 [thread overview]
Message-ID: <20160425105243.GA28454@pd.tnic> (raw)
In-Reply-To: <20160425004904.GD22633@zver>
On Mon, Apr 25, 2016 at 03:49:04AM +0300, Andrey Utkin wrote:
> IMO "bare minimum" term makes sense if it boots.
Boots where? On every system? You know that won't fly.
This bare minimum is trying to be of help only. No one says you should
be able to boot *every* guest kernel config with this.
For example, if your guest root fs image is ext4, then you must enable
ext4 support in the guest kernel. But that doesn't mean we need to carry
everything in kvmconfig. If we did, then we don't need it at all -
people can simply do "make allmodconfig" and have it all.
The idea of kvmconfig is to OR in the bare minimum of options into your
current .config and thus make the kernel more useful when booted as a
kvm guest - you'd still need to go and adjust it to your particular qemu
invocation.
In any case, here's how I'm booting my guests. You can see, for example,
that I'm using rtl8139 nic in the guest and for that I have it enabled
in my guest kernel .config.
$ qemu-system-x86_64
-enable-kvm
-gdb tcp::1234
-cpu Opteron_G5
-m 2048
-hda /home/boris/kvm/debian/sid-x86_64.img
-boot menu=off,order=c
-localtime
-net nic,model=rtl8139,macaddr=12:34:56:78:12:34
-net user,hostfwd=tcp::1235-:22
-usbdevice tablet
-kernel /home/boris/kernel/linux-2.6/arch/x86/boot/bzImage
-append "root=/dev/sda1 resume=/dev/sdb1 debug ignore_loglevel log_buf_len=16M earlyprintk=ttyS0,115200 console=ttyS0,115200 console=tty0 "
-monitor pty
-soundhw hda
-serial file:/home/boris/kvm/test-x86_64-1235.log
-snapshot
-smp 8
-virtfs local,path=/tmp,mount_tag=tmp,security_model=none
HTH.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-04-25 10:52 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
2016-04-25 10:52 ` Borislav Petkov [this message]
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=20160425105243.GA28454@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=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