From deb at es.net  Mon Jan 12 14:23:19 2009
From: deb at es.net (Deb Heller-Evans)
Date: Mon Jan 12 14:23:25 2009
Subject: 64-bit Centos5 xen kernel and creating a FreeBSD domU
Message-ID: <496BC05B.2030606@es.net>

I'm new to Xen, and have been digging around the Internet.  I have a Xen 
CentOS kernel installed on an Intel 64-bit system:

Linux myhost.com 2.6.18-92.el5xen #1 SMP Tue Jun 10 19:20:18 EDT 2008 
x86_64 x86_64 x86_64 GNU/Linux

Using:
xen-3.0.3-64.el5_2.9,
kernel-xen-2.6.18-92.el5

I need to learn FreeBSD, and so I thought I'd do it under CentOS using 
Xen.  My intent was to load FreeBSD 7.x as a domU, but as I perused the 
Internet, I am seeing that there are issues with Intel 64-bit CentOS 
systems and that the domU kernel needs to have PAE support (I have 16GB 
memory on my system).

Given the current state of the Universe, and the fact that I know next 
to nothing about FreeBSD at the moment, does anyone have any sage advise 
and recommendations for me?

Thanks (in advace - as they say),
deb


From mister.olli at googlemail.com  Tue Jan 13 11:04:06 2009
From: mister.olli at googlemail.com (Mister Olli)
Date: Tue Jan 13 11:05:48 2009
Subject: Problems with FreeBSD 8-CURRENT as Xen domU
Message-ID: <1231873436.24899.85.camel@phoenix.blechhirn.net>

hi...

I've managed to compile and setup a paravirtualized domU with FreeBSD 8
(SVN snapshot from 'head').

