From: Anthony Liguori <anthony@codemonkey.ws>
To: dlaor@redhat.com
Cc: Paolo Bonzini <pbonzini@redhat.com>, Avi Kivity <avi@redhat.com>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
kvm-devel <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Better qemu/kvm defaults (was Re: [RFC PATCH 0/4] Gang scheduling in CFS)
Date: Tue, 03 Jan 2012 16:45:19 -0600 [thread overview]
Message-ID: <4F0384FF.8070207@codemonkey.ws> (raw)
In-Reply-To: <4F0381CF.30204@redhat.com>
On 01/03/2012 04:31 PM, Dor Laor wrote:
>> We can just set this for pc-1.1. I don't see any real harm in doing that.
>
> Great, it 'only' took about 3 years from the time it got developed originally by
> Uri...
Someone just needs to send a patch.
>> When using 'guests-pick', we initially present the most compatible
>> network model (rtl8139, for instance). We would provide a paravirtual
>> channel (guest-agent?) that could be used to enumerate which models were
>> available and let guest decide which model to use for the next reboot.
>> You could also enable immediate switch over using hot plug.
>
> If guest uses an agent, it probably has virtio-serial driver and it indicates it
> has other virtio ones, otherwise, the agent won't fly
Right, but I still you want the ability for the guest to indicate that it would
like to use virtio drivers or not.
If you think about it, it makes no sense to choose which type of device gets
used in the hypervisor. In an ideal world, the guest would just figure out what
it wants to see and get that.
The same is probably true about most device model properties. rtc clock slew
policy is another good example. Instead of trying to figure out what the guest
type is, we should just let the guest request device model settings like that.
>>> We need to keep on recommending the best profile for virtualization,
>>> for Fedora
>>> I think it either enterprise-storage and maybe throughput-performance.
>>
>> I think that's more of a distro. It might be worth referring to in our
>> documentation but I'm not sure it's something we can do much about.
>
> Someone said on the kvm community call today: "no one reads documentation", so
> it better be a script. As noted about we do have it in my favorite distribution,
> I hoped all distributions gets it.
Indeed, "referring to it in our documentation" was a polite way of saying, it's
a distro problem :-)
The distro should let you choose a profile during installation or something like
that.
Regards,
Anthony Liguori
>
>
>> Regards,
>>
>> Anthony Liguori
>>
>>>
>>> If we have a such a script, it can call the matching tuned profile
>>> instead of
>>> tweaking every /sys option.
>>>
>>>>
>>>> Regards,
>>>>
>>>> Anthony Liguori
>>>>
>>>>> HTH,
>>>>> Dor
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
next prev parent reply other threads:[~2012-01-03 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111219083141.32311.9429.stgit@abhimanyu.in.ibm.com>
[not found] ` <20111219112326.GA15090@elte.hu>
[not found] ` <87sjke1a53.fsf@abhimanyu.in.ibm.com>
[not found] ` <4EF1B85F.7060105@redhat.com>
[not found] ` <877h1o9dp7.fsf@linux.vnet.ibm.com>
[not found] ` <20111223103620.GD4749@elte.hu>
[not found] ` <4EF701C7.9080907@redhat.com>
[not found] ` <87vcp4t45p.fsf@linux.vnet.ibm.com>
[not found] ` <4EF838BD.60406@redhat.com>
2011-12-29 16:07 ` [Qemu-devel] Better qemu/kvm defaults (was Re: [RFC PATCH 0/4] Gang scheduling in CFS) Dor Laor
2011-12-29 16:13 ` Avi Kivity
2011-12-29 16:16 ` Anthony Liguori
2012-01-01 10:16 ` Dor Laor
2012-01-01 14:01 ` Ronen Hod
2012-01-02 9:37 ` Dor Laor
2012-01-03 15:48 ` Anthony Liguori
2012-01-03 22:31 ` Dor Laor
2012-01-03 22:45 ` Anthony Liguori [this message]
2012-01-03 22:59 ` Dor Laor
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=4F0384FF.8070207@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=dlaor@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).