search for: rtc

...> 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 \ QEMU_OPTIONS="-rtc base=`date +%Y-%m-%dT12:%M:%S`" ^^ Adjust the hour (marked with ^^) to simulate selecting a different offset. Rich.

Calculate the offset of the physical host's Real Time Clock (RTC) from UTC and pass this to virt-v2v through the libvirt XML description of the physical machine. The libvirt XML is modified to add one of the following: (no <clock/> element) - if the RTC could not be read or there was some other time calculation error. <clock offset='utc'...

Anybody having issues with ztdummy under the current 2.6 RC7? I get the following errors when trying to modprobe ztdummy: "Unable to register zaptel rtc driver" Doing a Google on the error shows reference to a message from 2004 that said you might not have RTC compiled into the kernel. Checking via: cd /usr/src/linux-2.6.13-rc7 grep -i rtc .config shows: CONFIG_APM_RTC_IS_GMT=y CONFIG_RTC=m CONFIG_GEN_RTC=m CONFIG_GEN_RTC_X=y CONFIG_HPET...

Hello, Maybe I'm missing something here. What is the proper way to use RTC with ztdummy now? I'm using -HEAD from a day or two ago on Linux 2.6.11.11. In zaptel/Makefile, I changed CFLAGS to: CFLAGS+=-I. -O4 -g -Wall -DBUILDING_TONEZONE -DUSE_RTC #-DTONEZONE_DRIVER and I get.. make -C /lib/modules/2.6.11.11/build SUBDIRS=/usr/src/zaptel modules make[1]: Entering d...

Hello, In what we believe is now the final regression discovered when upgrading XenServer from Xen 4.1 to 4.3, there is an issue with RTC emulation. Win2003 SP2 is a WAET unaware operating system, whose RTC access pattern triggers Xen''s rtc_mode_no_ack logic. The result is that the domain falls into a tight loop reading RTC RegC, whoes value is always 0xc0. I have confirmed that switching Xen back to RTC strict mode fixes...

Hi guys, I was wondering whether there's anyone who could share his/her experiences with using Microsoft RTC Library. In particular I am wondering what Ethernet capacity should I have in scenario of 30 people using Microsoft RTC Library for SIP communication (PBX is obviously Asterisk :-) ) concurrently (alaw codec being used)? What problems can be expected in such scenario? Would a good 1 gBit switch be...

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...

...IP/2.0/UDP 111.111.111.8:5060;branch=z9hG4bK360502ae;rport From: "asterisk" <sip:asterisk@111.111.111.8>;tag=as348de10b To: <sip:111.111.111.50:16666>;tag=60ddafdb3c924f2f87bcd1fe186f7e7f Call-ID: 104d16a9260f074f7d3dba3235b1870a@111.111.111.8 CSeq: 102 INVITE User-Agent: RTC/1.2 Content-Length: 0

...compiled the xen binaries and the kernel with the sources. DomO starts without any problems, but when I run domU, it stops and freeze. My domU is a clone of my domO. ___________________________________________ unmounting old /dev unmounting old /proc unmounting old /sys INIT: version 2.86 booting rtc: IRQ 8 is not free. modprobe: FATAL: Error inserting rtc (/lib/modules/2.6.18.8_HwiXen/kernel/drivers/char/rtc.ko): Input/output error ___________________________________________ I added this line at the end of the domU configuration file, and the machine starts, without freezing : extra=''...

Hi, I'm trying to intall zaprtc on my machine (I don't have UHCI_USB nor Zaptel) and I have a strange behaviour during loading. When I do >make load I have : ./zaprtc.o: init_module: Input/ouput error With a quick dmesg got: rtc: I/O port 112 in not free Is someone have any idea to solve this ? I saw on the README file...

Hi all, I have installed centos 5.1 x86_64. 2.6.18-53.1.14.el5 Everything seems to be working fine except that the rtc module is not working. cat /proc/interrupts shows: CPU0 CPU1 0: 129 0 XT-PIC-XT timer 1: 330797 0 XT-PIC-XT i8042 2: 0 0 XT-PIC-XT cascade 3: 4 0 XT-PIC-XT 4:...