Currently I'm running into two mayor problems:
- The system time is not behaving as expected.
	Example:
	========
	I fired the domain up at 01:43 in the morning and watch the 
	clock. Time passes normally within the maschine, and the 
	suddenly jumps back to 01:30:<VARIES>. From there on time
	passes normally up to 15 minutes (the latest time I've seen
	is 01:44:52).
	Right now the domain is running for more than 18 hours, and the
	clock still says: Tue Jan 13 01:32:52 CET 2009

	Running 'ntpd' inside the domU doesn't help to solve the 
	problem.

	If found a lot of hints for linux domU's, which say that you
	need to set the sysctl 'xen.independent_wallclock' to '1' and
	run 'ntpd' in the domU to keep time correct.
	Does 'sysctl machdep.independent_wallclock=1' the same in 
	FreeBSD? (If so, this doesn' work.)

- 2-way SMP doesn't work.
	When I put the line
		vcpus=2
	into my config file, I get the following output during
	boot, and the domU is destroyed after the reboot by
	the kernel:
================================================================
# xm create 00_template_8-CURRENT.XENconfig -c
Using config file "./00_template_8-CURRENT.XENconfig".
Started domain template_8-CURRENT
WARNING: loader(8) metadata is missing!
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-CURRENT #3: Thu Jan  8 04:34:03 CET 2009
    root@template-8_CURRENT.localdomain:/usr/obj/usr/src/sys/freebsd8_XEN
WARNING: WITNESS option enabled, expect reduced performance.
Xen reported: 1600.056 MHz processor.
Timecounter "ixen" frequency 1000000000 Hz quality 0
CPU: AMD Athlon(tm) Processor (1600.06-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x662  Stepping = 2
  Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
  AMD Features=0xc0480800<SYSCALL,MP,MMX+,3DNow!+,3DNow!>
real memory  = 671088640 (640 MB)
avail memory = 649625600 (619 MB)
gdtpfn=3edd9 pdptpfn=11113
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
cpu=0 irq=0 vector=0
cpu=0 irq=0 vector=1
cpu=1 irq=0 vector=0
cpu=1 irq=0 vector=1
kbd0 at kbdmux0
xenbus0: <Xen Devices> on motherboard
xc0: <Xen Console> on motherboard
Timecounters tick every 10.000 msec
xbd0: 8192MB <Virtual Block Device> at device/vbd/768 on xenbus0
xbd0: attaching as ad0
GEOM: ad0s1: geometry does not match label (15h,63s != 255h,63s).
xn0: <Virtual Network Interface> at device/vif/0 on xenbus0
xn0: Ethernet address: 00:16:3e:06:c3:80
[XEN] netfront_backend_changed: newstate=2
Spanic: blockable sleep lock (sleep mutex) XCONS LOCK @ /usr/src/sys/dev/xen/console/console.c:290
cpuid = 1
Uptime: 1s
Cannot dump. Device not defined or unavailable.
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot,
--> or switch off the system now.
Rebooting...
================================================================

I've attached my kernelconfig file to this mail, if someone sees a
failure in it.

Any hints on how to solve these 2 problems would be really great. Using
FreeBSD in it's current state as domU really rocks. :-)))


greetz
olli
-------------- next part --------------
#
# XEN -- Kernel configuration for i386 XEN DomU
#
# $FreeBSD$

cpu		I686_CPU
ident		XEN

makeoptions	DEBUG=-g		# Build kernel with gdb(1) debug symbols
makeoptions	MODULES_OVERRIDE=""

options 	SCHED_ULE		# ULE scheduler
options 	PREEMPTION		# Enable kernel thread preemption
#options		SCHED_4BSD		 

options 	INET			# InterNETworking
#options 	INET6			# IPv6 communications protocols
#options 	SCTP			# Stream Control Transmission Protocol
options 	FFS			# Berkeley Fast Filesystem
options 	SOFTUPDATES		# Enable FFS soft updates support
options 	UFS_ACL			# Support for access control lists
options 	UFS_DIRHASH		# Improve performance on big directories
#options 	UFS_GJOURNAL		# Enable gjournal-based UFS journaling
#options 	NFSCLIENT		# Network Filesystem Client
#options 	NFSSERVER		# Network Filesystem Server
#options 	NFSLOCKD		# Network Lock Manager
#options 	NFS_ROOT		# NFS usable as /, requires NFSCLIENT
#options 	MSDOSFS			# MSDOS Filesystem
options 	CD9660			# ISO 9660 Filesystem
options 	PROCFS			# Process filesystem (requires PSEUDOFS)
options 	PSEUDOFS		# Pseudo-filesystem framework
options 	GEOM_PART_GPT		# GUID Partition Tables.
options 	GEOM_LABEL		# Provides labelization
options 	COMPAT_43TTY		# BSD 4.3 TTY compat (sgtty)
options 	COMPAT_FREEBSD4		# Compatible with FreeBSD4
options 	COMPAT_FREEBSD5		# Compatible with FreeBSD5
options 	COMPAT_FREEBSD6		# Compatible with FreeBSD6
options 	COMPAT_FREEBSD7		# Compatible with FreeBSD7
options 	KTRACE			# ktrace(1) support
options 	STACK			# stack(9) support
options 	SYSVSHM			# SYSV-style shared memory
options 	SYSVMSG			# SYSV-style message queues
options 	SYSVSEM			# SYSV-style semaphores
options 	_KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options 	KBD_INSTALL_CDEV	# install a CDEV entry in /dev
options 	AUDIT			# Security event auditing

# Debugging for use in -current
#options 	KDB			# Enable kernel debugger support.
#options 	DDB			# Support DDB.
#options 	GDB			# Support remote GDB.
#options 	INVARIANTS		# Enable calls of extra sanity checking
#options 	INVARIANT_SUPPORT	# Extra sanity checks of internal structures, required by INVARIANTS
options 	WITNESS			# Enable checks to detect deadlocks and cycles
#options 	WITNESS_SKIPSPIN	# Don't run witness on spinlocks for speed

options		PAE
nooption	NATIVE
option		XEN
nodevice	atpic
nodevice	isa
options		MCLSHIFT=12

# To make an SMP kernel, the next two lines are needed
options 	SMP			# Symmetric MultiProcessor Kernel
device		apic			# I/O APIC


device         atkbdc          # AT keyboard controller
device         atkbd           # AT keyboard
device         psm             # PS/2 mouse
device         pci

device		kbdmux		# keyboard multiplexer

# Pseudo devices.
device		loop		# Network loopback
device		random		# Entropy device
device		ether		# Ethernet support
device		tun		# Packet tunnel.
device		pty		# Pseudo-ttys (telnet etc)
#device		md		# Memory "disks"
#device		gif		# IPv6 and IPv4 tunneling
#device		faith		# IPv6-to-IPv4 relaying (translation)

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device		bpf		# Berkeley packet filter

From gaijin.k at gmail.com  Wed Jan 14 07:07:55 2009
From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko)
Date: Wed Jan 14 07:08:02 2009
Subject: 64-bit Centos5 xen kernel and creating a FreeBSD domU
In-Reply-To: <496BC05B.2030606@es.net>
References: <496BC05B.2030606@es.net>
Message-ID: <1231945646.1172.8.camel@RabbitsDen>

On Mon, 2009-01-12 at 14:12 -0800, Deb Heller-Evans wrote:
> I'm new to Xen, and have been digging around the Internet.  I have a Xen 
> CentOS kernel installed on an Intel 64-bit system:
> 
> Linux myhost.com 2.6.18-92.el5xen #1 SMP Tue Jun 10 19:20:18 EDT 2008 
> x86_64 x86_64 x86_64 GNU/Linux
> 
> Using:
> xen-3.0.3-64.el5_2.9,
> kernel-xen-2.6.18-92.el5
> 
> I need to learn FreeBSD, and so I thought I'd do it under CentOS using 
> Xen.  My intent was to load FreeBSD 7.x as a domU, but as I perused the 
> Internet, I am seeing that there are issues with Intel 64-bit CentOS 
> systems and that the domU kernel needs to have PAE support (I have 16GB 
> memory on my system).
> 
> Given the current state of the Universe, and the fact that I know next 
> to nothing about FreeBSD at the moment, does anyone have any sage advise 
> and recommendations for me?
Given that you are new to FreeBSD, I would recommend building
fully-virtualized (as opposed to paravirtualized) domU, provided that
your hardware and software supports that. That would give you stable
FreeBSD playground from which you could move on to -CURRENT, with its
Xen support, when you feel comfortable with the platform. I am running
fully-virtualized FreeBSD 6.4 domU under OpenSuSE 11.0/Xen 3.2.1 and it
seems to be quite happy. I have picked 6.4 just because that was what I
needed at the time, but I suspect that 7.1 would work too.

Just my 2c.

> 
> Thanks (in advace - as they say),
> deb
> 
> 
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"
-- 
Alexandre "Sunny" Kovalenko (????????? ?????????)

From Ron.Carter at cartersweb.net  Wed Jan 14 09:48:14 2009
From: Ron.Carter at cartersweb.net (Ron Carter)
Date: Wed Jan 14 09:48:21 2009
Subject: 64-bit Centos5 xen kernel and creating a FreeBSD domU
In-Reply-To: <1231945646.1172.8.camel@RabbitsDen>
References: <496BC05B.2030606@es.net> <1231945646.1172.8.camel@RabbitsDen>
Message-ID: <A3BFD7610AD8DE4198A516C0030F535E5C29@bronto.Carterswebnet.local>

I really like to get a copy of your image with paravirtualization built into it.  I running PF-Sense on XEN 5.0.  An would love to try to create a build of it that has the paravirtualized kernal and network drivers built into it.  That would be awesome.  

My build skills for freebsd are extreamly limited so I have been struggling with how to get it working and just trying to figure out what has to be done just to create a build.
RC 

-----Original Message-----
From: owner-freebsd-xen@freebsd.org [mailto:owner-freebsd-xen@freebsd.org] On Behalf Of Alexandre "Sunny" Kovalenko
Sent: Wednesday, January 14, 2009 10:07 AM
To: Deb Heller-Evans
Cc: freebsd-xen@freebsd.org
Subject: Re: 64-bit Centos5 xen kernel and creating a FreeBSD domU

On Mon, 2009-01-12 at 14:12 -0800, Deb Heller-Evans wrote:
> I'm new to Xen, and have been digging around the Internet.  I have a 
> Xen CentOS kernel installed on an Intel 64-bit system:
> 
> Linux myhost.com 2.6.18-92.el5xen #1 SMP Tue Jun 10 19:20:18 EDT 2008
> x86_64 x86_64 x86_64 GNU/Linux
> 
> Using:
> xen-3.0.3-64.el5_2.9,
> kernel-xen-2.6.18-92.el5
> 
> I need to learn FreeBSD, and so I thought I'd do it under CentOS using 
> Xen.  My intent was to load FreeBSD 7.x as a domU, but as I perused 
> the Internet, I am seeing that there are issues with Intel 64-bit 
> CentOS systems and that the domU kernel needs to have PAE support (I 
> have 16GB memory on my system).
> 
> Given the current state of the Universe, and the fact that I know next 
> to nothing about FreeBSD at the moment, does anyone have any sage 
> advise and recommendations for me?
Given that you are new to FreeBSD, I would recommend building fully-virtualized (as opposed to paravirtualized) domU, provided that your hardware and software supports that. That would give you stable FreeBSD playground from which you could move on to -CURRENT, with its Xen support, when you feel comfortable with the platform. I am running fully-virtualized FreeBSD 6.4 domU under OpenSuSE 11.0/Xen 3.2.1 and it seems to be quite happy. I have picked 6.4 just because that was what I needed at the time, but I suspect that 7.1 would work too.

Just my 2c.

> 
> Thanks (in advace - as they say),
> deb
> 
> 
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"
--
Alexandre "Sunny" Kovalenko (????????? ?????????)

_______________________________________________
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"
From mister.olli at googlemail.com  Thu Jan 15 04:54:58 2009
From: mister.olli at googlemail.com (Mister Olli)
Date: Thu Jan 15 04:55:06 2009
Subject: 64-bit Centos5 xen kernel and creating a FreeBSD domU
In-Reply-To: <A3BFD7610AD8DE4198A516C0030F535E5C29@bronto.Carterswebnet.local>
References: <496BC05B.2030606@es.net> <1231945646.1172.8.camel@RabbitsDen>
	<A3BFD7610AD8DE4198A516C0030F535E5C29@bronto.Carterswebnet.local>
Message-ID: <1232024088.18652.4.camel@phoenix.blechhirn.net>

hi...

I'm currently working on getting 8-CURRENT to run as para-virtualized
domU.

the system boots up, but I have some problems with time and SMP (see my
posting on jan 13.).

If you're interested in contributing work to solve that problem just
drop me an email...

greetz
olli


Am Mittwoch, den 14.01.2009, 12:48 -0500 schrieb Ron Carter:
> I really like to get a copy of your image with paravirtualization built into it.  I running PF-Sense on XEN 5.0.  An would love to try to create a build of it that has the paravirtualized kernal and network drivers built into it.  That would be awesome.  
> 
> My build skills for freebsd are extreamly limited so I have been struggling with how to get it working and just trying to figure out what has to be done just to create a build.
> RC 
> 
> -----Original Message-----
> From: owner-freebsd-xen@freebsd.org [mailto:owner-freebsd-xen@freebsd.org] On Behalf Of Alexandre "Sunny" Kovalenko
> Sent: Wednesday, January 14, 2009 10:07 AM
> To: Deb Heller-Evans
> Cc: freebsd-xen@freebsd.org
> Subject: Re: 64-bit Centos5 xen kernel and creating a FreeBSD domU
> 
> On Mon, 2009-01-12 at 14:12 -0800, Deb Heller-Evans wrote:
> > I'm new to Xen, and have been digging around the Internet.  I have a 
> > Xen CentOS kernel installed on an Intel 64-bit system:
> > 
> > Linux myhost.com 2.6.18-92.el5xen #1 SMP Tue Jun 10 19:20:18 EDT 2008
> > x86_64 x86_64 x86_64 GNU/Linux
> > 
> > Using:
> > xen-3.0.3-64.el5_2.9,
> > kernel-xen-2.6.18-92.el5
> > 
> > I need to learn FreeBSD, and so I thought I'd do it under CentOS using 
> > Xen.  My intent was to load FreeBSD 7.x as a domU, but as I perused 
> > the Internet, I am seeing that there are issues with Intel 64-bit 
> > CentOS systems and that the domU kernel needs to have PAE support (I 
> > have 16GB memory on my system).
> > 
> > Given the current state of the Universe, and the fact that I know next 
> > to nothing about FreeBSD at the moment, does anyone have any sage 
> > advise and recommendations for me?
> Given that you are new to FreeBSD, I would recommend building fully-virtualized (as opposed to paravirtualized) domU, provided that your hardware and software supports that. That would give you stable FreeBSD playground from which you could move on to -CURRENT, with its Xen support, when you feel comfortable with the platform. I am running fully-virtualized FreeBSD 6.4 domU under OpenSuSE 11.0/Xen 3.2.1 and it seems to be quite happy. I have picked 6.4 just because that was what I needed at the time, but I suspect that 7.1 would work too.
> 
> Just my 2c.
> 
> > 
> > Thanks (in advace - as they say),
> > deb
> > 
> > 
> > _______________________________________________
> > freebsd-xen@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"
> --
> Alexandre "Sunny" Kovalenko (????????? ?????????)
> 
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org

From mister.olli at googlemail.com  Thu Jan 15 09:19:35 2009
From: mister.olli at googlemail.com (Mister Olli)
Date: Thu Jan 15 09:19:42 2009
Subject: sysctl machdep.independent_wallclock
In-Reply-To: <eeef1a4c0901141233l327ad964jc6fdd3a937942696@mail.gmail.com>
References: <1231950392.18652.0.camel@phoenix.blechhirn.net>
	<eeef1a4c0901141233l327ad964jc6fdd3a937942696@mail.gmail.com>
Message-ID: <1232039939.18652.16.camel@phoenix.blechhirn.net>

hi...


>         what is the exact function of this sysctl setting?
> 
> I'm guessing it's something to do with Xen, having seen a few
> references in Linux for xen.machdep.independent_wallclock. 
> 
> Have a look here:
> http://docs.xensource.com/XenServer/4.0.1/guest/ch04s06.html

yeah, I know that sysctl from linux, but I wasn't quite sure if it is
the same in FreeBSD, since it's known as 'xen.independent_wallclock' in
linux and 'machdep.independent_wallclock' in FreeBSD.

I started reading the C-code of FreeBSD, and from my understanding the
function 'should' be the same, as it's really linked to the clock
handling with XEN in FreeBSD.

but from my understanding it's not completly implemented in 8-CURRENT
(as of 15 jan 2009; see the last lines):
================================
/*
 * Write system time back to RTC.  
 */
static void
domu_resettodr(void)
{
        unsigned long tm;
        int s;
        dom0_op_t op;
        struct shadow_time_info *shadow;

        shadow = &per_cpu(shadow_time, smp_processor_id());
        if (xen_disable_rtc_set)
                return;
        
        s = splclock();
        tm = time_second;
        splx(s);
        
        tm -= tz_minuteswest * 60 + (wall_cmos_clock ? adjkerntz : 0);
        
        if ((xen_start_info->flags & SIF_INITDOMAIN) &&
            !independent_wallclock)
        {
                op.cmd = DOM0_SETTIME;
                op.u.settime.secs        = tm;
                op.u.settime.nsecs       = 0;
                op.u.settime.system_time = shadow->system_timestamp;
                HYPERVISOR_dom0_op(&op);
                update_wallclock();
        } else if (independent_wallclock) {
                /* notyet */
                ;
        }               
}
================================
is that correct???

greetz
olli
>         

From xen at komadev.de  Thu Jan 29 07:53:17 2009
From: xen at komadev.de (Kai Mosebach)
Date: Thu Jan 29 07:53:26 2009
Subject: Instable 32bit domU on 64bit dom0 (w/Xen 3.3.1)
Message-ID: <11276352.23661233243265678.JavaMail.root@zim.freshx.de>

Hi,

i recently got my first FreeBSD 8 domU working and i am quite happy to see that there is eventually progress on the important Xen topic for FreeBSD.
Since this domU as a svn -head checkout from 23.01.09 still segfaults here and there i startet to rebuild the whole world with debugging symbols in the hope that the backtraces give more info's on where to find bugs.

Here are the first results from several core files which hang around in the system after a world build and i hope the developers here can make more sense out of it than me.

If you need further dumps/traces or have some advises how to go on from here, please let me know!

Best Kai

/usr/obj/usr/src/make.core

Program terminated with signal 11, Segmentation fault.
#0  0x0804da01 in Cmd_Exec (
   cmd=0x2812df00 "/usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin make   __MAKE_CONF=/etc/make.conf  -f /dev/null -V MAKEOBJDIRPREFIX dummy", 
   error=0xbf7fdb18) at /usr/src/usr.bin/make/job.c:2713
