From owner-freebsd-xen@FreeBSD.ORG Mon Oct 5 11:07:04 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 CDCA710656BF for ; Mon, 5 Oct 2009 11:07:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B9B318FC13 for ; Mon, 5 Oct 2009 11:07:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n95B74cR088857 for ; Mon, 5 Oct 2009 11:07:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n95B74ZD088855 for freebsd-xen@FreeBSD.org; Mon, 5 Oct 2009 11:07:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Oct 2009 11:07:04 GMT Message-Id: <200910051107.n95B74ZD088855@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org 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, 05 Oct 2009 11:07:04 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/136251 xen [xen] [patch] xn0 doesn't DHCP o kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. o kern/135179 xen [xen] Xen domU does not properly reboot o kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i o kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all o kern/135008 xen [xen] FreeBSD-current/Xen timecounter jumps o kern/134926 xen [xen] [panic] FreeBSD-current Xen DomU networking pani 7 problems total. From owner-freebsd-xen@FreeBSD.ORG Tue Oct 6 07:31:40 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 7A7C51065670 for ; Tue, 6 Oct 2009 07:31:40 +0000 (UTC) (envelope-from yury.buldakov@gmail.com) Received: from mail-qy0-f192.google.com (mail-qy0-f192.google.com [209.85.221.192]) by mx1.freebsd.org (Postfix) with ESMTP id 349C78FC15 for ; Tue, 6 Oct 2009 07:31:40 +0000 (UTC) Received: by qyk30 with SMTP id 30so4262629qyk.7 for ; Tue, 06 Oct 2009 00:31:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=nIIyTHQNknkdmUt4jBWXkQKaPflEyNuig+pBpoor6Ms=; b=n7Wy4fGwh9tkGjf0wzWElxcnX9xnokUXclrV4x7RVM1ggFcop90atUuer4ZPUiOC1W WY1jyK0Rhqa0Q/QwvugNTSlPUaPNtOQfHJFE9IvE28l29cWgQn8aPbfWUBCMeyQlyZ05 GDwUZxAPQsq9jGSfFs55eHYuI/HhLKJjfsTro= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=DRdmI8AfQU2Vrnp94cDNbWpM5ZEQnTe7erz3xiPobaE4pq6ZJ+Ic3Xq1jaAzyKt9u1 CWp2VBVPsslu0WMehcqiNQpNfbdTZoqPT2cHyhpbnSnABN2Xsc2ZOxzY44Zbmd9ZvR21 EkXUqQOhAY/lsjHPmEN7zXxB03jX00qapfi0Y= Received: by 10.224.116.13 with SMTP id k13mr932538qaq.246.1254814299508; Tue, 06 Oct 2009 00:31:39 -0700 (PDT) Received: from ?192.168.192.155? (cn-bgp-242.portaone.com [193.28.87.242]) by mx.google.com with ESMTPS id 7sm191056qwf.52.2009.10.06.00.31.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 06 Oct 2009 00:31:38 -0700 (PDT) Message-ID: <4ACAF24D.3010607@gmail.com> Date: Tue, 06 Oct 2009 10:31:25 +0300 From: "Yury A. Buldakov" User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [xen] FreeBSD Xen PVM DomU crashes 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: Tue, 06 Oct 2009 07:31:40 -0000 FreeBSD environment: uname -a FreeBSD pbox-xen-freebsd.silentnoise.intra 8.0-RC1 FreeBSD 8.0-RC1 #0 r: Mon Oct 5 12:58:34 EEST 2009 root@freebsd-8-buildbox.silentnoise.intra:/usr/obj/usr/src/sys/XEN i386 I have nfs-shared /usr/ports. While making pkgdb -aF my freebsd domU crashes: panic: HYPERVISOR_mmuext_op(&op, 1, NULL, DOMID_SELF) < 0: /usr/src/sys/i386/xen/xen_machdep.c:465 cpuid = 0 KDB: enter: panic [thread pid 4695 tid 100078 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> But in most cases it crashes with the following: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x107 fault code = supervisor read, page not present instruction pointer = 0x21:0xc01764e8 stack pointer = 0x29:0xd59f883c frame pointer = 0x29:0xd59f883c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 1, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 18518 (sendmail) [thread pid 18518 tid 100089 ] Stopped at strlen+0x8: cmpb $0,0(%edx) db> Tracing pid 18518 tid 100089 td 0xc2d876c0 strlen(107,d59f898c,0,d59f888c,c011a32b,...) at strlen+0x8 kvprintf(c035c5ae,c0108b80,d59f898c,a,d59f89cc,...) at kvprintf+0x8fe vsnprintf(c03d3460,100,c035c5ae,d59f89cc,0,...) at vsnprintf+0x3b panic(c035c5ae,107,c036d649,33e,16d,...) at panic+0x8d _mtx_lock_flags(c076d808,0,c036d649,33e,c30dfc00,...) at _mtx_lock_flags+0x9a netisr_clearqdrops(d59f8a28,c2d87764,c0512828,0) at netisr_clearqdrops+0x66e netisr_queue_src(1,0,c30dfc00,d59f8a6c,c01861ee,...) at netisr_queue_src+0xa7 netisr_queue(1,c30dfc00,c30dfc48,d59f8af8,d59f8a80,...) at netisr_queue+0x20 if_simloop(c237b000,c30dfc00,2,0,c01a299f,...) at if_simloop+0xfe looutput(c237b000,c30dfc00,d59f8b00,d59f8af8,c031fee4,...) at looutput+0x141 ip_output(c30dfc00,0,0,0,0,...) at ip_output+0x9cc tcp_output(c273d768,c246b840,1b9,c26501a4,c2d8c19c,...) at tcp_output+0x1540 tcp_ctloutput(c2d8c19c,c246b840,c2d876c0,25,d59f8c70,...) at tcp_ctloutput+0x933 soconnect(c2d8c19c,c246b840,c2d876c0,bf7fadc0,c246b840,...) at soconnect+0x52 kern_connect(c2d876c0,6,c246b840,c246b840,ffffffff,...) at kern_connect+0xa6 connect(c2d876c0,d59f8d08,c,c0364398,c039d138,...) at connect+0x46 syscall(d59f8d48) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x22 --- syscall (98, FreeBSD ELF32, connect), eip = 0x283b9e5b, esp = 0xbf7fac5c, ebp = 0xbf7fae88 --- From owner-freebsd-xen@FreeBSD.ORG Tue Oct 6 10:00:43 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 CFDA0106566B for ; Tue, 6 Oct 2009 10:00:43 +0000 (UTC) (envelope-from freebsd-xen@winnipeg.nl) Received: from mail.owl-ict.nl (mail.owl-ict.nl [80.69.76.80]) by mx1.freebsd.org (Postfix) with ESMTP id C02568FC19 for ; Tue, 6 Oct 2009 10:00:42 +0000 (UTC) Received: (qmail 14808 invoked by uid 89); 6 Oct 2009 09:33:59 -0000 Received: from uil.winnipeg.nl (HELO ?192.168.1.14?) (lotte@winnipeg.nl@83.161.204.37) by mail.owl-ict.nl with SMTP; 6 Oct 2009 11:33:59 +0200 Message-ID: <4ACB0F08.9080603@winnipeg.nl> Date: Tue, 06 Oct 2009 11:34:00 +0200 From: Lotte-Sara Laan User-Agent: Thunderbird 2.0.0.23 (X11/20090820) MIME-Version: 1.0 To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD 8.0RC1 and CURRENT panics when trying to boot as xenU 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: Tue, 06 Oct 2009 10:00:43 -0000 I've send this email to the freebsd-current mailinglist, but I think this is a better place for it (-; --------------------- I'm trying to get FreeBSD working under Xen 3.4.1 using the Gentoo dom0 kernel 2.6.29.6 I downloaded and compiled the 8.0RC1 and the CURRENT svn version revision 197720 from http://svn.freebsd.org/base/head with the KERNCONF=XEN option but when I'm starting my domU I'm getting the following panic: WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb 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 9.0-CURRENT #1 r197720: Sat Oct 3 14:09:31 CEST 2009 root@freebsd.winnipeg.nl:/usr/local/xen/current-obj/usr/src/sys/XEN-LOTJUH i386 WARNING: WITNESS option enabled, expect reduced performance. Xen reported: 2611.800 MHz processor. Timecounter "ixen" frequency 1000000000 Hz quality 0 CPU: AMD Phenom(tm) II X4 810 Processor (2611.80-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x100f42 Stepping = 2 Features=0x178bfbff Features2=0x802009 AMD Features=0xee500800 AMD Features2=0x37ff TSC: P-state invariant Data TLB: 48 entries, fully associative Instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 1073741824 (1024 MB) Physical memory chunk(s): 0x00000000008ab000 - 0x000000003ecb2fff, 1044414464 bytes (254984 pages) avail memory = 1040429056 (992 MB) APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) SMP: Added CPU 1 (AP) SMP: Added CPU 2 (AP) SMP: Added CPU 3 (AP) panic: HYPERVISOR_update_va_mapping(((unsigned long)(va)), (pa | 0x002 | 0x001 | pgeflag | pmap_cache_bits(mode, 0)), UVMF_INVLPG| UVMF_ALL) < 0: /usr/src/sys/i386/xen/pmap.c:1269 cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> bt Tracing pid 0 tid 0 td 0xc03e10f0 kdb_enter(c03698a8,c03698a8,c038e3f1,c06f9cd4,0,...) at kdb_enter+0x3a panic(c038e3f1,c0396429,c0396207,4f5,0,...) at panic+0x136 pmap_mapdev_attr(0,0,100000,6,c06f9d44,...) at pmap_mapdev_attr+0x13d pmap_mapbios(0,0,100000,1,c03c946c,...) at pmap_mapbios+0x27 x86bios_intr(c36e4840,0,0,76,c0395e2b,...) at x86bios_intr+0x1b0 module_register_init(c03dbe88,3040800,3040800,6fe000,0,...) at module_register_init+0xa7 mi_startup(6fe000,0,0,0,0,...) at mi_startup+0x96 btext() at btext+0x95 db> I'm getting the same panic when I add only 1 cpu. And I've tried revision 197775 now as well which gives me exactly the same panic. I'm using the following boot line for pygrub: kernel /boot/kernel/kernel vfs.root.mountfrom=ufs:xbd0,kern.hz=100,kern.smp.disabled=1,boot_verbose=1,boot_single=1 I've tried it with and without the kern.smp.disabled option And for 8.0RC1 I get: WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb 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-RC1 #0: Fri Oct 2 22:05:22 CEST 2009 root@freebsd.winnipeg.nl:/usr/local/xen/obj-xenbro2/usr/src/sys/XEN-LOTJUH WARNING: WITNESS option enabled, expect reduced performance. Xen reported: 2611.800 MHz processor. Timecounter "ixen" frequency 1000000000 Hz quality 0 CPU: AMD Phenom(tm) II X4 810 Processor (2611.80-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x100f42 Stepping = 2 Features=0x178bfbff Features2=0x802009 AMD Features=0xee500800 AMD Features2=0x37ff TSC: P-state invariant Data TLB: 48 entries, fully associative Instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 1073741824 (1024 MB) Physical memory chunk(s): 0x0000000000899000 - 0x000000003ecb2fff, 1044488192 bytes (255002 pages) avail memory = 1040502784 (992 MB) APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) ULE: setup cpu 0 [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) Event-channel device installed. mem: Pentium Pro MTRR support enabled null: nfslock: pseudo-device random: kbd0 at kbdmux0 io: Grant table initialized xenbus0: on motherboard xc0: on motherboard [XEN] xen_rtc_probe: probing Hypervisor RTC clock rtc0: on motherboard [XEN] xen_rtc_attach: attaching Hypervisor RTC clock rtc0: registered as a time-of-day clock (resolution 1000000us) npx0: INT 16 interface Device configuration finished. procfs registered Timecounters tick every 10.000 msec kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault whilelo0: bpf attached in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x21:0xc0320011 stack pointer = 0x29:0xc35c6ca0 frame pointer = 0x29:0xc35c6ca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 1, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 [XEN] hypervisor wallclock nudged; nudging TOD. [thread pid 11 tid 100003 ] Stopped at spinlock_enter+0x91: hlt db> bt Tracing pid 11 tid 100003 td 0xc3708b40 spinlock_enter(1,c35c6cf8,c00fb6fe,1,0,...) at spinlock_enter+0x91 cpu_idle(1,0,c035f75b,9e9,c3708b40,...) at cpu_idle+0x12 sched_idletd(0,c35c6d38,c035909c,343,c3706aa0,...) at sched_idletd+0x23e fork_exit(c00fb4c0,0,c35c6d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xc35c6d70, ebp = 0 --- db> Does anyone have any ideas about what's going wrong? Lotte-Sara Laan From owner-freebsd-xen@FreeBSD.ORG Sat Oct 10 02:43:51 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 C984A1065693; Sat, 10 Oct 2009 02:43:51 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (113901-app1.sourcehosting.net [72.32.213.11]) by mx1.freebsd.org (Postfix) with ESMTP id 6F1108FC08; Sat, 10 Oct 2009 02:43:51 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=cube.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MwRN1-000Jir-AH; Fri, 09 Oct 2009 22:07:48 -0400 Received: from [127.0.0.1] (fireball.entropy.prv [192.168.1.12]) by cube.entropy.prv (Postfix) with ESMTP id 92A8035BD1C7; Fri, 9 Oct 2009 22:07:43 -0400 (EDT) Message-ID: <4ACFEC6E.2030109@FreeBSD.org> Date: Fri, 09 Oct 2009 22:07:42 -0400 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Adrian Chadd References: <77abe410908211256g44dd20d8o9b50c20357e63a6b@mail.gmail.com> <4A94CD0D.8070902@prgmr.com> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=1C940290 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) Cc: freebsd-xen@freebsd.org Subject: Re: finishing up the xen port - would funding help? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org 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: Sat, 10 Oct 2009 02:43:51 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adrian Chadd wrote: > Give me a few days to get stuff together here and I'll see what I can > do in -head. > > Thanks for all your offers of support. > > adrian > [...] Hi everyone, I received an email from a contact @ Amazon AWS yesterday asking about the status of the FreeBSD Xen project. He and I connected earlier this year after a short exchange on Twitter and some emails about getting FreeBSD AMIs running on Amazon EC2. I told him that there was a thread on the freebsd-xen mailing list in August. My understanding is that the primary blocker is funding for the developers who have the skills required to bring the Xen support up to production quality. I also figured that it might take even more time to then port to the version of Xen used by Amazon. I hope to hear back from him soon with his thoughts. Obviously, it would be extremely helpful if Amazon funded the development, presuming there would be a long-term financial gain for them. If anyone has any feedback that I should relay to him, let me know. I also asked him if he wanted contact information for the FreeBSD/Xen developers and other folks who are involved in the project at a high level. I'll post back here if he does. Best regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKz+xu0sRouByUApARArKYAKCVziRDp71w977HHy2XpKxQsHgUXgCaA2fT RFxGu9dVA1s39MKn0+o6520= =Zg60 -----END PGP SIGNATURE----- From owner-freebsd-xen@FreeBSD.ORG Sat Oct 10 15:36:59 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 D2707106568B; Sat, 10 Oct 2009 15:36:59 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id 59E008FC08; Sat, 10 Oct 2009 15:36:58 +0000 (UTC) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.14.3/8.14.3) with ESMTP id n9AF2OUs060567; Sat, 10 Oct 2009 17:02:24 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.3/8.14.3/Submit) id n9AF2Oe9060566; Sat, 10 Oct 2009 11:02:24 -0400 (EDT) (envelope-from cracauer) Date: Sat, 10 Oct 2009 11:02:24 -0400 From: Martin Cracauer To: Greg Larkin Message-ID: <20091010150224.GA71643@cons.org> References: <77abe410908211256g44dd20d8o9b50c20357e63a6b@mail.gmail.com> <4A94CD0D.8070902@prgmr.com> <4ACFEC6E.2030109@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ACFEC6E.2030109@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-xen@freebsd.org Subject: Re: finishing up the xen port - would funding help? 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: Sat, 10 Oct 2009 15:36:59 -0000 Greg Larkin wrote on Fri, Oct 09, 2009 at 10:07:42PM -0400: > I also figured that it might take even more time to > then port to the version of Xen used by Amazon. What version is that and why do they assume they are still using it when the port is finished? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/