From owner-freebsd-xen@FreeBSD.ORG Mon Jul 25 11:07:22 2011 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 0F0AC106567D for ; Mon, 25 Jul 2011 11:07:22 +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 D86AE8FC2A for ; Mon, 25 Jul 2011 11:07:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p6PB7LJl046581 for ; Mon, 25 Jul 2011 11:07:21 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p6PB7LZ1046579 for freebsd-xen@FreeBSD.org; Mon, 25 Jul 2011 11:07:21 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Jul 2011 11:07:21 GMT Message-Id: <201107251107.p6PB7LZ1046579@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, 25 Jul 2011 11:07:22 -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/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/154302 xen [xen] [panic] [patch] xn0: Error 2 parsing device/vif/ o kern/153789 xen [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 24 problems total. From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 18:45:49 2011 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 67B53106566B for ; Tue, 26 Jul 2011 18:45:49 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.freebsd.org (Postfix) with ESMTP id 3937F8FC0A for ; Tue, 26 Jul 2011 18:45:48 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout3.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6QIZTcE074041 for ; Tue, 26 Jul 2011 11:35:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311705329; bh=sS+8sStePw7yeJ7J8QCIXifdgu3TsesytG22Xh2Y124=; h=Subject:From:To:Content-Type:Date:Message-ID:Mime-Version: Content-Transfer-Encoding; b=HGLngX/6HSWiqmJTAk5w1d0r2yRuivFFaztRHunJReEmppACYXiq/N43lFLC5w13X bL9fn4G0wDrjILF2XC3Bu1mgZFc2tKu9DLakRxSvd3xK7fDIbMv+u4MdbgW0N98TWr T2Q+EvP0ztJ4pqjgeAmTmq8cLP/glryQvusRqQu0= From: Sean Bruno To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 Jul 2011 11:35:29 -0700 Message-ID: <1311705329.3927.8.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Subject: FreeBSD 8, PV, i386 panic with vcpus > 1 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, 26 Jul 2011 18:45:49 -0000 I assume then, that the i386 PV instance cannot do more than 1 CPU at this time? sean Started domain ref8-xen32 (id=120) WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2011 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.2-STABLE #1 r224449: Tue Jul 26 09:53:36 PDT 2011 sbruno@ref8-xen32.freebsd.org:/usr/obj/dumpster/scratch/sbruno-scratch/8/sys/XEN i386 WARNING: WITNESS option enabled, expect reduced performance. Xen reported: 2493.746 MHz processor. Timecounter "ixen" frequency 1953125 Hz quality 0 CPU: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (2493.75-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x10676 Family = 6 Model = 17 Stepping = 6 Features=0xbfe3fbff Features2=0xce3bd AMD Features=0x20100000 AMD Features2=0x1 TSC: P-state invariant real memory = 805306368 (768 MB) avail memory = 777650176 (741 MB) gdtpfn=20103f pdptpfn=3d0be panic: HYPERVISOR_vcpu_op(VCPUOP_initialise, cpu, &ctxt): /dumpster/scratch/sbruno-scratch/8/sys/i386/xen/mp_machdep.c:930 cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> db> db> db> bt Tracing pid 0 tid 0 td 0xc03dec90 kdb_enter(c0369837,c0369837,c03915fd,c06b4ca8,0,...) at kdb_enter+0x3a panic(c03915fd,c03983a2,c0398124,3a2,c0398124,...) at panic+0x134 start_all_aps(c0396bf2,1,c03b2890,c036e574,0,...) at start_all_aps+0x7d4 cpu_mp_start(c03f3234,c036e574,0,1,fffffff,...) at cpu_mp_start+0x155 smp_topo_find(0,6040800,6040800,6b9000,0,...) at smp_topo_find+0xbf mi_startup(6b9000,0,0,0,0,...) at mi_startup+0xac btext() at btext+0x95 From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 18:53:04 2011 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 940B8106566B for ; Tue, 26 Jul 2011 18:53:04 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.freebsd.org (Postfix) with ESMTP id 7EF058FC13 for ; Tue, 26 Jul 2011 18:53:04 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout3.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6QIgcpd076378 for ; Tue, 26 Jul 2011 11:42:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311705758; bh=EPJ/wbT7XRaxsVIrA7QR0HA0fIA7T5K7BOPazifp2lY=; h=Subject:From:To:Content-Type:Date:Message-ID:Mime-Version: Content-Transfer-Encoding; b=OG+4LhljmQLsgS0xRAjlK04m8jJPjn8Wun6NmzxCzYTOBHqzAm/7BqT4PYvbeI1w0 JzbWosh3yHsZtbCaCdlykk2wUJcZJdDTyvriPN0EvPdFBlC8Qytfj0SbXhm8sV1s5x P/q2rv4QLtZMW/RFE+/zvEPrW2hTob3a/KmrmU+4= From: Sean Bruno To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 Jul 2011 11:42:37 -0700 Message-ID: <1311705757.3927.10.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Subject: FreeBSD Xen PV i386 --> 855MB Max? 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, 26 Jul 2011 18:53:04 -0000 I note that if I scale the i386 PV Xen kernel past 855MB, I get an insta panic at boot. I assume that there's a hard limit on the amount of RAMS we can use here? Using config file "./ref8-xen32". Started domain ref8-xen32 (id=133) WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2011 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.2-STABLE #1 r224449: Tue Jul 26 09:53:36 PDT 2011 sbruno@ref8-xen32.freebsd.org:/usr/obj/dumpster/scratch/sbruno-scratch/8/sys/XEN i386 WARNING: WITNESS option enabled, expect reduced performance. panic: pmap_init: page table page is out of range cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at 0xc010e68a: movl $0,0xc03f20b4 From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 18:58:58 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 1B908106564A for ; Tue, 26 Jul 2011 18:58:58 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from xps.daemonology.net (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx2.freebsd.org (Postfix) with SMTP id 32BD4153E8E for ; Tue, 26 Jul 2011 18:58:46 +0000 (UTC) Received: (qmail 71443 invoked from network); 26 Jul 2011 18:58:45 -0000 Received: from unknown (HELO xps.daemonology.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2011 18:58:45 -0000 Message-ID: <4E2F0E65.70603@freebsd.org> Date: Tue, 26 Jul 2011 11:58:45 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20101220 Thunderbird/3.0.11 MIME-Version: 1.0 To: Sean Bruno References: <1311705329.3927.8.camel@hitfishpass-lx.corp.yahoo.com> In-Reply-To: <1311705329.3927.8.camel@hitfishpass-lx.corp.yahoo.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD PV i386 panics 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, 26 Jul 2011 18:58:58 -0000 On 07/26/11 11:35, Sean Bruno wrote: > I assume then, that the i386 PV instance cannot do more than 1 CPU at > this time? Correct. SMP support was clearly started but never completed. > I note that if I scale the i386 PV Xen kernel past 855MB, I get an insta > panic at boot. I assume that there's a hard limit on the amount of RAMS > we can use here? There's a problem somewhere in FreeBSD's PV machine init code, but I haven't had an opportunity to track it down yet. I hope to look at this some time soon (if I can access the xen box in the cluster?) but I've been swamped lately. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 19:10:30 2011 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 919B71065673 for ; Tue, 26 Jul 2011 19:10:30 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.freebsd.org (Postfix) with ESMTP id 7753D8FC23 for ; Tue, 26 Jul 2011 19:10:30 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout3.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6QJAGOo088984; Tue, 26 Jul 2011 12:10:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311707416; bh=/P8HjH7sB5IcQnMVL3L7vQdOhf5N2t6KfQuD5oOHyYc=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=A/9dfYJ3aJRlNPsHWg5QT/uHgKPFu+7hQ8M7vXitjf10lXVCfbXLtEBvHTqiBU2y6 2F6jDzzsQ6bWYoKRuEnTmszey/oNCDC8aUmOCOAJKLnGBth5kwozW8Ew/1KDUue9Qx IyM0WpOYod5e2hLaamrE0dpQ3C2CRXpgUgt+UCbQ= From: Sean Bruno To: "K. Macy" In-Reply-To: References: <1311705757.3927.10.camel@hitfishpass-lx.corp.yahoo.com> Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 Jul 2011 12:10:15 -0700 Message-ID: <1311707415.3927.12.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD Xen PV i386 --> 855MB Max? 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, 26 Jul 2011 19:10:30 -0000 On Tue, 2011-07-26 at 12:01 -0700, K. Macy wrote: > It's an artifact of the initialization code and how the xen domain > builder configures the initial mapped memory. I've come against this > and fixed this issue in the past but I guess either the domain builder > has changed or the initial code has bit rotted. I can't commit so ask > Colin if he can fix. > > Cheers I have one of those "commit bits" if you have something in mind. sean From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 19:16:53 2011 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 D6E861065674 for ; Tue, 26 Jul 2011 19:16:53 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 916EB8FC0C for ; Tue, 26 Jul 2011 19:16:53 +0000 (UTC) Received: by vxg33 with SMTP id 33so804826vxg.13 for ; Tue, 26 Jul 2011 12:16:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=3YE87QDFRYpo4Y8G98XUpt5PGVT5iCjEt5ZLfL4QAbg=; b=cVN7LYSdkHbgmyBugItbmYYeMpPHFKrjhA3Ub1M8wCvEbmyi353aDM3YyBED6U05dB 9dQgYb920lcmgTCmSMKu34lD2XWdvnlduUFWHpQSIzNeKDzGD2uOfHjFOyh+l3/YoM7A cDR++/FSExdPzMB8PJut5XszXrOTvXBN08xdk= MIME-Version: 1.0 Received: by 10.52.32.37 with SMTP id f5mr5945214vdi.509.1311707417083; Tue, 26 Jul 2011 12:10:17 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.188.101 with HTTP; Tue, 26 Jul 2011 12:10:17 -0700 (PDT) In-Reply-To: <1311705329.3927.8.camel@hitfishpass-lx.corp.yahoo.com> References: <1311705329.3927.8.camel@hitfishpass-lx.corp.yahoo.com> Date: Tue, 26 Jul 2011 21:10:17 +0200 X-Google-Sender-Auth: wL3s-4GzUFxYRYzEqB_aiqy8iuU Message-ID: From: "K. Macy" To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD 8, PV, i386 panic with vcpus > 1 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, 26 Jul 2011 19:16:53 -0000 Correct, I put much of the infrastructure in place but did not end up "debugging it in to existence." Cheers On Tuesday, July 26, 2011, Sean Bruno wrote: > I assume then, that the i386 PV instance cannot do more than 1 CPU at > this time? > > sean > > > > Started domain ref8-xen32 (id=120) > WARNING: loader(8) metadata is missing! > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2011 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.2-STABLE #1 r224449: Tue Jul 26 09:53:36 PDT 2011 > > sbruno@ref8-xen32.freebsd.org:/usr/obj/dumpster/scratch/sbruno-scratch/8/sys/XEN i386 > WARNING: WITNESS option enabled, expect reduced performance. > Xen reported: 2493.746 MHz processor. > Timecounter "ixen" frequency 1953125 Hz quality 0 > CPU: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (2493.75-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x10676 Family = 6 Model = 17 > Stepping = 6 > > Features=0xbfe3fbff > > Features2=0xce3bd > AMD Features=0x20100000 > AMD Features2=0x1 > TSC: P-state invariant > real memory = 805306368 (768 MB) > avail memory = 777650176 (741 MB) > gdtpfn=20103f pdptpfn=3d0be > panic: HYPERVISOR_vcpu_op(VCPUOP_initialise, cpu, > &ctxt): /dumpster/scratch/sbruno-scratch/8/sys/i386/xen/mp_machdep.c:930 > cpuid = 0 > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at kdb_enter+0x3a: movl $0,kdb_why > db> > db> > db> > db> bt > Tracing pid 0 tid 0 td 0xc03dec90 > kdb_enter(c0369837,c0369837,c03915fd,c06b4ca8,0,...) at kdb_enter+0x3a > panic(c03915fd,c03983a2,c0398124,3a2,c0398124,...) at panic+0x134 > start_all_aps(c0396bf2,1,c03b2890,c036e574,0,...) at start_all_aps+0x7d4 > cpu_mp_start(c03f3234,c036e574,0,1,fffffff,...) at cpu_mp_start+0x155 > smp_topo_find(0,6040800,6040800,6b9000,0,...) at smp_topo_find+0xbf > mi_startup(6b9000,0,0,0,0,...) at mi_startup+0xac > btext() at btext+0x95 > > > _______________________________________________ > 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 Tue Jul 26 19:20:32 2011 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 8A35F1065674 for ; Tue, 26 Jul 2011 19:20:32 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2-b.corp.re1.yahoo.com (mrout2-b.corp.re1.yahoo.com [69.147.107.21]) by mx1.freebsd.org (Postfix) with ESMTP id 4843E8FC17 for ; Tue, 26 Jul 2011 19:20:31 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2-b.corp.re1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6QJ9n6M082070; Tue, 26 Jul 2011 12:09:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311707390; bh=3n5GosTl1R87gkyBu3GXI5YKtQAQHRkgvpvhAQqWvGs=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=IgvoU1DkAIWLyWM2hccMYvLffCGJgz+QXucFAXdZV89ZkHSGZEcHmFBHpKgG5l+e3 iebGck9rRWCvIsdh1XWyBrGwIFOYoCqqum0DqaJEJXKOitKh+eZzgwLpXXu5lkxS5s s2vY8txtJRLzc/ZeVDaRD03JSZGoOVxI/wD5ir1Y= From: Sean Bruno To: Colin Percival In-Reply-To: <4E2F0E65.70603@freebsd.org> References: <1311705329.3927.8.camel@hitfishpass-lx.corp.yahoo.com> <4E2F0E65.70603@freebsd.org> Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 Jul 2011 12:09:49 -0700 Message-ID: <1311707389.3927.11.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD PV i386 panics 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, 26 Jul 2011 19:20:32 -0000 On Tue, 2011-07-26 at 11:58 -0700, Colin Percival wrote: > On 07/26/11 11:35, Sean Bruno wrote: > > I assume then, that the i386 PV instance cannot do more than 1 CPU at > > this time? > > Correct. SMP support was clearly started but never completed. > > > I note that if I scale the i386 PV Xen kernel past 855MB, I get an insta > > panic at boot. I assume that there's a hard limit on the amount of RAMS > > we can use here? > > There's a problem somewhere in FreeBSD's PV machine init code, but I haven't had > an opportunity to track it down yet. I hope to look at this some time soon (if > I can access the xen box in the cluster?) but I've been swamped lately. > Yup, you're on my list to get access today. I'll get kerberos up and running on the hypervisor so you can screw around in a bit. Sean From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 19:30:54 2011 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 9D9F21065670 for ; Tue, 26 Jul 2011 19:30:54 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 52ED28FC0C for ; Tue, 26 Jul 2011 19:30:54 +0000 (UTC) Received: by vws18 with SMTP id 18so792522vws.13 for ; Tue, 26 Jul 2011 12:30:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=F9Gln0bvIogMunelkzHspz62lEmrtVfckP0LtbdzHIw=; b=sZfAnPyQQCoSdOAV7FbJsJTNN/317BYqKUpo8taEPUShjsxNdjnQIXQiKHH1J882Zj SWEiyG9u1oNfM80yZ+FYK3112w1IEYU2EopbmmHJK1Iq5KREwQqBbxi/uGahqGv5gx2o 7sqtu5uMcoeaXJ15d+2b2IzGN6p0bTju2ZCNw= MIME-Version: 1.0 Received: by 10.52.32.37 with SMTP id f5mr5936026vdi.509.1311706914285; Tue, 26 Jul 2011 12:01:54 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.188.101 with HTTP; Tue, 26 Jul 2011 12:01:54 -0700 (PDT) In-Reply-To: <1311705757.3927.10.camel@hitfishpass-lx.corp.yahoo.com> References: <1311705757.3927.10.camel@hitfishpass-lx.corp.yahoo.com> Date: Tue, 26 Jul 2011 21:01:54 +0200 X-Google-Sender-Auth: zZNAWD0EUT-qUt-vKPVkYX0lLB0 Message-ID: From: "K. Macy" To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD Xen PV i386 --> 855MB Max? 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, 26 Jul 2011 19:30:54 -0000 It's an artifact of the initialization code and how the xen domain builder configures the initial mapped memory. I've come against this and fixed this issue in the past but I guess either the domain builder has changed or the initial code has bit rotted. I can't commit so ask Colin if he can fix. Cheers On Tuesday, July 26, 2011, Sean Bruno wrote: > I note that if I scale the i386 PV Xen kernel past 855MB, I get an insta > panic at boot. I assume that there's a hard limit on the amount of RAMS > we can use here? > > Using config file "./ref8-xen32". > Started domain ref8-xen32 (id=133) > WARNING: loader(8) metadata is missing! > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2011 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.2-STABLE #1 r224449: Tue Jul 26 09:53:36 PDT 2011 > > sbruno@ref8-xen32.freebsd.org:/usr/obj/dumpster/scratch/sbruno-scratch/8/sys/XEN i386 > WARNING: WITNESS option enabled, expect reduced performance. > panic: pmap_init: page table page is out of range > cpuid = 0 > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at 0xc010e68a: movl $0,0xc03f20b4 > > > _______________________________________________ > 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 Tue Jul 26 19:53:39 2011 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 E649F1065674; Tue, 26 Jul 2011 19:53:39 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 840F78FC0A; Tue, 26 Jul 2011 19:53:39 +0000 (UTC) Received: by vxg33 with SMTP id 33so842365vxg.13 for ; Tue, 26 Jul 2011 12:53:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vZbZ06Llkv0j6o/WzDMB56c39rciD8+1HqMPPGgtXSo=; b=XvyWkYSq4kC7NuqWuJpq8eFJDeejnQdikei8MK2jG5/cHshIzpAX6APJPS3yn01XZN lXEhZwDlp/8l9FKuQozWTZB3GFDPtbYLJErb7oH/tJSj4Tm0Tw76ihs/Uf88mS61WOwO gy0j97aNi2I/4jBBkl3hVZMTocZ7g0slTt8tY= MIME-Version: 1.0 Received: by 10.52.97.227 with SMTP id ed3mr6211087vdb.442.1311710018733; Tue, 26 Jul 2011 12:53:38 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.188.101 with HTTP; Tue, 26 Jul 2011 12:53:38 -0700 (PDT) In-Reply-To: <1311707415.3927.12.camel@hitfishpass-lx.corp.yahoo.com> References: <1311705757.3927.10.camel@hitfishpass-lx.corp.yahoo.com> <1311707415.3927.12.camel@hitfishpass-lx.corp.yahoo.com> Date: Tue, 26 Jul 2011 21:53:38 +0200 X-Google-Sender-Auth: 8_GDLlqB_mHDWNW0LqKK3Yp0Wlo Message-ID: From: "K. Macy" To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD Xen PV i386 --> 855MB Max? 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, 26 Jul 2011 19:53:40 -0000 I thought I did too, but Neville Chamberlain appears to be alive and well amongst those that developers have chosen to represent them. On Tuesday, July 26, 2011, Sean Bruno wrote: > On Tue, 2011-07-26 at 12:01 -0700, K. Macy wrote: >> It's an artifact of the initialization code and how the xen domain >> builder configures the initial mapped memory. I've come against this >> and fixed this issue in the past but I guess either the domain builder >> has changed or the initial code has bit rotted. I can't commit so ask >> Colin if he can fix. > >> Cheers > > I have one of those "commit bits" if you have something in mind. > > sean > > From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 21:48:52 2011 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 539E6106564A for ; Tue, 26 Jul 2011 21:48:52 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id 3E68F8FC1D for ; Tue, 26 Jul 2011 21:48:52 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6QLmdXI062382 for ; Tue, 26 Jul 2011 14:48:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311716919; bh=Vrh0ukLVTEpMcb8mi9jCTvHyFXhY4vx82bUS7IKf3ds=; h=Subject:From:To:Content-Type:Date:Message-ID:Mime-Version: Content-Transfer-Encoding; b=CMdSEH0D7KZ8sqbKm5rAMdQ8YIEHFgclN0vQ6+NPGIBCd0LOjSFEpqZjku+QPe+Er kHU+AaZE874xG9yYVXoCHCrKmGRpEoCs+VhXl6z26crdDaXAUvt6c7ZYir842tU9k3 ZjDug4y9nQOUB0kUNM1A88jg0yZm/71gikGtAZ+s= From: Sean Bruno To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 Jul 2011 14:48:38 -0700 Message-ID: <1311716918.3927.20.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Subject: FreeBSD 8, PV i386 VNC fails? 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, 26 Jul 2011 21:48:52 -0000 Probably not doing it right. When I switched from pure HVM to PV on the i386 VMs in the cluster, VNC stopped working all together. Did I do it wrong? I've tried the following: vnc = 1 vncdisplay = 1 vncunused = 1 vncpasswd='' and vfb = [ "type = vnc, vncdisplay = 1, vncunused = 1, vncpasswd=''" ] The vfb = [] syntax seems to hang the VM on frame buffer initialization and it will not post. The old style syntax seems to allow the host to boot, but there is no VNC listening on the host. Understand that the old style syntax works just fine in HVM mode. Sean From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 22:05:27 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 1A8E21065670 for ; Tue, 26 Jul 2011 22:05:26 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from xps.daemonology.net (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx2.freebsd.org (Postfix) with SMTP id 6AA811513AC for ; Tue, 26 Jul 2011 22:04:49 +0000 (UTC) Received: (qmail 73249 invoked from network); 26 Jul 2011 22:04:48 -0000 Received: from unknown (HELO xps.daemonology.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2011 22:04:48 -0000 Message-ID: <4E2F3A00.7060404@freebsd.org> Date: Tue, 26 Jul 2011 15:04:48 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20101220 Thunderbird/3.0.11 MIME-Version: 1.0 To: Sean Bruno References: <1311716918.3927.20.camel@hitfishpass-lx.corp.yahoo.com> In-Reply-To: <1311716918.3927.20.camel@hitfishpass-lx.corp.yahoo.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD 8, PV i386 VNC fails? 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, 26 Jul 2011 22:05:27 -0000 On 07/26/11 14:48, Sean Bruno wrote: > Probably not doing it right. When I switched from pure HVM to PV on the > i386 VMs in the cluster, VNC stopped working all together. Did I do it > wrong? Is it possible to use PV with VNC? I thought under PV there wasn't any emulated console, just the Xen paravirtual console which lets you read and write characters as on a serial console. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 22:49:45 2011 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 94958106566B for ; Tue, 26 Jul 2011 22:49:45 +0000 (UTC) (envelope-from lsc@luke.xen.prgmr.com) Received: from luke.xen.prgmr.com (luke.xen.prgmr.com [38.99.2.47]) by mx1.freebsd.org (Postfix) with ESMTP id 841E68FC08 for ; Tue, 26 Jul 2011 22:49:45 +0000 (UTC) Received: by luke.xen.prgmr.com (Postfix, from userid 500) id C53A4105377; Tue, 26 Jul 2011 18:18:46 -0400 (EDT) Date: Tue, 26 Jul 2011 18:18:46 -0400 From: "Luke S. Crawford" To: Colin Percival Message-ID: <20110726221846.GE22861@luke.xen.prgmr.com> References: <1311716918.3927.20.camel@hitfishpass-lx.corp.yahoo.com> <4E2F3A00.7060404@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E2F3A00.7060404@freebsd.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-xen@freebsd.org Subject: Re: FreeBSD 8, PV i386 VNC fails? 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, 26 Jul 2011 22:49:45 -0000 On Tue, Jul 26, 2011 at 03:04:48PM -0700, Colin Percival wrote: > On 07/26/11 14:48, Sean Bruno wrote: > > Probably not doing it right. When I switched from pure HVM to PV on the > > i386 VMs in the cluster, VNC stopped working all together. Did I do it > > wrong? > > Is it possible to use PV with VNC? I thought under PV there wasn't any > emulated console, just the Xen paravirtual console which lets you read > and write characters as on a serial console. It's possible, redhat built a paravirtualized framebuffer to give pv guests a framebuffer http://www.xen.org/files/xensummit_4/Xenpvfb07_Armbruster.pdf I imagine the problem is probably hypervisor dependent; I mean, I don't know anyone who actually used the paravirtualized framebuffer, so it's probably not well tested, and may suffer from bit rot as other features are added to xen. I tested it, /I believe/ on rhel/centos 5.3. From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 23:40:35 2011 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 5C5621065670; Tue, 26 Jul 2011 23:40:35 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id 428448FC13; Tue, 26 Jul 2011 23:40:35 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6QNeQKG074282; Tue, 26 Jul 2011 16:40:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311723626; bh=dPmtwljPSsXt7TufNOXPa4pR5yRL25gQhr6y9Kwr7n4=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=eI7WyiG6YCwB4bvjhJLfXCwyYLhrWbRgLrhuYCkHroqYMeFkYwRNflyTyar9/OnP5 0yQDphv7QvZhgCObaYLsJFaAxIKc1LLm6LprDke9MfajPOM2N8OiGzwR3TuOgmcg6b hHJmq80hVNhFE6LIsH8qa9nfQ2R+t6W0LqcU1jPw= From: Sean Bruno To: "Luke S. Crawford" In-Reply-To: <20110726221846.GE22861@luke.xen.prgmr.com> References: <1311716918.3927.20.camel@hitfishpass-lx.corp.yahoo.com> <4E2F3A00.7060404@freebsd.org> <20110726221846.GE22861@luke.xen.prgmr.com> Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 Jul 2011 16:40:25 -0700 Message-ID: <1311723625.3927.22.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD 8, PV i386 VNC fails? 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, 26 Jul 2011 23:40:35 -0000 On Tue, 2011-07-26 at 15:18 -0700, Luke S. Crawford wrote: > On Tue, Jul 26, 2011 at 03:04:48PM -0700, Colin Percival wrote: > > On 07/26/11 14:48, Sean Bruno wrote: > > > Probably not doing it right. When I switched from pure HVM to PV on the > > > i386 VMs in the cluster, VNC stopped working all together. Did I do it > > > wrong? > > > > Is it possible to use PV with VNC? I thought under PV there wasn't any > > emulated console, just the Xen paravirtual console which lets you read > > and write characters as on a serial console. > > It's possible, redhat built a paravirtualized framebuffer to give > pv guests a framebuffer > > http://www.xen.org/files/xensummit_4/Xenpvfb07_Armbruster.pdf > > I imagine the problem is probably hypervisor dependent; I mean, > I don't know anyone who actually used the paravirtualized framebuffer, > so it's probably not well tested, and may suffer from bit rot as other > features are added to xen. I tested it, /I believe/ on rhel/centos 5.3. > _______________________________________________ I think that sort of makes sense to me. That is, there would need to be a PV framebuffer driver for PV mode to use it. I guess. Sean From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 23:43:37 2011 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 7693E106564A for ; Tue, 26 Jul 2011 23:43:37 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id 60CAA8FC0A for ; Tue, 26 Jul 2011 23:43:37 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6QNhWeT098742 for ; Tue, 26 Jul 2011 16:43:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311723812; bh=Dz+/0CJxkfTlwKH2VDEJtAf8+GHQxH0SzsFRf802g2s=; h=Subject:From:To:Content-Type:Date:Message-ID:Mime-Version: Content-Transfer-Encoding; b=Cla43IGwZfFU/lPlkM3Vphu4YbGl0z2lpEohDJFzVTItR78OsaGf8SZvqzwvP/yuW RhnAwf2R+ykrC5+0eCTsHT1W8cI75QWbfZm5YJy7YpoC/h16GNSi4wsbNo2m4up+N5 LC9AmpuvWq0denvKFJF+E3xU+Z3zN+c2r751oMAU= From: Sean Bruno To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 Jul 2011 16:43:31 -0700 Message-ID: <1311723811.3927.25.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Subject: FreeBSD 8, PV i386 Console 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, 26 Jul 2011 23:43:37 -0000 I can't quite tell what's happening (perhaps its ntpd and Xen something here), but this appears on the VM console about every 10 seconds. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. if the system is completely idle, I see: 26 Jul 15:56:02 ntpdate[543]: poll(): nfound = 0, error: Interrupted system call [XEN] hypervisor wallclock nudged; nudging TOD. thoughts? Sean From owner-freebsd-xen@FreeBSD.ORG Tue Jul 26 23:44:36 2011 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 503C8106564A for ; Tue, 26 Jul 2011 23:44:36 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0597F8FC08 for ; Tue, 26 Jul 2011 23:44:35 +0000 (UTC) Received: by vxg33 with SMTP id 33so1021020vxg.13 for ; Tue, 26 Jul 2011 16:44:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=gXa2nr+UrAQN0q0aRBNwiphXnYZ9vwRouIHWwqaf93s=; b=shTb/4UkkCN+Cxtc2FWJ8MT8yIwjMLEF5kTIuw5hqvuOCbxBakupqiiLRs/dQNxaCB Tjc1EoOYLJ/0N5SvHKO/A2qvm+8/Ee2HNV66vly2IHWXHfBGMYsIwdq+tMtEGd3WB/4j rNVXBscBA0bar8wsVC8rudy8siSnBaMS/cZwk= MIME-Version: 1.0 Received: by 10.52.175.100 with SMTP id bz4mr1242908vdc.174.1311723875157; Tue, 26 Jul 2011 16:44:35 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.188.101 with HTTP; Tue, 26 Jul 2011 16:44:35 -0700 (PDT) In-Reply-To: <1311723625.3927.22.camel@hitfishpass-lx.corp.yahoo.com> References: <1311716918.3927.20.camel@hitfishpass-lx.corp.yahoo.com> <4E2F3A00.7060404@freebsd.org> <20110726221846.GE22861@luke.xen.prgmr.com> <1311723625.3927.22.camel@hitfishpass-lx.corp.yahoo.com> Date: Wed, 27 Jul 2011 01:44:35 +0200 X-Google-Sender-Auth: 97pfJ-QB9GHlUAQuRlwYJ6BFKm4 Message-ID: From: "K. Macy" To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD 8, PV i386 VNC fails? 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, 26 Jul 2011 23:44:36 -0000 > > I think that sort of makes sense to me. That is, there would need to be > a PV framebuffer driver for PV mode to use it. I guess. Someone(TM) just needs to port the driver. FBs are fairly trivial to support. Cheers > Sean > > > _______________________________________________ > 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 Wed Jul 27 00:09:40 2011 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 9F60E1065670 for ; Wed, 27 Jul 2011 00:09:40 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id 8957F8FC13 for ; Wed, 27 Jul 2011 00:09:40 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6R09Beb006288 for ; Tue, 26 Jul 2011 17:09:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311725351; bh=F/qotvocw2Cqxa++z+4/32g4o3p7iVLDpGsLKMi4CTM=; h=Subject:From:To:Content-Type:Date:Message-ID:Mime-Version: Content-Transfer-Encoding; b=b3SwkUf5kwrCj+ja/gPCqKEUbRylEF1COQ2XQCzfpymJOBP8LHASVuVuqxr6+B8yu 6EdF5HOoASfWyKXJbM+nSe08HUAz6AQxf01m2eKnzwwJHY4mavBj/KWI1xoOFRieYj zbYV/Gc2EOGNU8htL3s75IZHdnoUXZB4hkFq0Qic= From: Sean Bruno To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 Jul 2011 17:09:10 -0700 Message-ID: <1311725350.3927.32.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Subject: Ok, so why is Sean whining so much today 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, 27 Jul 2011 00:09:40 -0000 I'm almost done building a test reference system in the Yahoo portion of the FreeBSD cluster. Nothing special, but I'm trying to get you folks some testing resources that are capable of being used for testing and development of Xen. The emails I'm sending are just the bits of things that I'm seeing fall out of a basic installation of 4 VMs (32/64bit version of 8/HEAD). Over the next few days I'll be "releasing" them for your general consumption and taking suggestions on what we should be doing with them. I'm hopeful that we can come up with some ideas to make the DomU code more accessible to end users. So, if you see things you'd like tested, or somewhere to run an idea, let use know on the clusteradm@ mail list and we'll take care of you. Sean From owner-freebsd-xen@FreeBSD.ORG Wed Jul 27 16:53:11 2011 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 DA49E106564A for ; Wed, 27 Jul 2011 16:53:11 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id C57088FC0C for ; Wed, 27 Jul 2011 16:53:11 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6RGqdVX002893 for ; Wed, 27 Jul 2011 09:52:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311785559; bh=LEsRPlEfkwgPH21l1Q58w+pQcE5ApGO8F+NUV9PD+nM=; h=Subject:From:To:Content-Type:Date:Message-ID:Mime-Version: Content-Transfer-Encoding; b=aCG1BxuACGbtEf9CkCwfzBOmiIupz0D0gLMbH3zbRaa7MQpKMw3xw8o+0tte54VaC R/Z6NxKBYhdBZt/Autpk+RE8pVFoRDyratuCGLnD9lAF8xTKOSw3GvCbeUVJ7r+yS6 xjI9RWeDYuTXxhOICPkVwAWvva3pWmWLWhu4HnBk= From: Sean Bruno To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Wed, 27 Jul 2011 09:52:39 -0700 Message-ID: <1311785559.2592.2.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Subject: FreeBSD 8, i386 PV panic at idle 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, 27 Jul 2011 16:53:11 -0000 Simple left my xen domu running over night. The console looks like this: rtc0: [XEN] xen_rtc_settime [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. [XEN] hypervisor wallclock nudged; nudging TOD. panic: HYPERVISOR_update_va_mapping(((unsigned long)(sysmaps->CADDR2)), (0x001 | 0x002 | xpmap_ptom(((m)->phys_addr)) | 0x020 | 0x040), UVMF_INVLPG| UVMF_ALL) < 0: /dumpster/scratch/sbruno-scratch/8/sys/i386/xen/pmap.c:3400 cpuid = 0 KDB: enter: panic [thread pid 61868 tid 100085 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> bt Tracing pid 61868 tid 100085 td 0xc3e0d2e0 kdb_enter(c0369837,c0369837,c03915fd,e1ae0acc,0,...) at kdb_enter+0x3a panic(c03915fd,c0398e3e,c039848a,d48,c05bc140,...) at panic+0x134 pmap_zero_page(c15d9038,e,0,40,e1ae0c14,...) at pmap_zero_page+0x112 vm_fault(c350e0ec,bf7ee000,2,8,bf7eed78,...) at vm_fault+0x1201 dblfault_handler() at dblfault_handler+0x4d7 --- trap 0x17, eip = 0, esp = 0, ebp = 0 --- The Dom0 has the following on its console: entOS release 5.6 (Final) Kernel 2.6.18-238.12.1.el5xen on an x86_64 xen1.freebsd.org login: (XEN) mm.c:2315:d146 Bad type (saw 4800000000000002 != exp e000000000000000) for mfn 1269f1 (pfn 25d7a) (XEN) mm.c:807:d146 Error getting mfn 1269f1 (pfn 25d7a) from L1 entry 00000001269f1063 for l1e_owner=146, pg_owner=146 DomU config: #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================ #---------------------------------------------------------------------------- # Kernel image file. #kernel = "/usr/lib/xen/boot/hvmloader" kernel = "/var/virt/freebsd-8-stable-i386-domu-kernel" #---------------------------------------------------------------------------- # device model to use: only qemu-dm available for now #device_model = '/usr/lib64/xen/bin/qemu-dm' #builder='hvm' # Initial memory allocation (in megabytes) for the new domain. memory = 855 # number of CPUS vcpus = 1 # A name for your domain. All domains must have different names. name = "ref8-xen32" arch = "i386" #Network interface. By default emules a realtek 8139. For a NetBSD guest you # have to disable re(4) and let rtk attach to use it. # ne2k_pci emulates a pci ne2000 clone; this his cpu-hungry in dom0 # pcnet emulates a AMD PCnet-PCI controller; but it corrupts packets with # pcn(4) under NetBSD. #vif = [ 'mac=00:16:3e:00:00:01, bridge=xenbr0, type=ioemu' ] vif = [ 'mac=00:16:3e:00:00:01, bridge=xenbr0, type=vbd' ] # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. # For hvm domains you can only use hda to hdd. You can set extra types # (e.g. cdrom) disk = [ 'file:/var/virt/FreeBSD-8.2-RELEASE-i386-disc1.iso,hdc:cdrom,r', 'file:/var/virt/ref8-xen32.bin,hda,w' ] extra = "vfs.root.mountfrom=ufs:/dev/ad0s1a" # floppy images; this doesn't seem to work currently. Use a iso image instead. #fda = '/home/domains/boot1.fs' # boot device: a = floppy, c= hard drive, d= cdrom (with the disk entry # before) # # boot CDROM image #boot='d' # boot from DISK file boot='c' # By default, 'xm create' will try to open an X window on the current display # for the virtal framebuffer. You can have the virtal framebuffer in vnc # instead, and connect using a vnc client (using localhost:$vncdisplay) # If vncunused is set to 1 (this is the default value), vncdisplay # will be set to the first unused port; so it's recommended to #vfb = [ "type = vnc, vncdisplay = 1, vncunused = 0, display = TEST" ] #Xen emulates a PS/2 mouse, but the pointer in the guest has difficulties # tracking the absolute position. Xen can emulate a USB tablet in addition # to the mouse which will report the absolute position of the pointer, # and make the mouse much easier to use. # usb=1 usbdevice='tablet' #usbdevice='mouse' serial='pty' on_reboot='restart' #============================================================================ From owner-freebsd-xen@FreeBSD.ORG Wed Jul 27 17:45:47 2011 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 77DA31065672 for ; Wed, 27 Jul 2011 17:45:47 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 515308FC15 for ; Wed, 27 Jul 2011 17:45:47 +0000 (UTC) Received: by pzk5 with SMTP id 5so8714266pzk.17 for ; Wed, 27 Jul 2011 10:45:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=G2enaJhQUSo68f6o/KyBWJ8z0iFJC6lylN49dLn7xAg=; b=t43NwXTSAwrT5b2xBwCYHPFupReczS9BY4l9iCyZUgo4GZSxWp7xenMHbyHAWD4QB5 bwk6WMwxHBMLJqyejZ11gOMsNbAOIN+9jfhSuZC7S5VmCK86knJ7uwDKwGXdKsfOs8fa Zc+Ngz1IIl0CpUQToApkxRGtSul9wt3qAtp48= MIME-Version: 1.0 Received: by 10.68.34.35 with SMTP id w3mr142626pbi.144.1311788746572; Wed, 27 Jul 2011 10:45:46 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.68.47.40 with HTTP; Wed, 27 Jul 2011 10:45:46 -0700 (PDT) In-Reply-To: <1311785559.2592.2.camel@hitfishpass-lx.corp.yahoo.com> References: <1311785559.2592.2.camel@hitfishpass-lx.corp.yahoo.com> Date: Wed, 27 Jul 2011 19:45:46 +0200 X-Google-Sender-Auth: qhYK1cYPq6koPRDTkH2hKrXSRFk Message-ID: From: "K. Macy" To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD 8, i386 PV panic at idle 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, 27 Jul 2011 17:45:47 -0000 It is possible to grab a coredump through xen. That would simplify diagnosis. I also wrote a patch to gdbserver that allowed one to treat a running VM or a core as a process. Cheers On Wed, Jul 27, 2011 at 6:52 PM, Sean Bruno wrote: > Simple left my xen domu running over night. =A0The console looks like > this: > rtc0: [XEN] xen_rtc_settime > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > [XEN] hypervisor wallclock nudged; nudging TOD. > panic: HYPERVISOR_update_va_mapping(((unsigned long)(sysmaps->CADDR2)), > (0x001 | 0x002 | xpmap_ptom(((m)->phys_addr)) | 0x020 | 0x040), > UVMF_INVLPG| UVMF_ALL) < > 0: /dumpster/scratch/sbruno-scratch/8/sys/i386/xen/pmap.c:3400 > cpuid =3D 0 > KDB: enter: panic > [thread pid 61868 tid 100085 ] > Stopped at =A0 =A0 =A0kdb_enter+0x3a: movl =A0 =A0$0,kdb_why > db> bt > Tracing pid 61868 tid 100085 td 0xc3e0d2e0 > kdb_enter(c0369837,c0369837,c03915fd,e1ae0acc,0,...) at kdb_enter+0x3a > panic(c03915fd,c0398e3e,c039848a,d48,c05bc140,...) at panic+0x134 > pmap_zero_page(c15d9038,e,0,40,e1ae0c14,...) at pmap_zero_page+0x112 > vm_fault(c350e0ec,bf7ee000,2,8,bf7eed78,...) at vm_fault+0x1201 > dblfault_handler() at dblfault_handler+0x4d7 > --- trap 0x17, eip =3D 0, esp =3D 0, ebp =3D 0 --- > > > The Dom0 has the following on its console: > entOS release 5.6 (Final) > Kernel 2.6.18-238.12.1.el5xen on an x86_64 > > xen1.freebsd.org login: (XEN) mm.c:2315:d146 Bad type (saw > 4800000000000002 !=3D exp e000000000000000) for mfn 1269f1 (pfn 25d7a) > (XEN) mm.c:807:d146 Error getting mfn 1269f1 (pfn 25d7a) from L1 entry > 00000001269f1063 for l1e_owner=3D146, pg_owner=3D146 > > > > DomU config: > #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > # Python configuration setup for 'xm create'. > # This script sets the parameters used when a domain is created using > 'xm create'. > # You use a separate script for each domain you want to create, or > # you can set the parameters for the domain on the xm command line. > #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > > #------------------------------------------------------------------------= ---- > # Kernel image file. > #kernel =3D "/usr/lib/xen/boot/hvmloader" > kernel =3D "/var/virt/freebsd-8-stable-i386-domu-kernel" > > #------------------------------------------------------------------------= ---- > # device model to use: only qemu-dm available for now > #device_model =3D '/usr/lib64/xen/bin/qemu-dm' > > #builder=3D'hvm' > > # Initial memory allocation (in megabytes) for the new domain. > memory =3D 855 > > # number of CPUS > vcpus =3D 1 > > # A name for your domain. All domains must have different names. > name =3D "ref8-xen32" > arch =3D "i386" > > #Network interface. By default emules a realtek 8139. For a NetBSD guest > you > # have to disable re(4) and let rtk attach to use it. > # ne2k_pci emulates a pci ne2000 clone; this his cpu-hungry in dom0 > # pcnet emulates a AMD PCnet-PCI controller; but it corrupts packets > with > # pcn(4) under NetBSD. > #vif =3D [ 'mac=3D00:16:3e:00:00:01, bridge=3Dxenbr0, type=3Dioemu' ] > vif =3D [ 'mac=3D00:16:3e:00:00:01, bridge=3Dxenbr0, type=3Dvbd' ] > > # Define the disk devices you want the domain to have access to, and > # what you want them accessible as. > # Each disk entry is of the form phy:UNAME,DEV,MODE > # where UNAME is the device, DEV is the device name the domain will see, > # and MODE is r for read-only, w for read-write. > # For hvm domains you can only use hda to hdd. You can set extra types > # (e.g. cdrom) > > disk =3D [ > =A0 =A0 =A0 =A0'file:/var/virt/FreeBSD-8.2-RELEASE-i386-disc1.iso,hdc:cdr= om,r', > =A0 =A0 =A0 =A0'file:/var/virt/ref8-xen32.bin,hda,w' > =A0 =A0 =A0 =A0] > > extra =3D "vfs.root.mountfrom=3Dufs:/dev/ad0s1a" > # floppy images; this doesn't seem to work currently. Use a iso image > instead. > #fda =3D '/home/domains/boot1.fs' > > # boot device: a =3D floppy, c=3D hard drive, d=3D cdrom (with the disk e= ntry > # before) > # > # boot CDROM image > #boot=3D'd' > # boot from DISK file > boot=3D'c' > > # By default, 'xm create' will try to open an X window on the current > display > # for the virtal framebuffer. You can have the virtal framebuffer in vnc > # instead, and connect using a vnc client (using localhost:$vncdisplay) > # If vncunused is set to 1 (this is the default value), vncdisplay > # will be set to the first unused port; so it's recommended to > #vfb =3D [ "type =3D vnc, vncdisplay =3D 1, vncunused =3D 0, display =3D = TEST" =A0] > > #Xen emulates a PS/2 mouse, but the pointer in the guest has > difficulties > # tracking the absolute position. Xen can emulate a USB tablet in > addition > # to the mouse which will report the absolute position of the pointer, > # and make the mouse much easier to use. > # > usb=3D1 > usbdevice=3D'tablet' > #usbdevice=3D'mouse' > > serial=3D'pty' > on_reboot=3D'restart' > #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > > > > _______________________________________________ > 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 Jul 28 16:20:38 2011 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 2457A106566C for ; Thu, 28 Jul 2011 16:20:38 +0000 (UTC) (envelope-from rmas@masxort.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id DAB518FC18 for ; Thu, 28 Jul 2011 16:20:37 +0000 (UTC) Received: by qwc9 with SMTP id 9so2010083qwc.13 for ; Thu, 28 Jul 2011 09:20:37 -0700 (PDT) Received: by 10.224.213.135 with SMTP id gw7mr162881qab.153.1311868146645; Thu, 28 Jul 2011 08:49:06 -0700 (PDT) Received: from RafaelMasPC ([208.67.166.179]) by mx.google.com with ESMTPS id 1sm752066qcy.31.2011.07.28.08.49.04 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Jul 2011 08:49:05 -0700 (PDT) From: "Rafael Mas" To: Date: Thu, 28 Jul 2011 11:49:14 -0400 Message-ID: <01e201cc4d3d$e733d7a0$b59b86e0$@com> MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_000_01E3_01CC4D1C.602237A0" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcxNPeaZvx/K2INVRiK/5NTJHWFYUQ== Content-Language: en-us X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: I am trying to install freebsd on Centos 5.6 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: Thu, 28 Jul 2011 16:20:38 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_01E3_01CC4D1C.602237A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Reader, =20 I am new to this list, and also to the installation of Freebsd on a Virtualez Xen box running on Centos 5.6. I am trying to find the proper documentation or tutorial to get this done, and I would like you to = guide me with some good tutorials that I can read to get this project accomplish = for my current company. I will appreciate all your help on this important matter. =20 Thank you for your reading time, and look forward for some good advice. =20 Best wishes and regards. =20 __________________________ Rafael Manuel M=E1s Rivero Sr. Systems Administrator enflyer_215 Phone: 954-455-6000 X809 Cell: 305-741-3324 WEB: www.enflyer.com =20 This information is private and confidential and intended for the = recipient only. If you are not the intended recipient of this message you are = hereby informed that you shall notify the sender immediately and delete the message. Dissemination, distribution or copying of this message is = strictly prohibited. ENSPOT. is entitled to complete the corresponding legal = actions against people that access unlawfully to the content of the messages = that have been sent from any of the companies within the structure of ENSPOT. This communication is for information purposes only and should not be regarded as an official statement from ENSPOT. Email transmission cannot = be guaranteed to be secure. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. This email = has been scanned by our Antivirus system =20 ------=_NextPart_000_01E3_01CC4D1C.602237A0-- From owner-freebsd-xen@FreeBSD.ORG Thu Jul 28 18:07:34 2011 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 783361065676 for ; Thu, 28 Jul 2011 18:07:34 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id 61AFE8FC1F for ; Thu, 28 Jul 2011 18:07:34 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6SI7RRw071085; Thu, 28 Jul 2011 11:07:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311876447; bh=ZaPaD/YmrYqy8NI2pvddXrnnJ8rt561gQ71M22jTqSU=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=ROAHg6MLwFrbYemBXhuuHei0c/4NLKQsaltVykpin+YECeFFiHdOYcdkJZT2CB/ay oTt6EGDKITXrtFZZnIgvCrla9s78C+b3uFNMcXKFM5Q33fkcEvNPVhq7nrJsXKHdJq 1mNxG3mjVH+S533rx0N40qTgGUbYST8EZXKyeQqY= From: Sean Bruno To: Rafael Mas In-Reply-To: <01e201cc4d3d$e733d7a0$b59b86e0$@com> References: <01e201cc4d3d$e733d7a0$b59b86e0$@com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 28 Jul 2011 11:07:27 -0700 Message-ID: <1311876447.2593.3.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" Subject: Re: I am trying to install freebsd on Centos 5.6 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: Thu, 28 Jul 2011 18:07:34 -0000 On Thu, 2011-07-28 at 08:49 -0700, Rafael Mas wrote: > Dear Reader, > > > > I am new to this list, and also to the installation of Freebsd on a > Virtualez Xen box running on Centos 5.6. I am trying to find the proper > documentation or tutorial to get this done, and I would like you to guide me > with some good tutorials that I can read to get this project accomplish for > my current company. I will appreciate all your help on this important > matter. > Good question. How far did you get and what problems are you experiencing? Sean From owner-freebsd-xen@FreeBSD.ORG Thu Jul 28 18:43:00 2011 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 3B8281065673 for ; Thu, 28 Jul 2011 18:43:00 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2-b.corp.re1.yahoo.com (mrout2-b.corp.re1.yahoo.com [69.147.107.21]) by mx1.freebsd.org (Postfix) with ESMTP id F24CB8FC16 for ; Thu, 28 Jul 2011 18:42:59 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2-b.corp.re1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6SIgagh083521; Thu, 28 Jul 2011 11:42:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311878556; bh=aws9f2RcNyjXiDRE6qcW95pQFDahx7nkLZ4MxHK47xo=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=mREJrmVG51CRzAaBEi6YIajRz3WoQk8pUK4+v0T47QrBChq7Xt22Yv98PQIRsG3LV plaxDQnbloi6mX8MJcODfR3AGWI2A5DviNwSBCz6ofSmYKWfvNdfSbNncm/txlFKug 2xZKxAoKekIoEbUbkMEHDCD4eJVA2Gp1A0RLN4f0= From: Sean Bruno To: Rafael Mas In-Reply-To: <024b01cc4d55$8ff04970$afd0dc50$@com> References: <01e201cc4d3d$e733d7a0$b59b86e0$@com> <1311876447.2593.3.camel@hitfishpass-lx.corp.yahoo.com> <024b01cc4d55$8ff04970$afd0dc50$@com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 28 Jul 2011 11:42:35 -0700 Message-ID: <1311878555.2593.4.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" Subject: RE: I am trying to install freebsd on Centos 5.6 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: Thu, 28 Jul 2011 18:43:00 -0000 Can you post the following? domU xen config for your VM the output of "ifconfig -a" on the domU the output of "uname -a" on the domU Sean On Thu, 2011-07-28 at 11:38 -0700, Rafael Mas wrote: > Dear Sean, Readers > > I am having problems right now... :( > > I was using the Kernel-Xen ver (3.1.2-238-9.1.el5) that is updated from the Centos-Base repo automatically. Reading some forum post on Xen, I decided to update the Xen to its latest Xen version 4.1.1 using a repo http://www.gitco.de/repo/GITCO-XEN4.1.1_x86_64.repo now, the machine starts but without starting any network interface it complains that IRQ Type mismatch when I try to ifup eth1 or 0. I am not sure if this is because changes on the Xen itself or ? . The sad part of this , is that this is one of my production servers. Have anyone have this kind of issue before with this repo ?, can it be solved without reinstalling/repairing the Linux Kernel ? > > I've attached a picture on this email with the specs of the error, any input will be super appreciated. > > Best Regards, > > > -----Original Message----- > From: Sean Bruno [mailto:seanbru@yahoo-inc.com] > Sent: Thursday, July 28, 2011 2:07 PM > To: Rafael Mas > Cc: freebsd-xen@freebsd.org > Subject: Re: I am trying to install freebsd on Centos 5.6 > > On Thu, 2011-07-28 at 08:49 -0700, Rafael Mas wrote: > > Dear Reader, > > > > > > > > I am new to this list, and also to the installation of Freebsd on a > > Virtualez Xen box running on Centos 5.6. I am trying to find the proper > > documentation or tutorial to get this done, and I would like you to guide me > > with some good tutorials that I can read to get this project accomplish for > > my current company. I will appreciate all your help on this important > > matter. > > > > > Good question. How far did you get and what problems are you > experiencing? > > Sean > From owner-freebsd-xen@FreeBSD.ORG Sat Jul 30 00:36:45 2011 Return-Path: Delivered-To: xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C8901065672 for ; Sat, 30 Jul 2011 00:36:45 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id 177BF8FC13 for ; Sat, 30 Jul 2011 00:36:45 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6U0OPg9098957; Fri, 29 Jul 2011 17:24:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311985465; bh=FvZYZ0sRyoAiNWNbzo5VPvfbkoLTixRG0wvF3R6faj0=; h=Subject:From:To:Cc:Content-Type:Date:Message-ID:Mime-Version: Content-Transfer-Encoding; b=DsNeX27BadzM/Mp84NLkI7a4OhDLqlU0eQMtW1VGtAbmKTgyGZ1uHmQ9gN0WLLdB4 ZBJzYfJ16x16par3HoLTJxF2O5gCZcYRtTSP0EEY8pNDO2p+yZXe8ebB0YiVQzpyQi FXr+PQvlj4ZiTe19ngZc+OWYUmyZSzza8Zy5IsQE= From: Sean Bruno To: xen@freebsd.org Content-Type: text/plain; charset="UTF-8" Date: Fri, 29 Jul 2011 17:24:25 -0700 Message-ID: <1311985465.2531.12.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 8bit Cc: Alexander Motin Subject: HVM boot fail, BETA-1 and current 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, 30 Jul 2011 00:36:45 -0000 Tried to boot up an BETA-1 XENHVM kernel today, apparently CAMATA doesn't work in this environment. Let me know if you want access to this VM as its in the cluster and I can trivially get you on the machine. /boot.config: -Dh Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS 639kB/2096128kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (root@farrell.cse.buffalo.edu, Thu Jul 28 16:09:55 UTC 2011) Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0xbb97c0 data=0x1431d0+0x2bc450 syms=[0x8 +0x110da8+0x8+0xf8650] - ______ ____ _____ _____ | ____| | _ \ / ____| __ \ | |___ _ __ ___ ___ | |_) | (___ | | | | | ___| '__/ _ \/ _ \| _ < \___ \| | | | | | | | | __/ __/| |_) |____) | |__| | | | | | | | || | | | |_| |_| \___|\___||____/|_____/|_____/ ``` ` s` `.....---.......--.``` -/ �������������Welcome to FreeBSD���������� � +o .--` /y:` +. � � yo`:. :o ` +- � 1. Boot [ENTER] � y/ -/` -o/ � 2. [Esc]ape to loader prompt � .- ::/sy +:. � 3. Reboot � / `-- / � � `: :` � Options: � `: :` � 4. [A]CPI Support: Enabled � / / � 5. Boot Safe [M]ode: NO � .- -. � 6. Boot [S]ingle User: NO � -- -. � 7. Boot [V]erbose: NO � `:` `:` � � .-- `--. � � .---.....----. ���������������������������������������� � GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb SMAP type=01 base=0000000000000000 len=000000000009fc00 SMAP type=02 base=000000000009fc00 len=0000000000000400 SMAP type=02 base=00000000000e0000 len=0000000000020000 SMAP type=01 base=0000000000100000 len=000000007ff00000 SMAP type=02 base=00000000fc000000 len=0000000004000000 Table 'FACP' at 0xfc005ee0 Table 'APIC' at 0xfc005fe0 APIC: Found table at 0xfc005fe0 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 2 ACPI ID 1: enabled SMP: Added CPU 2 (AP) Copyright (c) 1992-2011 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-BETA1 #0 r224482M: Fri Jul 29 16:42:18 PDT 2011 root@ref9-xen64.freebsd.org:/usr/obj/dumpster/scratch/sbruno-scratch/head/sys/XENHVM amd64 WARNING: WITNESS option enabled, expect reduced performance. Table 'FACP' at 0xfc005ee0 Table 'APIC' at 0xfc005fe0 ACPI: No SRAT table found Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff815c4000. Hypervisor: Origin = "XenVMMXenVMM" Calibrating TSC clock ... TSC clock: 2493823785 Hz CPU: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (2493.82-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x10676 Family = 6 Model = 17 Stepping = 6 Features=0x1781fbff Features2=0x80082201 AMD Features=0x20100800 AMD Features2=0x1 real memory = 2147483648 (2048 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) 0x00000000015f3000 - 0x000000007c38ffff, 2061094912 bytes (503197 pages) avail memory = 2045038592 (1950 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: INTR: Adding local APIC 2 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 x86bios: IVT 0x000000-0x0004ff at 0xfffffe0000000000 x86bios: SSEG 0x001000-0x001fff at 0xffffff800020d000 x86bios: EBDA 0x09f000-0x09ffff at 0xfffffe000009f000 x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe00000a0000 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 ULE: setup cpu 0 ULE: setup cpu 1 ACPI: RSDP 0xea020 00024 (v02 Xen) ACPI: XSDT 0xfc006050 00034 (v01 Xen HVM 00000000 HVML 00000000) ACPI: FACP 0xfc005ee0 000F4 (v04 Xen HVM 00000000 HVML 00000000) ACPI: DSDT 0xfc002c40 0321F (v02 Xen HVM 00000000 INTL 20090220) ACPI: FACS 0xfc002c00 00040 ACPI: APIC 0xfc005fe0 00070 (v02 Xen HVM 00000000 HVML 00000000) MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 1 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 5, irq 5 ioapic0: intpin 5 trigger: level ioapic0: intpin 5 polarity: low MADT: Interrupt override: source 10, irq 10 ioapic0: intpin 10 trigger: level ioapic0: intpin 10 polarity: low MADT: Interrupt override: source 11, irq 11 ioapic0: intpin 11 trigger: level ioapic0: intpin 11 polarity: low MADT: Forcing active-low polarity and level trigger for SCI ioapic0: intpin 9 polarity: low ioapic0: intpin 9 trigger: level ioapic0 irqs 0-47 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 Event-channel device installed. wlan: <802.11 Link Layer> kbd: new array size 4 kbd1 at kbdmux0 mem: nfslock: pseudo-device null: random: io: hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 acpi0: on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed ACPI timer: 1/1 1/0 1/1 1/1 1/0 1/1 1/1 1/0 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x1f48-0x1f4b on acpi0 cpu0: on acpi0 cpu0: switching to generic Cx mode cpu1: on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 10 11 Validation 0 10 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 10 11 Validation 0 11 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 10 11 Validation 0 5 N 0 5 10 11 After Disable 0 255 N 0 5 10 11 pcib0: port 0xcf8-0xcff on acpi0 pcib0: decoding 4 range 0-0xcf7 pcib0: decoding 4 range 0xd00-0xffff pcib0: decoding 3 range 0xa0000-0xbffff pcib0: decoding 3 range 0xf0000000-0xfbffffff pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x1237, revid=0x02 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7000, revid=0x00 domain=0, bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7010, revid=0x00 domain=0, bus=0, slot=1, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1 pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1 pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1 pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1 map[20]: type I/O Port, range 32, base 0xc120, size 4, enabled pcib0: allocated type 4 (0xc120-0xc12f) for rid 20 of pci0:0:1:1 found-> vendor=0x8086, dev=0x7020, revid=0x01 domain=0, bus=0, slot=1, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=5 map[20]: type I/O Port, range 32, base 0xc100, size 5, enabled pcib0: allocated type 4 (0xc100-0xc11f) for rid 20 of pci0:0:1:2 pcib0: matched entry for 0.1.INTD pcib0: slot 1 INTD hardwired to IRQ 23 found-> vendor=0x8086, dev=0x7113, revid=0x01 domain=0, bus=0, slot=1, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0004, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 pcib0: matched entry for 0.1.INTA pcib0: slot 1 INTA hardwired to IRQ 20 found-> vendor=0x1013, dev=0x00b8, revid=0x00 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type Prefetchable Memory, range 32, base 0xf0000000, size 25, enabled pcib0: allocated type 3 (0xf0000000-0xf1ffffff) for rid 10 of pci0:0:2:0 map[14]: type Memory, range 32, base 0xf3000000, size 12, enabled pcib0: allocated type 3 (0xf3000000-0xf3000fff) for rid 14 of pci0:0:2:0 found-> vendor=0x5853, dev=0x0001, revid=0x01 domain=0, bus=0, slot=3, func=0 class=ff-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[10]: type I/O Port, range 32, base 0xc000, size 8, enabled pcib0: allocated type 4 (0xc000-0xc0ff) for rid 10 of pci0:0:3:0 map[14]: type Prefetchable Memory, range 32, base 0xf2000000, size 24, enabled pcib0: allocated type 3 (0xf2000000-0xf2ffffff) for rid 14 of pci0:0:3:0 pcib0: matched entry for 0.3.INTA pcib0: slot 3 INTA hardwired to IRQ 28 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc120-0xc12f at device 1.1 on pci0 ata0: on atapci0 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 49 ata1: on atapci0 ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 50 uhci0: port 0xc100-0xc11f irq 23 at device 1.2 on pci0 ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 0 vector 51 usbus0: controller did not stop usbus0: on uhci0 usbus0: bpf attached uhci0: usbpf: Attached pci0: at device 1.3 (no driver attached) vgapci0: mem 0xf0000000-0xf1ffffff,0xf3000000-0xf3000fff at device 2.0 on pci0 xenpci0: port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 xenpci0: Xen version 3.4. ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 0 vector 52 xenstore0: on xenpci0 Grant table initialized attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 53 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 atrtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 54 Event timer "RTC" frequency 32768 Hz quality 0 psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0061 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 55 atkbd0: [GIANT-LOCKED] psm0: current command byte:0061 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 56 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 57 uart0: fast interrupt uart0: console (9600,n,8,1) ppc0: using extended I/O port range ppc0: SPP ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ioapic0: routing intpin 7 (ISA IRQ 7) to lapic 0 vector 58 ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 acpi0: wakeup code va 0xffffff800032f000 pa 0x4000 ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 1: ioport 0x1c00 alloc failed ahc_isa_probe 2: ioport 0x2c00 alloc failed ahc_isa_probe 3: ioport 0x3c00 alloc failed ahc_isa_probe 4: ioport 0x4c00 alloc failed ahc_isa_probe 5: ioport 0x5c00 alloc failed ahc_isa_probe 6: ioport 0x6c00 alloc failed ahc_isa_probe 7: ioport 0x7c00 alloc failed ahc_isa_probe 8: ioport 0x8c00 alloc failed ahc_isa_probe 9: ioport 0x9c00 alloc failed ahc_isa_probe 10: ioport 0xac00 alloc failed ahc_isa_probe 11: ioport 0xbc00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ahc_isa_probe 13: ioport 0xdc00 alloc failed ahc_isa_probe 14: ioport 0xec00 alloc failed ex_isa_identify() pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 isa_probe_children: disabling PnP devices atkbdc: atkbdc0 already exists; skipping it atrtc: atrtc0 already exists; skipping it attimer: attimer0 already exists; skipping it fdc: fdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sc: sc0 already exists; skipping it uart: uart0 already exists; skipping it isa_probe_children: probing non-PnP devices sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 uart1: failed to probe at port 0x2f8-0x2ff irq 3 on isa0 isa_probe_children: probing PnP devices Device configuration finished. procfs registered lapic: Divisor 2, Frequency 52732026 Hz Timecounters tick every 10.000 msec vlan: initialized, using hash tables with chaining usbus0: 12Mbps Full Speed USB v1.0 lo0: bpf attached hptrr: no controller detected. xenbusb_front0: on xenstore0 ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ugen0.1: at usbus0 uhub0: on usbus0 ata0: stat0=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x0 ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0xff msb=0xff ata1: reset tp2 stat0=00 stat1=00 devices=0x10000 (aprobe0:ata1:0:0:0): SIGNATURE: eb14 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: Serial Number QM00003 cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: cd present [310822 x 2048 byte records] xn0: at device/vif/0 on xenbusb_front0 xn0: bpf attached xn0: Ethernet address: 00:16:3e:00:00:04 GEOM: new disk cd0 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 pass0 at ata1 bus 0 scbus1 target 0 lun 0 pass0: Removable CD-ROM SCSI-0 device pass0: Serial Number QM00003 pass0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) xbd0: 607MB at device/vbd/5632 on xenbusb_front0 xbd0: attaching as ad2 xbd1: 10240MB at device/vbd/768 on xenbusb_front0 xbd1: attaching as ad0 SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x02000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 TSC timecounter discards lower 8 bit(s) Timecounter "TSC-low" frequency 9741499 Hz quality -100 WARNING: WITNESS option enabled, expect reduced performance. uhub0: 2 ports with 2 removable, self powered GEOM: new disk ad2 GEOM: new disk ad0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.2: at usbus0 ums0: on usbus0 ums0: 3 buttons and [Z] coordinates ID=0 Trying to mount root from ufs:/dev/ada0p2 [rw]... mountroot: waiting for device /dev/ada0p2 ... Mounting from ufs:/dev/ada0p2 failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/ada0p2 vfs.root.mountfrom.options=rw Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> From owner-freebsd-xen@FreeBSD.ORG Sat Jul 30 00:44:13 2011 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 B6F531065675; Sat, 30 Jul 2011 00:44:13 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2-b.corp.re1.yahoo.com (mrout2-b.corp.re1.yahoo.com [69.147.107.21]) by mx1.freebsd.org (Postfix) with ESMTP id 33DBA8FC1A; Sat, 30 Jul 2011 00:44:13 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2-b.corp.re1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p6U0hmqn019812; Fri, 29 Jul 2011 17:43:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1311986629; bh=nQj3miihxcaXdWD9ZmBY3qYv8LvM9PtIB/GuX2zs91s=; h=Subject:From:To:Cc:Content-Type:Date:Message-ID:Mime-Version: Content-Transfer-Encoding; b=SEeDYraiJ/rj2Ko560bACUY7XYfpP3GGKMqZeEZB5zVqpBGg1zbEdHm2RI3BzHS0d xP+HH2C+qEB0PWovXubCVcjYgkOg5ZKQTKid6eN46TItvU7JomLClFl20ZT4XQ2SgO 8pUvYjuN2fQTRpK1BU5xYqPen5kWg0VxaxKKrDpU= From: Sean Bruno To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Fri, 29 Jul 2011 17:43:48 -0700 Message-ID: <1311986628.2531.15.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Cc: Subject: BETA-1 NFS not working, Xen PV i386 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, 30 Jul 2011 00:44:13 -0000 Doesn't make a lot of sense here, but building with the i386 XEN kernel config yields the following boot up in PV mode. Odd ... it looks like i386/XEN needs: options NFSCL # New Network Filesystem Client Sean Using config file "./ref9-xen32". Started domain ref9-xen32 (id=38) WARNING: loader(8) metadata is missing! GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2011 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-BETA1 #0 r224482M: Fri Jul 29 13:34:25 PDT 2011 root@ref9-xen32.freebsd.org:/usr/obj/dumpster/scratch/sbruno-scratch/head/sys/XEN i386 WARNING: WITNESS option enabled, expect reduced performance. Xen reported: 2493.756 MHz processor. Timecounter "ixen" frequency 1953125 Hz quality 0 CPU: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (2493.76-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x10676 Family = 6 Model = 17 Stepping = 6 Features=0xbfe3fbff Features2=0xce3bd AMD Features=0x20100000 AMD Features2=0x1 real memory = 805306368 (768 MB) avail memory = 777121792 (741 MB) [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) [XEN] xen_rtc_probe: probing Hypervisor RTC clock rtc0: on motherboard [XEN] xen_rtc_attach: attaching Hypervisor RTC clock xenstore0: on motherboard xc0: on motherboard Event timer "ixen" quality 600 Timecounters tick every 10.000 msec xenbusb_front0: on xenstore0 [XEN] hypervisor wallclock nudged; nudging TOD. xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:00:00:03 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 xbd0: 497MB at device/vbd/5632 on xenbusb_front0 xbd0: attaching as ad2 xbd1: 10240MB at device/vbd/768 on xenbusb_front0 xbd1: attaching as ad0 Timecounter "TSC" frequency 2493756000 Hz quality 800 WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad0p2 []... WARNING: / was not properly dismounted rtc0: [XEN] xen_rtc_gettime rtc0: [XEN] xen_rtc_gettime: wallclock 1311892419 sec; 132269700 nsec rtc0: [XEN] xen_rtc_gettime: uptime 94008 sec; 379306109 nsec rtc0: [XEN] xen_rtc_gettime: TOD 1311986427 sec; 511575809 nsec Setting hostuuid: 1c127834-ab5a-c2e4-7b24-5ea29d364d9d. Setting hostid: 0xdea9fbfd. Entropy harvesting: interrupts ethernet point_to_point kickstart. Starting file system checks: ** SU+J Recovering /dev/ad0p2 ** Reading 33554432 byte journal from inode 4. ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. ***** FILE SYSTEM MARKED CLEAN ***** Mounting local file systems:. Setting hostname: ref9-xen32.freebsd.org. xn0: link state changed to DOWN xn0: link state changed to UP Starting Network: lo0 xn0. lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 xn0: flags=8843 metric 0 mtu 1500 options=503 ether 00:16:3e:00:00:03 nd6 options=29 media: Ethernet manual status: active Starting devd. DHCPREQUEST on xn0 to 255.255.255.255 port 67 DHCPACK from 69.147.83.62 bound to 69.147.83.99 -- renewal in 900 seconds. add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 add net fe80::: gateway ::1 add net ff02::: gateway ::1 kldload: can't load nfscl: File exists /etc/rc: WARNING: Unable to load kernel module nfscl ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout Creating and/or trimming log files. Starting syslogd. No core dumps found. Setting date via ntp. rtc0: [XEN] xen_rtc_settime 29 Jul 17:40:33 ntpdate[585]: step time server 69.147.83.54 offset -25202.462526 sec kldload: can't load nfscl: File exists /etc/rc: WARNING: Unable to load kernel module nfscl Setting NIS domain: freebsd. Starting rpcbind. Starting ypbind. Clearing /tmp (X related). Updating motd:. Mounting late file systems:mount_nfs: nfscl is not available mount_nfs: nfscl is not available mount_nfs: nfscl is not available . Mounting /etc/fstab filesystems failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Jul 29 17:40:34 ref9-xen32 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: From owner-freebsd-xen@FreeBSD.ORG Sat Jul 30 11:19:44 2011 Return-Path: Delivered-To: xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AC401065670 for ; Sat, 30 Jul 2011 11:19:44 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id EFD548FC0C for ; Sat, 30 Jul 2011 11:19:43 +0000 (UTC) Received: by fxe4 with SMTP id 4so4216889fxe.13 for ; Sat, 30 Jul 2011 04:19:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=HEp6HvS4u9dTIeQc8+W/5aoWfz+K9aSxFF5y95ekpLA=; b=TD+IYytzQ+/h6rlPNq9dG0BVoxKf+g/IeXiw3UocBZiPxphN3WOtiX2B4WmsSLcuzM MORpTuTlZu2otzFztj6OkfR+4jaE8Hnr0sj42EmyJoGkbu9nF6wjI3Hv3HW3L9vY/eiL 57H5lBk159TIF4X/jwVcAtIT5RvAqXKl7j+Y0= Received: by 10.223.99.149 with SMTP id u21mr3269340fan.121.1312022983730; Sat, 30 Jul 2011 03:49:43 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id j18sm793515faa.22.2011.07.30.03.49.41 (version=SSLv3 cipher=OTHER); Sat, 30 Jul 2011 03:49:42 -0700 (PDT) Sender: Alexander Motin Message-ID: <4E33E1AD.6030404@FreeBSD.org> Date: Sat, 30 Jul 2011 13:49:17 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Sean Bruno References: <1311985465.2531.12.camel@hitfishpass-lx.corp.yahoo.com> In-Reply-To: <1311985465.2531.12.camel@hitfishpass-lx.corp.yahoo.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: xen@freebsd.org Subject: Re: HVM boot fail, BETA-1 and current 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, 30 Jul 2011 11:19:44 -0000 Hi. Sean Bruno wrote: > Tried to boot up an BETA-1 XENHVM kernel today, apparently CAMATA > doesn't work in this environment. Let me know if you want access to this > VM as its in the cluster and I can trivially get you on the machine. Disks in XENHVM are usually not related to CAM. Once hypervisor detects use of PV drivers, it blocks disks detection via ATA emulation and exposes them as PV block devices. > xbd0: 607MB at device/vbd/5632 on xenbusb_front0 > xbd0: attaching as ad2 > xbd1: 10240MB at device/vbd/768 on xenbusb_front0 > xbd1: attaching as ad0 ... > GEOM: new disk ad2 > GEOM: new disk ad0 ... > Trying to mount root from ufs:/dev/ada0p2 [rw]... > mountroot: waiting for device /dev/ada0p2 ... > Mounting from ufs:/dev/ada0p2 failed with error 19. The only problem here is that xbd driver still tries to mimic old ATA device naming. Probably it should be fixed, but I don't see how to do it correctly. Its behavior with old ATA was closer, but IMHO was also not exactly correct. It could cause unit numbers collision if somebody decided to pass some PCI ATA controller inside the virtual machine. -- Alexander Motin