2713            if ((ps.child_pid = vfork()) == -1) {
(gdb) bt
#0  0x0804da01 in Cmd_Exec (
   cmd=0x2812df00 "/usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin make   __MAKE_CONF=/etc/make.conf  -f /dev/null -V MAKEOBJDIRPREFIX dummy", 
   error=0xbf7fdb18) at /usr/src/usr.bin/make/job.c:2713
#1  0x080544ed in Parse_DoVar (line=0x28128b00 "_MAKEOBJDIRPREFIX", 
   ctxt=0x2810e200) at /usr/src/usr.bin/make/parse.c:1520
#2  0x08055a1a in Parse_File (name=0xbf7fdbf8 "/usr/src/Makefile", 
   stream=0x80a4960) at /usr/src/usr.bin/make/parse.c:2457
#3  0x08051e68 in ReadMakefile (p=Variable "p" is not available.
) at /usr/src/usr.bin/make/main.c:323
#4  0x08051f24 in TryReadMakefile (p=0x8094744 "Makefile")
   at /usr/src/usr.bin/make/main.c:342
#5  0x080527c3 in main (argc=1, argv=0xbf7feddc)
   at /usr/src/usr.bin/make/main.c:1209
(gdb)



/usr/src/sbin/atacontrol/sh.core

Core was generated by `sh'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libedit.so.6...done.
Loaded symbols for /lib/libedit.so.6
Reading symbols from /lib/libncurses.so.7...done.
Loaded symbols for /lib/libncurses.so.7
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x080555e6 in forkshell (jp=0x2830c0c0, n=0x28304d94, mode=0) at /usr/src/bin/sh/jobs.c:746
746             pid = fork();
(gdb) bt
#0  0x080555e6 in forkshell (jp=0x2830c0c0, n=0x28304d94, mode=0) at /usr/src/bin/sh/jobs.c:746
#1  0x0804d759 in evalcommand (cmd=0x28304d94, flags=0, backcmd=0x0) at /usr/src/bin/sh/eval.c:747
#2  0x0804e725 in evaltree (n=0x28304d94, flags=0) at /usr/src/bin/sh/eval.c:267
#3  0x0804e4ff in evaltree (n=0x28304da4, flags=0) at /usr/src/bin/sh/eval.c:238
#4  0x0804e86c in evaltree (n=0x28304210, flags=0) at /usr/src/bin/sh/eval.c:341
#5  0x0804eba7 in evalstring (
    s=0xbf7fea84 "for entry in adjkerntz  atacontrol  atm  badsect  bsdlabel  camcontrol  ccdconfig  clri  comcontrol  conscontrol  ddb  devd  devfs  dhclient  dmesg  dump  dumpfs  dumpon  fdisk    ffsinfo  fsck   fsck_"...) at /usr/src/bin/sh/eval.c:169
#6  0x08056d98 in main (argc=3, argv=0xbf7fe9a8) at /usr/src/bin/sh/main.c:181




/usr/obj/usr/src/libexec/ftpd/make.core

Program terminated with signal 11, Segmentation fault.
#0  0x080898bf in memset ()
(gdb) bt
#0  0x080898bf in memset ()
#1  0x0000000c in ?? ()
#2  0x0806f8b2 in arena_malloc ()
#3  0x0807106b in malloc ()
#4  0x0805a2d1 in emalloc (len=256) at /usr/src/usr.bin/make/util.c:234
#5  0x08049d3f in Buf_Init (size=0) at /usr/src/usr.bin/make/buf.c:184
#6  0x0805a63a in VarCreate (name=0x2810d118 ".CURDIR", value=0xbf7fe0b6 "/usr/src/libexec/ftpd", flags=0) at /usr/src/usr.bin/make/var.c:214
#7  0x0805a68d in VarAdd (name=0x2810d118 ".CURDIR", val=0xbf7fe0b6 "/usr/src/libexec/ftpd", ctxt=0x28112180) at /usr/src/usr.bin/make/var.c:954
#8  0x0805d2fc in Var_Set (name=0x809409d ".CURDIR", val=0xbf7fe0b6 "/usr/src/libexec/ftpd", ctxt=0x28112180) at /usr/src/usr.bin/make/var.c:1009
#9  0x0805d321 in Var_SetGlobal (name=0x809409d ".CURDIR", value=0xbf7fe0b6 "/usr/src/libexec/ftpd") at /usr/src/usr.bin/make/var.c:1035
#10 0x0805243f in main (argc=3, argv=0xbf7fed74) at /usr/src/usr.bin/make/main.c:1115



/usr/obj/usr/src/usr.bin/telnet/as.core

Program terminated with signal 11, Segmentation fault.
#0  0x080480d6 in _start ()
(gdb) bt
#0  0x080480d6 in _start ()
#1  0x00000003 in ?? ()
From kmacy at freebsd.org  Thu Jan 29 15:18:09 2009
From: kmacy at freebsd.org (Kip Macy)
Date: Thu Jan 29 15:18:15 2009
Subject: Instable 32bit domU on 64bit dom0 (w/Xen 3.3.1)
In-Reply-To: <11276352.23661233243265678.JavaMail.root@zim.freshx.de>
References: <11276352.23661233243265678.JavaMail.root@zim.freshx.de>
Message-ID: <3c1674c90901291447r6454794et2449eb71d46df209@mail.gmail.com>

Working on it - sorry for the delay.

-Kip

On Thu, Jan 29, 2009 at 7:34 AM, Kai Mosebach <xen@komadev.de> wrote:
> Hi,
>
> i recently got my first FreeBSD 8 domU working and i am quite happy to see that there is eventually progress on the important Xen topic for FreeBSD.
> Since this domU as a svn -head checkout from 23.01.09 still segfaults here and there i startet to rebuild the whole world with debugging symbols in the hope that the backtraces give more info's on where to find bugs.
>
> Here are the first results from several core files which hang around in the system after a world build and i hope the developers here can make more sense out of it than me.
>
> If you need further dumps/traces or have some advises how to go on from here, please let me know!
>
> Best Kai
>
> /usr/obj/usr/src/make.core
>
> Program terminated with signal 11, Segmentation fault.
> #0  0x0804da01 in Cmd_Exec (
>   cmd=0x2812df00 "/usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin make   __MAKE_CONF=/etc/make.conf  -f /dev/null -V MAKEOBJDIRPREFIX dummy",
>   error=0xbf7fdb18) at /usr/src/usr.bin/make/job.c:2713
> 2713            if ((ps.child_pid = vfork()) == -1) {
> (gdb) bt
> #0  0x0804da01 in Cmd_Exec (
>   cmd=0x2812df00 "/usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin make   __MAKE_CONF=/etc/make.conf  -f /dev/null -V MAKEOBJDIRPREFIX dummy",
>   error=0xbf7fdb18) at /usr/src/usr.bin/make/job.c:2713
> #1  0x080544ed in Parse_DoVar (line=0x28128b00 "_MAKEOBJDIRPREFIX",
>   ctxt=0x2810e200) at /usr/src/usr.bin/make/parse.c:1520
> #2  0x08055a1a in Parse_File (name=0xbf7fdbf8 "/usr/src/Makefile",
>   stream=0x80a4960) at /usr/src/usr.bin/make/parse.c:2457
> #3  0x08051e68 in ReadMakefile (p=Variable "p" is not available.
> ) at /usr/src/usr.bin/make/main.c:323
> #4  0x08051f24 in TryReadMakefile (p=0x8094744 "Makefile")
>   at /usr/src/usr.bin/make/main.c:342
> #5  0x080527c3 in main (argc=1, argv=0xbf7feddc)
>   at /usr/src/usr.bin/make/main.c:1209
> (gdb)
>
>
>
> /usr/src/sbin/atacontrol/sh.core
>
> Core was generated by `sh'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /lib/libedit.so.6...done.
> Loaded symbols for /lib/libedit.so.6
> Reading symbols from /lib/libncurses.so.7...done.
> Loaded symbols for /lib/libncurses.so.7
> Reading symbols from /lib/libc.so.7...done.
> Loaded symbols for /lib/libc.so.7
> Reading symbols from /libexec/ld-elf.so.1...done.
> Loaded symbols for /libexec/ld-elf.so.1
> #0  0x080555e6 in forkshell (jp=0x2830c0c0, n=0x28304d94, mode=0) at /usr/src/bin/sh/jobs.c:746
> 746             pid = fork();
> (gdb) bt
> #0  0x080555e6 in forkshell (jp=0x2830c0c0, n=0x28304d94, mode=0) at /usr/src/bin/sh/jobs.c:746
> #1  0x0804d759 in evalcommand (cmd=0x28304d94, flags=0, backcmd=0x0) at /usr/src/bin/sh/eval.c:747
> #2  0x0804e725 in evaltree (n=0x28304d94, flags=0) at /usr/src/bin/sh/eval.c:267
> #3  0x0804e4ff in evaltree (n=0x28304da4, flags=0) at /usr/src/bin/sh/eval.c:238
> #4  0x0804e86c in evaltree (n=0x28304210, flags=0) at /usr/src/bin/sh/eval.c:341
> #5  0x0804eba7 in evalstring (
>    s=0xbf7fea84 "for entry in adjkerntz  atacontrol  atm  badsect  bsdlabel  camcontrol  ccdconfig  clri  comcontrol  conscontrol  ddb  devd  devfs  dhclient  dmesg  dump  dumpfs  dumpon  fdisk    ffsinfo  fsck   fsck_"...) at /usr/src/bin/sh/eval.c:169
> #6  0x08056d98 in main (argc=3, argv=0xbf7fe9a8) at /usr/src/bin/sh/main.c:181
>
>
>
>
> /usr/obj/usr/src/libexec/ftpd/make.core
>
> Program terminated with signal 11, Segmentation fault.
> #0  0x080898bf in memset ()
> (gdb) bt
> #0  0x080898bf in memset ()
> #1  0x0000000c in ?? ()
> #2  0x0806f8b2 in arena_malloc ()
> #3  0x0807106b in malloc ()
> #4  0x0805a2d1 in emalloc (len=256) at /usr/src/usr.bin/make/util.c:234
> #5  0x08049d3f in Buf_Init (size=0) at /usr/src/usr.bin/make/buf.c:184
> #6  0x0805a63a in VarCreate (name=0x2810d118 ".CURDIR", value=0xbf7fe0b6 "/usr/src/libexec/ftpd", flags=0) at /usr/src/usr.bin/make/var.c:214
> #7  0x0805a68d in VarAdd (name=0x2810d118 ".CURDIR", val=0xbf7fe0b6 "/usr/src/libexec/ftpd", ctxt=0x28112180) at /usr/src/usr.bin/make/var.c:954
> #8  0x0805d2fc in Var_Set (name=0x809409d ".CURDIR", val=0xbf7fe0b6 "/usr/src/libexec/ftpd", ctxt=0x28112180) at /usr/src/usr.bin/make/var.c:1009
> #9  0x0805d321 in Var_SetGlobal (name=0x809409d ".CURDIR", value=0xbf7fe0b6 "/usr/src/libexec/ftpd") at /usr/src/usr.bin/make/var.c:1035
> #10 0x0805243f in main (argc=3, argv=0xbf7fed74) at /usr/src/usr.bin/make/main.c:1115
>
>
>
> /usr/obj/usr/src/usr.bin/telnet/as.core
>
> Program terminated with signal 11, Segmentation fault.
> #0  0x080480d6 in _start ()
> (gdb) bt
> #0  0x080480d6 in _start ()
> #1  0x00000003 in ?? ()
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"
>
From js at alien8.de  Thu Jan 29 18:53:17 2009
From: js at alien8.de (Julian Stecklina)
Date: Thu Jan 29 18:53:24 2009
Subject: Time goes backwards
Message-ID: <877i4d1p46.fsf@tabernacle.localnet>

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)
From js at alien8.de  Thu Jan 29 19:05:01 2009
From: js at alien8.de (Julian Stecklina)
Date: Thu Jan 29 19:05:33 2009
Subject: kern.hz = 10
Message-ID: <87ocxp1tym.fsf@tabernacle.localnet>

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
    julian@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 1000000000 Hz quality 0