Greetings, I'm trying to create a server-based SIP chatroom (using MeetMe w/ ztdummy), where the clients will be mainly connecting with MS RTC Clients. I got the authentication working, but am having a problem where I can only hear audio when I am also making noise into the microphone. This appears to be the VAD/MOH problem mentioned on this list before. http://lists.digium.com/pipermail/asterisk-users/2003-October/023542.html Thi...

...thers with 2 X100P cards in each of them as well). I'm interested in using MeetMe in the one without the hardware (it works great in the ones with the hardware). I can't use ztdummy, because the system has usb-ohci drivers, rather than usb-uhci. I have read the little there is about zaprtc, and I am wondering whether there is a downside in turning off RTC support in the kernel, and recompiling. Are there other things that might break if I do this (it simply feels like a more "drastic" step than the ztdummy approach)? (I am running Red Hat 9.0) Finally, and this will sh...

...mU VMs (CentOS 5.6 x86_64) runs a cobol application, which in turn called ''clock'' to get timestamps. Changing this is non-trivial. When I try to call ''clock --debug'' I get: [root@vm0010 ~]# clock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=19: No such device. No usable clock interface found. Cannot access the Hardware Clock via any known method. The device exists: [root@vm0010 ~]# ls -lah /dev/rtc crw------- 1 root root 10, 135 Jul 12 18:00 /dev/rtc As I understand it, this is (in part?) to prevent domU from alte...

....am | 3 +- bootstrap | 2 -- conversion.c | 5 ++- cpuid.c | 4 +-- gui.c | 11 +++--- kernel-cmdline.c | 4 +-- kernel.c | 10 +++--- main.c | 11 +++--- nbd.c | 10 +++--- p2v.h | 5 ++- physical-xml.c | 6 +--- rtc.c | 13 ++++--- ssh.c | 57 ++++++++++++++--------------- whole-file.c | 94 ------------------------------------------------ 14 files changed, 58 insertions(+), 177 deletions(-) delete mode 100644 whole-file.c -- 2.21.0

...onolithic 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: consolidate toggling of RTC IRQ 3: adjust rtc_timer_update() 4: fix RTC hour conversions 5: used cached original value in RTC_REG_B writing code 6: generalize IRQ raising on RTC_REG_B writes Signed-off-by: Jan Beulich <jbeulich@suse.com>

...xen-hypervisor-4.4-amd64 Version: 4.4.1-8 Severity: normal Tags: patch The Xen hypervisor in Debian Jessie does not boot on recent HP server hardware (e.g. the current dl360 gen9 series) when using normal "legacy" boot. During boot, it panics with the message "System without CMOS RTC must be booted from EFI". This message was introduced in upstream commit f745566, "x86: honor ACPI indicating absence of CMOS RTC". After reports that this breaks booting on HP servers, because the hardware incorrectly sets the CMOS RTC Not Present flag, a workaround was made in...

...t fine: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.1.0.4 when I try to: hal04 dahdi # modprobe dahdi_dummy FATAL: Error inserting dahdi_dummy (/lib/modules/2.6.27.10/dahdi/dahdi_dummy.ko): Input/output error kernel messages gives me: dahdi_dummy: Unable to register DAHDI rtc driver I'm probably doing something silly here. Then I was curious, so I backed up to a 2.6.25.9 kernel I already had, and dahdi_dummy loaded just fine: dahdi_dummy: RTC rate is 1024 Does anybody know whether: * something changed in mainline kernel that breaks dahdi * there was a new kernel...

Does anyone have any idea why i am having this prob on 4.7? Thanks! ===> Extracting for rtc-2002.03.05.2_1 >> No MD5 checksum file. ===> Patching for rtc-2002.03.05.2_1 ===> Configuring for rtc-2002.03.05.2_1 ===> Building for rtc-2002.03.05.2_1 "/sys/conf/kmod.mk", line 66: "Do not use KMODDEPS on 5.0+, use MODULE_VERSION/MODULE_DEPEND" *** Error cod...

This patch rewrites the rtc/timeoffset entry so the VM''s record can be retrieved with the Java xmlrpc library. If the entry is ''None'' it upsets the xmlrpc parser. This fixes it, though maybe there''s a better place in xend to place similar code. Signed-off-by: Stefan Berger <stefanb@us.i...