Hi Fred, I did as you suggested below but it did not resolve the problem.
I also contacted one of the folks who maintain our virtual infrastructure to ask if the clock on the actual hardware was set to UTC or to local time. He said that he thought it was set to UTC and went on to say that he didn't really see how it could matter since the guest VM doesn't really have any direct access to the real hardware. He indicated that the VM only sees the abstracted environment, which he indicated should be presenting UTC. I rebooted the VM and checked the BIOS settings. The clock was set to UTC. Thanks for any other suggestions or insights you might have. Larry On Tue, May 1, 2012 at 10:02 AM, Grooms, Frederick W < frederick.w.gro...@xo.com> wrote: > It is hard for anyone to tell without access to the hardware CMOS > directly, but since you are off by an hour in the web services (and that is > the exact same problem we had) I would believe that your hardware is not > running as UTC/GMT. From what I have heard it is common to have the > physical machine set in a local timezone when one of the virtual machines > (or possibly could be) is a Windows OS. > > I would recommend changing UTC to false in the /etc/sysconfig/clock file > and running > /sbin/hwclock --hctosys > /sbin/hwclock --systohc > > Fred > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