CPU: Intel Pentium III Xeon (701.59-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6a1  Stepping = 1
  Features=0x383fbff<FPU,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)

From mister.olli at googlemail.com  Thu Jan 29 19:14:44 2009
From: mister.olli at googlemail.com (Mister Olli)
Date: Thu Jan 29 19:14:50 2009
Subject: kern.hz = 10
In-Reply-To: <87ocxp1tym.fsf@tabernacle.localnet>
References: <87ocxp1tym.fsf@tabernacle.localnet>
Message-ID: <1233285247.24925.4.camel@phoenix.blechhirn.net>

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?

--
Mr. Olli



Am Freitag, den 30.01.2009, 02:08 +0100 schrieb Julian Stecklina:
> 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
>     julian@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 1000000000 Hz quality 0
> CPU: Intel Pentium III Xeon (701.59-MHz 686-class CPU)
>   Origin = "GenuineIntel"  Id = 0x6a1  Stepping = 1
>   Features=0x383fbff<FPU,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

From mister.olli at googlemail.com  Thu Jan 29 19:21:16 2009
From: mister.olli at googlemail.com (Mister Olli)
Date: Thu Jan 29 19:21:22 2009
Subject: Time goes backwards
In-Reply-To: <877i4d1p46.fsf@tabernacle.localnet>
References: <877i4d1p46.fsf@tabernacle.localnet>
Message-ID: <1233285639.24925.12.camel@phoenix.blechhirn.net>

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'
- 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?

