From owner-freebsd-xen@FreeBSD.ORG Mon Jan 11 00:13:55 2010 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 DECA7106566C for ; Mon, 11 Jan 2010 00:13:55 +0000 (UTC) (envelope-from admin@dmarkey.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id 834B68FC08 for ; Mon, 11 Jan 2010 00:13:55 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 16so399089fgg.13 for ; Sun, 10 Jan 2010 16:13:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.239.187.204 with SMTP id m12mr1602028hbh.160.1263166980361; Sun, 10 Jan 2010 15:43:00 -0800 (PST) Date: Sun, 10 Jan 2010 23:43:00 +0000 Message-ID: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> From: David To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: HVM paravirt block/nic drivers X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: admin@dmarkey.com List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2010 00:13:55 -0000 Hi Guys/Girls, Successfully got a FreeBSD 8 HVM DomU installed. I see its using the emulated block/nic drivers. Is there any work being done on writing paravirt drivers for FreeBSD in HVM? Regards, David From owner-freebsd-xen@FreeBSD.ORG Mon Jan 11 09:58:40 2010 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 1CC6F106566C for ; Mon, 11 Jan 2010 09:58:40 +0000 (UTC) (envelope-from James.Smith@m247.com) Received: from mx1.spambobby.com (mx1.spambobby.com [89.238.146.58]) by mx1.freebsd.org (Postfix) with ESMTP id D29DA8FC15 for ; Mon, 11 Jan 2010 09:58:39 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mx1.spambobby.com (Postfix) with ESMTP id 7680016A432; Mon, 11 Jan 2010 09:58:39 +0000 (GMT) X-Virus-Scanned: by SpamTitan at ohtele.com Received: from staffmail.openhosting.co.uk (unknown [89.238.157.212]) by mx1.spambobby.com (Postfix) with ESMTP id 4710016A42B; Mon, 11 Jan 2010 09:58:31 +0000 (GMT) Received: from office-server1.m247.local ([fe80::24e5:567:7196:3452]) by office-server1.m247.local ([fe80::24e5:567:7196:3452%10]) with mapi; Mon, 11 Jan 2010 09:56:13 +0000 From: James Smith To: "admin@dmarkey.com" , "freebsd-xen@freebsd.org" Date: Mon, 11 Jan 2010 09:56:12 +0000 Thread-Topic: HVM paravirt block/nic drivers Thread-Index: AcqSUsL9OXTsUlQ1So+m6ifGu9FtFAAUW5mA Message-ID: <32668C1E8A82284F873E88308362605713957F6726@office-server1.m247.local> References: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> In-Reply-To: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: HVM paravirt block/nic drivers 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, 11 Jan 2010 09:58:40 -0000 Hi, Have you compiled XENHVM kernel? It makes some improvements to networking.= Ensure you add the correct device to /etc/rc.conf afterwards, I believe i= t changes to "xn0" when running XENHVM. Regards, James Smith, -----Original Message----- From: owner-freebsd-xen@freebsd.org [mailto:owner-freebsd-xen@freebsd.org] = On Behalf Of David Sent: 10 January 2010 23:43 To: freebsd-xen@freebsd.org Subject: HVM paravirt block/nic drivers Hi Guys/Girls, Successfully got a FreeBSD 8 HVM DomU installed. I see its using the emulated block/nic drivers. Is there any work being done on writing paravirt drivers for FreeBSD in HVM? Regards, David _______________________________________________ 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 Mon Jan 11 11:00:49 2010 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 3A7751065670 for ; Mon, 11 Jan 2010 11:00:49 +0000 (UTC) (envelope-from admin@dmarkey.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id CD8418FC17 for ; Mon, 11 Jan 2010 11:00:48 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 19so2087475fgg.13 for ; Mon, 11 Jan 2010 03:00:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.239.167.83 with SMTP id f19mr435590hbe.34.1263207645779; Mon, 11 Jan 2010 03:00:45 -0800 (PST) In-Reply-To: <32668C1E8A82284F873E88308362605713957F6726@office-server1.m247.local> References: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6726@office-server1.m247.local> Date: Mon, 11 Jan 2010 11:00:45 +0000 Message-ID: <6894a6471001110300l7c9a53ber7d0ba706184d1c97@mail.gmail.com> From: David To: James Smith Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: Re: HVM paravirt block/nic drivers X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: admin@dmarkey.com List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2010 11:00:49 -0000 Well, im using the AMD64 ISO image, So i'll have to recompile the kernel? Are there instructions anywhere? Thanks. David 2010/1/11 James Smith > Hi, > > Have you compiled XENHVM kernel? It makes some improvements to networking. > Ensure you add the correct device to /etc/rc.conf afterwards, I believe it > changes to "xn0" when running XENHVM. > > Regards, > James Smith, > > -----Original Message----- > From: owner-freebsd-xen@freebsd.org [mailto:owner-freebsd-xen@freebsd.org] > On Behalf Of David > Sent: 10 January 2010 23:43 > To: freebsd-xen@freebsd.org > Subject: HVM paravirt block/nic drivers > > Hi Guys/Girls, > > > Successfully got a FreeBSD 8 HVM DomU installed. I see its using the > emulated block/nic drivers. > > Is there any work being done on writing paravirt drivers for FreeBSD in > HVM? > > Regards, > > David > _______________________________________________ > 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 Mon Jan 11 11:07:12 2010 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 F318110656D4 for ; Mon, 11 Jan 2010 11:07:12 +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 E2F678FC24 for ; Mon, 11 Jan 2010 11:07:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o0BB7CRL034843 for ; Mon, 11 Jan 2010 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o0BB7CbR034841 for freebsd-xen@FreeBSD.org; Mon, 11 Jan 2010 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 Jan 2010 11:07:12 GMT Message-Id: <201001111107.o0BB7CbR034841@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, 11 Jan 2010 11:07:13 -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/141328 xen [xen] [panic] gstat exit causes kernel panic from unma o kern/140313 xen [xen] [panic] FreeBSD8 RC2 as PV domU crashes during c o kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. o kern/135179 xen [xen] Xen domU does not properly reboot o kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i o kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all o kern/135008 xen [xen] FreeBSD-current/Xen timecounter jumps o kern/134926 xen [xen] [panic] FreeBSD-current Xen DomU networking pani 8 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Jan 11 11:07:59 2010 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 32AC110656A3 for ; Mon, 11 Jan 2010 11:07:59 +0000 (UTC) (envelope-from James.Smith@m247.com) Received: from mx1.spambobby.com (mx1.spambobby.com [89.238.146.58]) by mx1.freebsd.org (Postfix) with ESMTP id 99BBE8FC17 for ; Mon, 11 Jan 2010 11:07:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mx1.spambobby.com (Postfix) with ESMTP id D5E3A16A425; Mon, 11 Jan 2010 11:07:59 +0000 (GMT) X-Virus-Scanned: by SpamTitan at ohtele.com Received: from staffmail.openhosting.co.uk (unknown [89.238.157.212]) by mx1.spambobby.com (Postfix) with ESMTP id CD54916A479; Mon, 11 Jan 2010 11:07:51 +0000 (GMT) Received: from office-server1.m247.local ([fe80::24e5:567:7196:3452]) by office-server1.m247.local ([fe80::24e5:567:7196:3452%10]) with mapi; Mon, 11 Jan 2010 11:05:34 +0000 From: James Smith To: "admin@dmarkey.com" Date: Mon, 11 Jan 2010 11:05:34 +0000 Thread-Topic: HVM paravirt block/nic drivers Thread-Index: AcqSrQTeU4r3YrBWT3Oq8hgr9XStPgAAA5rg Message-ID: <32668C1E8A82284F873E88308362605713957F6730@office-server1.m247.local> References: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6726@office-server1.m247.local> <6894a6471001110300l7c9a53ber7d0ba706184d1c97@mail.gmail.com> In-Reply-To: <6894a6471001110300l7c9a53ber7d0ba706184d1c97@mail.gmail.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: RE: HVM paravirt block/nic drivers 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, 11 Jan 2010 11:07:59 -0000 Compile kernel in the normal way, using the XENHVM config. cd /usr/src make kernel XENHVM edit /etc/rc.conf Change network interface to re0, save and reboot. Regards, James Smith, From: David [mailto:admin@dmarkey.com] Sent: 11 January 2010 11:01 To: James Smith Cc: freebsd-xen@freebsd.org Subject: Re: HVM paravirt block/nic drivers Well, im using the AMD64 ISO image, So i'll have to recompile the kernel? Are there instructions anywhere? Thanks. David 2010/1/11 James Smith > Hi, Have you compiled XENHVM kernel? It makes some improvements to networking.= Ensure you add the correct device to /etc/rc.conf afterwards, I believe i= t changes to "xn0" when running XENHVM. Regards, James Smith, -----Original Message----- From: owner-freebsd-xen@freebsd.org [= mailto:owner-freebsd-xen@freebsd.org]= On Behalf Of David Sent: 10 January 2010 23:43 To: freebsd-xen@freebsd.org Subject: HVM paravirt block/nic drivers Hi Guys/Girls, Successfully got a FreeBSD 8 HVM DomU installed. I see its using the emulated block/nic drivers. Is there any work being done on writing paravirt drivers for FreeBSD in HVM? Regards, David _______________________________________________ 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 Mon Jan 11 11:53:39 2010 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 E4214106566C for ; Mon, 11 Jan 2010 11:53:38 +0000 (UTC) (envelope-from admin@dmarkey.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id 733208FC19 for ; Mon, 11 Jan 2010 11:53:38 +0000 (UTC) Received: by fxm10 with SMTP id 10so7657181fxm.14 for ; Mon, 11 Jan 2010 03:53:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.239.193.134 with SMTP id j6mr1669353hbi.26.1263210812195; Mon, 11 Jan 2010 03:53:32 -0800 (PST) In-Reply-To: <32668C1E8A82284F873E88308362605713957F6730@office-server1.m247.local> References: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6726@office-server1.m247.local> <6894a6471001110300l7c9a53ber7d0ba706184d1c97@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6730@office-server1.m247.local> Date: Mon, 11 Jan 2010 11:53:32 +0000 Message-ID: <6894a6471001110353s20b1e7a6o62fe625de5f8a47@mail.gmail.com> From: David To: James Smith Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: Re: HVM paravirt block/nic drivers X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: admin@dmarkey.com List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2010 11:53:39 -0000 install -o root -g wheel -m 555 zfs.ko /boot/kernel install -o root -g wheel -m 555 zfs.ko.symbols /boot/kernel ===> zlib (install) install -o root -g wheel -m 555 zlib.ko /boot/kernel install -o root -g wheel -m 555 zlib.ko.symbols /boot/kernel kldxref /boot/kernel make: don't know how to make XENHVM. Stop Any Idea? 2010/1/11 James Smith > Compile kernel in the normal way, using the XENHVM config. > > > > cd /usr/src > > make kernel XENHVM > > edit /etc/rc.conf > > > > Change network interface to re0, save and reboot. > > > > Regards, > > James Smith, > > *From:* David [mailto:admin@dmarkey.com] > *Sent:* 11 January 2010 11:01 > *To:* James Smith > *Cc:* freebsd-xen@freebsd.org > *Subject:* Re: HVM paravirt block/nic drivers > > > > Well, im using the AMD64 ISO image, > > > > So i'll have to recompile the kernel? Are there instructions anywhere? > > > > Thanks. > > > > David > > 2010/1/11 James Smith > > Hi, > > Have you compiled XENHVM kernel? It makes some improvements to networking. > Ensure you add the correct device to /etc/rc.conf afterwards, I believe it > changes to "xn0" when running XENHVM. > > Regards, > James Smith, > > -----Original Message----- > From: owner-freebsd-xen@freebsd.org [mailto:owner-freebsd-xen@freebsd.org] > On Behalf Of David > Sent: 10 January 2010 23:43 > To: freebsd-xen@freebsd.org > Subject: HVM paravirt block/nic drivers > > Hi Guys/Girls, > > > Successfully got a FreeBSD 8 HVM DomU installed. I see its using the > emulated block/nic drivers. > > Is there any work being done on writing paravirt drivers for FreeBSD in > HVM? > > Regards, > > David > > _______________________________________________ > 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 Mon Jan 11 12:01:13 2010 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 1700A10656AC for ; Mon, 11 Jan 2010 12:01:13 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx1.freebsd.org (Postfix) with ESMTP id 9A7398FC19 for ; Mon, 11 Jan 2010 12:01:12 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 22so1919308eye.9 for ; Mon, 11 Jan 2010 04:01:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding; bh=waw/VuuMNUsy60AadFEu0mTnbS8+CE4y0M4uOQ4P3hg=; b=D7W+8+gT8ZeAideco6P4xDoLKxocmnFUsDceF2mzWiuvPYNKBmnwcpxhd4/4SME31h GCfQi7S0r/GWCKUQd+pUmV1ATKdq+ruR3hGBYxAwlV0v0vGdnPq05qNJ9vTyHSu3QrnT ow9LFtc/lwO/UfcL/O60jeJpCgqY/eFKaHAck= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=l5ysLrDEDhAGLdXtUUdfhvf4S1G3v8Y/iEyo5/cZlyz2Q6i9W0DFKSY4Y7TIW615aR D5EWYB3TPTzolI5T4udYpRyjbYUQCQD+1NywTMHujY02GhLZd+bOWZpAMWp34S0RbNP+ YMvUEn4eENMegHMwKsw1h/m6dbECffJ8YjwB4= MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.216.91.10 with SMTP id g10mr2333107wef.217.1263211261054; Mon, 11 Jan 2010 04:01:01 -0800 (PST) In-Reply-To: <6894a6471001110353s20b1e7a6o62fe625de5f8a47@mail.gmail.com> References: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6726@office-server1.m247.local> <6894a6471001110300l7c9a53ber7d0ba706184d1c97@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6730@office-server1.m247.local> <6894a6471001110353s20b1e7a6o62fe625de5f8a47@mail.gmail.com> From: Ivan Voras Date: Mon, 11 Jan 2010 13:00:39 +0100 X-Google-Sender-Auth: 2cf508809629ca54 Message-ID: <9bbcef731001110400i11a33a7rbe62a08d746bcdf9@mail.gmail.com> To: admin@dmarkey.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-xen@freebsd.org" , James Smith Subject: Re: HVM paravirt block/nic drivers 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, 11 Jan 2010 12:01:13 -0000 The given command was slightly wrong; it should have been: make kernel KERNCONF=3DXENHVM 2010/1/11 David : > install -o root -g wheel -m 555 =C2=A0 zfs.ko /boot/kernel > install -o root -g wheel -m 555 =C2=A0 zfs.ko.symbols /boot/kernel > =3D=3D=3D> zlib (install) > install -o root -g wheel -m 555 =C2=A0 zlib.ko /boot/kernel > install -o root -g wheel -m 555 =C2=A0 zlib.ko.symbols /boot/kernel > kldxref /boot/kernel > make: don't know how to make XENHVM. Stop > Any Idea? > > 2010/1/11 James Smith > >> =C2=A0Compile kernel in the normal way, using the XENHVM config. >> >> >> >> cd /usr/src >> >> make kernel XENHVM >> >> edit /etc/rc.conf >> >> >> >> Change network interface to re0, save and reboot. >> >> >> >> Regards, >> >> James Smith, >> >> *From:* David [mailto:admin@dmarkey.com] >> *Sent:* 11 January 2010 11:01 >> *To:* James Smith >> *Cc:* freebsd-xen@freebsd.org >> *Subject:* Re: HVM paravirt block/nic drivers >> >> >> >> Well, im using the AMD64 ISO image, >> >> >> >> So i'll have to recompile the kernel? Are there instructions anywhere? >> >> >> >> Thanks. >> >> >> >> David >> >> 2010/1/11 James Smith >> >> Hi, >> >> Have you compiled XENHVM kernel? =C2=A0It makes some improvements to net= working. >> =C2=A0Ensure you add the correct device to /etc/rc.conf afterwards, I be= lieve it >> changes to "xn0" when running XENHVM. >> >> Regards, >> James Smith, >> >> -----Original Message----- >> From: owner-freebsd-xen@freebsd.org [mailto:owner-freebsd-xen@freebsd.or= g] >> On Behalf Of David >> Sent: 10 January 2010 23:43 >> To: freebsd-xen@freebsd.org >> Subject: HVM paravirt block/nic drivers >> >> Hi Guys/Girls, >> >> >> Successfully got a FreeBSD 8 HVM DomU installed. I see its using the >> emulated block/nic drivers. >> >> Is there any work being done on writing paravirt drivers for FreeBSD in >> HVM? >> >> Regards, >> >> David >> >> _______________________________________________ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >> >> >> > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Mon Jan 11 12:20:04 2010 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 1DA5010656C1 for ; Mon, 11 Jan 2010 12:20:04 +0000 (UTC) (envelope-from admin@dmarkey.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id 9D2938FC12 for ; Mon, 11 Jan 2010 12:20:03 +0000 (UTC) Received: by fxm10 with SMTP id 10so7680075fxm.14 for ; Mon, 11 Jan 2010 04:19:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.239.167.83 with SMTP id f19mr444656hbe.34.1263212396795; Mon, 11 Jan 2010 04:19:56 -0800 (PST) In-Reply-To: <9bbcef731001110400i11a33a7rbe62a08d746bcdf9@mail.gmail.com> References: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6726@office-server1.m247.local> <6894a6471001110300l7c9a53ber7d0ba706184d1c97@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6730@office-server1.m247.local> <6894a6471001110353s20b1e7a6o62fe625de5f8a47@mail.gmail.com> <9bbcef731001110400i11a33a7rbe62a08d746bcdf9@mail.gmail.com> Date: Mon, 11 Jan 2010 12:19:56 +0000 Message-ID: <6894a6471001110419t5d9aa89cy35c146a4a5748e5@mail.gmail.com> From: David To: Ivan Voras Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" , James Smith Subject: Re: HVM paravirt block/nic drivers X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: admin@dmarkey.com List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2010 12:20:04 -0000 Thanks guys, got that working. How about block device drivers? 2010/1/11 Ivan Voras > The given command was slightly wrong; it should have been: > > make kernel KERNCONF=XENHVM > > > 2010/1/11 David : > > install -o root -g wheel -m 555 zfs.ko /boot/kernel > > install -o root -g wheel -m 555 zfs.ko.symbols /boot/kernel > > ===> zlib (install) > > install -o root -g wheel -m 555 zlib.ko /boot/kernel > > install -o root -g wheel -m 555 zlib.ko.symbols /boot/kernel > > kldxref /boot/kernel > > make: don't know how to make XENHVM. Stop > > Any Idea? > > > > 2010/1/11 James Smith > > > >> Compile kernel in the normal way, using the XENHVM config. > >> > >> > >> > >> cd /usr/src > >> > >> make kernel XENHVM > >> > >> edit /etc/rc.conf > >> > >> > >> > >> Change network interface to re0, save and reboot. > >> > >> > >> > >> Regards, > >> > >> James Smith, > >> > >> *From:* David [mailto:admin@dmarkey.com] > >> *Sent:* 11 January 2010 11:01 > >> *To:* James Smith > >> *Cc:* freebsd-xen@freebsd.org > >> *Subject:* Re: HVM paravirt block/nic drivers > >> > >> > >> > >> Well, im using the AMD64 ISO image, > >> > >> > >> > >> So i'll have to recompile the kernel? Are there instructions anywhere? > >> > >> > >> > >> Thanks. > >> > >> > >> > >> David > >> > >> 2010/1/11 James Smith > >> > >> Hi, > >> > >> Have you compiled XENHVM kernel? It makes some improvements to > networking. > >> Ensure you add the correct device to /etc/rc.conf afterwards, I believe > it > >> changes to "xn0" when running XENHVM. > >> > >> Regards, > >> James Smith, > >> > >> -----Original Message----- > >> From: owner-freebsd-xen@freebsd.org [mailto: > owner-freebsd-xen@freebsd.org] > >> On Behalf Of David > >> Sent: 10 January 2010 23:43 > >> To: freebsd-xen@freebsd.org > >> Subject: HVM paravirt block/nic drivers > >> > >> Hi Guys/Girls, > >> > >> > >> Successfully got a FreeBSD 8 HVM DomU installed. I see its using the > >> emulated block/nic drivers. > >> > >> Is there any work being done on writing paravirt drivers for FreeBSD in > >> HVM? > >> > >> Regards, > >> > >> David > >> > >> _______________________________________________ > >> freebsd-xen@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen > >> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > >> > >> > >> > > _______________________________________________ > > freebsd-xen@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > > > From owner-freebsd-xen@FreeBSD.ORG Mon Jan 11 12:23:04 2010 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 57EF1106566C for ; Mon, 11 Jan 2010 12:23:04 +0000 (UTC) (envelope-from admin@dmarkey.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id C03228FC20 for ; Mon, 11 Jan 2010 12:23:03 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 19so2115385fgg.13 for ; Mon, 11 Jan 2010 04:22:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.239.193.5 with SMTP id g5mr2757687hbi.3.1263212576866; Mon, 11 Jan 2010 04:22:56 -0800 (PST) In-Reply-To: <6894a6471001110419t5d9aa89cy35c146a4a5748e5@mail.gmail.com> References: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6726@office-server1.m247.local> <6894a6471001110300l7c9a53ber7d0ba706184d1c97@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6730@office-server1.m247.local> <6894a6471001110353s20b1e7a6o62fe625de5f8a47@mail.gmail.com> <9bbcef731001110400i11a33a7rbe62a08d746bcdf9@mail.gmail.com> <6894a6471001110419t5d9aa89cy35c146a4a5748e5@mail.gmail.com> Date: Mon, 11 Jan 2010 12:22:56 +0000 Message-ID: <6894a6471001110422m59c2250dp7fd218cad2231b32@mail.gmail.com> From: David To: Ivan Voras Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" , James Smith Subject: Re: HVM paravirt block/nic drivers X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: admin@dmarkey.com List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2010 12:23:04 -0000 Sorry, I see i'm using paravirt block device drivers. Timecounters tick every 1.000 msec acd0: CDROM at ata1-master WDMA2 xbd0: 5120MB at device/vbd/768 on xenbus0 xbd0: attaching as ad0 xbd1: 658MB at device/vbd/5632 on xenbus0 xbd1: attaching as ad2 xn0: at device/vif/0 on xenbus0 xn0: Ethernet address: 00:16:3e:03:68:45 WARNING: WITNESS option enabled, expect reduced performance. GEOM: ad0s1: geometry does not match label (16h,63s != 255h,63s). Trying to mount root from ufs:/dev/ad0s1a lock order reversal: 1st 0xffffff800a550778 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559 2nd 0xffffff0001440400 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e _sx_xlock() at _sx_xlock+0x55 ufsdirhash_acquire() at ufsdirhash_acquire+0x33 ufsdirhash_add() at ufsdirhash_add+0x19 ufs_direnter() at ufs_direnter+0x88b ufs_makeinode() at ufs_makeinode+0x31c VOP_CREATE_APV() at VOP_CREATE_APV+0x8d vn_open_cred() at vn_open_cred+0x423 kern_openat() at kern_openat+0x179 syscall() at syscall+0x1af Xfast_syscall() at Xfast_syscall+0xe1 --- syscall (5, FreeBSD ELF64, open), rip = 0x80096157c, rsp = 0x7fffffffd488, rbp = 0x800ab4700 --- 2010/1/11 David > Thanks guys, got that working. > > How about block device drivers? > > 2010/1/11 Ivan Voras > > The given command was slightly wrong; it should have been: >> >> make kernel KERNCONF=XENHVM >> >> >> 2010/1/11 David : >> > install -o root -g wheel -m 555 zfs.ko /boot/kernel >> > install -o root -g wheel -m 555 zfs.ko.symbols /boot/kernel >> > ===> zlib (install) >> > install -o root -g wheel -m 555 zlib.ko /boot/kernel >> > install -o root -g wheel -m 555 zlib.ko.symbols /boot/kernel >> > kldxref /boot/kernel >> > make: don't know how to make XENHVM. Stop >> > Any Idea? >> > >> > 2010/1/11 James Smith >> > >> >> Compile kernel in the normal way, using the XENHVM config. >> >> >> >> >> >> >> >> cd /usr/src >> >> >> >> make kernel XENHVM >> >> >> >> edit /etc/rc.conf >> >> >> >> >> >> >> >> Change network interface to re0, save and reboot. >> >> >> >> >> >> >> >> Regards, >> >> >> >> James Smith, >> >> >> >> *From:* David [mailto:admin@dmarkey.com] >> >> *Sent:* 11 January 2010 11:01 >> >> *To:* James Smith >> >> *Cc:* freebsd-xen@freebsd.org >> >> *Subject:* Re: HVM paravirt block/nic drivers >> >> >> >> >> >> >> >> Well, im using the AMD64 ISO image, >> >> >> >> >> >> >> >> So i'll have to recompile the kernel? Are there instructions anywhere? >> >> >> >> >> >> >> >> Thanks. >> >> >> >> >> >> >> >> David >> >> >> >> 2010/1/11 James Smith >> >> >> >> Hi, >> >> >> >> Have you compiled XENHVM kernel? It makes some improvements to >> networking. >> >> Ensure you add the correct device to /etc/rc.conf afterwards, I >> believe it >> >> changes to "xn0" when running XENHVM. >> >> >> >> Regards, >> >> James Smith, >> >> >> >> -----Original Message----- >> >> From: owner-freebsd-xen@freebsd.org [mailto: >> owner-freebsd-xen@freebsd.org] >> >> On Behalf Of David >> >> Sent: 10 January 2010 23:43 >> >> To: freebsd-xen@freebsd.org >> >> Subject: HVM paravirt block/nic drivers >> >> >> >> Hi Guys/Girls, >> >> >> >> >> >> Successfully got a FreeBSD 8 HVM DomU installed. I see its using the >> >> emulated block/nic drivers. >> >> >> >> Is there any work being done on writing paravirt drivers for FreeBSD in >> >> HVM? >> >> >> >> Regards, >> >> >> >> David >> >> >> >> _______________________________________________ >> >> freebsd-xen@freebsd.org mailing list >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> >> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >> >> >> >> >> >> >> > _______________________________________________ >> > freebsd-xen@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >> > >> > > From owner-freebsd-xen@FreeBSD.ORG Mon Jan 11 13:27:30 2010 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 E7A72106566B for ; Mon, 11 Jan 2010 13:27:30 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-ew0-f213.google.com (mail-ew0-f213.google.com [209.85.219.213]) by mx1.freebsd.org (Postfix) with ESMTP id 750A18FC08 for ; Mon, 11 Jan 2010 13:27:29 +0000 (UTC) Received: by ewy5 with SMTP id 5so10551850ewy.14 for ; Mon, 11 Jan 2010 05:27:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding; bh=+fSVXz9T73PnNlAAy6C9E7Dekf8LoqauwHI4TmzDdx0=; b=sTAjXsxqwxW5eRyR9l2hNKLdN//TxANdEQOeba0iZppUbBWBHyHpn0PedgptGHBt6h DqRs+0ZhGJOFn+Nl7sksZI1P+BGzcmngBE3pohcOANgetc4TA7/9lOQt5WLmBABL0sjS F3/d6PFP29sk7wYHvdGNVRF1OV598Sqd/MdFE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=FFXct0xbiag1gDUsoRMo0quxmBl/diBUrK4vuXYWcrtKhj7IGE5WRjQFdaxrz/sqEN eim7EVq+PwO60VebqHcVrdJhZ/sWww2V+r9V10tmv399VgQbtjaU7SfYLEBPFrBQxg6q DfxlCRsRXoxYwC4oo9czjLWECBTFaSMGi6NlU= MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.216.88.206 with SMTP id a56mr1233802wef.64.1263216443718; Mon, 11 Jan 2010 05:27:23 -0800 (PST) In-Reply-To: <6894a6471001110422m59c2250dp7fd218cad2231b32@mail.gmail.com> References: <6894a6471001101543k31e862ffq47fba968b264c7c1@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6726@office-server1.m247.local> <6894a6471001110300l7c9a53ber7d0ba706184d1c97@mail.gmail.com> <32668C1E8A82284F873E88308362605713957F6730@office-server1.m247.local> <6894a6471001110353s20b1e7a6o62fe625de5f8a47@mail.gmail.com> <9bbcef731001110400i11a33a7rbe62a08d746bcdf9@mail.gmail.com> <6894a6471001110419t5d9aa89cy35c146a4a5748e5@mail.gmail.com> <6894a6471001110422m59c2250dp7fd218cad2231b32@mail.gmail.com> From: Ivan Voras Date: Mon, 11 Jan 2010 14:27:03 +0100 X-Google-Sender-Auth: abe10156420d2502 Message-ID: <9bbcef731001110527u669999b7m2d40b6fe06417c80@mail.gmail.com> To: admin@dmarkey.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-xen@freebsd.org" , James Smith Subject: Re: HVM paravirt block/nic drivers 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, 11 Jan 2010 13:27:31 -0000 2010/1/11 David : > Sorry, I see i'm using paravirt block device drivers. > > Timecounters tick every 1.000 msec > acd0: CDROM at ata1-master WDMA2 > xbd0: 5120MB at device/vbd/768 on xenbus0 > xbd0: attaching as ad0 > xbd1: 658MB at device/vbd/5632 on xenbus0 > xbd1: attaching as ad2 You could use for example glabel labels to avoid changing device names. > xn0: at device/vif/0 on xenbus0 > xn0: Ethernet address: 00:16:3e:03:68:45 > WARNING: WITNESS option enabled, expect reduced performance. > GEOM: ad0s1: geometry does not match label (16h,63s !=3D 255h,63s). > Trying to mount root from ufs:/dev/ad0s1a > lock order reversal: > =C2=A01st 0xffffff800a550778 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bi= o.c:2559 > =C2=A02nd 0xffffff0001440400 dirhash (dirhash) @ You also appear to be using a CURRENT kernel, or at least a kernel with debugging enabled - which is fine if you know you want it. From owner-freebsd-xen@FreeBSD.ORG Mon Jan 11 15:20:49 2010 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 09298106568D for ; Mon, 11 Jan 2010 15:20:49 +0000 (UTC) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (www.scsiguy.com [70.89.174.89]) by mx1.freebsd.org (Postfix) with ESMTP id ADC5D8FC1A for ; Mon, 11 Jan 2010 15:20:48 +0000 (UTC) Received: from [192.168.0.6] (tumnus.scsiguy.com [192.168.0.6]) (authenticated bits=0) by aslan.scsiguy.com (8.14.3/8.14.3) with ESMTP id o0BEjxR8022619 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 11 Jan 2010 07:46:00 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-ID: <4B4B39A0.6080506@scsiguy.com> Date: Mon, 11 Jan 2010 07:45:52 -0700 From: "Justin T. Gibbs" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: James Smith References: <32668C1E8A82284F873E8830836260571392BD1B16@office-server1.m247.local> In-Reply-To: <32668C1E8A82284F873E8830836260571392BD1B16@office-server1.m247.local> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-xen@FreeBSD.org Subject: Re: XenTools development for FreeBSD 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, 11 Jan 2010 15:20:49 -0000 On 1/8/2010 1:23 AM, James Smith wrote: ... > We want to use XenServer (iscsi SAN storage) by Citrix and FreeBSD. > We've got a testing setup in place, so we can play around with the > features. FreeBSD runs and installs quite well within this environment, > along with Linux distros, Windows etc. There is something called > XenTools (commercial software from Citrix), amongst other things its > main job is to facilitate VM migration between nodes when using XenServer > (it is awesome, no ping drops, at worst higher latency for two pings > and then it's done). This runs on Linux ... but there is no FreeBSD > version. Is this part of the XenServer-Essentials package? Can you point to a URL that describes XenTools in more detail? Thanks, Justin From owner-freebsd-xen@FreeBSD.ORG Mon Jan 11 16:58:58 2010 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 D66D11065670 for ; Mon, 11 Jan 2010 16:58:58 +0000 (UTC) (envelope-from armyintelli@reliancemail.net) Received: from out24.rilinfo.net (out24.rilinfo.net [202.138.96.24]) by mx1.freebsd.org (Postfix) with ESMTP id 74DF98FC0C for ; Mon, 11 Jan 2010 16:58:54 +0000 (UTC) Received: from unknown (HELO Kalpesh-PC) ([123.237.96.195]) by smtpauth5.rilinfo.net with ESMTP; 11 Jan 2010 16:57:20 +0000 Message-ID: <20100110.ZUHTTVRKOQBJSEBT@bsnl.in> From: "Kalpesh Sharma" To: Date: Mon, 11 Jan 2010 22:28:46 +0530 Importance: Normal MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_646_5841_96265921.76079868" EM-Campaign: {939ED5F0-B126-41B4-AB19-94AF7D9F72BD} EM-Task: 69 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Kalpesh Sharma CV - 12 years Experienced Specialist with World Records. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kalpesh Sharma 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, 11 Jan 2010 16:58:58 -0000 This message is in MIME format with multi-part. Since your mail reader does not understand this format, some or all of this message may not be legible. ------=_NextPart_646_5841_96265921.76079868 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Respected=20Sir/Madam,=20 =20 It's=20my=20pleasure=20to=20get=20in=20touch=20with=20you.=20I=20am=20an=20e= xpert=20with=20world=20records=20and=20exceptional=20achievements=20in=20my=20= field.=20I=20am=20attaching=20my=20resume=20with=20this=20email.=20I=20kindly= =20request=20you=20to=20have=20a=20look=20incase=20my=20skills,=20expertise,=20= experience,=20etc.=20can=20play=20an=20primary=20role=20for=20your=20company'= s=20growth.=20I=20assure=20you=20with=20full=20confidence=20that=20once=20giv= en=20an=20opportunity,=20I=20will=20work=20hard=20to=20do=20as=20much=20as=20= possible=20best=20for=20the=20company.=20Because=20I=20believe=20that=20the=20= company=20for=20which=20I=20work=20is=20not=20just=20a=20place=20to=20fulfill= =20formality=20to=20come=20in=20morning=20and=20go=20back=20in=20evening,=20b= ut=20instead=20the=20company=20for=20which=20I=20work=20is=20like=20my=20home= .=20And=20a=20person=20who=20thinks=20his=20work=20place(company)=20his=20hom= e,=20will=20take=20care=20of=20his=20company=20in=20the=20same=20way=20as=20h= e=20takes=20care=20of=20the=20safety,=20growth=20and=20security=20of=20his=20= own=20home. =20 Thanking=20you, =20 Sincerely =20 Kalpesh=20Sharma =20 Note=20For=20Entertainment=20Industry=20Only:=20I=20am=20ready=20for=20worki= ng=20100%=20free=20of=20cost=20for=20short=20films,=20ad=20films,=20corporate= =20films=20and=20full=20featured=20films.=20And=20have=20more=20then=20suffic= ient=20knowledge=20and=20medium=20acting=20skills=20to=20give=20the=20best=20= delivery=20of=20my=20services.=20I=20will=20do=20free=20of=20cost=20just=20to= =20gain=20professional=20experience=20in=20entertainment=20industry.=20So,=20= only=20I=20will=20need=20is=20a=20certificate=20of=20good=20performance=20and= =20experience=20in=20entertainment=20industry.=20So,=20if=20you=20do=20not=20= have=20enough=20budget=20then=20feel=20free=20to=20get=20in=20touch=20with=20= me.=20However,=20the=20costs=20of=20food,=20accomodation=20and=20travel=20tha= t=20are=20an=20essential=20part=20of=20shooting=20will=20not=20be=20paid=20fr= om=20my=20pocket.=20I=20will=20give=20service=20100%=20free=20of=20cost=20wit= hout=20charging=20anything,=20but=20at=20the=20same=20time=20cost=20of=20acco= modation,=20food=20and=20travel=20will=20have=20to=20be=20borne=20by=20the=20= production=20company.=20As=20far=20as=20it=20concerns=20to=20delivery=20of=20= service=20and=20performance,=20I=20will=20try=20to=20do=20the=20best=20of=20b= est=20and=20assure=20you=20of=20satisfaction=20for=20the=20same=20at=20your=20= level. =20 My=20Quote:=20Marketing=20is=20an=20art=20of=20selling.=20Companies=20employ= ed=20marketing=20executives=20till=20date,=20but=20now=20there=20should=20be=20= a=20change.=20Start=20employing=20marketing=20actors. =20 My=20Primary=20Challenging=20Skill=20for=20Executive=20Position:=20I=20have=20= a=20lot=20of=20ideas=20for=20every=20industry=20sector.=20Once=20given=20an=20= opportunity,=20I=20challenge=20to=20prove=20my=20work=20with=20practical=20re= sults=20rather=20then=20floating=20in=20dream=20world=20and=20describing=20it= =20theoretically.=20I=20have=20worked=20at=20sophisticated=20levels=20and=20k= now=20those=20ideas,=20which=20will=20generate=20excellent=20revenue=20for=20= the=20companies.=20I=20research=20and=20then=20generate=20ideas,=20along=20wi= th=20taking=20care=20of=20every=20pros=20and=20cons=20involved. =20 Detailed=20Information=20of=20My=20Skills=20(Top=2015):=20 =20 Online=20Marketing=20Expert,=20Internet=20Advertising=20Expert,=20SEO,=20SEM= ,=20etc.=20 Article=20Writing=20Expert,=20Article=20Top=20Ranking=20Techniques,=20Bulk=20= Article=20Submissions.=20 Blog=20Marketing=20Expert,=20Forum=20Marketing=20Expert,=20Social=20Networki= ng=20Expert.=20 Media=20(Unique=20&=20Exclusive=20News),=20Arts=20&=20Entertainment=20Indust= ry=20Artist,=20Reporter,=20Writer,=20Assistant=20Director/=20Assistant=20Prod= ucer,=20etc.=20(Portfolio=20Images=20Attached=20for=20Entertainment=20Industr= y=20Related=20Jobs=20on=20http://www.desitara.com/shriganesh)=20 Networking=20(LAN=20of=20Wired/Wireless=20up=20to=2025=20PC).=20 Hardware=20Troubleshooting,=20Operating=20System=20Installations=20(Server/D= esktop/Laptop).=20 Information=20Security=20Expert,=20Ethical=20Hacking,=20Penetration=20Testin= g=20Expert,=20Vulnerability=20Assessment=20and=20Solutions.=20 Market=20Research,=20Web=20Research,=20Industry=20Research,=20Subject=20Spec= ific=20&=20Geo=20Specific=20Research.=20 Data=20Extraction,=20Email=20Extraction,=20Contact=20&=20Address=20Extractio= n.=20 Competitor=20Research,=20Analysis=20&=20Technical=20Intelligence=20 Business=20Development=20Director,=20Business=20Management,=20Business=20Pla= nning,=20Creative=20New=20Business=20Ideas=20Innovation,=20Planning=20and=20I= mplementing=20Business=20Strategies.=20 Linksys=20Wired/Wireless=20Router=20Configuration=20WAG325N=20&=20WRVS=20440= 0N.=20 Trainee/Assistant=20to=20Network=20Engineer=20Wide=20LAN/WAN=20Network,=20Co= rporate=20Network,=20Web=20Designing,=20Web=20Development,=20Web=20Programmin= g,=20Software=20Programming,=20Software=20Development,=20Software=20Engineeri= ng,=20Research=20&=20Development,=20Executive/Director/Corporate/Management=20= Levels,=20Software=20Testing=20Client/Server=20Level,=20Cisco=20Router=20CCNA= ,=20CCNP,=20CCIE=20Specialist,=20Sap=20Specialist,=20CISSP/CISA=20Specialist.= =20 Almost=20All=20Types=20of=20Administrative=20&=20Management=20Skills.=20 Moderate=20Legal=20Working=20Knowledge. ------=_NextPart_646_5841_96265921.76079868-- From owner-freebsd-xen@FreeBSD.ORG Mon Jan 11 17:04:28 2010 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 EC501106566B for ; Mon, 11 Jan 2010 17:04:28 +0000 (UTC) (envelope-from apowers@digipen.edu) Received: from smtp0.digipen.edu (smtp0.digipen.edu [206.15.72.68]) by mx1.freebsd.org (Postfix) with ESMTP id D2D528FC0A for ; Mon, 11 Jan 2010 17:04:28 +0000 (UTC) Received: from [10.10.10.56] (dit663.digipen.edu [10.10.10.56]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp0.digipen.edu (Postfix) with ESMTPSA id D57E5288B for ; Mon, 11 Jan 2010 09:04:26 -0800 (PST) Message-ID: <4B4B5A1B.8040401@digipen.edu> Date: Mon, 11 Jan 2010 09:04:27 -0800 From: Atom Powers User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b2pre Thunderbird/3.0 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <32668C1E8A82284F873E8830836260571392BD1B16@office-server1.m247.local> <4B4B39A0.6080506@scsiguy.com> In-Reply-To: <4B4B39A0.6080506@scsiguy.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: XenTools development for FreeBSD 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, 11 Jan 2010 17:04:29 -0000 On 1/11/2010 6:45 AM, Justin T. Gibbs wrote: > On 1/8/2010 1:23 AM, James Smith wrote: > > ... > >> We want to use XenServer (iscsi SAN storage) by Citrix and FreeBSD. >> We've got a testing setup in place, so we can play around with the >> features. FreeBSD runs and installs quite well within this environment, >> along with Linux distros, Windows etc. There is something called >> XenTools (commercial software from Citrix), amongst other things its >> main job is to facilitate VM migration between nodes when using XenServer >> (it is awesome, no ping drops, at worst higher latency for two pings >> and then it's done). This runs on Linux ... but there is no FreeBSD >> version. > > Is this part of the XenServer-Essentials package? Can you point to a > URL that describes XenTools in more detail? > It is available on the installation CD, as a mountable ISO once the VM is installed. (Downloads for Citrix Xen are here: http://www.citrix.com/lang/English/lp/lp_1688615.asp ) -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- Director of IT DigiPen Institute of Technology (425) 895-4443 From owner-freebsd-xen@FreeBSD.ORG Tue Jan 12 07:58:16 2010 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 B5873106566B for ; Tue, 12 Jan 2010 07:58:16 +0000 (UTC) (envelope-from bissont@gmail.com) Received: from mail-iw0-f177.google.com (mail-iw0-f177.google.com [209.85.223.177]) by mx1.freebsd.org (Postfix) with ESMTP id 7A20C8FC16 for ; Tue, 12 Jan 2010 07:58:16 +0000 (UTC) Received: by iwn7 with SMTP id 7so6989637iwn.7 for ; Mon, 11 Jan 2010 23:58:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :content-type:content-transfer-encoding:mime-version:subject:date :x-mailer; bh=bOFhaYGZGU1vl/93hH8cGbq9fCZTjVA4XZQunEP94RY=; b=C6uFGScPXI5nyF9PsTMWC4PJONQJwi353WY7cigj9Cl6wQob2pC6GsO09+fUri2b5D g3cp6g0h9FKVYs8Cq30vkkBYh+2Vd0e2R9S7quVoCoTNeM9LKj/ohH2TsY7t7cVFiVQU yELdToax5nDzCHbiukc1oOmIYXDzXbAFboYUA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer; b=jrAaweoaCgGuO7CoWYPkHNR0b4oTy7K9qw/kgfG0+sqPQuUNdKFdju1avFq91rm2CU F3A7sahJoM5xiqGlbFH4gBA9ZSGqo3qyqaFZOj/E4AHtFlqAkPtixj69hxVz65hqZAua VpI8sBOEj9eHKtIAnObKVgkdkk0lDyXnKiPFQ= Received: by 10.231.170.136 with SMTP id d8mr588491ibz.17.1263281763152; Mon, 11 Jan 2010 23:36:03 -0800 (PST) Received: from vshukla-lxp.hq.netapp.com (nat-198-95-226-230.netapp.com [198.95.226.230]) by mx.google.com with ESMTPS id 20sm5438863iwn.1.2010.01.11.23.36.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 11 Jan 2010 23:36:02 -0800 (PST) Message-Id: From: Timothy Bisson To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 11 Jan 2010 23:36:00 -0800 X-Mailer: Apple Mail (2.936) Subject: Can't boot 8/CURRENT hvm on Quad-Core Opteron 2352 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, 12 Jan 2010 07:58:16 -0000 Hi, I'm trying to run a FreeBSD 8/CURRENT hvm on XEN, but booting FreeBSD currently panics on a quad-core Operton 2352 box while booting from the iso (disabling ACPI doesn't help). However, I'm successful at running a FreeBSD 8/CURRENT hvm on XEN on a Intel Xeon Nehalem box. I tried booting the same installed disk image (from the Nehalem box) on the Operteron box, but that also resulted in a panic while booting. The CURRENT iso I'm using is from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201001/FreeBSD-9.0-CURRENT-201001-amd64-bootonly.iso I'm using Xen-3.3.1 on both physical boxes, and a BSD 6 hvm works on both the Nehalem and Operton boxes... Here's the backtrace from the opteron box: kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xffffffff80878193 stack pointer = 0x28:0xffffffff81044bb0 frame pointer = 0x28:0xffffffff81044bc0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () [thread pid 0 tid 0 ] Stopped at pmap_invalidate_cache_range+0x43: clflushl (%rdi) db> bt bt Tracing pid 0 tid 0 td 0xffffffff80c51fc0 pmap_invalidate_cache_range() at pmap_invalidate_cache_range+0x43 pmap_change_attr_locked() at pmap_change_attr_locked+0x368 pmap_change_attr() at pmap_change_attr+0x43 pmap_mapdev_attr() at pmap_mapdev_attr+0x112 lapic_init() at lapic_init+0x29 madt_setup_local() at madt_setup_local+0x26 apic_setup_local() at apic_setup_local+0x13 mi_startup() at mi_startup+0x59 btext() at btext+0x2c I took a look through the bug database and didn't see any similar problem reports. Is it reasonable to file a bug report? Is there additional information that I should be reporting? Thanks, Tim From owner-freebsd-xen@FreeBSD.ORG Tue Jan 12 09:36:35 2010 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 EA07E106566B for ; Tue, 12 Jan 2010 09:36:34 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 7A46C8FC18 for ; Tue, 12 Jan 2010 09:36:33 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o0C9aTZk028737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Jan 2010 11:36:29 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id o0C9aTIc094505; Tue, 12 Jan 2010 11:36:29 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id o0C9aSM2094504; Tue, 12 Jan 2010 11:36:28 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 12 Jan 2010 11:36:28 +0200 From: Kostik Belousov To: Timothy Bisson Message-ID: <20100112093628.GH62907@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="svZFHVx8/dhPCe52" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-xen@freebsd.org Subject: Re: Can't boot 8/CURRENT hvm on Quad-Core Opteron 2352 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, 12 Jan 2010 09:36:35 -0000 --svZFHVx8/dhPCe52 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 11, 2010 at 11:36:00PM -0800, Timothy Bisson wrote: > Hi, >=20 > I'm trying to run a FreeBSD 8/CURRENT hvm on XEN, but booting FreeBSD =20 > currently panics on a quad-core Operton 2352 box while booting from =20 > the iso (disabling ACPI doesn't help). >=20 > However, I'm successful at running a FreeBSD 8/CURRENT hvm on XEN on a = =20 > Intel Xeon Nehalem box. I tried booting the same installed disk image =20 > (from the Nehalem box) on the Operteron box, but that also resulted in = =20 > a panic while booting. >=20 > The CURRENT iso I'm using is from: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201001/FreeBSD-9.0-CURRENT-20= 1001-amd64-bootonly.iso >=20 > I'm using Xen-3.3.1 on both physical boxes, and a BSD 6 hvm works on =20 > both the Nehalem and Operton boxes... >=20 > Here's the backtrace from the opteron box: > kernel trap 9 with interrupts disabled >=20 >=20 > Fatal trap 9: general protection fault while in kernel mode > cpuid =3D 0; apic id =3D 00 > instruction pointer =3D 0x20:0xffffffff80878193 > stack pointer =3D 0x28:0xffffffff81044bb0 > frame pointer =3D 0x28:0xffffffff81044bc0 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D resume, IOPL =3D 0 > current process =3D 0 () > [thread pid 0 tid 0 ] > Stopped at pmap_invalidate_cache_range+0x43: =20 > clflushl (%rdi) > db> bt > bt > Tracing pid 0 tid 0 td 0xffffffff80c51fc0 > pmap_invalidate_cache_range() at pmap_invalidate_cache_range+0x43 > pmap_change_attr_locked() at pmap_change_attr_locked+0x368 > pmap_change_attr() at pmap_change_attr+0x43 > pmap_mapdev_attr() at pmap_mapdev_attr+0x112 > lapic_init() at lapic_init+0x29 > madt_setup_local() at madt_setup_local+0x26 > apic_setup_local() at apic_setup_local+0x13 > mi_startup() at mi_startup+0x59 > btext() at btext+0x2c >=20 >=20 > I took a look through the bug database and didn't see any similar =20 > problem reports. Is it reasonable to file a bug report? Is there =20 > additional information that I should be reporting? Set hw.clflush_disable=3D1 at the loader prompt. --svZFHVx8/dhPCe52 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAktMQpwACgkQC3+MBN1Mb4iwMQCfRsZmlC967tgmtAyRSvJtuQvu oMgAoLCRYGrnHH0WnHPKeD2eBdG4E06Q =aV2X -----END PGP SIGNATURE----- --svZFHVx8/dhPCe52-- From owner-freebsd-xen@FreeBSD.ORG Tue Jan 12 13:11:19 2010 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 8E430106566B for ; Tue, 12 Jan 2010 13:11:19 +0000 (UTC) (envelope-from info@deployis.eu) Received: from mail.deployis.eu (mail.deployis.eu [217.20.135.253]) by mx1.freebsd.org (Postfix) with ESMTP id 222938FC19 for ; Tue, 12 Jan 2010 13:11:18 +0000 (UTC) Received: from [80.95.75.131] (port=28117 helo=[192.168.2.192]) by mail.deployis.eu with esmtpsa (Exim 4.69 #1 (Debian)) id 1NUgDE-0001mj-2j from ; Tue, 12 Jan 2010 13:51:08 +0100 Message-ID: <4B4C703A.3000501@deployis.eu> Date: Tue, 12 Jan 2010 13:51:06 +0100 From: Deploy IS INFO User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-xen@freebsd.org, bissont@gmail.com References: <20100112093628.GH62907@deviant.kiev.zoral.com.ua> In-Reply-To: <20100112093628.GH62907@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Can't boot 8/CURRENT hvm on Quad-Core Opteron 2352 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, 12 Jan 2010 13:11:19 -0000 Kostik Belousov wrote: > On Mon, Jan 11, 2010 at 11:36:00PM -0800, Timothy Bisson wrote: >> Hi, >> >> I'm trying to run a FreeBSD 8/CURRENT hvm on XEN, but booting FreeBSD >> currently panics on a quad-core Operton 2352 box while booting from >> the iso (disabling ACPI doesn't help). >> >> However, I'm successful at running a FreeBSD 8/CURRENT hvm on XEN on a >> Intel Xeon Nehalem box. I tried booting the same installed disk image >> (from the Nehalem box) on the Operteron box, but that also resulted in >> a panic while booting. >> >> The CURRENT iso I'm using is from: >> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201001/FreeBSD-9.0-CURRENT-201001-amd64-bootonly.iso >> >> I'm using Xen-3.3.1 on both physical boxes, and a BSD 6 hvm works on >> both the Nehalem and Operton boxes... >> >> Here's the backtrace from the opteron box: >> kernel trap 9 with interrupts disabled >> >> >> Fatal trap 9: general protection fault while in kernel mode >> cpuid = 0; apic id = 00 >> instruction pointer = 0x20:0xffffffff80878193 >> stack pointer = 0x28:0xffffffff81044bb0 >> frame pointer = 0x28:0xffffffff81044bc0 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags = resume, IOPL = 0 >> current process = 0 () >> [thread pid 0 tid 0 ] >> Stopped at pmap_invalidate_cache_range+0x43: >> clflushl (%rdi) >> db> bt >> bt >> Tracing pid 0 tid 0 td 0xffffffff80c51fc0 >> pmap_invalidate_cache_range() at pmap_invalidate_cache_range+0x43 >> pmap_change_attr_locked() at pmap_change_attr_locked+0x368 >> pmap_change_attr() at pmap_change_attr+0x43 >> pmap_mapdev_attr() at pmap_mapdev_attr+0x112 >> lapic_init() at lapic_init+0x29 >> madt_setup_local() at madt_setup_local+0x26 >> apic_setup_local() at apic_setup_local+0x13 >> mi_startup() at mi_startup+0x59 >> btext() at btext+0x2c >> >> >> I took a look through the bug database and didn't see any similar >> problem reports. Is it reasonable to file a bug report? Is there >> additional information that I should be reporting? > > Set hw.clflush_disable=1 at the loader prompt. Hi, I'm trying also FreeBSD8 on a nehalem box. When I configure more than 2 vcpus for the HVM guest I met with the following: - With the XENHVM kernel the boot simply stops when the message about WITNESS performance came. No debug messages, nothing, just stops there and the PV drivers just attaches before the message - With the GENERIC kernel the re driver somehow fails to receive packages when 4 vcpus configured. Tcpdump showed that packages are going out, but somehow none received. I'd say it's not really a FreeBSD problem, but it's wierd enough. Could you verify these these two problem on the Opteron and your Nehalem machine? We are also using Xen-3.3.1. Regards, Andras From owner-freebsd-xen@FreeBSD.ORG Tue Jan 12 20:03:50 2010 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 0E47F1065672 for ; Tue, 12 Jan 2010 20:03:50 +0000 (UTC) (envelope-from fredmaeser@gmail.com) Received: from mail-yw0-f197.google.com (mail-yw0-f197.google.com [209.85.211.197]) by mx1.freebsd.org (Postfix) with ESMTP id C11A88FC0A for ; Tue, 12 Jan 2010 20:03:49 +0000 (UTC) Received: by ywh35 with SMTP id 35so13571196ywh.7 for ; Tue, 12 Jan 2010 12:03:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=MzOZyNDbrdmjN4NRUySsuSYMFhaO3YV1Fcficcc6g2M=; b=SmOU1TdVH7zQmEnnWiZdpf1rDQjOP7YG4vztx5pAkTibbM37GM4A8YHZmabI7Ro6/N wuoOQoeBSpD6arRJE40Qrl04AgqSNDMrS1rGn3wWlWth0RVOBjrIPt0yIcQhy78bLWmM k+T+c3sP3nFc4C8HH3rnmM671BIYkkE0amr08= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=W63A+4yOV+EvNJ2KtEwrLFNfzAWiVr5mo8EKbe9Hi3oUrNuL8fMV90qc9nZgKfETyV AweF/lh0dLs3ktdzNUZuIRJFuX6DpdjZ0fHAggxLik5H1XWLNXWrxnoZb6Mt5XX1CORO HTvXwpeuxYgYpIF/sx0b3nWgFBnwwwom9H3Rg= MIME-Version: 1.0 Sender: fredmaeser@gmail.com Received: by 10.91.19.11 with SMTP id w11mr4458132agi.114.1263325235047; Tue, 12 Jan 2010 11:40:35 -0800 (PST) Date: Tue, 12 Jan 2010 12:40:35 -0700 X-Google-Sender-Auth: e6cd54901b416ab8 Message-ID: <5903990b1001121140wa3bd39ah6c950aeace925a3@mail.gmail.com> From: Fred Crandall To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Kernel panic and general question on stability for FreeBSD 8 xen domU X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2010 20:03:50 -0000 Hi there all, I have a paravirtualized FreeBSD 8 xen domU going that I have intermittent and repeatable kernel panic issues with. This is using a i386 xen paravirtualized kernel from up to date (as of this morning at the latest try) RELENG_8 sources. Ive tried this on a linux 64bit dom0 and 32bit dom0 both running xen 3.4.2. The kernel will panic at random from anywhere form a few hours to a few days with: panic: mutex vm page queue mutex not owned at /usr/src/sys/i386/xen/xen_machdep.c:431 KDB: enter: panic Fairly low load when this happens, currently the domU machine only runs some minor sendmail load. I can also get the domU virtual to kernel panic in the same way on demand by having the configure script run on the libgcrypt port or by running and exiting memtest. The libgcrypt issue being the same as described in PR 140313. Also tried running the domU kernel without SMP support, I see the same results. So curious if anyone has any ideas on something Im missing or if others see similar issues on a RELENG_8 i386 xen kernel. Below, is also my current kernel configuration. cpu I686_CPU ident XEN makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols makeoptions MODULES_OVERRIDE="" options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption #options SCHED_4BSD options INET # InterNETworking options INET6 # IPv6 communications protocols options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD # Network Lock Manager options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AUDIT # Security event auditing # Debugging for use in -current options KDB # Enable kernel debugger support. options DDB # Support DDB. options GDB # Support remote GDB. options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed options PAE nooption NATIVE option XEN nodevice atpic nodevice isa options MCLSHIFT=12 options IPFIREWALL # To make an SMP kernel, the next two lines are needed #options SMP # Symmetric MultiProcessor Kernel #device apic # I/O APIC device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device pci device kbdmux # keyboard multiplexer # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter The domU kernel is booted via pvgrub, ther kernel called via: kernel /boot/kernel/kernel vfs.root.mountfrom=ufs:xbd0s1a,kern.hz=100,xencons=tty Thanks all, Fred From owner-freebsd-xen@FreeBSD.ORG Tue Jan 12 21:06:00 2010 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 EA285106568D for ; Tue, 12 Jan 2010 21:06:00 +0000 (UTC) (envelope-from fredmaeser@gmail.com) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id A1E508FC20 for ; Tue, 12 Jan 2010 21:06:00 +0000 (UTC) Received: by yxe1 with SMTP id 1so21218185yxe.3 for ; Tue, 12 Jan 2010 13:05:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=yoO+bUb4rkc1E3NazOmkXXEfBy4i5Tls7NzTbsIpGL4=; b=a6C2vKxRYkCl15earKp4IwiUFRaFw8T9X4oFCVZed6SL8W4N/sM+cVObCMZsGlBOXg gVTPPFeTpi6xI36KmgR2/tuNi2GwuT5VrEUpfXkdHwvE44GSKdd/LzYcaWp0kNQxAFvf SzfGsVPPcgjrTzNw7TqvzFLU7+ufRgiILylZQ= DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=hmvvQMJ961R5Wx+kZsvdrSvnk3eWVZDYQAgibpO51zwIfwM+lPY3ZBrt+34hvA9fbr xs6ev7L3R6wjBRsIwkCznVZ7uh4ys77mkadTMZJShmaRCOa0v/sX8GBTNtD0ktB6jKiL k7TXj3JG4fGY8A/8tSmAEIlxu8xfWq/8weqzk= MIME-Version: 1.0 Sender: fredmaeser@gmail.com Received: by 10.90.16.12 with SMTP id 12mr2171965agp.46.1263330351268; Tue, 12 Jan 2010 13:05:51 -0800 (PST) In-Reply-To: <4B4CE3A9.3030001@deployis.eu> References: <5903990b1001121140wa3bd39ah6c950aeace925a3@mail.gmail.com> <4B4CE3A9.3030001@deployis.eu> Date: Tue, 12 Jan 2010 14:05:51 -0700 X-Google-Sender-Auth: 4f4a942247ac5717 Message-ID: <5903990b1001121305h3a50e0a3q7e8eb92227112f48@mail.gmail.com> From: Fred Crandall To: =?ISO-8859-1?Q?G=F3t_Andr=E1s?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-xen@freebsd.org Subject: Re: Kernel panic and general question on stability for FreeBSD 8 xen domU X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2010 21:06:01 -0000 No. Single CPU configured for the guest. Fred On Tue, Jan 12, 2010 at 2:03 PM, G=F3t Andr=E1s wr= ote: > Hi, > > Did you give more than one vcpus to the guest? > > Regards, > > Andras > > Fred Crandall wrote: >> >> Hi there all, >> >> I have a paravirtualized =A0FreeBSD 8 xen domU going that I have >> intermittent and repeatable kernel panic issues with. This is using a >> i386 xen paravirtualized kernel from up to date (as of this morning at >> the latest try) RELENG_8 sources. Ive tried this on a linux 64bit dom0 >> and 32bit dom0 both running xen 3.4.2. =A0The kernel will panic at >> random from anywhere form a few hours to a few days with: >> >> panic: mutex vm page queue mutex not owned at >> /usr/src/sys/i386/xen/xen_machdep.c:431 >> KDB: enter: panic >> >> Fairly low load when this happens, currently the domU machine only >> runs some minor sendmail load. I can also get the domU virtual to >> kernel panic in the same way on demand by having the configure script >> run on the libgcrypt port or by running and exiting memtest. The >> libgcrypt issue being the same as described in PR 140313. >> >> Also tried running the domU kernel without SMP support, I see the same >> results. >> >> So curious if anyone has any ideas on something Im missing or if >> others see similar issues on a RELENG_8 i386 xen kernel. >> >> Below, is also my current kernel configuration. >> >> cpu =A0 =A0 =A0 =A0 =A0 =A0 I686_CPU >> ident =A0 =A0 =A0 =A0 =A0 XEN >> >> makeoptions =A0 =A0 DEBUG=3D-g =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# Build ke= rnel with gdb(1) debug >> symbols >> makeoptions =A0 =A0 MODULES_OVERRIDE=3D"" >> >> options =A0 =A0 =A0 =A0 SCHED_ULE =A0 =A0 =A0 =A0 =A0 =A0 =A0 # ULE sche= duler >> options =A0 =A0 =A0 =A0 PREEMPTION =A0 =A0 =A0 =A0 =A0 =A0 =A0# Enable k= ernel thread preemption >> #options =A0 =A0 =A0 =A0SCHED_4BSD >> >> options =A0 =A0 =A0 =A0 INET =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# In= terNETworking >> options =A0 =A0 =A0 =A0 INET6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # IPv6= communications protocols >> options =A0 =A0 =A0 =A0 SCTP =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# St= ream Control Transmission >> Protocol >> options =A0 =A0 =A0 =A0 FFS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Be= rkeley Fast Filesystem >> options =A0 =A0 =A0 =A0 SOFTUPDATES =A0 =A0 =A0 =A0 =A0 =A0 # Enable FFS= soft updates support >> options =A0 =A0 =A0 =A0 UFS_ACL =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Suppor= t for access control lists >> options =A0 =A0 =A0 =A0 UFS_DIRHASH =A0 =A0 =A0 =A0 =A0 =A0 # Improve pe= rformance on big >> directories >> options =A0 =A0 =A0 =A0 UFS_GJOURNAL =A0 =A0 =A0 =A0 =A0 =A0# Enable gjo= urnal-based UFS >> journaling >> options =A0 =A0 =A0 =A0 NFSCLIENT =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Network = Filesystem Client >> options =A0 =A0 =A0 =A0 NFSSERVER =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Network = Filesystem Server >> options =A0 =A0 =A0 =A0 NFSLOCKD =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# Networ= k Lock Manager >> options =A0 =A0 =A0 =A0 NFS_ROOT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# NFS us= able as /, requires >> NFSCLIENT >> options =A0 =A0 =A0 =A0 MSDOSFS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # MSDOS = Filesystem >> options =A0 =A0 =A0 =A0 CD9660 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# ISO = 9660 Filesystem >> options =A0 =A0 =A0 =A0 PROCFS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# Proc= ess filesystem (requires >> PSEUDOFS) >> options =A0 =A0 =A0 =A0 PSEUDOFS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# Pseudo= -filesystem framework >> options =A0 =A0 =A0 =A0 GEOM_PART_GPT =A0 =A0 =A0 =A0 =A0 # GUID Partiti= on Tables. >> options =A0 =A0 =A0 =A0 GEOM_LABEL =A0 =A0 =A0 =A0 =A0 =A0 =A0# Provides= labelization >> options =A0 =A0 =A0 =A0 COMPAT_43TTY =A0 =A0 =A0 =A0 =A0 =A0# BSD 4.3 TT= Y compat (sgtty) >> options =A0 =A0 =A0 =A0 COMPAT_FREEBSD4 =A0 =A0 =A0 =A0 # Compatible wit= h FreeBSD4 >> options =A0 =A0 =A0 =A0 COMPAT_FREEBSD5 =A0 =A0 =A0 =A0 # Compatible wit= h FreeBSD5 >> options =A0 =A0 =A0 =A0 COMPAT_FREEBSD6 =A0 =A0 =A0 =A0 # Compatible wit= h FreeBSD6 >> options =A0 =A0 =A0 =A0 COMPAT_FREEBSD7 =A0 =A0 =A0 =A0 # Compatible wit= h FreeBSD7 >> options =A0 =A0 =A0 =A0 KTRACE =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# ktra= ce(1) support >> options =A0 =A0 =A0 =A0 STACK =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # stac= k(9) support >> options =A0 =A0 =A0 =A0 SYSVSHM =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # SYSV-s= tyle shared memory >> options =A0 =A0 =A0 =A0 SYSVMSG =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # SYSV-s= tyle message queues >> options =A0 =A0 =A0 =A0 SYSVSEM =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # SYSV-s= tyle semaphores >> options =A0 =A0 =A0 =A0 _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B rea= l-time >> extensions >> options =A0 =A0 =A0 =A0 KBD_INSTALL_CDEV =A0 =A0 =A0 =A0# install a CDEV= entry in /dev >> options =A0 =A0 =A0 =A0 AUDIT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Secu= rity event auditing >> >> # Debugging for use in -current >> options =A0 =A0 =A0 =A0 KDB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # En= able kernel debugger support. >> options =A0 =A0 =A0 =A0 DDB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Su= pport DDB. >> options =A0 =A0 =A0 =A0 GDB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Su= pport remote GDB. >> options =A0 =A0 =A0 =A0 INVARIANTS =A0 =A0 =A0 =A0 =A0 =A0 =A0# Enable c= alls of extra sanity >> checking >> options =A0 =A0 =A0 =A0 INVARIANT_SUPPORT =A0 =A0 =A0 # Extra sanity che= cks of internal >> structures, required by INVARIANTS >> options =A0 =A0 =A0 =A0 WITNESS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Enable= checks to detect >> deadlocks and cycles >> options =A0 =A0 =A0 =A0 WITNESS_SKIPSPIN =A0 =A0 =A0 =A0# Don't run witn= ess on spinlocks >> for speed >> >> options =A0 =A0 =A0 =A0 PAE >> nooption =A0 =A0 =A0 =A0NATIVE >> option =A0 =A0 =A0 =A0 =A0XEN >> nodevice =A0 =A0 =A0 =A0atpic >> nodevice =A0 =A0 =A0 =A0isa >> options =A0 =A0 =A0 =A0 MCLSHIFT=3D12 >> >> options =A0 =A0 =A0 =A0 IPFIREWALL >> # To make an SMP kernel, the next two lines are needed >> #options =A0 =A0 =A0 =A0SMP =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Sy= mmetric MultiProcessor Kernel >> #device =A0 =A0 =A0 =A0 apic =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# I/= O APIC >> >> >> device =A0 =A0 =A0 =A0 =A0atkbdc =A0 =A0 =A0 =A0 =A0# AT keyboard contro= ller >> device =A0 =A0 =A0 =A0 =A0atkbd =A0 =A0 =A0 =A0 =A0 # AT keyboard >> device =A0 =A0 =A0 =A0 =A0psm =A0 =A0 =A0 =A0 =A0 =A0 # PS/2 mouse >> device =A0 =A0 =A0 =A0 =A0pci >> >> device =A0 =A0 =A0 =A0 =A0kbdmux =A0 =A0 =A0 =A0 =A0# keyboard multiplex= er >> >> # Pseudo devices. >> device =A0 =A0 =A0 =A0 =A0loop =A0 =A0 =A0 =A0 =A0 =A0# Network loopback >> device =A0 =A0 =A0 =A0 =A0random =A0 =A0 =A0 =A0 =A0# Entropy device >> device =A0 =A0 =A0 =A0 =A0ether =A0 =A0 =A0 =A0 =A0 # Ethernet support >> device =A0 =A0 =A0 =A0 =A0tun =A0 =A0 =A0 =A0 =A0 =A0 # Packet tunnel. >> device =A0 =A0 =A0 =A0 =A0pty =A0 =A0 =A0 =A0 =A0 =A0 # Pseudo-ttys (tel= net etc) >> device =A0 =A0 =A0 =A0 =A0md =A0 =A0 =A0 =A0 =A0 =A0 =A0# Memory "disks" >> device =A0 =A0 =A0 =A0 =A0gif =A0 =A0 =A0 =A0 =A0 =A0 # IPv6 and IPv4 tu= nneling >> device =A0 =A0 =A0 =A0 =A0faith =A0 =A0 =A0 =A0 =A0 # IPv6-to-IPv4 relay= ing (translation) >> >> # The `bpf' device enables the Berkeley Packet Filter. >> # Be aware of the administrative consequences of enabling this! >> # Note that 'bpf' is required for DHCP. >> device =A0 =A0 =A0 =A0 =A0bpf =A0 =A0 =A0 =A0 =A0 =A0 # Berkeley packet = filter >> >> >> The domU kernel is booted via pvgrub, ther kernel called via: >> >> kernel /boot/kernel/kernel >> vfs.root.mountfrom=3Dufs:xbd0s1a,kern.hz=3D100,xencons=3Dtty >> >> >> Thanks all, >> >> Fred >> _______________________________________________ >> 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 Jan 12 21:41:20 2010 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 0BD811065670 for ; Tue, 12 Jan 2010 21:41:20 +0000 (UTC) (envelope-from got.andras@deployis.eu) Received: from mail.deployis.eu (mail.deployis.eu [217.20.135.253]) by mx1.freebsd.org (Postfix) with ESMTP id 914A18FC19 for ; Tue, 12 Jan 2010 21:41:19 +0000 (UTC) Received: from bc9d0c05.mobile.pool.telekom.hu ([188.157.12.5]:44276) by mail.deployis.eu with esmtpsa (Exim 4.69 #1 (Debian)) id 1NUntr-0008UX-Pi from ; Tue, 12 Jan 2010 22:03:40 +0100 Message-ID: <4B4CE3A9.3030001@deployis.eu> Date: Tue, 12 Jan 2010 22:03:37 +0100 From: =?ISO-8859-1?Q?G=F3t_Andr=E1s?= User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Fred Crandall References: <5903990b1001121140wa3bd39ah6c950aeace925a3@mail.gmail.com> In-Reply-To: <5903990b1001121140wa3bd39ah6c950aeace925a3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org Subject: Re: Kernel panic and general question on stability for FreeBSD 8 xen domU X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2010 21:41:20 -0000 Hi, Did you give more than one vcpus to the guest? Regards, Andras Fred Crandall wrote: > Hi there all, > > I have a paravirtualized FreeBSD 8 xen domU going that I have > intermittent and repeatable kernel panic issues with. This is using a > i386 xen paravirtualized kernel from up to date (as of this morning at > the latest try) RELENG_8 sources. Ive tried this on a linux 64bit dom0 > and 32bit dom0 both running xen 3.4.2. The kernel will panic at > random from anywhere form a few hours to a few days with: > > panic: mutex vm page queue mutex not owned at > /usr/src/sys/i386/xen/xen_machdep.c:431 > KDB: enter: panic > > Fairly low load when this happens, currently the domU machine only > runs some minor sendmail load. I can also get the domU virtual to > kernel panic in the same way on demand by having the configure script > run on the libgcrypt port or by running and exiting memtest. The > libgcrypt issue being the same as described in PR 140313. > > Also tried running the domU kernel without SMP support, I see the same results. > > So curious if anyone has any ideas on something Im missing or if > others see similar issues on a RELENG_8 i386 xen kernel. > > Below, is also my current kernel configuration. > > cpu I686_CPU > ident XEN > > makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols > makeoptions MODULES_OVERRIDE="" > > options SCHED_ULE # ULE scheduler > options PREEMPTION # Enable kernel thread preemption > #options SCHED_4BSD > > options INET # InterNETworking > options INET6 # IPv6 communications protocols > options SCTP # Stream Control Transmission Protocol > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big directories > options UFS_GJOURNAL # Enable gjournal-based UFS journaling > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > options NFSLOCKD # Network Lock Manager > options NFS_ROOT # NFS usable as /, requires NFSCLIENT > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires PSEUDOFS) > options PSEUDOFS # Pseudo-filesystem framework > options GEOM_PART_GPT # GUID Partition Tables. > options GEOM_LABEL # Provides labelization > options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options COMPAT_FREEBSD5 # Compatible with FreeBSD5 > options COMPAT_FREEBSD6 # Compatible with FreeBSD6 > options COMPAT_FREEBSD7 # Compatible with FreeBSD7 > options KTRACE # ktrace(1) support > options STACK # stack(9) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > options AUDIT # Security event auditing > > # Debugging for use in -current > options KDB # Enable kernel debugger support. > options DDB # Support DDB. > options GDB # Support remote GDB. > options INVARIANTS # Enable calls of extra sanity checking > options INVARIANT_SUPPORT # Extra sanity checks of internal > structures, required by INVARIANTS > options WITNESS # Enable checks to detect deadlocks and cycles > options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed > > options PAE > nooption NATIVE > option XEN > nodevice atpic > nodevice isa > options MCLSHIFT=12 > > options IPFIREWALL > # To make an SMP kernel, the next two lines are needed > #options SMP # Symmetric MultiProcessor Kernel > #device apic # I/O APIC > > > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > device pci > > device kbdmux # keyboard multiplexer > > # Pseudo devices. > device loop # Network loopback > device random # Entropy device > device ether # Ethernet support > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > device faith # IPv6-to-IPv4 relaying (translation) > > # The `bpf' device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > # Note that 'bpf' is required for DHCP. > device bpf # Berkeley packet filter > > > The domU kernel is booted via pvgrub, ther kernel called via: > > kernel /boot/kernel/kernel > vfs.root.mountfrom=ufs:xbd0s1a,kern.hz=100,xencons=tty > > > Thanks all, > > Fred > _______________________________________________ > 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 Jan 13 03:53:37 2010 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 E3CC01065670 for ; Wed, 13 Jan 2010 03:53:36 +0000 (UTC) (envelope-from bissont@gmail.com) Received: from mail-qy0-f174.google.com (mail-qy0-f174.google.com [209.85.221.174]) by mx1.freebsd.org (Postfix) with ESMTP id 964768FC13 for ; Wed, 13 Jan 2010 03:53:36 +0000 (UTC) Received: by qyk4 with SMTP id 4so10500043qyk.7 for ; Tue, 12 Jan 2010 19:53:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=sRKTTOFOnP3OIx7TF7RDwbKjdWmpBVEy/tfKdzO6Www=; b=TD3ubH/7NPRK8LRCtkIqpnDFTuxzw97LJzwVhymEDLeVG3si1kT/2Q4qJmQv8y1S1M arQUc5yMtIzMCoU3OSWKGX6I2iqJbjwtk6Ep196nn85HcRqCu174Eu1/u/ePRxl47yNz JQWv/U1cn0ii94toIWbbPkIPI6kjDOKEa9dN0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=PkScxUted9Mm70h6l0WnTidRkUMp3iAw6Lys+17kRwWetvQV+wym/XfjaTSaPuOXdg hXXLlG0k5+g6OKfa7ccx4FzqM+Xw6Wq8HVLHKft+tt8MK8pO+C4f5Bs/oeET88/WC2ke T05A3mX/YXr2kFZVFunAEH0rETQ73vEnlSZNM= Received: by 10.224.96.70 with SMTP id g6mr18248628qan.247.1263354809022; Tue, 12 Jan 2010 19:53:29 -0800 (PST) Received: from chow3-lxp.hq.netapp.com (nat-198-95-226-231.netapp.com [198.95.226.231]) by mx.google.com with ESMTPS id 21sm6062743qyk.0.2010.01.12.19.53.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 12 Jan 2010 19:53:27 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Tim Bisson In-Reply-To: <20100112093628.GH62907@deviant.kiev.zoral.com.ua> Date: Tue, 12 Jan 2010 19:53:25 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20100112093628.GH62907@deviant.kiev.zoral.com.ua> To: Kostik Belousov X-Mailer: Apple Mail (2.1077) Cc: freebsd-xen@freebsd.org Subject: Re: Can't boot 8/CURRENT hvm on Quad-Core Opteron 2352 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, 13 Jan 2010 03:53:37 -0000 On Jan 12, 2010, at 1:36 AM, Kostik Belousov wrote: > On Mon, Jan 11, 2010 at 11:36:00PM -0800, Timothy Bisson wrote: >> Hi, >>=20 >> I'm trying to run a FreeBSD 8/CURRENT hvm on XEN, but booting FreeBSD = =20 >> currently panics on a quad-core Operton 2352 box while booting from =20= >> the iso (disabling ACPI doesn't help). >>=20 >> However, I'm successful at running a FreeBSD 8/CURRENT hvm on XEN on = a =20 >> Intel Xeon Nehalem box. I tried booting the same installed disk image = =20 >> (from the Nehalem box) on the Operteron box, but that also resulted = in =20 >> a panic while booting. >>=20 >> The CURRENT iso I'm using is from: >> = ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201001/FreeBSD-9.0-CURRENT-201= 001-amd64-bootonly.iso >>=20 >> I'm using Xen-3.3.1 on both physical boxes, and a BSD 6 hvm works on =20= >> both the Nehalem and Operton boxes... >>=20 >> Here's the backtrace from the opteron box: >> kernel trap 9 with interrupts disabled >>=20 >>=20 >> Fatal trap 9: general protection fault while in kernel mode >> cpuid =3D 0; apic id =3D 00 >> instruction pointer =3D 0x20:0xffffffff80878193 >> stack pointer =3D 0x28:0xffffffff81044bb0 >> frame pointer =3D 0x28:0xffffffff81044bc0 >> code segment =3D base 0x0, limit 0xfffff, type 0x1b >> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags =3D resume, IOPL =3D 0 >> current process =3D 0 () >> [thread pid 0 tid 0 ] >> Stopped at pmap_invalidate_cache_range+0x43: =20 >> clflushl (%rdi) >> db> bt >> bt >> Tracing pid 0 tid 0 td 0xffffffff80c51fc0 >> pmap_invalidate_cache_range() at pmap_invalidate_cache_range+0x43 >> pmap_change_attr_locked() at pmap_change_attr_locked+0x368 >> pmap_change_attr() at pmap_change_attr+0x43 >> pmap_mapdev_attr() at pmap_mapdev_attr+0x112 >> lapic_init() at lapic_init+0x29 >> madt_setup_local() at madt_setup_local+0x26 >> apic_setup_local() at apic_setup_local+0x13 >> mi_startup() at mi_startup+0x59 >> btext() at btext+0x2c >>=20 >>=20 >> I took a look through the bug database and didn't see any similar =20 >> problem reports. Is it reasonable to file a bug report? Is there =20 >> additional information that I should be reporting? >=20 > Set hw.clflush_disable=3D1 at the loader prompt. Thank you. I should have read the Release Notes...= From owner-freebsd-xen@FreeBSD.ORG Fri Jan 15 03:43:01 2010 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 4C9B31065672 for ; Fri, 15 Jan 2010 03:43:01 +0000 (UTC) (envelope-from bissont@gmail.com) Received: from mail-qy0-f174.google.com (mail-qy0-f174.google.com [209.85.221.174]) by mx1.freebsd.org (Postfix) with ESMTP id F0CBA8FC15 for ; Fri, 15 Jan 2010 03:43:00 +0000 (UTC) Received: by qyk4 with SMTP id 4so227326qyk.7 for ; Thu, 14 Jan 2010 19:42:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=YB+5eBWnLyvXUhtklUG5Vqn3imlWuqFBV2GGVq1CXyw=; b=BcTsN8TXEvSqaU6wy7rOFe20tAqrHtb3wayRmnAoufSgqwYfluNVf4xWCaTPKFFqcc NUWzcbUDJikHNBN+O6BkSKOPjpXfjsgyoRyH5WG0vok6saet/SwKMltSlY40pHfI41tk W6w3/0LBMpwJdh9gwdZH3oxl2Wv1iOg2ptevc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=hmEGI6Zujs4vjEhirciCpxZTIYo+e7uX8pSqZgLdMVP9kd+7F/7xLQVeM/VXtTtgGo Iual3m8oFTTij055LOtSO/KMq2ItJCqMaaZ7Qwr2dKQGDRNVSpvFWXv3ipd0h3fEqltH jbbHgPG6jhqJKwy/g5Di+A7a+yKKHrdY2pM/E= Received: by 10.229.62.71 with SMTP id w7mr1612914qch.92.1263526964620; Thu, 14 Jan 2010 19:42:44 -0800 (PST) Received: from chow3-lxp.hq.netapp.com (nat-198-95-226-231.netapp.com [198.95.226.231]) by mx.google.com with ESMTPS id 23sm1086086iwn.15.2010.01.14.19.42.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 14 Jan 2010 19:42:43 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Tim Bisson In-Reply-To: <4B4C703A.3000501@deployis.eu> Date: Thu, 14 Jan 2010 19:42:42 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <1A8F87C2-3790-42CA-B98C-2017B3F8EF9C@gmail.com> References: <20100112093628.GH62907@deviant.kiev.zoral.com.ua> <4B4C703A.3000501@deployis.eu> To: Deploy IS INFO X-Mailer: Apple Mail (2.1077) Cc: freebsd-xen@freebsd.org Subject: Re: Can't boot 8/CURRENT hvm on Quad-Core Opteron 2352 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: Fri, 15 Jan 2010 03:43:01 -0000 On Jan 12, 2010, at 4:51 AM, Deploy IS INFO wrote: >=20 >=20 > Kostik Belousov wrote: >> On Mon, Jan 11, 2010 at 11:36:00PM -0800, Timothy Bisson wrote: >>> Hi, >>>=20 >>> I'm trying to run a FreeBSD 8/CURRENT hvm on XEN, but booting = FreeBSD currently panics on a quad-core Operton 2352 box while booting = from the iso (disabling ACPI doesn't help). >>>=20 >>> However, I'm successful at running a FreeBSD 8/CURRENT hvm on XEN on = a Intel Xeon Nehalem box. I tried booting the same installed disk image = (from the Nehalem box) on the Operteron box, but that also resulted in = a panic while booting. >>>=20 >>> The CURRENT iso I'm using is from: >>> = ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201001/FreeBSD-9.0-CURRENT-201= 001-amd64-bootonly.iso >>>=20 >>> I'm using Xen-3.3.1 on both physical boxes, and a BSD 6 hvm works on = both the Nehalem and Operton boxes... >>>=20 >>> Here's the backtrace from the opteron box: >>> kernel trap 9 with interrupts disabled >>>=20 >>>=20 >>> Fatal trap 9: general protection fault while in kernel mode >>> cpuid =3D 0; apic id =3D 00 >>> instruction pointer =3D 0x20:0xffffffff80878193 >>> stack pointer =3D 0x28:0xffffffff81044bb0 >>> frame pointer =3D 0x28:0xffffffff81044bc0 >>> code segment =3D base 0x0, limit 0xfffff, type 0x1b >>> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >>> processor eflags =3D resume, IOPL =3D 0 >>> current process =3D 0 () >>> [thread pid 0 tid 0 ] >>> Stopped at pmap_invalidate_cache_range+0x43: clflushl = (%rdi) >>> db> bt >>> bt >>> Tracing pid 0 tid 0 td 0xffffffff80c51fc0 >>> pmap_invalidate_cache_range() at pmap_invalidate_cache_range+0x43 >>> pmap_change_attr_locked() at pmap_change_attr_locked+0x368 >>> pmap_change_attr() at pmap_change_attr+0x43 >>> pmap_mapdev_attr() at pmap_mapdev_attr+0x112 >>> lapic_init() at lapic_init+0x29 >>> madt_setup_local() at madt_setup_local+0x26 >>> apic_setup_local() at apic_setup_local+0x13 >>> mi_startup() at mi_startup+0x59 >>> btext() at btext+0x2c >>>=20 >>>=20 >>> I took a look through the bug database and didn't see any similar = problem reports. Is it reasonable to file a bug report? Is there = additional information that I should be reporting? >> Set hw.clflush_disable=3D1 at the loader prompt. >=20 > Hi, >=20 > I'm trying also FreeBSD8 on a nehalem box. When I configure more than = 2 vcpus for the HVM guest I met with the following: >=20 > - With the XENHVM kernel the boot simply stops when the message about = WITNESS performance came. No debug messages, nothing, just stops there = and the PV drivers just attaches before the message >=20 > - With the GENERIC kernel the re driver somehow fails to receive = packages when 4 vcpus configured. Tcpdump showed that packages are going = out, but somehow none received. I'd say it's not really a FreeBSD = problem, but it's wierd enough. >=20 > Could you verify these these two problem on the Opteron and your = Nehalem machine? We are also using Xen-3.3.1. >=20 > Regards, > Andras The XENHVM kernel works fine (both boxes) with more than 2 vcpus. I = received a panic regarding the xn driver, but that went away once I = configured the vif to use netfront. I don't know what model you specify to use the re driver, but the ed and = em drivers work fine.