Time goes backwards
Hello, on my FreeBSD 8-CURRENT Xen DomU printing `date' each second gives me this: Sun Jan 25 00:55:12 UTC 2009 Sun Jan 25 00:55:13 UTC 2009 Sun Jan 25 00:55:14 UTC 2009 Sun Jan 25 00:49:50 UTC 2009 Sun Jan 25 00:49:51 UTC 2009 Sun Jan 25 00:49:52 UTC 2009 Sun Jan 25 00:49:53 UTC 2009 Sun Jan 25 00:49:55 UTC 2009 Sun Jan 25 00:49:56 UTC 2009 Sun Jan 25 00:49:57 UTC 2009 Sun Jan 25 00:49:58 UTC 2009 Sun Jan 25 00:49:59 UTC 2009 Sun Jan 25 00:50:00 UTC 2009 Sun Jan 25 00:50:01 UTC 2009 Sun Jan 25 00:50:02 UTC 2009 ... 8 mins pass ... Sun Jan 25 00:58:25 UTC 2009 Sun Jan 25 00:58:26 UTC 2009 Sun Jan 25 00:58:27 UTC 2009 Sun Jan 25 00:49:49 UTC 2009 Sun Jan 25 00:49:50 UTC 2009 It should increase every second, shouldn't it? ;) MfG, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp) ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
kern.hz = 10
Hello, I have an 8-CURRENT (as of yesterday) DomU running. kern.hz is set to 10. Is this intended? This gives some strange effects: $ ping www.google.de PING www.l.google.com (74.125.39.99): 56 data bytes 64 bytes from 74.125.39.99: icmp_seq=0 ttl=246 time=100.000 ms 64 bytes from 74.125.39.99: icmp_seq=1 ttl=246 time=0.000 ms 64 bytes from 74.125.39.99: icmp_seq=2 ttl=246 time=0.000 ms dmesg: FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #0 r187877: Thu Jan 29 16:32:39 CET 2009 jul...@bsd-xen-builder.localnet:/usr/home/julian/src/obj/usr/home/julian/sr c/head/sys/BLITZXEN WARNING: WITNESS option enabled, expect reduced performance. Xen reported: 701.590 MHz processor. Timecounter ixen frequency 10 Hz quality 0 CPU: Intel Pentium III Xeon (701.59-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6a1 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 268435456 (256 MB) avail memory = 254689280 (242 MB) cpu=0 irq=0 vector=0 cpu=0 irq=0 vector=1 kbd0 at kbdmux0 xenbus0: Xen Devices on motherboard xc0: Xen Console on motherboard Timecounters tick every 100.000 msec xbd0: 4096MB Virtual Block Device at device/vbd/51713 on xenbus0 xn0: Virtual Network Interface at device/vif/0 on xenbus0 xn0: Ethernet address: aa:00:4b:17:23:8e [XEN] netfront_backend_changed: newstate=2 Btw, it is very cool to see FreeBSD on Xen. :) Regards, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp) ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: kern.hz = 10
Mister Olli mister.o...@googlemail.com writes: Hi, I've never experimented with the kern.hz variable, but on all configuration examples for 8-CURRENT if always seen 'kern.hz=100'. From where did you get your configuration? I use the default config (albeit renamed to BLITZXEN) from 8-CURRENT. Regards, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp) ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Time goes backwards
Mister Olli mister.o...@googlemail.com writes: Hi, I've had time problems too. The clock did not go backwards, but forwards for some time sime, and then jumped back to a certain date. Like Sun Jan 25 00:55:12 UTC 2009 ... Sun Jan 25 01:08:35 UTC 2009 Sun Jan 25 00:55:12 UTC 2009 Sun Jan 25 00:55:13 UTC 2009 ... This is almost exactly the date my box reports... Strange. It took me quite some time to find a solution that helped for me: - activate the independent_wallclock in domO by 'sysctl xen.independent_wallclock=1' I'll try to convince the admin of the box and report back. ;) But it should really be properly fixed as it is quite a showstopper. I don't dare to build ports on that box (or do anything else involving make...). Regards, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp) ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Time goes backwards
Mister Olli mister.o...@googlemail.com writes: Hi, I've had time problems too. The clock did not go backwards, but forwards for some time sime, and then jumped back to a certain date. Like Sun Jan 25 00:55:12 UTC 2009 ... Sun Jan 25 01:08:35 UTC 2009 Sun Jan 25 00:55:12 UTC 2009 Sun Jan 25 00:55:13 UTC 2009 ... It took me quite some time to find a solution that helped for me: - activate the independent_wallclock in domO by 'sysctl xen.independent_wallclock=1' I booted the DomU with machdep.independent_wallclock=1 as kernel parameter instead. But that didn't work. sysctl still reported it as 0. I've tried setting machdep.xen_disable_rtc_set and machdep.independent_wallclock after booting, but it does not help either. - edit and configure '/etc/ntpd.conf' in domU - edit '/etc/rc.conf' and add the following lines # NTP stuff ntpdate_enable=YES ntpdate_flags=-b YOUR_NTP_SERVER ntpd_enable=YES - reboot domU If you try it on your problem, could you please give me some feedback if it worked? Doesn't work. :-/ MfG, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp) ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Xen in Virtual Machine?
Hello, I am trying to build a kvm (or VirtualBox) virtual machine to painlessly experiment with Xen on my 32-bit Linux laptop (Core Duo L2400 with hardware virtualization foo) or my 64-bit Linux desktop box (Phenom 8450). So far neither of the two manage to run Xen with either of the above mentioned VMMs. Has someone already done this or am I out of luck and have to get a real test box? Regards, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp) ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen in Virtual Machine?
Kip Macy km...@freebsd.org writes: On Mon, Feb 9, 2009 at 4:35 PM, Julian Stecklina j...@alien8.de wrote: Kip Macy km...@freebsd.org writes: I'll try VMWare. Thanks for the advice. I am still puzzled why Xen presents such a problem for hardware-virtualization based VMMs. Maybe the virtualization guys at our university can clear that up... 32-bit Xen uses segments in an unusual way. They may not be implementing emulation support for this correctly. Do you mean using additional protection rings? Yes, no one does that except Xen. Regards, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp) ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Time goes backwards
Kip Macy km...@freebsd.org writes: I will take a closer look. This is clearly a separate issue from the loss of timer interrupts - I had assumed that they were related. I've seen that you made some changes to the timer code. Is this related to this issue? Btw, VMWare didn't cut it either in building a virtual Xen test box. *bummer* Regards, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp) ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