--
Mr. Olli



Am Freitag, den 30.01.2009, 03:53 +0100 schrieb Julian Stecklina:
> 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,

From js at alien8.de  Thu Jan 29 19:23:13 2009
From: js at alien8.de (Julian Stecklina)
Date: Thu Jan 29 19:23:22 2009
Subject: kern.hz = 10
References: <87ocxp1tym.fsf@tabernacle.localnet>
	<1233285247.24925.4.camel@phoenix.blechhirn.net>
Message-ID: <871vul1nqk.fsf@tabernacle.localnet>

Mister Olli <mister.olli@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)

From kmacy at freebsd.org  Thu Jan 29 19:23:43 2009
From: kmacy at freebsd.org (Kip Macy)
Date: Thu Jan 29 19:23:49 2009
Subject: kern.hz = 10
In-Reply-To: <87ocxp1tym.fsf@tabernacle.localnet>
References: <87ocxp1tym.fsf@tabernacle.localnet>
Message-ID: <3c1674c90901291923r22cf9e90ieadd5043ad7f30be@mail.gmail.com>

On Thu, Jan 29, 2009 at 5:08 PM, Julian Stecklina <js@alien8.de> wrote:
> 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
>
It probably took a few ticks for ARP resolution to occur.

-Kip

> dmesg:
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 8.0-CURRENT #0 r187877: Thu Jan 29 16:32:39 CET 2009
>    julian@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 1000000000 Hz quality 0
> CPU: Intel Pentium III Xeon (701.59-MHz 686-class CPU)
>  Origin = "GenuineIntel"  Id = 0x6a1  Stepping = 1
>  Features=0x383fbff<FPU,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-unsubscribe@freebsd.org"
>
From js at alien8.de  Thu Jan 29 20:01:36 2009
From: js at alien8.de (Julian Stecklina)
Date: Thu Jan 29 20:01:42 2009
Subject: Time goes backwards
In-Reply-To: <1233285639.24925.12.camel@phoenix.blechhirn.net> (Mister Olli's
	message of "Fri, 30 Jan 2009 04:20:39 +0100")
