search for: rtc_timeoffset

libxl__domain_build_info_setdefault may be called several times, so rtc_timeoffset can''t be setted in it. Move rtc_timeoffset setting logic to libxl__build_pre. Reported-by: Teck Choon Giam <giamteckchoon@gmail.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: Lin Ming <mlin@ss.pku.edu.cn> --- tools/libxl/libxl_create.c | 9 ----...

Implement "rtc_timeoffset" and "localtime" options compatible as xm. rtc_timeoffset is the offset between host time and guest time. localtime means to specify whether the emulted RTC appears as UTC or is offset by the host. Acked-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: Lin Ming <m...

Hello techs, We used XL toolkit for Xen hypervisor for starting Windows hvm VMs and the option rtc_timeoffset worked perfectly with XL. It helped us to set correct Timezone time/offset for Windows HVM VMs from inside virtual_machine xen config. For example: Below option WORKS perfectly with XL toolkit. [root@hw12xen ~]# cat goillltawdlssq.xl.cfg | grep offset rtc_timeoffset = "7200" # +2 hours...

On 02/16/2018 08:37 AM, Volo M. wrote: > Hello techs, > > We used XL toolkit for Xen hypervisor for starting Windows hvm VMs and the > option rtc_timeoffset worked perfectly with XL. It helped us to set correct > Timezone time/offset for Windows HVM VMs from inside virtual_machine xen config. > > For example: > Below option WORKS perfectly with XL toolkit. > [root@hw12xen ~]# cat goillltawdlssq.xl.cfg | grep offset > rtc_timeoffset...

...nks a lot in advance for your answers... On Fri, Feb 16, 2018 at 8:37 PM, Jim Fehlig <jfehlig@suse.com> wrote: > On 02/16/2018 08:37 AM, Volo M. wrote: > >> Hello techs, >> >> We used XL toolkit for Xen hypervisor for starting Windows hvm VMs and >> the option rtc_timeoffset worked perfectly with XL. It helped us to set >> correct Timezone time/offset for Windows HVM VMs from inside >> virtual_machine xen config. >> >> For example: >> Below option WORKS perfectly with XL toolkit. >> [root@hw12xen ~]# cat goillltawdlssq.xl.cfg | grep...

Hello, Could you please clarify if below patch is going to be released every with some stable version of libvirt. Do you have any info which version? https://www.redhat.com/archives/libvir-list/2018-February/msg00981.html Thank you in advance for your answer.

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

...t should be precise right at boot time also. The timezone is CET (UTC+1), on the Linux host /usr/share/zoneinfo/Europe/Budapest is copied over /etc/localtime. When there is no DST (Daylight Savings Time), I need the following settings for the Windoes guest to have the same time as the host: ---- rtc_timeoffset=-7200 viridian=1 ---- Now when DST came in, I need the following (notice the -7200 vs 7200): ---- rtc_timeoffset=7200 viridian=1 ---- Since I didn''t know the last one, I have restarted my DC, and there where many errors in the event log. On Linux currently I get: [root@dom0 ~]# date Sat...

