similar to: Time is off by an hour in my XEN vm

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

Unlike the <cpu> node (see the other thread on the libguestfs ML), reading the Real Time Clock doesn't require libvirt and does work :-) For reference, read: https://libvirt.org/formatdomain.html#elementsTime https://en.wikipedia.org/wiki/Time_zone To test this you can run virt-p2v under qemu with a RTC offset: make -C p2v \ run-virt-p2v-in-a-vm \

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

On 06/11/2017 07:00 AM, Larry Fahnoe wrote: > Hi Ben, > > On RHEL/CentOS 7, libvirt-guests (which comes from libvirt-client) on the host controls the suspend vs. shutdown behavior of the guests. By default the guests suspend, but if you want them to shutdown, change the ON_SHUTDOWN setting in /etc/sysconfig/libvirt-guests. I don't have any Windows guests, but the linux guests work

I installed CentOS 5 on a server today (wiping clean the drive which had 4.4 on it). During installation I picked the correct timezone, location and all. Yet, upon booting the machine, it seems to think that it's 6 hours earlier than it really is. The BIOS has the correct time and date on it. /etc/locatime was originally what /usr/share/zoneinfo/America/Denver would've

Hello, I'm having a major problem with the timestamps in both the Icecast access.log and error.log. The timestamp on the logfiles themselves is accurate, but the logging of the various connections to my streams is in UTC. No matter how I try to configure the hwclock or the system clock, the log timestamp is always UTC, which is 8 hours ahead of my current time zone. I've even tried

Hey there, Has anyone tackled the best way to shut down a VM running Win10 running in RedHat's (CentOS 7) KVM/QEMU VM manager? I'm looking at this link to follow:

Hi all, I am having an issue with some older CentOS 5.3 servers. Every time the server boots, it gives the error "Cannot access the hardware clock by any known method", and then promptly sets the time 5 hours behind the hardware clock, down to the second. After the system is up. "hwclock" works fine. hwclock --debug does not show any error at all. The hardware clock is

Hi, I'm getting the message in the subject when I run systat -vm on a lightly loaded server. Top shows interesting CPU usage %: CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Some Googling tells me that a fix for this went in around 1998 in sys/i386/isa/clock.c, see http://www.geocrawler.com/archives/3/159/1998/7/0/777198/ (fix verified to be present in

The UIP(update in progress) is set when RTC is in updating. And the update cycle begins 244us later after UIP is set. Signed-off-by: Yang Zhang <yang.z.zhang@Intel.com> diff -r 47cb862a07c2 -r edc35b026509 xen/arch/x86/hvm/rtc.c --- a/xen/arch/x86/hvm/rtc.c Mon Mar 05 14:39:07 2012 +0800 +++ b/xen/arch/x86/hvm/rtc.c Mon Mar 05 14:39:41 2012 +0800 @@ -28,6 +28,8 @@ #include

While in the upstream kernel I''m unable to find any use of XENPF_settime (and the DOM0_SETTIME alias of it) at all, in the 2.6.18 tree (and the forward ports of it) the function gets used only when ntp_synced() returns true (and - that''s minor - when independent_wallclock is not set). It would however seem to me that this doesn''t cover the case where the host clock gets

This patch series makes suspend support in qemu alot more useful. Right now the guest can put itself into s3, but qemu will wakeup the guest instantly. With this patch series applied the guest will stay suspended instead and there are a few events which can kick the guest out of suspend state: A monitor command, ps/2 input, serial input, rtc. Not much yet, but it''s a start with the

Hi list, one and hopefully last strange thing I figured out ist the systime of my guests. Dom0 uses ntp for time syncronisation. I set the time on my guests manually but after reboot any machine (Windows server, XP, Freebsd, even PV Machines like ubuntu) all run local time - 2 hours. /proc/sys/xen/independent_wallclock is set to 0 so actually the time should be set by dom0...(?) Any

In an effort to reduce the code, start to use few bits of GLib: - replace the gnulib c-type module - replace the gnulib getprogname module - use g_spawn_sync to launch curl, and drop a file reading function Pino Toscano (6): Include glib.h in p2v.h Use g_ascii_isspace instead of c_isspace from gnulib Use g_get_prgname instead of getprogname from gnulib build: remove no more used gnulib

hey list! having a slightly odd time issue on one host... can I get some help with this? This is the current time from a working system: Sun Apr 17 00:28:18 EDT 2011 However from the problem system this is the time: Sat Apr 16 20:30:01 EDT 2011 I have set the time zone as such: lrwxrwxrwx 1 root root 23 Apr 16 19:41 /etc/localtime -> /usr/share/zoneinfo/EST But when I run ntpdate

Is there any way to get virsh / libvirt to create a domain such that I can later connect to it via QMP (without hacking the code)? The command line that libvirt creates for my current setup looks like this: /usr/local/bin/qemu-system-x86_64 -S -M pc-0.12 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name winxpsp2 -uuid ab244939-c804-1aff-68b6-9324f174c3c8 -nodefconfig -nodefaults

Hi there, is there a way to set a guest to start with a specific date and time. (e.g. when guest boots, starting guest time should always be (2017-02-05T12:00:00)). I've tried something like this in my kvm domain: <clock offset='variable' adjustment='-86400' basis='localtime'> <timer name='rtc' tickpolicy='delay'

Hi, all I need building my own install server and want install my custom world, custom kernel and other in non-interactive mode. With 6.1-beta3 it work in mass (I not try install my kernel). With 6.1-beta4 and more fresh I can't get non-interactive installation. 1. I can't find how to select timezone non-interactive. 2. I can't good variant for installing my own kernel (now I use

Finally I got around to breaking up the similarly named monolithic patch that caused a regression shortly before the 4.2 release and got therefore reverted. This series consists of the broken up pieces that - according to my testing - don''t expose the reported lockup; the 7th will need debugging to understand what''s wrong there. 1: use RTC_* names instead of literal numbers 2:

My domain xml is like this: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>2008-2</name> <uuid>6325d8a5-468d-42e9-b5cb-9a04f5f34e80</uuid> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <vcpu