Sebastian Plagemann
2009-Apr-07 11:20 UTC
[Xen-users] Debian + XEN 3.2. + Windows VM || ping problems
Hi,
it''s not really a problem...
After installing a Windows 2003 Server on a Debian based XEN 3.2. the
response time of a ping is very strange.
------------
Ping wird ausgeführt für 184.1.3.1 mit 32 Bytes Daten:
Antwort von 184.1.3.1: Bytes=32 Zeit<1ms TTL=255
Antwort von 184.1.3.1: Bytes=32 Zeit=10427ms TTL=255
Antwort von 184.1.3.1: Bytes=32 Zeit=-10420ms TTL=255
Antwort von 184.1.3.1: Bytes=32 Zeit=-10432ms TTL=255
------------
First I thought this is a problem with the GPLPV drivers, but also on a
"fresh" installation it is the same.
Has anybody noticed the same behaviour? And does anybody know why there
are negative response times?
Thanks
Sebastian
--
Bitte prüfen Sie der Umwelt zuliebe, ob der Ausdruck dieser Mail erforderlich
ist.
Oldenburgische Landesbank AG
Vorsitzender des Aufsichtsrates: Andree Moschner
Vorstand: Benedikt Buhl, Sprecher
Dr. Peter Schinzing, stellv. Sprecher
Dr. Stefan Friedmann
Sitz der Gesellschaft: Oldenburg (Oldb)
Registergericht: Oldenburg (Oldb)
HR-Nummer: HRB 3003
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Andrew Lyon
2009-Apr-07 13:10 UTC
Re: [Xen-users] Debian + XEN 3.2. + Windows VM || ping problems
2009/4/7 Sebastian Plagemann <sebastian.plagemann@olb.de>:> Hi, > it''s not really a problem... > After installing a Windows 2003 Server on a Debian based XEN 3.2. the > response time of a ping is very strange. > > ------------ > Ping wird ausgeführt für 184.1.3.1 mit 32 Bytes Daten: > > Antwort von 184.1.3.1: Bytes=32 Zeit<1ms TTL=255 > Antwort von 184.1.3.1: Bytes=32 Zeit=10427ms TTL=255 > Antwort von 184.1.3.1: Bytes=32 Zeit=-10420ms TTL=255 > Antwort von 184.1.3.1: Bytes=32 Zeit=-10432ms TTL=255 > ------------ > > First I thought this is a problem with the GPLPV drivers, but also on a > "fresh" installation it is the same. > Has anybody noticed the same behaviour? And does anybody know why there are > negative response times? > > Thanks > Sebastian > > -- > Bitte prüfen Sie der Umwelt zuliebe, ob der Ausdruck dieser Mail > erforderlich ist. > > Oldenburgische Landesbank AG > > Vorsitzender des Aufsichtsrates: Andree Moschner > Vorstand: Benedikt Buhl, Sprecher > Dr. Peter Schinzing, stellv. Sprecher > Dr. Stefan Friedmann > Sitz der Gesellschaft: Oldenburg (Oldb) > Registergericht: Oldenburg (Oldb) > HR-Nummer: HRB 3003 > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >Try adding timer_mode=1 to your hvm config file. Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sebastian Plagemann
2009-Apr-07 13:26 UTC
Re: [Xen-users] Debian + XEN 3.2. + Windows VM || ping problems
seems to be working... thank you Andrew Lyon schrieb:> 2009/4/7 Sebastian Plagemann <sebastian.plagemann@olb.de>: > >> Hi, >> it''s not really a problem... >> After installing a Windows 2003 Server on a Debian based XEN 3.2. the >> response time of a ping is very strange. >> >> ------------ >> Ping wird ausgeführt für 184.1.3.1 mit 32 Bytes Daten: >> >> Antwort von 184.1.3.1: Bytes=32 Zeit<1ms TTL=255 >> Antwort von 184.1.3.1: Bytes=32 Zeit=10427ms TTL=255 >> Antwort von 184.1.3.1: Bytes=32 Zeit=-10420ms TTL=255 >> Antwort von 184.1.3.1: Bytes=32 Zeit=-10432ms TTL=255 >> ------------ >> >> First I thought this is a problem with the GPLPV drivers, but also on a >> "fresh" installation it is the same. >> Has anybody noticed the same behaviour? And does anybody know why there are >> negative response times? >> >> Thanks >> Sebastian >> >> -- >> Bitte prüfen Sie der Umwelt zuliebe, ob der Ausdruck dieser Mail >> erforderlich ist. >> >> Oldenburgische Landesbank AG >> >> Vorsitzender des Aufsichtsrates: Andree Moschner >> Vorstand: Benedikt Buhl, Sprecher >> Dr. Peter Schinzing, stellv. Sprecher >> Dr. Stefan Friedmann >> Sitz der Gesellschaft: Oldenburg (Oldb) >> Registergericht: Oldenburg (Oldb) >> HR-Nummer: HRB 3003 >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > Try adding timer_mode=1 to your hvm config file. > > Andy > >-- Bitte prüfen Sie der Umwelt zuliebe, ob der Ausdruck dieser Mail erforderlich ist. Oldenburgische Landesbank AG Vorsitzender des Aufsichtsrates: Andree Moschner Vorstand: Benedikt Buhl, Sprecher Dr. Peter Schinzing, stellv. Sprecher Dr. Stefan Friedmann Sitz der Gesellschaft: Oldenburg (Oldb) Registergericht: Oldenburg (Oldb) HR-Nummer: HRB 3003 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew Lyon
2009-Apr-07 14:28 UTC
Re: [Xen-users] Debian + XEN 3.2. + Windows VM || ping problems
On Tue, Apr 7, 2009 at 2:37 PM, Sebastian Plagemann <sebastian.plagemann@olb.de> wrote:> Hi, > just one question: what does this timer_mode do? > > Thanks > SebastianDetails of the bug you hit can be found at http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=895 , but I''ve never found a description of what the difference is between the available timer modes, I just use mode 1 for windows hvm''s. Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew Lyon
2009-Apr-07 14:37 UTC
Re: [Xen-users] Debian + XEN 3.2. + Windows VM || ping problems
On Tue, Apr 7, 2009 at 3:28 PM, Andrew Lyon <andrew.lyon@gmail.com> wrote:> On Tue, Apr 7, 2009 at 2:37 PM, Sebastian Plagemann > <sebastian.plagemann@olb.de> wrote: >> Hi, >> just one question: what does this timer_mode do? >> >> Thanks >> Sebastian > > Details of the bug you hit can be found at > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=895 , but I''ve > never found a description of what the difference is between the > available timer modes, I just use mode 1 for windows hvm''s. > > Andy >I just found this explanation: Timer_mode 0/1 track exact number of timer interrupt which need be injected to guest. If timer interrupts cannot be injected on time, pending_count++. The difference is that for mode 0, guest TSC is also hold back if there are timer interrupts pending, while for mode 1 guest TSC always equals to (host TSC - constant offset) Time mode 2/3 don''t inject each pending time interrupt to guest, hoping guest OS itself can handle time interrupt lost and adjust time using platform timer (e.g. HPET)''s counter. Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users