...sr/lib/xen/boot/hvmloader" boot = "d" device_model = "/usr/lib64/xen/bin/qemu-dm" vfb = [ "type=vnc,vncunused=1" ] disk = [ "phy:/dev/sdd,hda,w" ] disk = [ "phy:/dev/loop0,hdc:cdrom,r" ] vif = [ "mac=00:16:3E:EE:16:2F,bridge=xenbr0" ] rtc_timeoffset=36000 # AEST #rtc_timeoffset=39600 # AEDST usb = 1 usbdevice = "tablet" _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...th previous versions it was possible... here the config - it is an opnsense (openbsd) hvm domU: name = "fenrir.chao5.int" uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" maxmem = 2048 memory = 2048 loader = '/usr/lib64/xen/boot/hvmloader' type = "hvm" vcpus = 2 rtc_timeoffset = 0 localtime = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vnc = 1 vncunused = 0 vncdisplay = 100 vnclisten = "0.0.0.0" keymap = "de" vif = [ "mac=00:16:3e:05:30:04,bridge=xenbr5,script=vif-bridge,model=e1000", &q...

...nfig.py Wed Nov 28 13:36:56 2007 +0000 +++ b/tools/python/xen/xend/XendConfig.py Wed Nov 28 09:48:59 2007 -0700 @@ -129,7 +129,8 @@ XENAPI_PLATFORM_CFG = [ ''acpi'', ''apic'', ''nographic'', ''pae'', ''rtc_timeoffset'', ''serial'', ''sdl'', ''soundhw'',''stdvga'', ''usb'', ''usbdevice'', ''vnc'', ''vncconsole'', ''vncdis...

Since upgrading to b129, I''ve noticed that my system clock is ahead by five hours, exactly how much I am behind UTC (US Eastern Time). The strange thing is it only happens when I have xen enabled. If I ''svcadm disable milestone/xvm; reboot'' the clock is correct again. If I correct the time manually, ntp knocks it right back ahead again. Oddly enough, even ntp knows

Changes since v1: - Removed libxl vncviewer related dependencies - The vncviewer function was modified to accept a domid instead of domspec; - main_vncviewer was updated to reflect the new use. - A domain_create structure is now passed to the parse_config_data where required/feasible (NULL otherwise) - xl restore now have long options for vncviewer/vncviewer-autopass; docs updated. - Updated

...eymap'', ''''], [''localtime'', 0], [''nographic'', 0], [''oos'', 1], [''pae'', 1], [''pci'', []], [''pci_msitranslate'', 1], [''pci_power_mgmt'', 0], [''rtc_timeoffset'', 0], [''soundhw'', ''''], [''stdvga'', 0], [''timer_mode'', 1], [''usb'', 1], [''usbdevice'', ''tablet''], [''vcpus'', ''4''], [''vncun...

...#39;'], [''online_vcpus'', ''1''], [''image'', [''linux'', [''kernel'', ''/boot/vmlinux-2.6.18-xen-3.1-domU_32''], [''args'', ''root=/dev/xvda1 ro 3''], [''rtc_timeoffset'', ''0''], [''notes'', [''HV_START_LOW'', ''4118806528''], [''FEATURES'', ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap |pae_pgdir_above_4gb|supervisor_mode_kernel'...

...'nographic'', 0], [''soundhw'', ''''], [''vncunused'', 1], [''sdl'', 0], [''display'', ''localhost:10.0''], [''xauthority'', ''/root/.Xauthority''], [''rtc_timeoffset'', ''0''], [''monitor'', 0], [''acpi'', 1], [''apic'', 1], [''usb'', 0], [''usbdevice'', ''''], [''keymap'', ''''], [''pci'', []],...

...;keymap'', ''''], [''localtime'', 3], [''nographic'', 0], [''oos'', 1], [''pae'', 1], [''pci'', []], [''pci_msitranslate'', 1], [''pci_power_mgmt'', 0], [''rtc_timeoffset'', 0], [''sdl'', 0], [''soundhw'', ''sb16''], [''stdvga'', 0], [''timer_mode'', 1], [''usb'', 0], [''usbdevice'', ''''], [''vcpus'', 1], [''...

Hi all, I 've such a config on xen (4.14): name = "marax.chao5.int" uuid = "e0de3cb7-3937-417d-8d63-b0993b377b6a" maxmem = 16384 memory = 16384 kernel = '/usr/lib64/xen/boot/hvmloader' vcpus = 16 rtc_timeoffset = 0 localtime = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vif = [ "mac=00:16:3e:05:01:10,bridge=xenbr5,script=vif-bridge,model=e1000" ] parallel = "none" serial = "none" type = "hvm" loader = "/usr...

...th previous versions it was possible... here the config - it is an opnsense (openbsd) hvm domU: name = "fenrir.chao5.int" uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" maxmem = 2048 memory = 2048 loader = '/usr/lib64/xen/boot/hvmloader' type = "hvm" vcpus = 2 rtc_timeoffset = 0 localtime = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vnc = 1 vncunused = 0 vncdisplay = 100 vnclisten = "0.0.0.0" keymap = "de" vif = [ "mac=00:16:3e:05:30:04,bridge=xenbr5,script=vif-bridge,model=e1000", &q...

...e the config - it is an opnsense (openbsd) hvm domU: > > name = "fenrir.chao5.int" > uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" > maxmem = 2048 > memory = 2048 > loader = '/usr/lib64/xen/boot/hvmloader' > type = "hvm" > vcpus = 2 > rtc_timeoffset = 0 > localtime = 1 > on_poweroff = "destroy" > on_reboot = "restart" > on_crash = "restart" > vnc = 1 > vncunused = 0 > vncdisplay = 100 > vnclisten = "0.0.0.0" > keymap = "de" > vif = [ > "mac=00:16:3e:05:30:0...