Description of problem: I use Xen 4.4.1 (XL) with libvirt 1.2.14 on Debian Jessie. With Windows 2008 R2 und Windows 2012 R2 (both tested) the clock ist always wrong (2 hours behind) and shows always RTC time. It does not matter what I set into the libvirt XML config tag <clock> (Windows normally uses localtime). I have tested really everything with no success. Version-Release number of selected component (if applicable): Libvirt 1.2.9 and 1.2.14 tested. Xen 4.4.1 with XL backend. Kernel 3.16.7 from Debian Jessie How reproducible: Setup a Windows 2008 R2 guest with virt-manager >=1.0.1 and check clock. Steps to Reproduce: 1. Simply install Debian Jessie with Xen 4.4.1 and libvirt 1.2.9 from repo. 2. Create Windows >=2008 R2 Guest with virt-manager and start. 3. Check clock. Actual results: Windows clock is ALWAYS RTC (checked with cat /proc/driver/rtc on xen host) regardless of clock settings in Libvirt XML config of guest. Expected results: Clock shows RTC+2 hours. Additional info: 1. When I convert XML to native (xl) and start the guest the clock is always correct (RTC+2 hours) 2. Checking with "ps aux | grep GUEST" does not show anything about clock, timer or rtc. 3. Booting the same server with KVM and recreate the guest (same Windows installation) with virt-manager the clock is correct too and with "ps aux..." I can see rtc and timer options from qemu. Does libvirt lack clock timer support with xl driver?
Sorry this didn't receive a timely response. Can you confirm this is still relevant with newer libvirt and libxl? If so I'll ping one of the xen libvirt maintainers
(In reply to Cole Robinson from comment #1) > Sorry this didn't receive a timely response. Can you confirm this is still > relevant with newer libvirt and libxl? If so I'll ping one of the xen > libvirt maintainers This response comes really late. In the meantime I have decided against libvirt, sorry.