From owner-freebsd-xen@freebsd.org Mon May 9 10:37:54 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EABCEB342E6 for ; Mon, 9 May 2016 10:37:54 +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 mx1.freebsd.org (Postfix) with ESMTPS id DBA81178A for ; Mon, 9 May 2016 10:37:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49Abs6f086169 for ; Mon, 9 May 2016 10:37:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 197344] tx checksum broken on XEN Date: Mon, 09 May 2016 10:37:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.22 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, 09 May 2016 10:37:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197344 Roger Pau Monn=C3=83=C2=A9 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |royger@freebsd.org --- Comment #2 from Roger Pau Monn=C3=83=C2=A9 --- AFAICT, this is possibly a duplicate of PR 188261, can you please confirm t= hat the issues you are seeing always happen when doing packet forwarding? Also, and in order to try to solve this, can you please post a very simple configuration that can be used to reproduce the issue? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon May 9 10:40:11 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1948AB34331 for ; Mon, 9 May 2016 10:40:11 +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 mx1.freebsd.org (Postfix) with ESMTPS id 0986017FD for ; Mon, 9 May 2016 10:40:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49AeAor089455 for ; Mon, 9 May 2016 10:40:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 09 May 2016 10:40:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE 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.22 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, 09 May 2016 10:40:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #8 from Roger Pau Monn=C3=83=C2=A9 --- Hello, I would really like to reproduce this, but sadly my FreeBSD network knowled= ge is very limited, so please bear with me. When you say: "Set this first machine up with (for example) 'gateway_enable=3D"YES"' etc.= and configure it to route or NAT traffic to the Internet." Can you please provide examples about how to route NAT traffic to the Inter= net? A very simple (reduced) use-case that can be used to reproduce this issue w= ould help me a lot. Thanks, Roger. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon May 9 11:12:07 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15A2AB34ED9 for ; Mon, 9 May 2016 11:12:07 +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 mx1.freebsd.org (Postfix) with ESMTPS id 05F841D9C for ; Mon, 9 May 2016 11:12:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49BC6WK096951 for ; Mon, 9 May 2016 11:12:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 09 May 2016 11:12:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: meyer.sydney@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.22 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, 09 May 2016 11:12:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #9 from Sydney Meyer --- In its most basic form, without doing nat, without have pf loaded, the prob= lem comes up e.g. in the following setup: (PC1) 10.0.1.2/24 on xn0 <--> 10.0.1.1/24 on xn0 (FreeBSD DomU Router) 10.0.2.1/24 on xn1 <--> (PC2) 10.0.2.2/24 on xn0. - Install FreeBSD on DomU Router with 2 paravirtual network interfaces in different subnets - sysctl net.inet.ip.forwarding=3D1 on Router - Setup PC1/2 with FreeBSD/Linux/Windows with the FreeBSD Router as their Gateway. - On PC1: dd if=3D/dev/zero bs=3D1M | nc -l 5001 - On PC2: nc 1.2.3.4 5001 | dd of=3D/dev/zero bs=3D1M - Or any other TCP-Connection, e.g. ssh, for that matter. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon May 9 11:12:32 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14545B34F1C for ; Mon, 9 May 2016 11:12:32 +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 mx1.freebsd.org (Postfix) with ESMTPS id 984B51EC8 for ; Mon, 9 May 2016 11:12:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49BCUBi097988 for ; Mon, 9 May 2016 11:12:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 209327] Under XenServer 6.5 - Live Migration results in a Kernel Panic when the VM 'Lands' on the other Node Date: Mon, 09 May 2016 11:12:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.22 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, 09 May 2016 11:12:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209327 Roger Pau Monn=C3=83=C2=A9 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |royger@freebsd.org --- Comment #2 from Roger Pau Monn=C3=83=C2=A9 --- Sadly I don't seem to be able to reproduce this using Open Source Xen on my hardware. I've sent a patch to update the FreeBSD version that's used for testing with Open Source Xen to 10.3, the test cluster contains quite a lot of different hardware, so it might be able to trigger it. The crash itself looks quite weird, it seems to be caused by the IPIs that = are sent to CPUs in order to setup the PV timers (xentimer_resume). Also vector= 30 is used to deliver security exceptions [0], which I don't even know how they are triggered... Anyway, will get back when I have more information about this. [0] http://wiki.osdev.org/Exceptions --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon May 9 14:26:05 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49A22B34858 for ; Mon, 9 May 2016 14:26:05 +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 mx1.freebsd.org (Postfix) with ESMTPS id 3A0F91648 for ; Mon, 9 May 2016 14:26:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49EQ49U057578 for ; Mon, 9 May 2016 14:26:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 09 May 2016 14:26:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE 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.22 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, 09 May 2016 14:26:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #10 from Roger Pau Monn=C3=83=C2=A9 --- (In reply to Sydney Meyer from comment #9) Just as a side note, I haven't been able to reproduce this using a FreeBSD Dom0, I will now try with a Linux Dom0 (I guess Linux is more picky about checksums?). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon May 9 16:02:24 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D522B34F87 for ; Mon, 9 May 2016 16:02:24 +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 mx1.freebsd.org (Postfix) with ESMTPS id 3DC3616EF for ; Mon, 9 May 2016 16:02:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49G2NHM093926 for ; Mon, 9 May 2016 16:02:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 09 May 2016 16:02:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pgadmin@pse-consulting.de 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.22 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, 09 May 2016 16:02:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #11 from Andreas Pflug --- It is a problem with DomUs, not Dom0. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon May 9 16:08:30 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC7C9B331C6 for ; Mon, 9 May 2016 16:08:30 +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 mx1.freebsd.org (Postfix) with ESMTPS id DD87E1BFF for ; Mon, 9 May 2016 16:08:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49G8TCI006549 for ; Mon, 9 May 2016 16:08:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 197344] tx checksum broken on XEN Date: Mon, 09 May 2016 16:08:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pgadmin@pse-consulting.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- 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.22 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, 09 May 2016 16:08:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197344 --- Comment #3 from Andreas Pflug --- #188261 apparently describes the same problem. How to reproduce: DomU #1 <-> DomU/Router <-> DomU #2 all on same Xen host. Accessing DomU#2 from DomU#1 (e.g. ssh) hardly works, until tx checksum is disabled. When a host that's not hosted on the same Xen machine is involved, everything works as expected. Tested with Xen4.1 and 4.4, DomU/Router FreeBSD 10.1 (pfSense) and 10.2 (opnSense). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon May 9 17:22:26 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D4F5B34B5D for ; Mon, 9 May 2016 17:22:26 +0000 (UTC) (envelope-from StephenJo@LivingComputerMuseum.org) Received: from mail.vulcan.com (wstmsx1.vulcan.com [216.220.192.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "outlook.vulcan.com", Issuer "Entrust Certification Authority - L1K" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D7411A89 for ; Mon, 9 May 2016 17:22:25 +0000 (UTC) (envelope-from StephenJo@LivingComputerMuseum.org) Received: from WSTMAIL1.corp.vnw.com (10.0.41.230) by WSTMSX1.corp.vnw.com (10.0.41.48) with Microsoft SMTP Server (TLS) id 15.1.225.42; Mon, 9 May 2016 10:22:03 -0700 Received: from WSTMAIL1.corp.vnw.com (10.0.41.230) by WSTMail1.corp.vnw.com (10.0.41.230) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Mon, 9 May 2016 10:22:03 -0700 Received: from 505CAS1.corp.vnw.com (10.0.100.217) by WSTMAIL1.corp.vnw.com (10.0.41.230) with Microsoft SMTP Server (TLS) id 15.0.1130.7 via Frontend Transport; Mon, 9 May 2016 10:22:03 -0700 Received: from 505MBX1.corp.vnw.com ([169.254.2.139]) by 505CAS1.corp.vnw.com ([10.0.100.217]) with mapi id 14.03.0266.001; Mon, 9 May 2016 10:22:03 -0700 From: Stephen Jones To: "freebsd-xen@freebsd.org" Subject: RE: xn ethernet issues as DOMU under NetBSD DOM0 Thread-Topic: RE: xn ethernet issues as DOMU under NetBSD DOM0 Thread-Index: AdGqF0wb6BV+TKtXT3qy1n2nMmsZQw== Date: Mon, 9 May 2016 17:22:02 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.95.80.23] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 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, 09 May 2016 17:22:26 -0000 Roger writes: > I'm worried it might have something to do with the "feature-sg" node that= 's exported on the backend path. It seems like FreeBSD correctly > acknowle= dges it, but there might be some bugs there. > Stephen, can you paste the output of running `xenstore-ls -fp` on the Dom= 0 when the FreeBSD DomU has booted? Could you also paste the kernel > dmesg= of the FreeBSD guest? > What seems even more strange is the fact that it works during installs bu= t not after, the kernel is exactly the same for installers, so I'm puzzled. This actually may be related to the TX checksum issue. I've confirmed that= during installation I can use FTP to download distros which explains why the installation process works "fine" but when I spawn a shell, I canno= t successfully make an ssh connection to a remote host. After installation, I confirmed that I can indeed run FTP (which is how I g= ot the sys src to build a new kernel). I setup telnetd and was able to log= in remotely but any long output would get clobbered. Here is the xenstore-ls -fp output you requested. Is there anything I shou= ld provide concerning a possible link to the TX checksum bug? /local/domain/0/backend/vbd/96 =3D "" (n0) /local/domain/0/backend/vbd/96/768 =3D "" (n0,r96) /local/domain/0/backend/vbd/96/768/frontend =3D "/local/domain/96/device/vb= d/768" (n0,r96) /local/domain/0/backend/vbd/96/768/params =3D "/vps/domu/freebsd30" (n0,r= 96) /local/domain/0/backend/vbd/96/768/script =3D "/usr/pkg/etc/xen/scripts/blo= ck" (n0,r96) /local/domain/0/backend/vbd/96/768/physical-device =3D "1052387" (n0,r96) /local/domain/0/backend/vbd/96/768/frontend-id =3D "96" (n0,r96) /local/domain/0/backend/vbd/96/768/online =3D "1" (n0,r96) /local/domain/0/backend/vbd/96/768/removable =3D "0" (n0,r96) /local/domain/0/backend/vbd/96/768/bootable =3D "1" (n0,r96) /local/domain/0/backend/vbd/96/768/state =3D "4" (n0,r96) /local/domain/0/backend/vbd/96/768/dev =3D "hda" (n0,r96) /local/domain/0/backend/vbd/96/768/type =3D "phy" (n0,r96) /local/domain/0/backend/vbd/96/768/mode =3D "w" (n0,r96) /local/domain/0/backend/vbd/96/768/device-type =3D "disk" (n0,r96) /local/domain/0/backend/vbd/96/768/discard-enable =3D "1" (n0,r96) /local/domain/0/backend/vbd/96/768/vnd =3D "/dev/vnd30d" (n0,r96) /local/domain/0/backend/vbd/96/768/hotplug-status =3D "connected" (n0,r96= ) /local/domain/0/backend/vbd/96/768/sectors =3D "41943040" (n0,r96) /local/domain/0/backend/vbd/96/768/info =3D "0" (n0,r96) /local/domain/0/backend/vbd/96/768/sector-size =3D "512" (n0,r96) /local/domain/0/backend/vbd/96/768/feature-flush-cache =3D "1" (n0,r96) /local/domain/0/backend/vbd/96/5632 =3D "" (n0,r96) /local/domain/0/backend/vbd/96/5632/frontend =3D "/local/domain/96/device/v= bd/5632" (n0,r96) /local/domain/0/backend/vbd/96/5632/params =3D "/vps/domu_spare_disks/smj_8= 0" (n0,r96) /local/domain/0/backend/vbd/96/5632/script =3D "/usr/pkg/etc/xen/scripts/bl= ock" (n0,r96) /local/domain/0/backend/vbd/96/5632/physical-device =3D "5246467" (n0,r96= ) /local/domain/0/backend/vbd/96/5632/frontend-id =3D "96" (n0,r96) /local/domain/0/backend/vbd/96/5632/online =3D "1" (n0,r96) /local/domain/0/backend/vbd/96/5632/removable =3D "1" (n0,r96) /local/domain/0/backend/vbd/96/5632/bootable =3D "1" (n0,r96) /local/domain/0/backend/vbd/96/5632/state =3D "4" (n0,r96) /local/domain/0/backend/vbd/96/5632/dev =3D "hdc" (n0,r96) /local/domain/0/backend/vbd/96/5632/type =3D "phy" (n0,r96) /local/domain/0/backend/vbd/96/5632/mode =3D "r" (n0,r96) /local/domain/0/backend/vbd/96/5632/device-type =3D "cdrom" (n0,r96) /local/domain/0/backend/vbd/96/5632/discard-enable =3D "0" (n0,r96) /local/domain/0/backend/vbd/96/5632/vnd =3D "/dev/vnd80d" (n0,r96) /local/domain/0/backend/vbd/96/5632/hotplug-status =3D "connected" (n0,r9= 6) /local/domain/0/backend/vbd/96/5632/sectors =3D "572924" (n0,r96) /local/domain/0/backend/vbd/96/5632/info =3D "4" (n0,r96) /local/domain/0/backend/vbd/96/5632/sector-size =3D "512" (n0,r96) /local/domain/0/backend/vbd/96/5632/feature-flush-cache =3D "1" (n0,r96) /local/domain/0/backend/console/96 =3D "" (n0) /local/domain/0/backend/console/96/0 =3D "" (n0,r96) /local/domain/0/backend/console/96/0/frontend =3D "/local/domain/96/console= " (n0,r96) /local/domain/0/backend/console/96/0/frontend-id =3D "96" (n0,r96) /local/domain/0/backend/console/96/0/online =3D "1" (n0,r96) /local/domain/0/backend/console/96/0/state =3D "1" (n0,r96) /local/domain/0/backend/console/96/0/protocol =3D "vt100" (n0,r96) /local/domain/0/backend/vif/96 =3D "" (n0) /local/domain/0/backend/vif/96/0 =3D "" (n0,r96) /local/domain/0/backend/vif/96/0/frontend =3D "/local/domain/96/device/vif/= 0" (n0,r96) /local/domain/0/backend/vif/96/0/frontend-id =3D "96" (n0,r96) /local/domain/0/backend/vif/96/0/online =3D "1" (n0,r96) /local/domain/0/backend/vif/96/0/state =3D "4" (n0,r96) /local/domain/0/backend/vif/96/0/script =3D "/usr/pkg/etc/xen/scripts/vif-b= ridge" (n0,r96) /local/domain/0/backend/vif/96/0/mac =3D "00:16:3e:00:00:30" (n0,r96) /local/domain/0/backend/vif/96/0/bridge =3D "bridge0" (n0,r96) /local/domain/0/backend/vif/96/0/handle =3D "0" (n0,r96) /local/domain/0/backend/vif/96/0/type =3D "vif_ioemu" (n0,r96) /local/domain/0/backend/vif/96/0/vifname =3D "xvif96i0" (n0,r96) /local/domain/0/backend/vif/96/0/feature-rx-copy =3D "1" (n0,r96) /local/domain/0/backend/vif/96/0/feature-rx-flip =3D "1" (n0,r96) /local/domain/0/backend/vif/96/0/hotplug-status =3D "connected" (n0,r96) /local/domain/0/backend/vkbd/96 =3D "" (n0) /local/domain/0/backend/vkbd/96/0 =3D "" (n0,r96) /local/domain/0/backend/vkbd/96/0/frontend =3D "/local/domain/96/device/vkb= d/0" (n0,r96) /local/domain/0/backend/vkbd/96/0/frontend-id =3D "96" (n0,r96) /local/domain/0/backend/vkbd/96/0/online =3D "1" (n0,r96) /local/domain/0/backend/vkbd/96/0/state =3D "2" (n0,r96) /local/domain/0/backend/vkbd/96/0/feature-abs-pointer =3D "1" (n0,r96) /local/domain/0/backend/vkbd/96/0/hotplug-status =3D "connected" (n0,r96) /local/domain/0/device-model/96 =3D "" (n0) /local/domain/0/device-model/96/disable_pf =3D "0" (n0) /local/domain/0/device-model/96/state =3D "running" (n0) /local/domain/12/memory/videoram =3D "4096" (n0,r12) /local/domain/17/store/ring-ref =3D "5966062" (n0,r17) /local/domain/17/console/ring-ref =3D "5966061" (n0,r17) /local/domain/32/memory/videoram =3D "4096" (n0,r32) /local/domain/61/memory/videoram =3D "4096" (n0,r61) /local/domain/96 =3D "" (n0,r96) /local/domain/96/vm =3D "/vm/27da8f93-0916-e611-ae8b-0025902ad41a" (n0,r9= 6) /local/domain/96/name =3D "freebsd30" (n0,r96) /local/domain/96/cpu =3D "" (n0,r96) /local/domain/96/cpu/0 =3D "" (n0,r96) /local/domain/96/cpu/0/availability =3D "online" (n0,r96) /local/domain/96/memory =3D "" (n0,r96) /local/domain/96/memory/static-max =3D "1048576" (n0,r96) /local/domain/96/memory/target =3D "1044480" (n0,r96) /local/domain/96/memory/videoram =3D "4096" (n0,r96) /local/domain/96/device =3D "" (n0,r96) /local/domain/96/device/suspend =3D "" (n0,r96) /local/domain/96/device/suspend/event-channel =3D "" (n96) /local/domain/96/device/vbd =3D "" (n0,r96) /local/domain/96/device/vbd/768 =3D "" (n96,r0) /local/domain/96/device/vbd/768/backend =3D "/local/domain/0/backend/vbd/96= /768" (n96,r0) /local/domain/96/device/vbd/768/backend-id =3D "0" (n96,r0) /local/domain/96/device/vbd/768/state =3D "4" (n96,r0) /local/domain/96/device/vbd/768/virtual-device =3D "768" (n96,r0) /local/domain/96/device/vbd/768/device-type =3D "disk" (n96,r0) /local/domain/96/device/vbd/768/ring-ref =3D "8" (n96,r0) /local/domain/96/device/vbd/768/event-channel =3D "7" (n96,r0) /local/domain/96/device/vbd/768/protocol =3D "x86_64-abi" (n96,r0) /local/domain/96/device/vbd/5632 =3D "" (n96,r0) /local/domain/96/device/vbd/5632/backend =3D "/local/domain/0/backend/vbd/9= 6/5632" (n96,r0) /local/domain/96/device/vbd/5632/backend-id =3D "0" (n96,r0) /local/domain/96/device/vbd/5632/state =3D "1" (n96,r0) /local/domain/96/device/vbd/5632/virtual-device =3D "5632" (n96,r0) /local/domain/96/device/vbd/5632/device-type =3D "cdrom" (n96,r0) /local/domain/96/device/vkbd =3D "" (n0,r96) /local/domain/96/device/vkbd/0 =3D "" (n96,r0) /local/domain/96/device/vkbd/0/backend =3D "/local/domain/0/backend/vkbd/96= /0" (n96,r0) /local/domain/96/device/vkbd/0/backend-id =3D "0" (n96,r0) /local/domain/96/device/vkbd/0/state =3D "1" (n96,r0) /local/domain/96/device/vif =3D "" (n0,r96) /local/domain/96/device/vif/0 =3D "" (n96,r0) /local/domain/96/device/vif/0/backend =3D "/local/domain/0/backend/vif/96/0= " (n96,r0) /local/domain/96/device/vif/0/backend-id =3D "0" (n96,r0) /local/domain/96/device/vif/0/state =3D "4" (n96,r0) /local/domain/96/device/vif/0/handle =3D "0" (n96,r0) /local/domain/96/device/vif/0/mac =3D "00:16:3e:00:00:30" (n96,r0) /local/domain/96/device/vif/0/tx-ring-ref =3D "768" (n96,r0) /local/domain/96/device/vif/0/rx-ring-ref =3D "265" (n96,r0) /local/domain/96/device/vif/0/event-channel =3D "8" (n96,r0) /local/domain/96/device/vif/0/request-rx-copy =3D "1" (n96,r0) /local/domain/96/device/vif/0/feature-rx-notify =3D "1" (n96,r0) /local/domain/96/device/vif/0/feature-sg =3D "1" (n96,r0) /local/domain/96/device/vif/0/feature-gso-tcpv4 =3D "1" (n96,r0) /local/domain/96/control =3D "" (n0,r96) /local/domain/96/control/shutdown =3D "" (n96) /local/domain/96/control/platform-feature-multiprocessor-suspend =3D "1" = (n0,r96) /local/domain/96/control/platform-feature-xs_reset_watches =3D "1" (n0,r9= 6) /local/domain/96/hvmloader =3D "" (n0,r96) /local/domain/96/hvmloader/bios =3D "rombios" (n0,r96) /local/domain/96/hvmloader/allow-memory-relocate =3D "1" (n0,r96) /local/domain/96/data =3D "" (n96) /local/domain/96/domid =3D "96" (n0,r96) /local/domain/96/store =3D "" (n0,r96) /local/domain/96/store/port =3D "1" (n0,r96) /local/domain/96/store/ring-ref =3D "1044476" (n0,r96) /local/domain/96/platform =3D "" (n0,r96) /local/domain/96/platform/acpi =3D "1" (n0,r96) /local/domain/96/platform/acpi_s3 =3D "1" (n0,r96) /local/domain/96/platform/acpi_s4 =3D "1" (n0,r96) /local/domain/96/console =3D "" (n0,r96) /local/domain/96/console/backend =3D "/local/domain/0/backend/console/96/0"= (n0,r96) /local/domain/96/console/backend-id =3D "0" (n96,r0) /local/domain/96/console/limit =3D "1048576" (n0,r96) /local/domain/96/console/type =3D "xenconsoled" (n0,r96) /local/domain/96/console/output =3D "pty" (n0,r96) /local/domain/96/console/tty =3D "/dev/pts/12" (n0,r96) /local/domain/96/console/port =3D "2" (n0,r96) /local/domain/96/console/ring-ref =3D "1044479" (n0,r96) /local/domain/96/console/vnc-port =3D "5900" (n0,r96) /local/domain/96/console/vnc-listen =3D "192.94.73.43" (n0,r96) /local/domain/96/image =3D "" (n0,r96) /local/domain/96/image/device-model-pid =3D "22682" (n0,r96) /vm/27da8f93-0916-e611-ae8b-0025902ad41a =3D "" (n0,r96) /vm/27da8f93-0916-e611-ae8b-0025902ad41a/name =3D "freebsd30" (n0,r96) /vm/27da8f93-0916-e611-ae8b-0025902ad41a/uuid =3D "27da8f93-0916-e611-ae8b-= 0025902ad41a" (n0,r96) /vm/27da8f93-0916-e611-ae8b-0025902ad41a/rtc =3D "" (n0,r96) /vm/27da8f93-0916-e611-ae8b-0025902ad41a/rtc/timeoffset =3D "" (n0,r96) /vm/27da8f93-0916-e611-ae8b-0025902ad41a/image =3D "" (n0,r96) /vm/27da8f93-0916-e611-ae8b-0025902ad41a/image/ostype =3D "hvm" (n0,r96) /vm/27da8f93-0916-e611-ae8b-0025902ad41a/start_time =3D "1462814106.77" (= n0,r96) /libxl/96 =3D "" (n0) /libxl/96/dm-version =3D "qemu_xen_traditional" (n0) From owner-freebsd-xen@freebsd.org Mon May 9 17:36:48 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B65D2B34E0A for ; Mon, 9 May 2016 17:36:48 +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 mx1.freebsd.org (Postfix) with ESMTPS id 951651301 for ; Mon, 9 May 2016 17:36:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49HakPV024901 for ; Mon, 9 May 2016 17:36:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 09 May 2016 17:36:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE 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.22 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, 09 May 2016 17:36:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #12 from Roger Pau Monn=C3=83=C2=A9 --- (In reply to Andreas Pflug from comment #11) I know, I'm just pointing out that this doesn't happen with a FreeBSD Dom0 running FreeBSD DomUs. I guess you are always using a Linux Dom0? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Tue May 10 08:43:23 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7316DB34F2C for ; Tue, 10 May 2016 08:43:23 +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 mx1.freebsd.org (Postfix) with ESMTPS id 634621EB5 for ; Tue, 10 May 2016 08:43:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4A8hLn6091285 for ; Tue, 10 May 2016 08:43:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Tue, 10 May 2016 08:43:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pgadmin@pse-consulting.de 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.22 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, 10 May 2016 08:43:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #13 from Andreas Pflug --- Yes, only Linux Dom0. I've only seen one anomaly with offloading, which was fixed in Windows PVM drivers a long time ago, so I assume that there's something in FreeBSD Dom0 that's disguising the bug. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Tue May 10 09:01:42 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1EEE0B336B5 for ; Tue, 10 May 2016 09:01:42 +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 mx1.freebsd.org (Postfix) with ESMTPS id 0EC431AC9 for ; Tue, 10 May 2016 09:01:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4A91fFf076898 for ; Tue, 10 May 2016 09:01:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 209327] Under XenServer 6.5 - Live Migration results in a Kernel Panic when the VM 'Lands' on the other Node Date: Tue, 10 May 2016 09:01:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kpielorz@tdx.co.uk X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- 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.22 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, 10 May 2016 09:01:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209327 --- Comment #3 from kpielorz@tdx.co.uk --- Hi, In your test - did you use shared storage? Having looked at this yesterday, and this morning - I tried setting up a completely separate pool - and found: - Live migration with local storage in XenCenter Works. - Live migration with shared (iSCSI) storage panics. - Live migration from shared (iSCSI) to local storage panics. - Live migration from local storage to shared (iSCSI) panics. All of the above complete fine with FreeBSD 10.2. I've also tested this on = both our production XenServer 6.5 / HP Proliant Gen8 pool - and test 6.5 / Proli= ant Gen9 pool - with the same results. I don't know if your test used shared, or local storage. -Karl --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Tue May 10 10:38:33 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CA98B356E1 for ; Tue, 10 May 2016 10:38:33 +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 mx1.freebsd.org (Postfix) with ESMTPS id 0D0EE18CA for ; Tue, 10 May 2016 10:38:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4AAcW76074149 for ; Tue, 10 May 2016 10:38:32 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 209327] Under XenServer 6.5 - Live Migration results in a Kernel Panic when the VM 'Lands' on the other Node Date: Tue, 10 May 2016 10:38:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- 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.22 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, 10 May 2016 10:38:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209327 --- Comment #4 from Roger Pau Monn=C3=83=C2=A9 --- (In reply to kpielorz from comment #3) That's even more weird. Could it be that the VM with local storage only has= 1 vCPU, while the VMs with shared storage have more than 1 vCPU? Could you try to migrate a VM with only 1 vCPU and see if the same happens? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Tue May 10 10:42:32 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DA83B359FD for ; Tue, 10 May 2016 10:42:32 +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 mx1.freebsd.org (Postfix) with ESMTPS id 0DD571E40 for ; Tue, 10 May 2016 10:42:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4AAgVh1086742 for ; Tue, 10 May 2016 10:42:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 209327] Under XenServer 6.5 - Live Migration results in a Kernel Panic when the VM 'Lands' on the other Node Date: Tue, 10 May 2016 10:42:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-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: --- X-Bugzilla-Assigned-To: royger@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created 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.22 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, 10 May 2016 10:42:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209327 Roger Pau Monn=C3=83=C2=A9 changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress Assignee|freebsd-xen@FreeBSD.org |royger@freebsd.org --- Comment #5 from Roger Pau Monn=C3=83=C2=A9 --- Created attachment 170177 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D170177&action= =3Dedit Proposed fix Could you also try the following patch on a VM with vCPUs > 1? It should apply cleanly against either 10.3-RELEASE source or the stable/10 branch, and you should only need to recompile the kernel. FWIW, I would just download 10.3 sources, apply the patch and recompile the kernel. Thanks. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Tue May 10 14:49:46 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5583DB360CB for ; Tue, 10 May 2016 14:49:46 +0000 (UTC) (envelope-from prvs=9316acc9e=wei.liu2@citrix.com) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB01C11FB; Tue, 10 May 2016 14:49:44 +0000 (UTC) (envelope-from prvs=9316acc9e=wei.liu2@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,604,1454976000"; d="scan'208";a="359548379" Date: Tue, 10 May 2016 15:48:33 +0100 From: Wei Liu To: Stephen Jones CC: "'K. Macy'" , 'Miguel C' , "wei.liu2@citrix.com" , "'freebsd-xen@freebsd.org'" Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 Message-ID: <20160510144833.GJ12241@citrix.com> References: <20160503072441.qgqgaw52sijybg4a@mac> <20160503093211.hkmbbqr6t2fbxqqa@mac> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 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, 10 May 2016 14:49:46 -0000 I've only gotten two emails on this, so forgive me if this has been discussed. On Sat, May 07, 2016 at 04:11:52PM +0000, Stephen Jones wrote: > From: kmacybsd@gmail.com [mailto:kmacybsd@gmail.com] On Behalf Of K. Macy > >That would explain it. If the Linux backend supports TSO, then netfront will of course advertise TSO. And >presumably there's no way to query the netback, since Xen is linux-centric. Assuming you haven't already I would >disable TSO. > > > Or have you already tried that? > > This morning I've tried building a kernel without the TCP_OFFLOAD option. When booting the new system, I see this in dmesg: > > xn0: at device/vif/0 on xenbusb_front0 > xn0: Ethernet address: 00:16:3e:00:00:30 > xn0: backend features: feature-sg feature-gso-tcp4 > xn_txeof: WARNING: response is -1! > This means the backend returns -1 for the tx request, but -1 is just a general error code so it doesn't reveal much. It would be interesting to see if there is anything shown on the backend side -- if netbsd's netback logs something. > Ifconfig -v xn0 looks like: > > xn0: flags=8843 metric 0 mtu 1500 > options=403 > > Pings work, ftp works (I was able to get the src.txz file off of ftp.freebsd.org to build the kernel) > ssh does not work (handshaking fails) but I can login via telnet. However, just about anything > that requires lots of output gets a bit clobbered. > > Are there any other kernel/sysctl parameters I should be disabling? > > It is almost working, but I need help to know if this is a netfront or a netback issue. If it is a NetBSD issue > I'll move the discussion over to port-xen@netbsd.org I think what you can do is to try the same kernel with a Linux backend. That would be a good way of telling which side is at fault. Wei. From owner-freebsd-xen@freebsd.org Tue May 10 16:00:44 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DF57B35ADC for ; Tue, 10 May 2016 16:00:44 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF4621044; Tue, 10 May 2016 16:00:43 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id u64so20203617lff.3; Tue, 10 May 2016 09:00:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fz/HdIHP0uWbNsGznZdJFksh7cg0HUb37+Yw/9AHSZo=; b=qOfRb1eYBilgQty2JKAsV0ibEq1bTCKyMtWr8bs2eEmoBmQAflwIVaqUscrRkGINPK xM9QYB6AW4ZVL9lB2g3uOHH1p4hdgSsulFnWyskqbXoFd1PJMxm7M7wbfvw3RE6yVsKd Ns6pbXnO44I8hlppnxtzcZto8V8ZvHkimEZ11FddAstaeEiuE7c+OGVflZ6b8Uwz8KTm ZTBxATHCdGtWzUi59gBJAQFD6QzWFmLYfbTbByPvVn91laeALKdNvZmgsUn8SP3+6zVz oGGsyzeoYjn0xX51NmyNVXjD53gkGANUm4+YggvlqzxoTrqoadC1hS1JRu54lJa9FqYz tOHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fz/HdIHP0uWbNsGznZdJFksh7cg0HUb37+Yw/9AHSZo=; b=H6iFBK9EBsI89gO9uTs50zML+En8sOTefHSxNcXtNYyl78KovP675YqUEXHAkq8pW4 7L/mOBfMSnDl4I+/CPByRlVNimY5frWzK5M7RTZBgbOAPxK/bUQNd35gJMnr4Ny2QHZd hlGyfPMjECJLB9AG52VZoTMLsWv6a3AFLTPhwOAcRSb6KI4aKrHrMKXe4//KM5Ttv3+R NxPQ/IaxZKcWIJL3mjTaWR94qXqGpX9HdTY559YLe9XNoMNo5LtU9n5NFrwFCBf6Ij5o DyZCwx0qcAjf8T+2y5xx2u/4ASc+w4VRQvk/yB7Gjx7mZnzj1xCdWcT3hEtGdS1Ze2Pr RQDw== X-Gm-Message-State: AOPr4FU1pPZrHQ+LA+69i5jEFYAQY+kAKZ8Q907reg4BgxGlmbghDZzivyT6Nl2rtw4647mkQllHnTdJyjFnhQ== X-Received: by 10.25.16.215 with SMTP id 84mr15354821lfq.18.1462896042297; Tue, 10 May 2016 09:00:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.15.213 with HTTP; Tue, 10 May 2016 09:00:02 -0700 (PDT) In-Reply-To: <20160510144833.GJ12241@citrix.com> References: <20160503072441.qgqgaw52sijybg4a@mac> <20160503093211.hkmbbqr6t2fbxqqa@mac> <20160510144833.GJ12241@citrix.com> From: Miguel C Date: Tue, 10 May 2016 17:00:02 +0100 Message-ID: Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 To: Wei Liu Cc: Stephen Jones , "K. Macy" , "freebsd-xen@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 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, 10 May 2016 16:00:44 -0000 See this PR from 2014 --> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 (there another earlier about the same error message on 9.X and that was fixed on 10-CURRENT at the time, but was "broke" later) The issue happen with any NetBSD version from 5.x to 7.x with any xen version but it only stared in FreeBSD 10-Current, so I was always inclined to this being a regression in 10 not a NetBSD backend issue. Also I did post in netbsd mailling list and the reply was something in the lines of "was working fine, nothing changed at our side, so its probably FreeBSD problem" Also as I posted in that PR I experienced a similar issue with Windows GPLPV drivers and the dev fixed it, the issue was that certain features were not supported and the frontend just assume they were cause that's how it works on linux, and I'm no expert so I can go into much detail, but it was related to checksum, tso and I think gso. I tried to bisect the git commits, but there was simply to much changes, what I did find was that this never worked on 10.x +++ only 9, anyway everything was reported there and eventually I got no replies back so I gave up on NetBSD+FreeBSD-10. Unfortunately this needs someone with proper skills on either side (netbsd/freeBSD) to be fixed, the perfect solution would be to add NetBSD backend support for this things (just not sure if its worth the time for the possible performance gain!? - also that's a question for the NetBSD folks ofc) From owner-freebsd-xen@freebsd.org Thu May 12 09:35:37 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75EE3B37D04 for ; Thu, 12 May 2016 09:35:37 +0000 (UTC) (envelope-from prvs=93319c3d4=roger.pau@citrix.com) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 144691358 for ; Thu, 12 May 2016 09:35:36 +0000 (UTC) (envelope-from prvs=93319c3d4=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,609,1454976000"; d="scan'208";a="353413084" Date: Thu, 12 May 2016 11:35:25 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Miguel C CC: Wei Liu , "freebsd-xen@freebsd.org" , Stephen Jones Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 Message-ID: <20160512093525.i6c64lqckyk3qgiq@mac> References: <20160503093211.hkmbbqr6t2fbxqqa@mac> <20160510144833.GJ12241@citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 09:35:37 -0000 Hello, On Tue, May 10, 2016 at 05:00:02PM +0100, Miguel C wrote: > See this PR from 2014 --> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 > > (there another earlier about the same error message on 9.X and that was > fixed on 10-CURRENT at the time, but was "broke" later) > > The issue happen with any NetBSD version from 5.x to 7.x with any xen > version but it only stared in FreeBSD 10-Current, so I was always inclined > to this being a regression in 10 not a NetBSD backend issue. Also I did > post in netbsd mailling list and the reply was something in the lines of > "was working fine, nothing changed at our side, so its probably FreeBSD > problem" > > Also as I posted in that PR I experienced a similar issue with Windows > GPLPV drivers and the dev fixed it, the issue was that certain features > were not supported and the frontend just assume they were cause that's how > it works on linux, and I'm no expert so I can go into much detail, but it > was related to checksum, tso and I think gso. > > I tried to bisect the git commits, but there was simply to much changes, > what I did find was that this never worked on 10.x +++ only 9, anyway > everything was reported there and eventually I got no replies back so I > gave up on NetBSD+FreeBSD-10. > > Unfortunately this needs someone with proper skills on either side > (netbsd/freeBSD) to be fixed, the perfect solution would be to add NetBSD > backend support for this things (just not sure if its worth the time for > the possible performance gain!? - also that's a question for the NetBSD > folks ofc) I think I have found what's causing the issue, but I don't have a NetBSD Dom0 in order to test the fix, could some of you please test the following patch and report back: https://people.freebsd.org/~royger/0001-xen-netfront-fix-feature-detection.patch It should apply cleanly against FreeBSD HEAD. Thanks, Roger. From owner-freebsd-xen@freebsd.org Thu May 12 14:14:29 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0A41B36CA1 for ; Thu, 12 May 2016 14:14:29 +0000 (UTC) (envelope-from StephenJo@LivingComputerMuseum.org) Received: from mail.vulcan.com (wstcas2.vulcan.com [216.220.192.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.vulcan.com", Issuer "Entrust Certification Authority - L1K" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE8DA19A5 for ; Thu, 12 May 2016 14:14:28 +0000 (UTC) (envelope-from StephenJo@LivingComputerMuseum.org) Received: from WSTMAIL1.corp.vnw.com (10.0.41.230) by WSTCAS2.corp.vnw.com (10.0.41.64) with Microsoft SMTP Server (TLS) id 14.3.266.1; Thu, 12 May 2016 07:13:05 -0700 Received: from WSTMAIL1.corp.vnw.com (10.0.41.230) by WSTMail1.corp.vnw.com (10.0.41.230) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Thu, 12 May 2016 07:13:04 -0700 Received: from 505CAS2.corp.vnw.com (10.0.100.210) by WSTMAIL1.corp.vnw.com (10.0.41.230) with Microsoft SMTP Server (TLS) id 15.0.1130.7 via Frontend Transport; Thu, 12 May 2016 07:13:04 -0700 Received: from 505MBX1.corp.vnw.com ([169.254.2.139]) by 505CAS2.corp.vnw.com ([10.0.100.210]) with mapi id 14.03.0266.001; Thu, 12 May 2016 07:13:04 -0700 From: Stephen Jones To: "'freebsd-xen@freebsd.org'" CC: =?iso-8859-1?Q?=27Roger_Pau_Monn=E9=27_=28roger=2Epau=40citrix=2Ecom=29?= , "Miguel C (miguelmclara@gmail.com)" , Wei Liu Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 FIXED! Thread-Topic: xn ethernet issues as DOMU under NetBSD DOM0 FIXED! Thread-Index: AdGsWCvs64f0hdjxS726AnSBgohAJg== Date: Thu, 12 May 2016 14:13:03 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.100.218] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 14:14:29 -0000 Roger writes: > I think I have found what's causing the issue, but I don't have a NetBSD > Dom0 in order to test the fix, could some of you please test the followin= g patch and report back: > > > https://people.freebsd.org/~royger/0001-xen-netfront-fix-feature-detectio= n.patch > > It should apply cleanly against FreeBSD HEAD. --- a/sys/dev/xen/netfront/netfront.c +++ b/sys/dev/xen/netfront/netfront.c @@ -2016,7 +2016,7 @@ xn_query_features(struct netfront_info *np) device_printf(np->xbdev, "backend features:"); =20 if (xs_scanf(XST_NIL, xenbus_get_otherend_path(np->xbdev), - "feature-sg", NULL, "%d", &val) < 0) + "feature-sg", NULL, "%d", &val) !=3D 0) val =3D 0; =20 np->maxfrags =3D 1; @@ -2026,7 +2026,7 @@ xn_query_features(struct netfront_info *np) } =20 if (xs_scanf(XST_NIL, xenbus_get_otherend_path(np->xbdev), - "feature-gso-tcpv4", NULL, "%d", &val) < 0) + "feature-gso-tcpv4", NULL, "%d", &val) !=3D 0) val =3D 0; =20 np->xn_ifp->if_capabilities &=3D ~(IFCAP_TSO4|IFCAP_LRO); FreeBSD freebsd 11.0-CURRENT FreeBSD 11.0-CURRENT #1: Thu May 12 13:48:47 U= TC 2016 root@freebsd:/usr/src/sys/amd64/compile/SDF amd64 xn0: flags=3D8843 metric 0 mtu 1500 options=3D3 ether 00:16:3e:00:00:30 inet 192.94.73.150 netmask 0xffffff00 broadcast 192.94.73.255=20 nd6 options=3D29 media: Ethernet manual status: active xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:00:00:30 xn0: backend features: xn0: link state changed to DOWN xn0: link state changed to UP Indeed this does fix the issue. I am now able to ssh into a FreeBSD 11 DOM= U running on a NetBSD DOM0. I've done some basic in/out transfers over sftp and rates look good, no err= ors. Thank you for putting in an effort to get this working. I hope that your d= iff will be incorporated quickly into=20 FreeBSD 11 and backported where that can be done. =20 From owner-freebsd-xen@freebsd.org Thu May 12 16:22:56 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5E92B379A8 for ; Thu, 12 May 2016 16:22:56 +0000 (UTC) (envelope-from prvs=93319c3d4=roger.pau@citrix.com) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EA0B17AD for ; Thu, 12 May 2016 16:22:55 +0000 (UTC) (envelope-from prvs=93319c3d4=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,610,1454976000"; d="scan'208";a="360287554" Date: Thu, 12 May 2016 18:22:47 +0200 From: 'Roger Pau =?iso-8859-1?B?TW9ubuknIChyb2dlci5wYXVAY2l0cml4LmNvbSk=?= To: Stephen Jones CC: "'freebsd-xen@freebsd.org'" , "Miguel C (miguelmclara@gmail.com)" , Wei Liu Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 FIXED! Message-ID: <20160512162247.64x5hyud5i2jfgqy@mac> References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 16:22:56 -0000 On Thu, May 12, 2016 at 02:13:03PM +0000, Stephen Jones wrote: > Roger writes: > > > I think I have found what's causing the issue, but I don't have a NetBSD > > Dom0 in order to test the fix, could some of you please test the following patch and report back: > > > > > > https://people.freebsd.org/~royger/0001-xen-netfront-fix-feature-detection.patch > > > > It should apply cleanly against FreeBSD HEAD. > > --- a/sys/dev/xen/netfront/netfront.c > +++ b/sys/dev/xen/netfront/netfront.c > @@ -2016,7 +2016,7 @@ xn_query_features(struct netfront_info *np) > device_printf(np->xbdev, "backend features:"); > > if (xs_scanf(XST_NIL, xenbus_get_otherend_path(np->xbdev), > - "feature-sg", NULL, "%d", &val) < 0) > + "feature-sg", NULL, "%d", &val) != 0) > val = 0; > > np->maxfrags = 1; > @@ -2026,7 +2026,7 @@ xn_query_features(struct netfront_info *np) > } > > if (xs_scanf(XST_NIL, xenbus_get_otherend_path(np->xbdev), > - "feature-gso-tcpv4", NULL, "%d", &val) < 0) > + "feature-gso-tcpv4", NULL, "%d", &val) != 0) > val = 0; > > np->xn_ifp->if_capabilities &= ~(IFCAP_TSO4|IFCAP_LRO); > > FreeBSD freebsd 11.0-CURRENT FreeBSD 11.0-CURRENT #1: Thu May 12 13:48:47 UTC 2016 root@freebsd:/usr/src/sys/amd64/compile/SDF amd64 > > xn0: flags=8843 metric 0 mtu 1500 > options=3 > ether 00:16:3e:00:00:30 > inet 192.94.73.150 netmask 0xffffff00 broadcast 192.94.73.255 > nd6 options=29 > media: Ethernet manual > status: active > > xn0: at device/vif/0 on xenbusb_front0 > xn0: Ethernet address: 00:16:3e:00:00:30 > xn0: backend features: > xn0: link state changed to DOWN > xn0: link state changed to UP > > Indeed this does fix the issue. I am now able to ssh into a FreeBSD 11 DOMU running on a NetBSD DOM0. > I've done some basic in/out transfers over sftp and rates look good, no errors. > > Thank you for putting in an effort to get this working. I hope that your diff will be incorporated quickly into > FreeBSD 11 and backported where that can be done. Done, it's committed to HEAD: https://svnweb.freebsd.org/base?view=revision&revision=299542 And I plan to backport it to stable/10 in 3 days. Thanks for testing it! Roger. From owner-freebsd-xen@freebsd.org Fri May 13 01:59:41 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA618B37BDC for ; Fri, 13 May 2016 01:59:41 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 186161EEC for ; Fri, 13 May 2016 01:59:41 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id u64so81383696lff.3 for ; Thu, 12 May 2016 18:59:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GOXkjdbD6dNzOjOpItsweH9xfrYNUo4tLNvtB/2WWD8=; b=E8zFpAjlHMxQIWDLy/mEIj/kQj7jfyYX+tmHV518IsiYAcbRpU/iU1CvNc3gnCaT7v K1WqsUzJouJvv+lBgU150QZKkUMHVIwCxDDcGxlvIJvmwVfNyjw+6FgmQC366Y3qpkDq YOLlVOnXXMp62gqWIwtH7we+0JO+dwxYEhcHnKhrtL3uaVfeh6kY4EODKco0G1nCqA1+ M0SmBSiQLfqj9FsaHq9zMKo6D7omDP1SN+QMmiKLbAx+otQYZn/qFDNnfCw8FVEYRKkS TuxeJVJVLrlP8ju5rnaDGCsXoIo2d/XEveh04ZsKfqxg7HpGDzIv2HGTVMiGdQXac1OF U0tA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GOXkjdbD6dNzOjOpItsweH9xfrYNUo4tLNvtB/2WWD8=; b=WPeuAlbyUwNeXTMpaIX0spt+AJOWAOn10kQYgoqM/BThgTHD/9IRguBZEf1EM8uhpA SDog9v7e61FZ6OrqoSaTtIH5YdphLCdBV9gmN8DcvO3gl8/hlymGzn4GqCGZOOPJvw/I dgblxCI2Di9WZcKJWrFI2bfDlV1wgd3MfY/mqk9yawdU+9SYo+IrYNij0R3fOlFcuMxj Lwjl6j1HJjbrnIeSXDZdagJKcDXdZc36PQZOliflKoO+Ser8HptPf0iQWLPl/gZUBR8u /a4bIIGbt+eZ5kAU0pFr+Rz/rVs/u+6P9c+iyVKQ94VP0Q0dbJmD9Uxq0uAqmrCC34BR 7hmw== X-Gm-Message-State: AOPr4FUQgpTxsDdWa02pkgPpgF2rno3+pQUtgSBzgvBDXT4//MNw4Plno58zKM875GUsJxGkqGK5TL6FFkD+kg== X-Received: by 10.25.83.10 with SMTP id h10mr4772757lfb.39.1463104778752; Thu, 12 May 2016 18:59:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.15.213 with HTTP; Thu, 12 May 2016 18:58:59 -0700 (PDT) In-Reply-To: <20160512162247.64x5hyud5i2jfgqy@mac> References: <20160512162247.64x5hyud5i2jfgqy@mac> From: Miguel C Date: Fri, 13 May 2016 02:58:59 +0100 Message-ID: Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 FIXED! To: =?UTF-8?B?J1JvZ2VyIFBhdSBNb25uw6knIChyb2dlci5wYXVAY2l0cml4LmNvbSk=?= Cc: Stephen Jones , "freebsd-xen@freebsd.org" , Wei Liu Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 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, 13 May 2016 01:59:41 -0000 On Thu, May 12, 2016 at 5:22 PM, 'Roger Pau Monn=C3=A9' (roger.pau@citrix.c= om) < roger.pau@citrix.com> wrote: > On Thu, May 12, 2016 at 02:13:03PM +0000, Stephen Jones wrote: > > Roger writes: > > > > > I think I have found what's causing the issue, but I don't have a > NetBSD > > > Dom0 in order to test the fix, could some of you please test the > following patch and report back: > > > > > > > > > > https://people.freebsd.org/~royger/0001-xen-netfront-fix-feature-detectio= n.patch > > > > > > It should apply cleanly against FreeBSD HEAD. > > > > --- a/sys/dev/xen/netfront/netfront.c > > +++ b/sys/dev/xen/netfront/netfront.c > > @@ -2016,7 +2016,7 @@ xn_query_features(struct netfront_info *np) > > device_printf(np->xbdev, "backend features:"); > > > > if (xs_scanf(XST_NIL, xenbus_get_otherend_path(np->xbdev), > > - "feature-sg", NULL, "%d", &val) < 0) > > + "feature-sg", NULL, "%d", &val) !=3D 0) > > val =3D 0; > > > > np->maxfrags =3D 1; > > @@ -2026,7 +2026,7 @@ xn_query_features(struct netfront_info *np) > > } > > > > if (xs_scanf(XST_NIL, xenbus_get_otherend_path(np->xbdev), > > - "feature-gso-tcpv4", NULL, "%d", &val) < 0) > > + "feature-gso-tcpv4", NULL, "%d", &val) !=3D 0) > > val =3D 0; > > > > np->xn_ifp->if_capabilities &=3D ~(IFCAP_TSO4|IFCAP_LRO); > > > > FreeBSD freebsd 11.0-CURRENT FreeBSD 11.0-CURRENT #1: Thu May 12 > 13:48:47 UTC 2016 root@freebsd:/usr/src/sys/amd64/compile/SDF amd64 > > > > xn0: flags=3D8843 metric 0 mtu = 1500 > > options=3D3 > > ether 00:16:3e:00:00:30 > > inet 192.94.73.150 netmask 0xffffff00 broadcast 192.94.73.255 > > nd6 options=3D29 > > media: Ethernet manual > > status: active > > > > xn0: at device/vif/0 on xenbusb_front0 > > xn0: Ethernet address: 00:16:3e:00:00:30 > > xn0: backend features: > > xn0: link state changed to DOWN > > xn0: link state changed to UP > > > > Indeed this does fix the issue. I am now able to ssh into a FreeBSD 11 > DOMU running on a NetBSD DOM0. > > I've done some basic in/out transfers over sftp and rates look good, no > errors. > > > > Thank you for putting in an effort to get this working. I hope that > your diff will be incorporated quickly into > > FreeBSD 11 and backported where that can be done. > > Done, it's committed to HEAD: > > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D299542 > > And I plan to backport it to stable/10 in 3 days. > > Thanks for testing it! > > FYI I patch local 10.3 system and works fine as expected, with better network performance then 9.3 At least according to iperf3 Connecting to host 10.x.x.x, port 5201 [ 4] local 10.x.x.67 port 54607 connected to 10.x.x.x port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 177 MBytes 1.48 Gbits/sec 0 94.0 MBytes [ 4] 1.00-2.00 sec 192 MBytes 1.61 Gbits/sec 0 138 MBytes [ 4] 2.00-3.00 sec 200 MBytes 1.68 Gbits/sec 0 186 MBytes [ 4] 3.00-4.00 sec 222 MBytes 1.86 Gbits/sec 0 230 MBytes [ 4] 4.00-5.00 sec 227 MBytes 1.91 Gbits/sec 0 274 MBytes [ 4] 5.00-6.00 sec 209 MBytes 1.75 Gbits/sec 0 318 MBytes [ 4] 6.00-7.00 sec 212 MBytes 1.78 Gbits/sec 0 366 MBytes [ 4] 7.00-8.00 sec 215 MBytes 1.81 Gbits/sec 0 389 MBytes [ 4] 8.00-9.00 sec 220 MBytes 1.85 Gbits/sec 0 452 MBytes [ 4] 9.00-10.00 sec 235 MBytes 1.97 Gbits/sec 0 489 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 2.06 GBytes 1.77 Gbits/sec 0 sende= r [ 4] 0.00-10.00 sec 2.06 GBytes 1.77 Gbits/sec receiver On 9 the max I could get was 700Mb/sec (host to guest) so this is pretty nice :) Many thanks for the fix Roger Roger. > From owner-freebsd-xen@freebsd.org Fri May 13 02:02:01 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7A07B37C2A for ; Fri, 13 May 2016 02:02:01 +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 mx1.freebsd.org (Postfix) with ESMTPS id B515110FC for ; Fri, 13 May 2016 02:02:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4D221Au065427 for ; Fri, 13 May 2016 02:02:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1) Date: Fri, 13 May 2016 02:02:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: miguelmclara@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_severity bug_status 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.22 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, 13 May 2016 02:02:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188369 miguelmclara@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Severity|Affects Only Me |Affects Many People Status|In Progress |Closed --- Comment #13 from miguelmclara@gmail.com --- Fixed by https://svnweb.freebsd.org/base?view=3Drevision&revision=3D299542 should be MFC to stable/10 soon so closing this :) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Sat May 14 19:33:25 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 582C7B3B2B9 for ; Sat, 14 May 2016 19:33:25 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D30461845 for ; Sat, 14 May 2016 19:33:24 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: by mail-lf0-x232.google.com with SMTP id m64so102199230lfd.1 for ; Sat, 14 May 2016 12:33:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TP/PIIqig/yGNxoPk7MODwMXXCu5uXWGynhz+Z35tSg=; b=dZXQs5+FEtuzyfgBqydbKlEvCN+Ls28ieLsDYn4rCUrEquAIvtdH0ohq4YzsTLTlMN QvDpN4QkoGG7oGtjzjo88PwBszLkMurmW3PELq+76oxa4YYr2WPOoTUssPDfPD1+9hq/ qeWGu6EE6KWJ4kKTTO0sUiHyHjoH8WWLt+bKQt5sEKvRvn9W4opqX2TzHRs/hFKiZQE/ 4Foj0si8wpIUAZzFdHG54GDna7esEbndZS/73WooDKsfd41MFAQ++xY2mrrvgOimKDX0 2CduG0NHeehLxIFNr//UDS4mSx5FgYjLahW2WR1RwJA1K9wjCT+ngqH20j56i7zhVz3R 8Cgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TP/PIIqig/yGNxoPk7MODwMXXCu5uXWGynhz+Z35tSg=; b=MaQrem9dhqXUKBLbaLH4GnBFrnj+V/124NKMhEtbBarWDyJdc0gbu5REKU/RmzVSk8 PlHPXEqGs4zoKA2u3eBWT4zje/hHhuBhNIQ7LfHPfVQIcnV9zd+lfoUFN5oV+okbVWL9 MmRZ7ewY/DLdhKhPAa5Hp/OTAwLXQ3gpT7cTzcF/lplpXtB1qvCaTBNvDRcE4xNZVsUy 50xXd5H0qU8BWDM798zNSHzuxJXxyD5e37lbgi4BXC9I837bnaBeW1+l5Un/lvLgqGIR ABVEb/RJAhPF2ecLTMTCrCU7v2iZKcja44i2XqYRDDpimGqNo4nTs/PFtvMOsYoPkYaY dTJQ== X-Gm-Message-State: AOPr4FUhCsZU4VVvPphYCip8fmqg9Iiu1NT/Mlp+Q3wzwwYQO8Q8uIIFHJWrFHlnnUj/ExZOmOCP3C7cVIGU5A== X-Received: by 10.25.207.131 with SMTP id f125mr9486356lfg.62.1463254402952; Sat, 14 May 2016 12:33:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.15.213 with HTTP; Sat, 14 May 2016 12:32:43 -0700 (PDT) In-Reply-To: References: <20160512162247.64x5hyud5i2jfgqy@mac> From: Miguel C Date: Sat, 14 May 2016 20:32:43 +0100 Message-ID: Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 FIXED! To: =?UTF-8?B?J1JvZ2VyIFBhdSBNb25uw6knIChyb2dlci5wYXVAY2l0cml4LmNvbSk=?= Cc: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 May 2016 19:33:25 -0000 Somewhat related to this is the fact that at some point "xenhvm" as not longer available as a module, this means if I want to upgrade 9.3 machine to 10.3 with freebsd-update I get stuck with the bug, but before this change I could just patch the xenhvm module and rebuild the single module... Now I guess I need to rebuild the full kernel to do it? Or is there a way around that?