Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hmm, at first glance the BIOS is set to UTC which corresponds to a -7:00 offset which is correct for PDT. So I guess I am wrong and it does look like a UTC/BIOS clock problem.
Still waiting on the confirmation for your Windows date/time settings.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Quote:
Originally Posted by mostlyharmless
Interestingly, to me at least, I've seen this problem with booting a VM of Windows under Linux. Clearly care has to be taken to ensure that VM upon booting doesn't read the UTC as localtime. At least the host doesn't get changed.
With VirtualBox, at least, there is an option to set the VM BIOS clock to UTC or not for just this situation.
Mind you, the registry trick will still work in a VM.
Yes, using libvirt or qemu directly it's pretty straightforward to pass the clock=localtime to Windows, but the default is utc, so you have to remember to do that.
It is set to time.windows. What am I supposed to do to fix it? So many different variables, opinions, I lost track what to to.
Chris.
P.S. Linux is not running very good, lot of problems. Windows is rock solid. Might have to format and reinstall Linux again (second time in two weeks. Will post in another subject).
You are looking at your internet time sync setting in Windows, not libvirt settings. The internet time sync will work, but, as noted previously in the thread, may be delayed and just hides the problem until next boot.
If you use a virt-manager to setup your VM (not dual booting) it'll usually pick the correct options. You can check them afterwards. On the other hand, if your Linux install is flaky you might as well fix that first.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Quote:
Originally Posted by happydog500
It is set to time.windows. What am I supposed to do to fix it? So many different variables, opinions, I lost track what to to.
Chris.
P.S. Linux is not running very good, lot of problems. Windows is rock solid. Might have to format and reinstall Linux again (second time in two weeks. Will post in another subject).
I think the easiest way is the registry change that myself and KARNVORbeefRAGE pointed out that lets Windows use UTC system clock also. It certainly works for me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
