similar to: Where is xtime updated in a domU with an independent wallclock?

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

I don''t want my dom0 to update the clock in my HVM domU. I''ve already disabled network-based time synchronization inside the HVM. I''ve tried setting /proc/sys/xen/independent_wallclock=1 and then restarting xend, but the guest still gets the correct time. Any ideas on how to accomplish this? Steve Brueckner, ATC-NY _______________________________________________

(Moving from offlist discussion.) I''m interested in opinions... Assume there are four single vcpu domains A, B, C, D, running on a 2-CPU physical machine. We wish to test for time skew on domain A. Assuming B, C, and D are all running some workload that attempts to fully saturate the (single) cpu. 1) Should the affect on domain A be essentially the same regardless of what load

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

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.

Hi, I got a problem during geo-replication: The master Gluster server log has the following error every second: [2011-07-26 04:20:50.618532] W [libxlator.c:128:cluster_markerxtime_cbk] 0-flvol-dht: Unable to get <uuid>.xtime attr While the slave log has the error every a few seconds: [2011-07-26 04:25:08.77133] E [stat-prefetch.c:695:sp_remove_caches_from_all_fds_opened]

Hi, This is Chandra. I have Polycom IP 501 phone. Its showing wrong time on the display screen. How can I set the "New York" time? What value I have to give to GMT offset value? Look forward to your response. Thank you. Regards, Chandra. --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.

Call update_domain_wallclock_time on hvm_latch_shinfo_size even if the bitness of the guest has already been set, this fixes the problem with the wallclock not being set for PVHVM guests on resume from migration. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Jan Beulich <JBeulich@suse.com> Cc: Keir Fraser <keir@xen.org> Cc: George Dunlap

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

The initial values of the wallclock time in the shared info page are set for PVHVM guests when the hypercall page is initialized, since the hypercall page is not reinitialized on resume, the hypervisor wallclock time is not properly set on resume. Fix it by forcing an update of the wallclock values when the shared info page is mapped. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>

Hi Jean, I'm trying to compile the encode.c and or the test programs that are on the site and in libspeex respectively. however, i keep getting some undefined references to the basic speex functions(see compiler log). a query on google showed that this question was posed but no answer given. I traced them down to speex.c. however when i build my project i still get these undefined referneces.

The paravirtualized guests are offered wallclock time referenced to UTC only, while fully virtualized guests are given the option via the config file (localtime parameter) of starting with UTC time or local time. What would it take to optionally provide localtime to the paravirtualized guests as well? For a guest that launches assuming localtime as its time basis, then later deriving UTC from it

> -----Original Message----- > From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users- > bounces@lists.digium.com] On Behalf Of Noah Miller > Sent: Wednesday, April 25, 2007 9:52 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [asterisk-users] My Polycom IP 501 is formatted its file > systemitself > > Hi Chandra - > >

F.Y.I >>> "Tian, Kevin" <kevin.tian@intel.com> 08.11.27. 11:50 >>>Sorry for a typo. I did mean domU instead of dom0. :-) The point here is that time_resume will sync to new system time and wall clock at restore, and thus pv guest should be able to continue... Xen system time is not wallclock time which just counts up from power up. As Keir points out, only its

I am trying to cross compile openssh for arm5b-jungo-gnu-gcc,, and also using openssl and zlib from same compiler arm5b-jungo-gnu-gcc but i am getting following error,,, /usr/local/openrg/armv5b-jungo-linux-gnu/bin/armv5b-jungo-linux-gnu-ld: warning: cannot find entry symbol _start; defaulting to 0000b9c8 /usr/local/openrg/armv5b-jungo-linux-gnu/bin/../armv5b-jungo-linux-gnu/lib/libcrypto.so:

Hey all! I'm trying to do a bit of logic here so that a user only has to dial one code to pause/unpause in a queue (e.g. *0 will (un)pause depending on the users's state). My logic looks fine to me but every time ${PQMSTATUS} shows up empty. Here's the extensions.conf part.... exten => *0,1,NoOp(${PQMSTATUS}) exten => *0,n,Macro(user-callerid,SKIPTTL,) exten =>

It''s come to our attention, that the time gets screwed up when set between EPOCH and EPOCH + uptime. This may not seem important (because we don''t live in the 70s anymore) but it makes LTP fail. LTP has a date test that checks what happens when set to EPOCH + 100 secs + 100 nsecs, and makes sure that it gets a proper result. The following patches helps xen handle the case

I am very new to linux and openSSH ,, i am trying to compile openssh for jungo openrg IXP45. but while configuring i am getting following error,, hecking for libgen.h... yes checking for getspnam... yes checking for library containing basename... none required checking for deflate in -lz... no configure: error: *** zlib missing - please install first or check config.log *** if anybody will me

Hi! Can anybody explain how Xen deals with time? On traditional, non-virtualized systems I run an ntpd on every system to keep the time accurate. But what to do on xenified systems? Do all the domU''s get the time from dom0 meaning it is sufficient to run an ntpd there or do I have it to setup in every domU? Thanks for your help! Kind regards, Stephan

Hi folks, I tried to find out what xen version upstream intends to use in 5.3, but did not find anything. So now I hope that there is some secret knowledge among the CentOS people you could share? :-) Any hint or link would be helpful. Thanks in advance, Dirk