From: Thomas Mueller <thomas@chaschperli.ch>
To: kvm-devel@lists.sourceforge.net
Subject: Re: virtio & minimal .config
Date: Mon, 18 Feb 2008 17:51:42 +0100 [thread overview]
Message-ID: <47B9B79E.1060807@chaschperli.ch> (raw)
In-Reply-To: <47B99261.7090701@codemonkey.ws>
Hi Anthony
>> has anybody out there a minimalistic .config to build a minimal guest
>> kernel image with virtio enabled?
>>
>
> I usually do a make defconfig, enable the CONFIG_VIRTIO_* options in
> .config, then do a make oldconfig and answer 'y' to all of the questions.
ok, i'll give it a try. But "make defconfig" will make a new .config. So
i think there won't ever be any 'y' to give to "make oldconfig"?
anyhow. after "make defconfig" there was no "CONFIG_VIRTIO_BLK" in it.
But in "make menuconfig" i found and enabled it (also
CONFIG_VIRTIO_NIC). (maybe some issues of -rc2)
>> all my tries with virtio ended up with a kernel panic not finding the
>> harddisk... Is virtio for the disk supported by kvm-60 and do i need to
>> enable it on the command line? Without my own virtio enabled kernel
>> things work just fine.
>>
>
> Please post your command line for launching KVM. Make sure you have a
> root parameter like "root=/dev/vda1".
the "vda1" thing i didn't know. thanks. will also give it a try - tomorrow.
Is "virtio" block device replacing SATA/SCSI - are the SCSI/SATA
drivers needed on guest?
thanks
- Thomas
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-18 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 14:06 virtio & minimal .config Thomas Mueller
2008-02-18 14:12 ` Anthony Liguori
2008-02-18 16:51 ` Thomas Mueller [this message]
2008-02-18 17:35 ` Anthony Liguori
2008-02-19 7:39 ` Thomas Mueller
2008-02-19 7:39 ` Thomas Mueller
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=47B9B79E.1060807@chaschperli.ch \
--to=thomas@chaschperli.ch \
--cc=kvm-devel@lists.sourceforge.net \
/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