Hi all, One of our domU 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 altering dom0''s date/time. Obviously, this is a good thing, but can the device be made available to domU VMs in a "read-only" mode? Thanks! -- Digimer E-Mail: digimer@alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "I feel confined, only free to expand myself within boundaries." _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Diego Molina
2011-Jul-13 11:39 UTC
Re: [Xen-users] Problem in linux domU re: /dev/rtc and hwclock
Hi, (just to cover things up) may it be possible to change the cobol instruction to use the system time instead of the hardware time? That would be like executing `date'' command instead ''hwclock''. 2011/7/12, Digimer <linux@alteeve.com>:> Hi all, > > One of our domU 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 altering > dom0''s date/time. Obviously, this is a good thing, but can the device be > made available to domU VMs in a "read-only" mode? > > Thanks! > > -- > Digimer > E-Mail: digimer@alteeve.com > Freenode handle: digimer > Papers and Projects: http://alteeve.com > Node Assassin: http://nodeassassin.org > "I feel confined, only free to expand myself within boundaries." > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Possibly Parallel Threads
- New Tutorial - RHCS + DRBD + KVM; 2-Node HA on EL6
- New Tutorial - RHCS + DRBD + KVM; 2-Node HA on EL6
- OT: Recommendation for a good Internationalized terminal software
- Patches to enable MTUs >1500 in el5.6 ready for testing.
- Setting up virtual ''ethX'' devices in Xen 3.4