OVM Guest wrong hardware clock

Hi,
I'm running an Enterprise Linux 6.3 (PVM) on an OVM host.
The problem is that the date in the EL guest doesn't correspond to the date in the OVM host. The time in /var/log/messages is skewed: it's 6hours too early.
The hwclock on the host:
[root@lnx-iaovm01 /]# hwclock
Fri 17 May 2013 10:53:51 AM CEST -0.737400 seconds
Output of the command on the guest:
[root@lnx-ianag01 vm]# hwclock --debug
hwclock from util-linux-ng 2.17.2
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
I tried the following solution: ln -s /dev/rtc0 /dev/rtc
but I don't have a /dev/rtc0 directory so this isn't very successful
I also tried setting my TZ in my /etc/profile (so the "date" command atleast is correct but since this is just an environment variable so it doesn't really help either).

Isn't it easier to just enable ntp to sync your VM with a clocksource locally in your network or on the internet?

Similar Messages

OL5.8 OVM Guest number of CPU´s

Hi,
does anyone can help we understand if it is possible and a good idea to configure more virtual CPU´s
in a OVM Guest as cores integrated in the physical hardware.
We have a 2 cpu 6 core OVM hardware and try to configure 20 virtual cpu´s in ONE guest system.
I don´t like that idea....
Thanks *T

..So xm info told me that
release : 2.6.18-128.2.1.4.44.el5xen
version : #1 SMP Thu Nov 10 22:05:12 EST 2011
machine : i686
nr_cpus : 16
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
So we have 16 cores inclusive Hyper-Threading or 16 cores *2 ?
cat /proc/pcuinfo
rocessor     : 15
vendor_id     : GenuineIntel
cpu family     : 6
model          : 44
model name     : Intel(R) Xeon(R) CPU E5640 @ 2.67GHz
stepping     : 2
cpu MHz          : 2665.912
cache size     : 12288 KB
I´m confused :-/
Oracle Support told us to set the vCPU´s to 20 because of we have 10 intances on on OVGuest....
Thanks *T

Hardware clock and system clock don't match

hello. i recently upgraded to kde 4.7, and i don't know if it's the culprit or not, but my system clock is now ahead of the hardware clock by the timezone offset.
my timezone is Asia/Manila, which is UTC+8. so if the correct time is 00:00, the system time is 08:00.
i dual boot with windows so the HARDWARECLOCK setting in /etc/rc.conf is set to localtime.
interestingly, the commands "hwclock --show" and "date" both show PHT as the timezone, but with the aforementioned time skew. to illustrate:
# hwclock --show
Fri 05 Aug 2011 10:45:02 AM PHT -0.500309 seconds
# date
Fri Aug 5 18:45:02 PHT 2011
running "hwclock --hctosys" fixes the problem while logged in, but restarting the computer reverts the problem. i could put a daemon that runs the command at startup, but i never needed to do that before and i'm not inclined to at the moment. i think this is just a misconfiguration somewhere.
thanks for any help you could give.

hello. it is
hwclock from util-linux 2.19.1
Using /dev interface to clock.
Last drift adjustment done at 1312511647 seconds after 1969
Last calibration done at 1304274137 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/08/05 12:08:46
Hw clock time : 2011/08/05 12:08:46 = 1312517326 seconds since 1969
Fri 05 Aug 2011 12:08:46 PM PHT -0.690104 seconds

Hardware Clocking Error PCI-5122

I tried to run the vi attached (which i've run many times before) and my computer bluescreen. When it rebooted, I could no longer use my PCI-5122 digitizer card. When I try to do a device test or device reset in MAX, it tells me that theres a hardware clocking error.. I was using an external trigger for the aquisition, but don't think I was using an external reference clock. Could someone help me fix this?
Thanks
NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5
Solved!
Go to Solution.
Attachments:
OPO Monitor.vi ‏53 KB

Hi,
This error may be the result of a hardware failure where the only
solution is a repair or replacement. There are however, some basic
troubleshooting steps that have been known to correct this issue
without a return.
Reboot the PC or PXI controller.
Try a different PCI or PXI slot.
Update the driver to the latest version.
If possible try the card on a different machine.
If these steps to not correct the issue then it is likely the
board requires repair which can be arranged by contacting National
Instruments Technical support (in france: 01 57 66 24 24).
Best regards,
Thomas B. | CLAD
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Inscrivez-vous gratuitement aux Journées Techniques : de l'acquisition de données au contrôle/com...

[SOLVED] System time is +4hrs from hardware clock

Hello again.
Now I can't set up my system`s time properly. (Set system time from hardware clock)
Timezone is GMT+4 (Europe/Samara) and hardware clock (RTC) is set to proper time so does UTC.
But system`s time itself is 4 hours in the future from HW clock!
# hwclock --hctosys --utc
does nothing.
# timedatectl set-local-rtc 1
or
# timedatectl set-time "$mytime"
both do nothing and output following error:
Failed to issue method call: The name org.freedesktop.PolicyKit1 was not provided by any .service files
Also, removing /etc/adjtime does nothing!
How can I fix it?
Last edited by eruditorum (2012-11-25 10:52:14)

ewaller,
hwclock from util-linux 2.22.1
Using /dev interface to clock.
Last drift adjustment done at 1353744432 seconds after 1969
Last calibration done at 1353744432 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2012/11/25 05:40:17
Hw clock time : 2012/11/25 05:40:17 = 1353822017 seconds since 1969
Sun 25 Nov 2012 09:40:17 AM SAMT -0.907738 seconds
Last edited by eruditorum (2012-11-25 04:35:10)

[SOLVED] Gnome clock is 2 hours off hardware clock

hi, i'm not sure if this is the right place to post but here we go..
I've just installed arch on my laptop and now everything seems to work pretty well, although the clock in gnome/cinnamon is 2 hours off hwclock/localtime. Does anyone have a suggestion how to fix this? I don't seem to be able to edit it manually through the gui
Last edited by frmi (2012-08-21 15:29:45)

2ManyDogs wrote:
When you did the install, did you do this step: https://wiki.archlinux.org/index.php/Be … clock_time
frmi wrote: the clock in gnome/cinnamon is 2 hours off hwclock/localtime
Does this mean your hardware clock is set to loacal time?
What does
sudo hwclock
return (and is that local time)?
and what is in /etc/adjtime?
This just made me realise that it's the hwclock which is off localtime.
Would
# hwclock --systohc --utc
Set the clock properly or should i use localtime instead of utc?
anyway here's the output:
[fm@fm-lap ~]$ sudo hwclock
Password:
2012-08-19T15:39:23 CEST -0.145579 seconds
[fm@fm-lap ~]$ cat /etc/adjtime
0.000000 0 0.000000
0
UTC
Last edited by frmi (2012-08-19 11:50:01)

KDM crash - hardware clock

I had some problems with a computer running KDE4 at work. KDM would crash back to console. Login in from console as root and switch between run levels back and forth - init 3 and back to init 5 - would get KDM up and running with no problem though.
Fix:
- in BIOS hardware clock was two hours back in time, adjusting it correctly mad KDM start correctly
From kdm.log:
kdmgreet(2657)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
This message is persistent even though KDM now starts. Intriguingly, at least for me, is the fact that the log after adjustment of time is two hours ahead of time. During crashes is was correct. System time was and is correct (ntpd).
Two questions:
- how come KDM log doesn't adhere to neither system or BIOS hardware clock?
- is it reasonable that such a "small" error causes KDM to crash?
The first question seems to be answered by the fact that kdm.log complaints about not being able to connect to D-Bus server. However why doesn't it? Dbus is started as it should, and no other services seem to

To restate the problem:
Microsoft Windows expects the hardware clock on the machine upon which it is running to be local time. Linux machines and others set and use the hardware clock as UTC (aka GMT) time. Thus, when a machine can be dual-booted,
there is a discrepancy in the reported time. You can modify the other operating system parameters to deal with a hardware clock in local time, or you can change Windows to cope with a UTC hardware clock.
While it is possible to kluge the time zone as is mentioned below, a simpler solution is to
synchronize Windows time with a NIST server ("time.windows.gov", e.g.) vs. the default Windows time server "time.windows.com". You can do this in the "Internet Time" tab when you click on the date/time on the system bar. Once it refreshes,
the time in Windows will be the correct local time, vs. the previously incorrect time.
One drawback of this method is that after booting into Windows, the incorrect time will be displayed until a refresh is performed against the NIST server. You can adjust how often this occurs on the "Internet Time" tab as
well. Another drawback is, of course, that you need an Internet connection.
I triple-checked that using this method does NOT change the hardware clock, which is good. I have used this method for a while. Your results may vary. Hope this helps.

Hardware clocking error # 200550, PCI-5122

The PCI-5122 does not pass the self test. It
says "error 200550 occured. Possible reason: Hardware clocking error
occured". I'm not using any external clock and my PC is 3Ghz pentium
with Windows XP and Labview 7.0. Uninstall/install of NI_Scope and NI DAQmx didn't
help.
By the way, if I put PCI-5911 card instead of PCI-5122 into the same PCI slot, it works fine.

Hello Danraz,
It sounds like you have followed all of the recommended steps for troubleshooting for this type of error. As one additional step you could test it in another PC if you have one available. Unfortunately, you will most likely need to send your board in for repair. Please contact support to make arrangements. You will be asked to provide them the serial number of your board in order to have the board repaired, and they may also verify your troubleshooting steps at this time.
Regards,
Jennifer O.
Product Support Engineer - High Speed Digitizers

Wrong hardware configuration

Hi,
when I tried request my licence key I got an e-mail with a demo licence and the following text. I need change my database of DB2/EXS to Microsoft SQL Server. Does anybody know how to correct this?
Wrong hardware configuration
Your installation 0020268639 was contractually licensed with the following
hardware configuration:
NT/INTEL / DB2/EXS ( valid until 31.12.9999 )
The data from your license key request for system B01 does not match
this data. You will therefore only receive a fixed-term license key.
Please check your entries and, if necessary, inform your contract
department at SAP about possible changes to the hardware configuration.
After correcting the hardware configuration, please request a new
license key for this system.

Hi Rodolpho,
I think you'll need to put a support request through to SAP and tell them that the contractual information is incorrect. The contractual information is maintained by SAP themselves so there is no way for you to directly edit it. When raising a support request you can choose Administration--Licensing as the component and this will ensure that your query will be sent to the licensing department.
Kind Regards,
Owen

Hardware Clock in UTC

In the past it was possible to have the computer's hardware clock in UTC using the following setting
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
"RealTimeIsUniversal"=dword:00000001
With Windows 8.1 this settings seems to be ignored.
How do I set the hardware timer to UTC?
(a similar question was asked ages ago in http://social.technet.microsoft.com/Forums/windows/en-US/8b7ce360-a9b1-4358-84cb-3559b063b1d2/windows-7-internet-time-update-and-realtimeisuniversal-utc-registry-hack?forum=w7itproinstall )

To restate the problem:
Microsoft Windows expects the hardware clock on the machine upon which it is running to be local time. Linux machines and others set and use the hardware clock as UTC (aka GMT) time. Thus, when a machine can be dual-booted,
there is a discrepancy in the reported time. You can modify the other operating system parameters to deal with a hardware clock in local time, or you can change Windows to cope with a UTC hardware clock.
While it is possible to kluge the time zone as is mentioned below, a simpler solution is to
synchronize Windows time with a NIST server ("time.windows.gov", e.g.) vs. the default Windows time server "time.windows.com". You can do this in the "Internet Time" tab when you click on the date/time on the system bar. Once it refreshes,
the time in Windows will be the correct local time, vs. the previously incorrect time.
One drawback of this method is that after booting into Windows, the incorrect time will be displayed until a refresh is performed against the NIST server. You can adjust how often this occurs on the "Internet Time" tab as
well. Another drawback is, of course, that you need an Internet connection.
I triple-checked that using this method does NOT change the hardware clock, which is good. I have used this method for a while. Your results may vary. Hope this helps.

Hardware Clock Delayed

Hello everybody. Since I installed Arch I realised that my laptop BIOS clock and my Archlinux clock as well are 2 hours delayed, but Ubuntu's clock is on hour.
And if I change in the BIOS menu the hardware clock and set it on hour when I reboot the laptop it sets it -2 hours again.
Maybe this is irrelevant but I live in GTM+2 (¿the clock sets to GTM? I don't know)
Someone gets an idea?
Thank you!

Check the "TIMEZONE" and "HARDWARECLOCK" entries in your /etc/rc.config. Mine are set to "UTC" (hardwareclock) since Arch is my only OS on my machine and "Europe/Berlin" for timezone. Another possibility would be using NTP to sync your clock with a timeserver.

How do I synchronize a 250x250 Scan AO and AI with hardware clocks?

Hi,
I am building a Scanning tunneling Microscope STM which requires a 250 by 250 pixel scan with a delay of about 1ms between pixels. I want to start the scan with a software trigger. The scan entails outputting an x and y value using two AO channels , wait about 1ms then read a tunnel current analog input value at that position, store it in an array and repeat till done. The array will then be plotted using an intensity graph.
As an option, I would like to plot a single line of the scan as it is completed to allow operator monitoring as the scan is produced. I have programmed this in sw using nested while loops but the overhead is too great for 1ms pixel sample times.
I have found a close solution in forum under the AI delay following an AO that used a hardware trigger to start process : See" AODelayAI.vi"
I have a PCI MIO 16E-4 DAQ board and am using LABVIEW 6.
PS: Is there any discrete that is generated by an AO which can be used to trigger an AI or a counter?

I have several follow up questions:
Q1)Re your suggestion to use the AO to trigger a counter : What signals sources from AO processes are available to route to the counter trigger? I have no external sources.
Q2)
What about this alternative proposal for a single AI read at each point?
a) use counter0 to generate a single pulse (about 1ms wide) , low phase 1, hi phase 2. Start counter with SW.
b) set AI trigger to output of counter0. Trigger on hi to low edge.
c) set AO trigger identical to AI trigger. Trigger on low to hi edge.
Read
Set AI scan rate and number of scans to match the AO scan parameters with timing based on internal scan clocks.
Q3)I foresee a possible need to make 20 to 100 AI samples at each (x,y) point for post processing averaging of noise effects. What modifications are needed to AI trigger scheme to make these reads to a buffer and read the buffer without adding significant software overhead?
Thanks again

Sync Hardware-clock with ntp

Hi everybody,
I don't know if I'm right here, but I don't know, whereelse I can post my problem.
I use xntp to sync my Solaris8 servers with a NetwareServer over ntp using xntp.
Everything seems to work fine, but my Hardwareclock does not sync with the received time. In ntp.conf I set "enable pll" wich should enable HW-Clock to sync but when I use the "date"-command time keeps different (about 6 minutes) from the ntp-server.
What's wrong with my configuration?
Thanks so far
Sabine

brebs wrote:11-minute sync mode
Right, I've checked from `adjtimex --print`, that 11 minute mode is indeed on here (supposedly activated by ntpd). This should mean that with ntpd in effect, `hwclock --systohc` is indeed unnecessary at all (also doesn't hurt).
tjwoosta wrote:I also noticed that when I reboot my clock always goes back to being out of sync untill about 10 minutes later when ntp syncs it.
How much is the clock off when the system boots up? And how long has the system been down?
Or did you mean really "reboot"? In that case, I guess the 11 minute mode is off.
Running ntpdate at bootup as brebs suggested should be fine. Adding ntpdate to your DAEMONS array should do it (but I'm not sure if it will disable 11 minute mode).
Below is my current point of view on this issue (correct me if anything is wrong):
If you want to maintain the RTC accurately, you use hwclock as the *only* program that ever sets/adjusts the RTC. To do this, you must prevent anything else from setting the RTC, e.g. the 11 minute mode, or another OS. This has the benefit of relatively accurate time at boot up, by running `hwclock --adjust && hwclock --hctosys`.
On the other hand, if you can't prevent others from setting the RTC, don't use hwclock to set/adjust RTC at all. The downside is that any drift of the RTC when the system is down will not be adjusted at boot up, but can only be corrected later by ntpd + the 11 minite mode, or whatever.
Last edited by lolilolicon (2011-05-09 07:46:55)

Dual Core Center displaying wrong CPU clock speed

Hi,
I've got the 965 Platinum board and I have overclocked my E6300 Allendale to 2.331ghz (from 1.86ghz). My problem is that the MSI Dual Core Center is showing my CPU as being clocked at 2.997mhz. It seems to think that, because I've upped the FSB to 333mhz, I must have a CPU with a multiplier of 9 instead of the 7 of the E6300.
If Dual Core Center is not reading the CPU clock correctly how can I trust that it's reading the temperature right (which is really the only reason Ihave it loaded at all). I know the CPU is only set at 2.331 because the BIOS gets it right, System Properties gets it right and Intel's Thermal Analysis Tool gets it right. It's only the Dual Core Center that gets it wrong.

Make sure you are using the newest version of DCC.
Other than that, DCC might not be the best tool to monitor your system.
Quote
how can I trust that it's reading the temperature right (which is really the only reason Ihave it loaded at all).
To monitor core tempertatures use Coretemp: http://www.thecoolest.zerobrains.com/CoreTemp/
A very good program to monitor all kinds of stuff ist everst 3.5.

Hardware clock in PCI-6052E

Is there any indication either it uses windows clock or DAQ STC built in timer.
my question is how we know that a normal
programme in labview is using which clock???

Dear Haider,
Since you are using AI Start, your analog input is hardware timed. This means that your data is read from the buffer at regular times. Everything else in your program is software timed. I know this because the software is doing the checking for the condition and the digital lines of the PCI-6052E can be output with hardware timing, but it involves using the an analog clock. For more information on this look at the examples in the Example Finder (LabVIEW help menu>>Find Examples) under Browse Hardware Input and Output>>Traditional DAQ>>Digital Input and Output>>E Series.
Have a great day!
Marni S.

OVM Guest wrong hardware clock

Similar Messages

Maybe you are looking for