From: Sasha Levin <levinsasha928@gmail.com>
To: Rabin Vincent <rabin@rab.in>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Michal Marek <mmarek@suse.cz>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] config: Add 'make kvmconfig'
Date: Thu, 27 Oct 2011 22:46:49 +0200 [thread overview]
Message-ID: <1319748409.3235.0.camel@lappy> (raw)
In-Reply-To: <CAH+eYFBw99Yb-x+QEyZiXZ4yL3r=jr1Z+Gk95DG3hsYLkC_R_A@mail.gmail.com>
On Thu, 2011-10-27 at 23:35 +0530, Rabin Vincent wrote:
> On Thu, Oct 27, 2011 at 17:37, Sasha Levin <levinsasha928@gmail.com> wrote:
> > +config KVMTOOL_TEST_ENABLE
> > + bool "Enable options to create a bootable tools/kvm/ kernel"
> > + select NET
> > + select NETDEVICES
> > + select PCI
> > + select BLK_DEV
> > + select NETWORK_FILESYSTEMS
> > + select INET
> > + select EXPERIMENTAL
> > + select SERIAL_8250
> > + select SERIAL_8250_CONSOLE
> > + select IP_PNP
> > + select IP_PNP_DHCP
> > + select BINFMT_ELF
> > + select PCI_MSI
> > + select KGDB
> > + select KGDB_SERIAL_CONSOLE
> > + select VIRTIO
> > + select VIRTIO_RING
> > + select VIRTIO_PCI
> > + select VIRTIO_BLK
> > + select VIRTIO_CONSOLE
> > + select VIRTIO_NET
> > + select 9P_FS
> > + select NET_9P
> > + select NET_9P_VIRTIO
>
> This lot doesn't seem to be enough for me on next-20111025. I seem to
> have to also enable CONFIG_FB_VESA for the kernel to boot.
>
> Without CONFIG_FB_VESA, I just get:
>
> $ tools/kvm/kvm run --debug arch/x86/boot/bzImage --disk
> ~/kernel/linux-0.2.img
> # kvm run -k arch/x86/boot/bzImage -m 448 -c 4 --name guest-11466
> PPrroobbiinngg EEDDDD ((eedddd==ooffff ttoo ddiissaabbllee))...... ookk
> <no more output>
This is a kvm tools issue and should be fixed within kvm tools.
--
Sasha.
next prev parent reply other threads:[~2011-10-27 19:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 12:07 [PATCH] config: Add 'make kvmconfig' Sasha Levin
2011-10-27 12:12 ` Pekka Enberg
2011-10-27 12:37 ` Ingo Molnar
2011-10-27 12:51 ` Michal Marek
2011-10-27 13:34 ` Ingo Molnar
2011-10-27 14:11 ` Pekka Enberg
2011-10-27 14:32 ` Michal Marek
2011-10-27 15:05 ` Arnaud Lacombe
2011-10-27 15:19 ` Arnaud Lacombe
2011-10-27 15:30 ` Pekka Enberg
2011-10-27 18:05 ` Rabin Vincent
2011-10-27 20:46 ` Sasha Levin [this message]
2011-10-27 19:34 ` Sam Ravnborg
2011-10-28 7:03 ` Ingo Molnar
2011-10-28 7:23 ` Sasha Levin
2011-10-28 7:39 ` Ingo Molnar
2011-10-28 7:47 ` Sasha Levin
2011-10-28 7:52 ` Ingo Molnar
2011-10-28 7:52 ` Geert Uytterhoeven
2011-10-28 7:54 ` Ingo Molnar
2011-10-28 12:08 ` Matthias Schniedermeyer
2011-10-28 12:29 ` Ingo Molnar
2011-10-28 13:05 ` Matthias Schniedermeyer
2011-11-02 8:41 ` Ingo Molnar
2011-11-02 9:07 ` Michal Marek
2011-11-02 9:17 ` Ingo Molnar
2011-11-02 9:24 ` Michal Marek
2011-11-02 9:39 ` Ingo Molnar
2011-11-02 10:06 ` Pekka Enberg
2011-10-28 9:16 ` Sasha Levin
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=1319748409.3235.0.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mmarek@suse.cz \
--cc=penberg@cs.helsinki.fi \
--cc=rabin@rab.in \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).