From owner-freebsd-xen@FreeBSD.ORG Mon Jan 12 22:23:18 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCE5E1065673 for ; Mon, 12 Jan 2009 22:23:18 +0000 (UTC) (envelope-from deb@es.net) Received: from postal1.es.net (postal2.es.net [198.128.3.206]) by mx1.freebsd.org (Postfix) with ESMTP id C7BD58FC18 for ; Mon, 12 Jan 2009 22:23:18 +0000 (UTC) (envelope-from deb@es.net) Received: from [127.0.0.1] (rtfm.es.net [198.128.1.53]) by postal2.es.net (Postal Node 2) with ASMTP id TXY15544 for ; Mon, 12 Jan 2009 14:12:44 -0800 Message-ID: <496BC05B.2030606@es.net> Date: Mon, 12 Jan 2009 14:12:43 -0800 From: Deb Heller-Evans User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Sender-IP: 198.128.1.53 X-Sender-Domain: es.net X-Recipent: ; X-Sender: X-To_Name: X-To_Domain: freebsd.org X-To: freebsd-xen@freebsd.org X-To_Email: freebsd-xen@freebsd.org X-To_Alias: freebsd-xen Subject: 64-bit Centos5 xen kernel and creating a FreeBSD domU X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 22:23:19 -0000 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 owner-freebsd-xen@FreeBSD.ORG Tue Jan 13 19:04:05 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C195D1065760 for ; Tue, 13 Jan 2009 19:04:05 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 07AAF8FC14 for ; Tue, 13 Jan 2009 19:04:04 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: by bwz13 with SMTP id 13so567168bwz.19 for ; Tue, 13 Jan 2009 11:04:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to :content-type:date:message-id:mime-version:x-mailer; bh=agXKFqSqueSBYkA5hLbgkIjnXXojcAEIl8N5ioYhPYU=; b=A7d/TV+McLXcZMYosDvrVhb0G6fE7pTIOOaQzJU+SmZwiOI4XupeYNtI+HSdXlbD37 CBR7tioXhh8qovTtSnKuZKR1GJeCbzfo53zlBhHsxRK+Ky0AoP8UJbQt0PtNlXPCwVEI qFZg5GWlVDjxHzrPaXKrPpdtBsGtuWaqY4dME= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:reply-to:to:content-type:date:message-id:mime-version :x-mailer; b=cYYngMYcTVq0XdCCZ4UJk/6j3AJilu3bGGhA0qBOx45hVgxJARbG0LyUTa5WB0gAUX 18l12iE0pbXXqnPPitzSx6yWMJUBHwn+d6DSlNoj7AR0s++HerKdbLVKiWFiFmAK1bmZ os9oyXJtjI9Jvi0EF+mKLZyCCecI43tUbDj60= Received: by 10.223.113.3 with SMTP id y3mr22998933fap.71.1231873443721; Tue, 13 Jan 2009 11:04:03 -0800 (PST) Received: from ?10.30.1.100? (vpn-or.studi-planet.com [78.47.172.52]) by mx.google.com with ESMTPS id c28sm22567553fka.34.2009.01.13.11.04.01 (version=SSLv3 cipher=RC4-MD5); Tue, 13 Jan 2009 11:04:02 -0800 (PST) From: Mister Olli To: freebsd-xen@freebsd.org, freebsd-questions@freebsd.org Content-Type: multipart/mixed; boundary="=-/F0E39/XpYOEhYcp/1Gw" Date: Tue, 13 Jan 2009 20:03:56 +0100 Message-Id: <1231873436.24899.85.camel@phoenix.blechhirn.net> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 Cc: Subject: Problems with FreeBSD 8-CURRENT as Xen domU X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mister.olli@googlemail.com List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 19:04:06 -0000 --=-/F0E39/XpYOEhYcp/1Gw Content-Type: text/plain Content-Transfer-Encoding: 7bit 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:. 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 AMD Features=0xc0480800 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: on motherboard xc0: on motherboard Timecounters tick every 10.000 msec xbd0: 8192MB at device/vbd/768 on xenbus0 xbd0: attaching as ad0 GEOM: ad0s1: geometry does not match label (15h,63s != 255h,63s). xn0: 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 --=-/F0E39/XpYOEhYcp/1Gw Content-Disposition: attachment; filename=freebsd8_XEN Content-Type: text/plain; name=freebsd8_XEN; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit # # 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 --=-/F0E39/XpYOEhYcp/1Gw-- From owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 15:07:55 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8318A106572D for ; Wed, 14 Jan 2009 15:07:55 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 35E838FC17 for ; Wed, 14 Jan 2009 15:07:55 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by an-out-0708.google.com with SMTP id c2so253468anc.13 for ; Wed, 14 Jan 2009 07:07:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=txLn6vc77eiOIHc0GA/vK9Ry+bbLKZWa8Fm+1rsXeRU=; b=km448kp2wvlI/xVABZbaJSMVSuQMQ9D0QayFGKSPmORHmm6hjUgIU5QiHDorAuNiKJ dFI8NqY5M5z34VGXsdXjNeFuLLksgXgkQ/k1gTJA9AeMqa+0mbVy5AQbcam3Y06gzMbU Zsr7Suomag1Nwm7Ha8aADBiAcOMDFEHICz42g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=VYm9okx4pxqZ+9SWgHpCTgxwxazRNpazQURWocFniHjAHr3zppYm4Qv/zRSoFKclYD HDnbzdbX2jntlEFiFTpNZp05b5R7nNm2r6Za9pSLvUPPmxzb2LAa5I42k6OOC7UhpKs9 Yk2cs9RZmIjcDG3lJ07+c4lEGucZzCwjDK+qc= Received: by 10.100.105.13 with SMTP id d13mr137191anc.102.1231945674312; Wed, 14 Jan 2009 07:07:54 -0800 (PST) Received: from ?10.0.3.231? ([70.111.173.38]) by mx.google.com with ESMTPS id c23sm48259017ana.55.2009.01.14.07.07.53 (version=SSLv3 cipher=RC4-MD5); Wed, 14 Jan 2009 07:07:53 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: Deb Heller-Evans In-Reply-To: <496BC05B.2030606@es.net> References: <496BC05B.2030606@es.net> Content-Type: text/plain; charset=utf-8 Date: Wed, 14 Jan 2009 10:07:26 -0500 Message-Id: <1231945646.1172.8.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-xen@freebsd.org Subject: Re: 64-bit Centos5 xen kernel and creating a FreeBSD domU X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 15:07:55 -0000 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 owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 17:48:14 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 350E41065673 for ; Wed, 14 Jan 2009 17:48:14 +0000 (UTC) (envelope-from Ron.Carter@cartersweb.net) Received: from cartersweb.net (nc-208-17-66-204.sta.embarqhsd.net [208.17.66.204]) by mx1.freebsd.org (Postfix) with ESMTP id CD6E58FC1B for ; Wed, 14 Jan 2009 17:48:13 +0000 (UTC) (envelope-from Ron.Carter@cartersweb.net) Date: Wed, 14 Jan 2009 12:48:11 -0500 Message-ID: In-Reply-To: <1231945646.1172.8.camel@RabbitsDen> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 64-bit Centos5 xen kernel and creating a FreeBSD domU thread-index: Acl2WpElpLow2jXtRdaIWWpkUb57kQAFUeYg Content-class: urn:content-classes:message References: <496BC05B.2030606@es.net> <1231945646.1172.8.camel@RabbitsDen> From: "Ron Carter" X-MimeOLE: Produced By Microsoft Exchange V6.5 To: "Deb Heller-Evans" Cc: freebsd-xen@freebsd.org Subject: RE: 64-bit Centos5 xen kernel and creating a FreeBSD domU X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 17:48:14 -0000 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. =20 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=20 -----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=20 > Xen CentOS kernel installed on an Intel 64-bit system: >=20 > 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 >=20 > Using: > xen-3.0.3-64.el5_2.9, > kernel-xen-2.6.18-92.el5 >=20 > 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=20 > the Internet, I am seeing that there are issues with Intel 64-bit=20 > CentOS systems and that the domU kernel needs to have PAE support (I=20 > have 16GB memory on my system). >=20 > 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=20 > 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. >=20 > Thanks (in advace - as they say), > deb >=20 >=20 > _______________________________________________ > 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 (=EF=CC=C5=CB=D3=C1=CE=C4=D2 = =EB=CF=D7=C1=CC=C5=CE=CB=CF) _______________________________________________ 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 owner-freebsd-xen@FreeBSD.ORG Thu Jan 15 12:54:58 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EA591065673 for ; Thu, 15 Jan 2009 12:54:58 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.190]) by mx1.freebsd.org (Postfix) with ESMTP id E68C38FC22 for ; Thu, 15 Jan 2009 12:54:57 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: by fk-out-0910.google.com with SMTP id k31so654224fkk.11 for ; Thu, 15 Jan 2009 04:54:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=+VWvofGCgLTP4pf80OerodBFowPQ4pnyLbMB2Tkrk7A=; b=DVHAwLDsSq+9yb9dy1l4uIjSs1UdjwNM5AUNEGSIpi3uqPE8Y/n0ZmMNRxQ1g9WBW2 puxaX1nJpn3Q2qP3zwpzcZtx4vtEWIujL+5f4EgPa/tAn09HFPCHTi4B+ppMjpX460xR c8ki2aLywxVrg6anwKINsq8nv8etfqtoIxmfI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:reply-to:to:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=DgLMzvPbqUAOyP6JK21YTwfq8NvMBrFbMM76O6qdw7+k8S69n/YK0K2ylWKzFowYCe 1RQTWv4b2eDVkgU0XywcB9uOHLCVObWiJvtXTjYPYVnh+4DZaHbz2FGh2xBfXgkDtTmd GOZZ7ZHySpROPckSvkGdmo12XFZMc2qGiN7oM= Received: by 10.223.109.84 with SMTP id i20mr1564095fap.42.1232024096814; Thu, 15 Jan 2009 04:54:56 -0800 (PST) Received: from ?10.30.1.139? (vpn-or.studi-planet.com [78.47.172.52]) by mx.google.com with ESMTPS id b17sm32004210fka.35.2009.01.15.04.54.55 (version=SSLv3 cipher=RC4-MD5); Thu, 15 Jan 2009 04:54:55 -0800 (PST) From: Mister Olli To: freebsd-xen@freebsd.org In-Reply-To: References: <496BC05B.2030606@es.net> <1231945646.1172.8.camel@RabbitsDen> Content-Type: text/plain; charset=UTF-8 Date: Thu, 15 Jan 2009 13:54:48 +0100 Message-Id: <1232024088.18652.4.camel@phoenix.blechhirn.net> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 Content-Transfer-Encoding: 8bit Subject: RE: 64-bit Centos5 xen kernel and creating a FreeBSD domU X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mister.olli@googlemail.com List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 12:54:58 -0000 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 owner-freebsd-xen@FreeBSD.ORG Thu Jan 15 17:19:34 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FC5910656D1; Thu, 15 Jan 2009 17:19:34 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 98CA28FC0C; Thu, 15 Jan 2009 17:19:33 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: by bwz13 with SMTP id 13so4123497bwz.19 for ; Thu, 15 Jan 2009 09:19:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=EhIz6vXXcROC61OxHSi9PeBf+T99MS6vR4ZkY7oNLf4=; b=oxOMC9/xshE6EyVZhbyoYXxMi8f0LBm9SUgNaZtfQVP+fHQ5u0oLamaORK9RaFpbGQ ftrfGgIrDn83SRjuIVgf+ISS3iDM/fiZW7rHfNEAzmjZkwO4WKNZL7Hn77ZUV2TljNpt TAU+gBEhkeXykyKHgYkahwTG4N2eo1XLrP5ik= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:reply-to:to:cc:in-reply-to:references:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; b=CbNY7U8MBjyte0kHW318yb7Q02Jxy3+qsLNaH7Lfs7XLAHao5wGAcGIUJEqa2CBJPb 5dO+NwUkW15ECE69/iIPiJ8C8l/CYBO5JW60syUUMr0+MrL/He0LTq8SxleyQonkDSYK iGlUZ5lgaOiJxgu13LKElNchYfCzPPQT5zyF4= Received: by 10.223.110.6 with SMTP id l6mr1081786fap.52.1232039946534; Thu, 15 Jan 2009 09:19:06 -0800 (PST) Received: from ?10.30.1.139? (vpn-or.studi-planet.com [78.47.172.52]) by mx.google.com with ESMTPS id d13sm41202fka.20.2009.01.15.09.19.04 (version=SSLv3 cipher=RC4-MD5); Thu, 15 Jan 2009 09:19:05 -0800 (PST) From: Mister Olli To: Freminlins In-Reply-To: References: <1231950392.18652.0.camel@phoenix.blechhirn.net> Content-Type: text/plain Date: Thu, 15 Jan 2009 18:18:59 +0100 Message-Id: <1232039939.18652.16.camel@phoenix.blechhirn.net> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org, freebsd-questions@freebsd.org Subject: Re: sysctl machdep.independent_wallclock X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mister.olli@googlemail.com List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 17:19:35 -0000 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 >