1 |
Am 2011-07-21 02:41, schrieb Albert Hopkins: |
2 |
> |
3 |
> |
4 |
> On Wednesday, July 20 at 23:43 (+0200), Stefan G. Weichinger said: |
5 |
> |
6 |
> [...] |
7 |
>> Are there any recommended kernel-config-settings for a performant |
8 |
>> and non-drifting KVM-server? |
9 |
> |
10 |
> Well, KVM_CLOCK obviously: |
11 |
> |
12 |
> KVM_CLOCK bool "KVM paravirtualized clock" select PARAVIRT select |
13 |
> PARAVIRT_CLOCK |
14 |
> |
15 |
> Turning on this option will allow you to run a paravirtualized clock |
16 |
> when running over the KVM hypervisor. Instead of relying on a PIT (or |
17 |
> probably other) emulation by the underlying device model, the host |
18 |
> provides the guest with timing infrastructure such as time of day, |
19 |
> and system time |
20 |
|
21 |
I wasn't sure if this option was for the server/host or for using it in |
22 |
the kernel of the guest-vm (like the virtio-drivers ...). |
23 |
|
24 |
Thanks for telling me! |
25 |
|
26 |
Stefan |