From owner-freebsd-xen@freebsd.org Sun Apr 1 02:38:32 2018 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF683F74690 for ; Sun, 1 Apr 2018 02:38:32 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A9CC83F75 for ; Sun, 1 Apr 2018 02:38:31 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w312cTKK075774; Sat, 31 Mar 2018 19:38:29 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w312cSHg075773; Sat, 31 Mar 2018 19:38:28 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201804010238.w312cSHg075773@pdx.rh.CN85.dnsmgr.net> Subject: Re: [Bug 224003] xen kernel panics In-Reply-To: <5ABFD26B.8030601@gfsys.co.uk> To: Chris Date: Sat, 31 Mar 2018 19:38:28 -0700 (PDT) CC: freebsd-xen@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 01 Apr 2018 02:38:32 -0000 > On 03/31/18 18:11, Chris wrote: > > On 03/30/18 18:05, Rodney W. Grimes wrote: > > > >> I can affirm that a E56xx cpu should be very capable of supporting Xen. > >> CPU: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz (3059.07-MHz K8-class CPU) > >> Origin="GenuineIntel" Id=0x206c2 Family=0x6 Model=0x2c Stepping=2 > >> Features=0xbfebfbff > >> > >> Features2=0x29ee3ff > >> > >> AMD Features=0x2c100800 > >> AMD Features2=0x1 > >> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > >> TSC: P-state invariant, performance statistics > >> > > Looks like this might be the problem:- > > > (XEN) [VT-D]Disabling IOMMU due to Intel 5500/5520/X58 Chipset errata > > #47, #53 > > Been in a rush today, but should have looked at that a bit more closely > before posting, as istr, saw that mentioned as a bug eleswhere back > from 2015 or so.... https://support.citrix.com/article/CTX136517 That has some info on how to work around this issue. You can turn of the interrupt remapping and still have an iommu, though it is not going be very effective for passthrough of devices. Its linux centric, and I am not quiet sure how to apply those knobs to loader.conf to make xen do the right thing, but it should be possible. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-xen@freebsd.org Mon Apr 2 13:36:59 2018 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB39EF59E3C for ; Mon, 2 Apr 2018 13:36:58 +0000 (UTC) (envelope-from prvs=623839fe0=roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [185.25.65.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.citrix.com", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D4427EC96 for ; Mon, 2 Apr 2018 13:36:57 +0000 (UTC) (envelope-from prvs=623839fe0=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.48,395,1517875200"; d="scan'208";a="70911289" Date: Mon, 2 Apr 2018 14:35:39 +0100 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: "Rodney W. Grimes" CC: Chris , Subject: Re: [Bug 224003] xen kernel panics Message-ID: <20180402133539.4x2wvuz4tia3nukp@MacBook-Pro-de-Roger.local> References: <5ABFD26B.8030601@gfsys.co.uk> <201804010238.w312cSHg075773@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <201804010238.w312cSHg075773@pdx.rh.CN85.dnsmgr.net> User-Agent: NeoMutt/20180323 X-ClientProxiedBy: AMSPEX02CAS02.citrite.net (10.69.22.113) To AMSPEX02CL02.citrite.net (10.69.22.126) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.25 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, 02 Apr 2018 13:36:59 -0000 On Sat, Mar 31, 2018 at 07:38:28PM -0700, Rodney W. Grimes wrote: > > On 03/31/18 18:11, Chris wrote: > > > On 03/30/18 18:05, Rodney W. Grimes wrote: > > > > > >> I can affirm that a E56xx cpu should be very capable of supporting Xen. > > >> CPU: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz (3059.07-MHz K8-class CPU) > > >> Origin="GenuineIntel" Id=0x206c2 Family=0x6 Model=0x2c Stepping=2 > > >> Features=0xbfebfbff > > >> > > >> Features2=0x29ee3ff > > >> > > >> AMD Features=0x2c100800 > > >> AMD Features2=0x1 > > >> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > > >> TSC: P-state invariant, performance statistics > > >> > > > > Looks like this might be the problem:- > > > > > (XEN) [VT-D]Disabling IOMMU due to Intel 5500/5520/X58 Chipset errata > > > #47, #53 > > > > Been in a rush today, but should have looked at that a bit more closely > > before posting, as istr, saw that mentioned as a bug eleswhere back > > from 2015 or so.... > > https://support.citrix.com/article/CTX136517 > > That has some info on how to work around this issue. You can turn > of the interrupt remapping and still have an iommu, though it is > not going be very effective for passthrough of devices. Just add iommu=no-intremap to your xen_cmdline in loader.conf. Roger. From owner-freebsd-xen@freebsd.org Tue Apr 3 14:42:21 2018 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B814F85228 for ; Tue, 3 Apr 2018 14:42:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF97380894 for ; Tue, 3 Apr 2018 14:42:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 15E3C1AC7B for ; Tue, 3 Apr 2018 14:42:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w33EgJS1071299 for ; Tue, 3 Apr 2018 14:42:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w33EgJqN071298 for freebsd-xen@FreeBSD.org; Tue, 3 Apr 2018 14:42:19 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest Date: Tue, 03 Apr 2018 14:42:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bhavesh.davda@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.25 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, 03 Apr 2018 14:42:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188990 --- Comment #23 from Bhavesh Davda --- Hi Roger, it's been quite some time since that last update and am wondering= if this slipped through the cracks. Thanks. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Tue Apr 3 14:50:26 2018 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65590F85AB1 for ; Tue, 3 Apr 2018 14:50:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0256480D0D for ; Tue, 3 Apr 2018 14:50:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3B60D1AC94 for ; Tue, 3 Apr 2018 14:50:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w33EoPZv084472 for ; Tue, 3 Apr 2018 14:50:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w33EoPM8084470 for freebsd-xen@FreeBSD.org; Tue, 3 Apr 2018 14:50:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest Date: Tue, 03 Apr 2018 14:50:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.25 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, 03 Apr 2018 14:50:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188990 --- Comment #24 from Roger Pau Monn=C3=A9 --- Hello, Maybe the dhclient fix is more appropriate? I'm quite lost, so I would recommend that you create a differential review = with what you consider better and add hrs, adrian and the network group as reviewers. Thanks! --=20 You are receiving this mail because: You are the assignee for the bug.=