From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>,
nikola.ciprich@linuxbox.cz, Christoph Hellwig <hch@infradead.org>
Subject: Re: kvm tuning guide
Date: Wed, 30 Sep 2009 08:20:35 +0200 [thread overview]
Message-ID: <4AC2F8B3.8000408@redhat.com> (raw)
In-Reply-To: <20090930050939.GB8714@develbox.linuxbox.cz>
On 09/30/2009 07:09 AM, Nikola Ciprich wrote:
> "The default, IDE, is highly supported by guests but may be slow, especially with disk arrays. If your guest supports it, use the virtio interface:"
> Avi,
> what is the status of data integrity issues Chris Hellwig summarized some time ago?
>
I don't know. Christoph?
> Is it safe to recommend virtio to newbies already?
I think so.
> Shouldn't SCSI
> be safer (where applicable)?
>
SCSI suffers from being untested, and I think doesn't truly offer the
parallelism it appears to.
> nik
>
>
> On Tue, Sep 29, 2009 at 07:30:55PM +0200, Avi Kivity wrote:
>
>> I wrote a short tuning guide for kvm,
>> http://www.linux-kvm.org/page/Tuning_KVM. It should all be well known
>> to the list, but a newbie is born every minute. Please review and
>> expand!
>>
>> --
>> error compiling committee.c: too many arguments to function
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-09-30 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 17:30 kvm tuning guide Avi Kivity
2009-09-29 17:40 ` Leandro Quibem Magnabosco
2009-09-30 5:09 ` Nikola Ciprich
2009-09-30 6:20 ` Avi Kivity [this message]
2009-09-30 16:03 ` Christoph Hellwig
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=4AC2F8B3.8000408@redhat.com \
--to=avi@redhat.com \
--cc=extmaillist@linuxbox.cz \
--cc=hch@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/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).