similar to: XenParavirtOps wiki page updates

The time appears to be perfect inside dom0, however all the domU''s tend to have a slightly faster date which gets further out of sync every day. I''m currently using Xen 3.0.3 with Gentoo Linux, under 3.0.2 I had no problems with domU clocks. Are there any known issues which could cause this? I''d strongly prefer not to run ntpd in every domU, having all domU clocks in

Hi, using SLES10 I''m unable to synchronize the time of DomU with that of Dom0. There is a persistent offset of about 3 seconds! Here''s a small history (not actual output): remote refid st t when poll reach delay offset jitter rkdvmso1.dvm.kl 192.168.0.11 5 u - 64 1 0.136 -2977.1 0.099 *rkdvmso1.dvm.kl 192.168.0.11 5 u 2 64

Hello everyone! I been observing some peculiar time drift on my Xen domains (dom0 and domUs). The time (as returned by timeofday) on my domains drifts at an almost steady rate from the real time ( as read from the time stamp counter ). The drift is so constant that it makes me think there should be some simple explanation for it in the way Xen keeps time. Some info about my set up: guest OS:

HI, guys Recently,I met a problem. Xen''s version: 3.4.3 guest os:redhat 4.8 32bit And xen.independent_wallclock = 1 has been set. The time of guest os change to be fast suddenly, about 2000 second. because the change is too wild, ntp didn''t sync to the ntp server''s time. my application is dependent on the systme time. And this occurs a lot of times. I don''t

Hi, I am facing problem in sync time within DomU with Dom0. After gone through mailing lists, I have set /proc/sys/xen/independent_wallclock to 0. But still DomU are not syncing their time :-S Machine using kernel-xen-2.6.19-1.2911.fc6 xen-3.0.3-3.fc6 xen-libs-3.0.3-3.fc6 Please advice to solve this weird problem, Thanks _______________________________________________ Xen-users mailing list

Hi all, I''m experiencing problems with time: after I sync time both into dom0 and dom1 with public ntp servers, times are not the same. Do you have the same problem? Thanks Marco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

On a selection of boxes, ntpd running in Xen Dom0 reproducibly exhibits extermely high noise/jitter. Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise. Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0? Is the problem a config issue, or a bug? Already reported this downstream; everybody''s "stumped".

On a selection of boxes, ntpd running in Xen Dom0 reproducibly exhibits extermely high noise/jitter. Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise. Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0? Is the problem a config issue, or a bug? Already reported this downstream; everybody''s "stumped".

Hi all, finally I have managed to upgrade to Xen 4.0 (actually it reports Xen 4.1-unstable) and Debian''s Linux kernel 2.6.32-4-xen-amd64. Now I am wondering what happend to independent_wallclock. There is no more /sys/xen and sysctl complains error: "xen.independent_wallclock" is an unknown key Does anybody know more about this? Thanks + best regards, Stephan

Hi all, finally I have managed to upgrade to Xen 4.0 (actually it reports Xen 4.1-unstable) and Debian''s Linux kernel 2.6.32-4-xen-amd64. Now I am wondering what happend to independent_wallclock. There is no more /sys/xen and sysctl complains error: "xen.independent_wallclock" is an unknown key Does anybody know more about this? Thanks + best regards, Stephan

Hello, I know, often asked, often discussed .. No recommendation from Citrix. What is the better solution? 1) use ntp in the XEN host and synchronize the guests with the clock running on the control domain (independent_wallclock=0, what the default is) 2) or use ntp in host and guest (and independent_wallclock=1) I ask, because the XEN host (bare metal) has a more stable clock and if the ntp

Hey, I have rather new installation of xen, dom0 is running ntpd and is perfectly in time. All domU''s are ~23s in future. Running ntpd on the domU''s seem to have no effect, /proc/sys/xen/independent_wallclock appears to have no effect. I''m running xen-unstable and 2.6.16-rc4 in AMD64 box. Any tip would be appricated. Thanks, -- ++ytti

Hi all, I am running Scientific Linux 5.1 (rhel 5.1 compatible) 64bit on a 2x4core system with 16 gb ram with 3 Scientific Linux 4.6 (rhel 4.6 compatible) guests an one Scientific Linux 5.1 guest. I do not run ntp on the guests but only on dom0. One specific Scientific Linux 4 domU always looses time synchronization with dom0. All the others SL4 and the SL5 domUs remain synchronized. There

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-2 Severity: normal Hi, Take the following config file (standard lenny kernel and initrd, with some customization for iSCSI root): name = "lenny3" kernel = "vmlinuz-2.6.26-2-686-bigmem" ramdisk = "initrd.img-2.6.26-2-686-bigmem" memory = 100 vcpus = 1 vif = [ 'mac=00:16:3e:00:00:17, bridge=br695,

Hi all, where can I set the date in domU. ''ntpdate -u ...'' works but dosn''t set the date. date MMDDhhmm has also no effect. What can I do? -- cu Roland Kruggel  mailto: rk-liste@gmx.de System: Intel 3.2Ghz, Debian etch, 2.6.15, KDE 3.4 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Signed-off-by: Ferenc Wagner <Ferenc Wagner wferi at niif.hu> --- doc/syslinux.txt | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/doc/syslinux.txt b/doc/syslinux.txt index 76cae24..0ec2695 100644 --- a/doc/syslinux.txt +++ b/doc/syslinux.txt @@ -163,11 +163,10 @@ IPAPPEND flag_val [PXELINUX only] ... based on the input from the DHCP/BOOTP or PXE boot

"H. Peter Anvin" <hpa at zytor.com> writes: > On 12/12/2013 12:31 AM, Ferenc Wagner wrote: > >> Shall I rebase it to the current firmware head? >> >> Also, 5.2.3 was released a couple of days ago. It's a bugfix release. >> I made it into a sepearete commit (pushed). >> >> Better default Lua paths (source and binary) would be

On Oct 17, 2014, at 1:30 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > >> On 10/17/2014 12:19 AM, Ferenc Wagner wrote: >> "H. Peter Anvin" <hpa at zytor.com> writes: >> >>> I would like to do a short cycle for 6.04, because 64-bit support for >>> ext4 has come up as a very high priority. Therefore I do not want to

Geert Stappers <stappers at stappers.nl> writes: > Op 2013-10-15 om 20:03 schreef Ferenc W?gner: > >> lua: import Lua 5.2.2 > > Posted as [patch01/21] > Which was too big for the mailinglist. > So some other way is needed to share that information ... Hmm, yes. The series is available at https://github.com/wferi/syslinux as well (lua52 branch, based on upstream

On 01/02/2014 04:09 AM, Ferenc Wagner wrote: > > Issuing another make after this gave the previous error again: > > isolinux.asm:1102: error: TIMES value -4 is negative > I just fixed this one... it seems to be a consequence of merging in the MOVZX isolinux fix into the firmware branch. -hpa