References: <877i4d1p46.fsf@tabernacle.localnet>
	<1233285639.24925.12.camel@phoenix.blechhirn.net>
Message-ID: <87d4e530iy.fsf@tabernacle.localnet>

Mister Olli <mister.olli@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)
From kmacy at freebsd.org  Thu Jan 29 20:15:39 2009
From: kmacy at freebsd.org (Kip Macy)
Date: Thu Jan 29 20:15:46 2009
Subject: Time goes backwards
In-Reply-To: <87d4e530iy.fsf@tabernacle.localnet>
References: <877i4d1p46.fsf@tabernacle.localnet>
	<1233285639.24925.12.camel@phoenix.blechhirn.net>
	<87d4e530iy.fsf@tabernacle.localnet>
Message-ID: <3c1674c90901292015y103fbd5dv2cf87af39fe18b1d@mail.gmail.com>

I have some fundamental stability bugs I'm trying to fix right now.
I'll fix that once these are addressed.

-Kip




On Thu, Jan 29, 2009 at 8:01 PM, Julian Stecklina <js@alien8.de> wrote:
> Mister Olli <mister.olli@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-unsubscribe@freebsd.org"
>
From kai at freshx.de  Fri Jan 30 02:03:17 2009
From: kai at freshx.de (Kai Mosebach)
Date: Fri Jan 30 02:03:52 2009
Subject: Time goes backwards
In-Reply-To: <1233285639.24925.12.camel@phoenix.blechhirn.net>
Message-ID: <C5A88624.3841%kai@freshx.de>

Hi,

Since I changed the sysctl wallclock, I don't have any time issues anymore.
make was mourning a lot about timestamps before, but this also has gone
now...

Best Kai

On 1/30/09 4:20 AM, "Mister Olli" <mister.olli@googlemail.com> wrote:

> 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'
> - 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?
> 
> --
> Mr. Olli
> 
> 
> 
> Am Freitag, den 30.01.2009, 03:53 +0100 schrieb Julian Stecklina:
>> 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,
> 
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"


From ivoras at freebsd.org  Fri Jan 30 02:35:42 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Fri Jan 30 02:35:48 2009
Subject: kern.hz = 10
In-Reply-To: <871vul1nqk.fsf@tabernacle.localnet>
References: <87ocxp1tym.fsf@tabernacle.localnet>
	<1233285247.24925.4.camel@phoenix.blechhirn.net>
	<871vul1nqk.fsf@tabernacle.localnet>
Message-ID: <9bbcef730901300214s19c91071vf9241cd7cd40ba57@mail.gmail.com>

2009/1/30 Julian Stecklina <js@alien8.de>:
> Mister Olli <mister.olli@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.

Due to bad performance of high HZ in VMs, in 8-CURRENT it is
explicitly reduced to 10 if the kernel is running under any kind of
virtual environment. This is a somewhat theoretical number and
probably needs tuning.

If you're interested in trying it out, you can increase it by adding
"kern.hz=xxx" to /boot/loader.conf and seeing what is the actual
performance influence of high HZ under Xen.
From mister.olli at googlemail.com  Fri Jan 30 04:49:29 2009
From: mister.olli at googlemail.com (Mister Olli)
Date: Fri Jan 30 04:49:35 2009
Subject: Time goes backwards
In-Reply-To: <87d4e530iy.fsf@tabernacle.localnet>
References: <877i4d1p46.fsf@tabernacle.localnet>
	<1233285639.24925.12.camel@phoenix.blechhirn.net>
	<87d4e530iy.fsf@tabernacle.localnet>
Message-ID: <1233319731.24925.14.camel@phoenix.blechhirn.net>

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.

