On Mon, Mar 22, 2010 at 10:55:18AM +0100, Alexander Graf wrote:
>
> On 22.03.2010, at 10:15, Dor Laor wrote:
>
> > On 03/21/2010 01:29 PM, Thomas Løcke wrote:
> >> Hey,
> >>
> >> What is considered "best practice" when running a KVM host with a
> >> mixture of Linux and Windows guests?
> >>
> >
On Mon, Mar 22, 2010 at 11:36 AM, Jan Kiszka wrote:
> Don't know what Windows does with the RTC, but the idea behind -rtc
> clock=host is to provide an accurate time source to guest without
> paravirtualized guest kernel drivers or an ntp installation in the
> guest. Last time I checked, hwclock r
Dor Laor wrote:
> On 03/21/2010 01:29 PM, Thomas Løcke wrote:
>> Hey,
>>
>> What is considered "best practice" when running a KVM host with a
>> mixture of Linux and Windows guests?
>>
>> Currently I have ntpd running on the host, and I start my guests using
>> "-rtc base=localhost,clock=host", wit
On 22.03.2010, at 10:15, Dor Laor wrote:
> On 03/21/2010 01:29 PM, Thomas Løcke wrote:
>> Hey,
>>
>> What is considered "best practice" when running a KVM host with a
>> mixture of Linux and Windows guests?
>>
>> Currently I have ntpd running on the host, and I start my guests using
>> "-rtc ba
On 03/21/2010 01:29 PM, Thomas Løcke wrote:
Hey,
What is considered "best practice" when running a KVM host with a
mixture of Linux and Windows guests?
Currently I have ntpd running on the host, and I start my guests using
"-rtc base=localhost,clock=host", with an extra "-tdf" added for
Windows
Hey,
What is considered "best practice" when running a KVM host with a
mixture of Linux and Windows guests?
Currently I have ntpd running on the host, and I start my guests using
"-rtc base=localhost,clock=host", with an extra "-tdf" added for
Windows guests, just to keep their clock from driftin