I just copied over your times to show the pattern it moves in ;-))
The time to which it jumps back is usually around the time I created the
domU, and time ticks only 15min forward at max, until a jump back in
time happens.

--
Mr. Olli

From mister.olli at googlemail.com  Fri Jan 30 04:53:26 2009
From: mister.olli at googlemail.com (Mister Olli)
Date: Fri Jan 30 04:53:33 2009
Subject: kern.hz = 10
In-Reply-To: <9bbcef730901300214s19c91071vf9241cd7cd40ba57@mail.gmail.com>
References: <87ocxp1tym.fsf@tabernacle.localnet>
	<1233285247.24925.4.camel@phoenix.blechhirn.net>
	<871vul1nqk.fsf@tabernacle.localnet>
	<9bbcef730901300214s19c91071vf9241cd7cd40ba57@mail.gmail.com>
Message-ID: <1233319967.24925.19.camel@phoenix.blechhirn.net>

Hi,

> Due to bad performance of high HZ in VMs, in 8-CURRENT it is
> explicitly reduced to 10 if the kernel is running under any kind of
> virtual environment. This is a somewhat theoretical number and
> probably needs tuning.

Oh I didn't knew that. *SORRY*


> If you're interested in trying it out, you can increase it by adding
> "kern.hz=xxx" to /boot/loader.conf and seeing what is the actual
> performance influence of high HZ under Xen.

I've run on 100HZ quite some time now and did have the impression that
8-CURRENT is slow. It's even faster on copy processes as 7 under VMware
on a host machine which is 3 years younger...

..
Mr. Olli

From ivoras at freebsd.org  Fri Jan 30 06:13:41 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Fri Jan 30 06:13:47 2009
Subject: kern.hz = 10
In-Reply-To: <1233319967.24925.19.camel@phoenix.blechhirn.net>
References: <87ocxp1tym.fsf@tabernacle.localnet>
	<1233285247.24925.4.camel@phoenix.blechhirn.net>
	<871vul1nqk.fsf@tabernacle.localnet>
	<9bbcef730901300214s19c91071vf9241cd7cd40ba57@mail.gmail.com>
	<1233319967.24925.19.camel@phoenix.blechhirn.net>
Message-ID: <9bbcef730901300613h1d4a3565xd6a0cbea4f70af00@mail.gmail.com>

2009/1/30 Mister Olli <mister.olli@googlemail.com>:

> I've run on 100HZ quite some time now and did have the impression that
> 8-CURRENT is slow. It's even faster on copy processes as 7 under VMware
> on a host machine which is 3 years younger...

This might or (probably) might not be due to HZ.

If you're interested in testing, here's what you should do:

1. compile a 8-CURRENT kernel without debugging (WITNESS, INVARIANTS &
their support kernel options)
2. compile a 8-CURRENT world without malloc debugging (see
http://wiki.freebsd.org/DefaultDebuggingKnobs)
3. run some repeatable tests - I'd suggest some file system benchmarks
on a RAM (md) drive, see http://man.freebsd.org/md like bonnie++ and
blogbench and some network tests with iperf
4. change HZ in loader.conf and test again, in exactly the same way as
before (in 3.)

Benchmarks that are not repeatable are useless. Repeatable means by
you (so e.g. the host machine must be in the same state - no
additional programs running, etc., see
http://wiki.freebsd.org/BenchmarkAdvice) and by others when following
your steps exactly.
From js at alien8.de  Fri Jan 30 07:31:51 2009
From: js at alien8.de (Julian Stecklina)
Date: Fri Jan 30 07:32:25 2009
Subject: kern.hz = 10
References: <87ocxp1tym.fsf@tabernacle.localnet>
	<1233285247.24925.4.camel@phoenix.blechhirn.net>
	<871vul1nqk.fsf@tabernacle.localnet>
	<9bbcef730901300214s19c91071vf9241cd7cd40ba57@mail.gmail.com>
Message-ID: <8763jwkdym.fsf@tabernacle.localnet>

Ivan Voras <ivoras@freebsd.org> writes:

> 2009/1/30 Julian Stecklina <js@alien8.de>:
>> Mister Olli <mister.olli@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.
>
> Due to bad performance of high HZ in VMs, in 8-CURRENT it is
> explicitly reduced to 10 if the kernel is running under any kind of
> virtual environment. This is a somewhat theoretical number and
> probably needs tuning.

Probably.

> If you're interested in trying it out, you can increase it by adding
> "kern.hz=xxx" to /boot/loader.conf and seeing what is the actual
> performance influence of high HZ under Xen.

I am going to do that once the timing stuff is figured out. No point in
making benchmarks when the clock is confused. :)

I cannot repeat it enough: Still great 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)

From tomislav.novak at gmail.com  Sat Jan 31 09:28:36 2009
From: tomislav.novak at gmail.com (Tomislav Novak)
Date: Sat Jan 31 09:28:43 2009
Subject: Install FreeBSD-7.1 (domU) to a filesystem image
Message-ID: <878wor1ji7.fsf@gmail.com>

Hello!

I have set up Slackware Linux 12.0 as dom0 (Xen 3.3.1, Linux 2.6.18.8, 
built from source) and I'm playing with FreeBSD as a domU.

It's currently, due to some circumstances, not possible for me to
install FreeBSD to a separate partition(s), so I'm using a file-backed
VBD. Kernel and filesystem images are those from 

    http://www.fsmware.com/xenofreebsd/7.0/download/

and they work perfectly. However, the filesystem image contains only the
basic stuff, and I need a few more packages (e.g. newer gcc version,
X11 etc.). I don't have access to any other FreeBSD system so I can't
copy necessary files, build 8.0-CURRENT etc. Is it possible to install
FreeBSD from an installation media directly to the filesystem image on
disk?

Thanks in advance,
Tomislav
From ivoras at freebsd.org  Sat Jan 31 10:08:54 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Sat Jan 31 10:09:01 2009
Subject: Install FreeBSD-7.1 (domU) to a filesystem image
In-Reply-To: <878wor1ji7.fsf@gmail.com>
References: <878wor1ji7.fsf@gmail.com>
Message-ID: <9bbcef730901311008y2e724441md934377762b1c475@mail.gmail.com>

2009/1/31 Tomislav Novak <tomislav.novak@gmail.com>:
> Hello!
>
> I have set up Slackware Linux 12.0 as dom0 (Xen 3.3.1, Linux 2.6.18.8,
> built from source) and I'm playing with FreeBSD as a domU.
>
> It's currently, due to some circumstances, not possible for me to
> install FreeBSD to a separate partition(s), so I'm using a file-backed
> VBD. Kernel and filesystem images are those from
>
>    http://www.fsmware.com/xenofreebsd/7.0/download/
>
> and they work perfectly. However, the filesystem image contains only the
> basic stuff, and I need a few more packages (e.g. newer gcc version,
> X11 etc.). I don't have access to any other FreeBSD system so I can't
> copy necessary files, build 8.0-CURRENT etc. Is it possible to install
> FreeBSD from an installation media directly to the filesystem image on
> disk?

If the image you downloaded contains the whole FreeBSD "base" system,
simply install whatever you need like on a normal system. See
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ for
details.

(Note that, for example, the system compiler - gcc - is a part of the
base system and you cannot upgrade it as you would on Linux).
From js at alien8.de  Sat Jan 31 11:23:00 2009
From: js at alien8.de (Julian Stecklina)
Date: Sat Jan 31 11:23:08 2009
Subject: Install FreeBSD-7.1 (domU) to a filesystem image
References: <878wor1ji7.fsf@gmail.com>
Message-ID: <87bptns2kd.fsf@tabernacle.localnet>

Tomislav Novak <tomislav.novak@gmail.com> writes:

> Hello!
>
> I have set up Slackware Linux 12.0 as dom0 (Xen 3.3.1, Linux 2.6.18.8, 
> built from source) and I'm playing with FreeBSD as a domU.
>
> It's currently, due to some circumstances, not possible for me to
> install FreeBSD to a separate partition(s), so I'm using a file-backed
> VBD. Kernel and filesystem images are those from 
>
>     http://www.fsmware.com/xenofreebsd/7.0/download/
>
> and they work perfectly. However, the filesystem image contains only the
> basic stuff, and I need a few more packages (e.g. newer gcc version,
> X11 etc.). I don't have access to any other FreeBSD system so I can't
> copy necessary files, build 8.0-CURRENT etc. Is it possible to install
> FreeBSD from an installation media directly to the filesystem image on
> disk?

You could mount another file-backed disk and build CURRENT on that from
the provided image.

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)

From tomislav.novak at gmail.com  Sat Jan 31 12:31:37 2009
From: tomislav.novak at gmail.com (Tomislav Novak)
Date: Sat Jan 31 12:31:43 2009
Subject: Install FreeBSD-7.1 (domU) to a filesystem image
In-Reply-To: <9bbcef730901311008y2e724441md934377762b1c475@mail.gmail.com>
	(Ivan Voras's message of "Sat, 31 Jan 2009 19:08:52 +0100")
References: <878wor1ji7.fsf@gmail.com>
	<9bbcef730901311008y2e724441md934377762b1c475@mail.gmail.com>
Message-ID: <87bptntdxb.fsf@gmail.com>

Ivan Voras <ivoras@freebsd.org> writes:

> 2009/1/31 Tomislav Novak <tomislav.novak@gmail.com>:
>> Hello!
>>
>> I have set up Slackware Linux 12.0 as dom0 (Xen 3.3.1, Linux 2.6.18.8,
>> built from source) and I'm playing with FreeBSD as a domU.
>>
>> It's currently, due to some circumstances, not possible for me to
>> install FreeBSD to a separate partition(s), so I'm using a file-backed
>> VBD. Kernel and filesystem images are those from
>>
>>    http://www.fsmware.com/xenofreebsd/7.0/download/
>>
>> and they work perfectly. However, the filesystem image contains only the
>> basic stuff, and I need a few more packages (e.g. newer gcc version,
>> X11 etc.). I don't have access to any other FreeBSD system so I can't
>> copy necessary files, build 8.0-CURRENT etc. Is it possible to install
>> FreeBSD from an installation media directly to the filesystem image on
>> disk?
>
> If the image you downloaded contains the whole FreeBSD "base" system,
> simply install whatever you need like on a normal system. See
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ for
> details.

Thanks. I'll try mounting an installation CD in domU and installing
packages from there.

What I tried so far is booting livefs, running mdconfig and trying to
install to /dev/mdX. Didn't work like I expected, though. :)

-- 
T.
From mister.olli at googlemail.com  Sat Jan 31 15:24:19 2009
From: mister.olli at googlemail.com (Mister Olli)
Date: Sat Jan 31 15:24:26 2009
Subject: Time goes backwards
In-Reply-To: <3c1674c90901292015y103fbd5dv2cf87af39fe18b1d@mail.gmail.com>
References: <877i4d1p46.fsf@tabernacle.localnet>
	<1233285639.24925.12.camel@phoenix.blechhirn.net>
	<87d4e530iy.fsf@tabernacle.localnet>
	<3c1674c90901292015y103fbd5dv2cf87af39fe18b1d@mail.gmail.com>
Message-ID: <1233444220.6549.19.camel@phoenix.blechhirn.net>

Hi,

is there some kind of notification when you commited changes to the XEN
code in HEAD?

--
Mr. Olli


Am Donnerstag, den 29.01.2009, 20:15 -0800 schrieb Kip Macy:
> I have some fundamental stability bugs I'm trying to fix right now.
> I'll fix that once these are addressed.
> 
> -Kip
> 
> 
> 
> 
> On Thu, Jan 29, 2009 at 8:01 PM, Julian Stecklina <js@alien8.de> wrote:
> > Mister Olli <mister.olli@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-unsubscribe@freebsd.org"
> >

From kmacy at freebsd.org  Sat Jan 31 16:00:53 2009
From: kmacy at freebsd.org (Kip Macy)
Date: Sat Jan 31 16:01:00 2009
Subject: Time goes backwards
In-Reply-To: <1233444220.6549.19.camel@phoenix.blechhirn.net>
References: <877i4d1p46.fsf@tabernacle.localnet>
	<1233285639.24925.12.camel@phoenix.blechhirn.net>
	<87d4e530iy.fsf@tabernacle.localnet>
	<3c1674c90901292015y103fbd5dv2cf87af39fe18b1d@mail.gmail.com>
	<1233444220.6549.19.camel@phoenix.blechhirn.net>
Message-ID: <3c1674c90901311600t63183ee1x79e8d0a9e2b71b3f@mail.gmail.com>

There is an svn mailing list that sends out mail on all updates.

-Kip



On Sat, Jan 31, 2009 at 3:23 PM, Mister Olli <mister.olli@googlemail.com> wrote:
> Hi,
>
> is there some kind of notification when you commited changes to the XEN
> code in HEAD?
>
> --
> Mr. Olli
>
>
> Am Donnerstag, den 29.01.2009, 20:15 -0800 schrieb Kip Macy:
>> I have some fundamental stability bugs I'm trying to fix right now.
>> I'll fix that once these are addressed.
>>
>> -Kip
>>
>>
>>
>>
>> On Thu, Jan 29, 2009 at 8:01 PM, Julian Stecklina <js@alien8.de> wrote:
>> > Mister Olli <mister.olli@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-unsubscribe@freebsd.org"
>> >
>
>