From owner-freebsd-xen@freebsd.org Sun Jul 19 15:58:33 2015 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 335069A5CFB for ; Sun, 19 Jul 2015 15:58:33 +0000 (UTC) (envelope-from gnn@freebsd.org) Received: from smtp.hungerhost.com (smtp.hungerhost.com [216.38.53.177]) (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 58B391255; Sun, 19 Jul 2015 15:58:32 +0000 (UTC) (envelope-from gnn@freebsd.org) Received: from cpe-74-73-224-71.nyc.res.rr.com ([74.73.224.71]:52233 helo=[192.168.0.8]) by vps.hungerhost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from ) id 1ZGqz1-0006q5-Ey; Sun, 19 Jul 2015 11:58:31 -0400 From: "George Neville-Neil" To: "Colin Percival" Cc: "Kristof Provost" , "Mark Felder" , freebsd-xen@freebsd.org Subject: Re: Networking under Xen Date: Sun, 19 Jul 2015 11:58:20 -0400 Message-ID: <55D3D012-140C-4230-8F23-5975D1A5CACD@freebsd.org> In-Reply-To: <55A611B1.6000000@freebsd.org> References: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com> <1436890526.3162974.323521249.6B73E6E2@webmail.messagingengine.com> <55A55AE8.4090101@freebsd.org> <1436901780.3211878.323698017.360F8D73@webmail.messagingengine.com> <20F2398D-ECDF-4CF4-966D-18C894779C4C@FreeBSD.org> <55A611B1.6000000@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailer: MailMate (1.9.2r5107) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - freebsd.org X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 19 Jul 2015 15:58:33 -0000 On 15 Jul 2015, at 3:54, Colin Percival wrote: > On 07/15/15 00:44, Kristof Provost wrote: >>> On 14 Jul 2015, at 21:23, Mark Felder wrote: >>> On Tue, Jul 14, 2015, at 13:54, Colin Percival wrote: >>>> More precisely *pf* is a known issue. It's inserting TCP checksums >>>> into TSO packets. I reported this a long time ago and I don't know >>>> why pf still hasn't been fixed. >>> >>> I think Kristof may have solved this in HEAD with all of the care >>> and >>> feeding he has been doing to pf, but I haven't verified. >> >> I wouldn’t expect so. As far as I know I’ve not fixed anything >> TSO or >> checksum related. > > In my tests, deleting these lines from pf_ioctl.c > > 3570 /* We need a proper CSUM befor we start (s. OpenBSD ip_output) */ > 3571 if ((*m)->m_pkthdr.csum_flags & CSUM_DELAY_DATA) { > 3572 in_delayed_cksum(*m); > 3573 (*m)->m_pkthdr.csum_flags &= ~CSUM_DELAY_DATA; > 3574 } > > unbreaks pf+TSO on EC2 instances. I'm not entirely sure why these > lines > are there in the first place, which is why I didn't want to simply go > in > and remove them -- but it may be that wrapping those lines in > something > like "if ((csum_flags & CSUM_TSO) == 0)" would solve the problem > without > breaking anything else. > Since Kristof is already working on this, I'll let him address it. If necessary open a PR on this specifically please. Best, George From owner-freebsd-xen@freebsd.org Sun Jul 19 16:14:18 2015 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 1AC3A9A5088 for ; Sun, 19 Jul 2015 16:14:18 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F0E01F7A; Sun, 19 Jul 2015 16:14:17 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from [IPv6:2a02:1811:2419:4e02:bd50:12cb:817:8fd5] (unknown [IPv6:2a02:1811:2419:4e02:bd50:12cb:817:8fd5]) by venus.codepro.be (Postfix) with ESMTPSA id 4402211E1F; Sun, 19 Jul 2015 18:14:13 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3067\)) Subject: Re: Networking under Xen From: Kristof Provost In-Reply-To: <55D3D012-140C-4230-8F23-5975D1A5CACD@freebsd.org> Date: Sun, 19 Jul 2015 18:14:12 +0200 Cc: Colin Percival , Mark Felder , freebsd-xen@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <609839ED-847B-4D24-B234-F7B401DE5C8C@FreeBSD.org> References: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com> <1436890526.3162974.323521249.6B73E6E2@webmail.messagingengine.com> <55A55AE8.4090101@freebsd.org> <1436901780.3211878.323698017.360F8D73@webmail.messagingengine.com> <20F2398D-ECDF-4CF4-966D-18C894779C4C@FreeBSD.org> <55A611B1.6000000@freebsd.org> <55D3D012-140C-4230-8F23-5975D1A5CACD@freebsd.org> To: George Neville-Neil X-Mailer: Apple Mail (2.3067) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 19 Jul 2015 16:14:18 -0000 > On 19 Jul 2015, at 17:58, George Neville-Neil wrote: > Since Kristof is already working on this, I'll let him address it. If = necessary > open a PR on this specifically please. It=E2=80=99s on my todo list, but I=E2=80=99d like to take another run = at PR 172648 first. Regards, Kristof From owner-freebsd-xen@freebsd.org Sun Jul 19 16:16:28 2015 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 50BB99A5104 for ; Sun, 19 Jul 2015 16:16:28 +0000 (UTC) (envelope-from gnn@freebsd.org) Received: from smtp.hungerhost.com (smtp.hungerhost.com [216.38.53.177]) (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 2068110C3; Sun, 19 Jul 2015 16:16:27 +0000 (UTC) (envelope-from gnn@freebsd.org) Received: from cpe-74-73-224-71.nyc.res.rr.com ([74.73.224.71]:52351 helo=[192.168.0.8]) by vps.hungerhost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from ) id 1ZGrGM-0002Ek-ED; Sun, 19 Jul 2015 12:16:26 -0400 From: "George Neville-Neil" To: "Kristof Provost" Cc: "Colin Percival" , "Mark Felder" , freebsd-xen@freebsd.org Subject: Re: Networking under Xen Date: Sun, 19 Jul 2015 12:16:15 -0400 Message-ID: In-Reply-To: <609839ED-847B-4D24-B234-F7B401DE5C8C@FreeBSD.org> References: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com> <1436890526.3162974.323521249.6B73E6E2@webmail.messagingengine.com> <55A55AE8.4090101@freebsd.org> <1436901780.3211878.323698017.360F8D73@webmail.messagingengine.com> <20F2398D-ECDF-4CF4-966D-18C894779C4C@FreeBSD.org> <55A611B1.6000000@freebsd.org> <55D3D012-140C-4230-8F23-5975D1A5CACD@freebsd.org> <609839ED-847B-4D24-B234-F7B401DE5C8C@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailer: MailMate (1.9.2r5107) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - freebsd.org X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 19 Jul 2015 16:16:28 -0000 On 19 Jul 2015, at 12:14, Kristof Provost wrote: >> On 19 Jul 2015, at 17:58, George Neville-Neil >> wrote: >> Since Kristof is already working on this, I'll let him address it. >> If necessary >> open a PR on this specifically please. > > It’s on my todo list, but I’d like to take another run at PR > 172648 first. > Works for me. Thanks, George From owner-freebsd-xen@freebsd.org Sun Jul 19 19:22:27 2015 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 D042E9A63F6 for ; Sun, 19 Jul 2015 19:22:27 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (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 648F3196C for ; Sun, 19 Jul 2015 19:22:27 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: by wicmv11 with SMTP id mv11so585865wic.0 for ; Sun, 19 Jul 2015 12:22:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=WI0UrvYQT1A+Bfmy/pL4YfRab8fUnsu848AduIDNeOU=; b=yBIpVpkeHblZNdecZADn4tqZFKhWShs5lX09wssO4xjtwIx5yBZ/KAfz7ZGAAn80YP nu7+ANRfBYcUF+zShsROxwmgMRaLe+OVanyUIMRSU9A+Y9o7fwFMUZf+L3RuRgPKvFFe dQBmFVmBO9hzDdpBwreSQjw9PTAnG7DesY1fro76bxhbfxw3qisOmTVJvX/5bQT3NZl5 dxfwEeZItIq/+WXvndSiJtqLAJXed5sz59V63XGZNEpASxnlM1kUz2kCONawSFwV0ieh 47yNpwz1o6CkWHOdcFGMe8iIo02yj6ctbZQTdE8la3SS9k5JE+ysSt72EHt2Rm/tq4/3 0dfQ== X-Received: by 10.180.91.196 with SMTP id cg4mr1028366wib.16.1437333745715; Sun, 19 Jul 2015 12:22:25 -0700 (PDT) Received: from [10.0.30.93] (131.69-67-87.adsl-dyn.isp.belgacom.be. [87.67.69.131]) by smtp.gmail.com with ESMTPSA id lg6sm3911380wjb.10.2015.07.19.12.22.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 Jul 2015 12:22:24 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3067\)) Subject: Re: Networking under Xen From: Sydney Meyer In-Reply-To: <4B6D4AEF-6107-4F95-9F5A-F0EA137809AC@gmail.com> Date: Sun, 19 Jul 2015 21:22:24 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <41967713-C2DE-4657-96ED-F8BE3491D4EA@gmail.com> References: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com> <1436890526.3162974.323521249.6B73E6E2@webmail.messagingengine.com> <4B6D4AEF-6107-4F95-9F5A-F0EA137809AC@gmail.com> To: freebsd-xen@freebsd.org X-Mailer: Apple Mail (2.3067) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 19 Jul 2015 19:22:28 -0000 Also i have noticed, when TSO is disabled IPv4 TCP Performance also = drops from ~10 Gb/s to ~3 Gb/s, the same as with IPv6. I have read = threads from around 2010 about the networking stack not having support = for TSO on IPv6 Packets. May this be the problem in this case? > On 14 Jul 2015, at 23:44, Sydney Meyer wrote: >=20 >=20 >> On 14 Jul 2015, at 18:15, Mark Felder wrote: >>=20 >>=20 >>=20 >> On Tue, Jul 14, 2015, at 07:36, Sydney Meyer wrote: >>> Hello everybody, >>>=20 >>> i have noticed some odd behaviour with networking under Xen with = FreeBSD >>> 10 as a DomU. >>>=20 >>> - IPv6 (TCP) bandwith drops from ~10 Gbit/s IPv4 to around 3 Gbit/s = IPv6. >>> (measured with iperf) >>>=20 >>=20 >> What is the "before" and "after" here? When is FreeBSD successfully >> doing 10Gbit/s and when isn't it? Is pf enabled? Are you scrubbing? >=20 > With two clean 10.1 AMD64 DomU installations both with a single, = pinned cpu, without pf enabled the TCP performance between the two = hosts, measured with iperf, differs between ~10 Gb/s on IPv4 and ~3 Gb/s = on IPv6. With pf enabled and "scrub in all" the difference is almost the = same. >>=20 >>> - Dropped/Stalled Connections with TCP Segmentation Offload and pf >>> enabled. >>>=20 >>=20 >> TSO is a known issue. I've been turning it off for years to get = FreeBSD >> to play nice on Xen. >=20 > This one i am still investigating, because it happens only in = "certain" situations (which are not clear to me, atm), but the host = seems to drop ACK Packets in some situations like when connected to via = IPSEC or via double NAT. This happens only when pf it actually enabled. = Disabling TSO on the xn-interface seems to help. >>=20 >>> - IPSEC-enabled Kernel TCP Performance drops from ~10 Gbit/s to ~200 >>> Mbit/s (iperf). >>>=20 >>=20 >> Are you saying FreeBSD non-IPSEC kernel can do 10Gbit/s TCP = performance, >> but IPSEC kernel immediately drops it to 200Mbit/s? >=20 > As for the apparent performance drop with IPSEC enabled Kernels = without security associations installed, i am unable to reproduce this = now, not on 10.0 or 10.1 nor 10 STABLE. Only when actually _using_ IPSec = the performance drops from ~10Gb/s to around ~200Mb/s whether actually = encrypting esp traffic or not. > This clearly must have been a mistake on my side, although i could = have sworn that i checked this two times before asking on the forums and = the -net mailing list a few weeks ago. Well then, i am sincerely sorry = about this one. >> _______________________________________________ >> 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" >=20 From owner-freebsd-xen@freebsd.org Mon Jul 20 16:04:40 2015 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 B931F9A626D for ; Mon, 20 Jul 2015 16:04:40 +0000 (UTC) (envelope-from prvs=636686ac5=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 725941C29 for ; Mon, 20 Jul 2015 16:04:39 +0000 (UTC) (envelope-from prvs=636686ac5=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.15,508,1432598400"; d="scan'208";a="282606024" Message-ID: <55AD1C09.7040500@citrix.com> Date: Mon, 20 Jul 2015 18:04:25 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Jeroen van der Ham , Subject: Re: Xen console on 10.1 DomU References: <4C92646F-4307-4A45-B35E-DFBD09A71313@dckd.nl> In-Reply-To: <4C92646F-4307-4A45-B35E-DFBD09A71313@dckd.nl> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 20 Jul 2015 16:04:40 -0000 El 17/07/15 a les 21.02, Jeroen van der Ham ha escrit: > Hi, > > What is the current way of getting a xen console on a FreeBSD 10.1 DomU? > > I’ve been searching on: > * https://wiki.freebsd.org/FreeBSD/Xen (reasonably up to date, but has no info on console) > * http://wiki.xen.org (completely outdated, “official” documentation points to installation of FreeBSD 7.2(!)) > > I found instructions to add a line to /boot/loader.conf (console="comconsole”) > or a line to /etc/ttys (xc0 "/usr/libexec/getty Pc" vt100 on secure) You shouldn't need to modify /etc/ttys at all unless you are using a FreeBSD PVH guest or Dom0. > But in either case I am getting an error on the Linux Dom0: > xenconsole: Could not read tty from store: No such file or directory > > Is it still possible to get a console from a Linux Dom0? How? > What would be the best place to publish instructions for that? Which kind of guest are you trying to get the console from? If it's a HVM guest (I'm only guessing here), you need to add serial='pty' to your xl configuration file and then follow https://www.freebsd.org/doc/handbook/serialconsole-setup.html. Roger. From owner-freebsd-xen@freebsd.org Mon Jul 20 16:11:40 2015 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 554A49A64CE for ; Mon, 20 Jul 2015 16:11:40 +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 424B11262 for ; Mon, 20 Jul 2015 16:11:40 +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 t6KGBepe092596 for ; Mon, 20 Jul 2015 16:11:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 195978] Add vlan support to xen netfront Date: Mon, 20 Jul 2015 16:11:37 +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-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- 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.20 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, 20 Jul 2015 16:11:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195978 --- Comment #6 from Roger Pau Monn=C3=83=C2=A9 --- I'm quite lost on this one because I have 0 experience with vlans. Marcelo seems to have vlans working with netfront, but I guess there's something I'm missing. Can someone please clarify what's missing? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon Jul 20 19:02:45 2015 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 B93F79A68F2 for ; Mon, 20 Jul 2015 19:02:45 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from positron.dckd.nl (positron.dckd.nl [IPv6:2a02:898:62:f6::63]) (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 7F6EA1DEE for ; Mon, 20 Jul 2015 19:02:45 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from [192.168.178.228] (5ED24C08.cm-7-3b.dynamic.ziggo.nl [94.210.76.8]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by positron.dckd.nl (Postfix) with ESMTPSA id 21962260AD; Mon, 20 Jul 2015 19:02:40 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Xen console on 10.1 DomU From: Jeroen van der Ham In-Reply-To: <55AD1C09.7040500@citrix.com> Date: Mon, 20 Jul 2015 21:02:17 +0200 Cc: freebsd-xen@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <59CA2328-4AC7-4098-8BCA-6A5A5E9A5929@dckd.nl> References: <4C92646F-4307-4A45-B35E-DFBD09A71313@dckd.nl> <55AD1C09.7040500@citrix.com> To: =?utf-8?Q?Roger_Pau_Monn=C3=A9?= X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 20 Jul 2015 19:02:45 -0000 Hi, > On 20 Jul 2015, at 18:04, Roger Pau Monn=C3=A9 = wrote: >=20 > El 17/07/15 a les 21.02, Jeroen van der Ham ha escrit: >> Hi, >>=20 >> What is the current way of getting a xen console on a FreeBSD 10.1 = DomU? >>=20 >> I=E2=80=99ve been searching on: >> * https://wiki.freebsd.org/FreeBSD/Xen (reasonably up to date, but = has no info on console) >> * http://wiki.xen.org (completely outdated, =E2=80=9Cofficial=E2=80=9D = documentation points to installation of FreeBSD 7.2(!)) >>=20 >> I found instructions to add a line to /boot/loader.conf = (console=3D"comconsole=E2=80=9D) >> or a line to /etc/ttys (xc0 "/usr/libexec/getty Pc" vt100 = on secure) >=20 > You shouldn't need to modify /etc/ttys at all unless you are using a > FreeBSD PVH guest or Dom0. >=20 >> But in either case I am getting an error on the Linux Dom0: >> xenconsole: Could not read tty from store: No such file or directory >>=20 >> Is it still possible to get a console from a Linux Dom0? How? >> What would be the best place to publish instructions for that? >=20 > Which kind of guest are you trying to get the console from? >=20 > If it's a HVM guest (I'm only guessing here), you need to add > serial=3D'pty' to your xl configuration file and then follow > https://www.freebsd.org/doc/handbook/serialconsole-setup.html. Thanks, that did the trick. Now the question remains where to document this properly so that others = will not be mislead by all the other advice out there? Jeroen. From owner-freebsd-xen@freebsd.org Mon Jul 20 19:40:34 2015 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 766839A403F for ; Mon, 20 Jul 2015 19:40:34 +0000 (UTC) (envelope-from prvs=164384a8b9=jwest@ezwind.net) Received: from ezwind.net (booby.ezwind.net [199.188.211.150]) by mx1.freebsd.org (Postfix) with ESMTP id 4E39B119F for ; Mon, 20 Jul 2015 19:40:33 +0000 (UTC) (envelope-from prvs=164384a8b9=jwest@ezwind.net) X-MDAV-Result: clean X-MDAV-Processed: ezwind.net, Mon, 20 Jul 2015 14:40:04 -0500 X-Spam-Processed: ezwind.net, Mon, 20 Jul 2015 14:40:04 -0500 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on Booby X-Spam-Level: X-Spam-Status: No, score=-4.7 required=6.0 tests=BAYES_00,NO_RELAYS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from jayPC by ezwind.net (MDaemon PRO v15.0.3) with ESMTPA id 28-md50000002595.msg for ; Mon, 20 Jul 2015 14:40:03 -0500 X-MDRemoteIP: 97.91.122.42 X-MDHelo: jayPC X-MDArrival-Date: Mon, 20 Jul 2015 14:40:03 -0500 X-Authenticated-Sender: jwest@ezwind.net X-Return-Path: prvs=164384a8b9=jwest@ezwind.net X-Envelope-From: jwest@ezwind.net X-MDaemon-Deliver-To: freebsd-xen@freebsd.org From: "Jay West" To: Subject: multipath status changed, freebsd fails Date: Mon, 20 Jul 2015 14:40:03 -0500 Message-ID: <007601d0c323$e0299e80$a07cdb80$@ezwind.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdDDItzkBfQOwTFlTLaDgCTbRtZxJA== Content-Language: en-us X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 20 Jul 2015 19:40:34 -0000 I realize that this may not be a freebsd-xen issue, but not sure where = to turn so thought I'd check here first. We have a pool of about 10 xenservers (v6.5). All the servers are using = multipath to connect to multiple nas, and each has multiple paths on = different subnets. All seems to work ok, but.... About every 3 or 4 weeks, xencenter will throw an alert... "Multipath = status has changed". Further looking in xencenter shows multipath status = is AOK. However, a few VM's are down. Recovery is just restarting those = VM's. What is odd - is that every time this occurs, the VM's that failed are = always FreeBSD (10.0-Release, most are P9) VM's, none of the windows VMs = fail. Are there any known issues with FreeBSD where a blip in multipath = status causes the VM to shutdown? I'd think this is a xenserver thing = and not a freebsd thing... but thought I'd check. Any advice = appreciated! J From owner-freebsd-xen@freebsd.org Tue Jul 21 01:22:24 2015 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 EAEE39A6F86 for ; Tue, 21 Jul 2015 01:22: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 D15D11F11 for ; Tue, 21 Jul 2015 01:22: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 t6L1MOV4071170 for ; Tue, 21 Jul 2015 01:22:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 195978] Add vlan support to xen netfront Date: Tue, 21 Jul 2015 01:22:25 +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-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bugs.freebsd.org@zengel.info X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 21 Jul 2015 01:22:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195978 --- Comment #7 from Grischa Zengel --- 1. You have to look if netback can have frames with >= 1522 Bytes. See 802.1q at http://www.firewall.cx/networking-topics/vlan-networks/219-vlan-tagging.html Here is some code from Linux: netfront (DomU): http://lxr.free-electrons.com/source/drivers/net/xen-netfront.c netback (Dom0): http://lxr.free-electrons.com/source/drivers/net/xen-netback/xenbus.c 2a. https://www.freebsd.org/cgi/man.cgi?query=altq&sektion=4 2b. https://www.freebsd.org/cgi/man.cgi?query=altq&sektion=9&apropos=0&manpath=FreeBSD+10.1-RELEASE#HOW_TO_CONVERT_THE_EXISTING_DRIVERS I can't help much more. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@freebsd.org Tue Jul 21 01:29:44 2015 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 8417D9A7084 for ; Tue, 21 Jul 2015 01:29:44 +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 70D53AE for ; Tue, 21 Jul 2015 01:29:44 +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 t6L1Ti83073424 for ; Tue, 21 Jul 2015 01:29:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 195978] Add vlan support to xen netfront Date: Tue, 21 Jul 2015 01:29:44 +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-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bugs.freebsd.org@zengel.info X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- 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.20 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, 21 Jul 2015 01:29:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195978 --- Comment #8 from Grischa Zengel --- (In reply to Roger Pau Monn=C3=83=C2=A9 from comment #6) Really missing is ALTQ to have throttling and VLAN tagging with MTU 1504 (called Baby Jumbo Frames). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Tue Jul 21 07:35:12 2015 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 28C279A6C39 for ; Tue, 21 Jul 2015 07:35:12 +0000 (UTC) (envelope-from prvs=637e9ed86=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 D5E2F10BC for ; Tue, 21 Jul 2015 07:35:11 +0000 (UTC) (envelope-from prvs=637e9ed86=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.15,514,1432598400"; d="scan'208";a="282818759" Message-ID: <55ADF616.4090200@citrix.com> Date: Tue, 21 Jul 2015 09:34:46 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Jay West , Subject: Re: multipath status changed, freebsd fails References: <007601d0c323$e0299e80$a07cdb80$@ezwind.net> In-Reply-To: <007601d0c323$e0299e80$a07cdb80$@ezwind.net> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 21 Jul 2015 07:35:12 -0000 Hello, El 20/07/15 a les 21.40, Jay West ha escrit: > I realize that this may not be a freebsd-xen issue, but not sure where to turn so thought I'd check here first. > > We have a pool of about 10 xenservers (v6.5). All the servers are using multipath to connect to multiple nas, and each has multiple paths on different subnets. All seems to work ok, but.... > > About every 3 or 4 weeks, xencenter will throw an alert... "Multipath status has changed". Further looking in xencenter shows multipath status is AOK. However, a few VM's are down. Recovery is just restarting those VM's. > > What is odd - is that every time this occurs, the VM's that failed are always FreeBSD (10.0-Release, most are P9) VM's, none of the windows VMs fail. Are there any known issues with FreeBSD where a blip in multipath status causes the VM to shutdown? I'd think this is a xenserver thing and not a freebsd thing... but thought I'd check. Any advice appreciated! >From a FreeBSD (or guest in general) point of view, there's no notion of multipath or the backing storage details in general, so I very much doubt it has anything to do with FreeBSD. Are you only running Windows and FreeBSD guests? Do you have the PV drivers installed on Windows guests? Can you get the output of the VMs that automatically restart? Do they crash and reboot or are they rebooted by xencenter? It might be possible that XenServer does an unexpected virtual hard drive state change when the multipath status changes and that this makes FreeBSD crash, but without a ddb trace it's impossible to know. Roger. From owner-freebsd-xen@freebsd.org Tue Jul 21 07:40:51 2015 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 6E2259A6CAF for ; Tue, 21 Jul 2015 07:40:51 +0000 (UTC) (envelope-from prvs=637e9ed86=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 25C6F12A5 for ; Tue, 21 Jul 2015 07:40:50 +0000 (UTC) (envelope-from prvs=637e9ed86=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.15,514,1432598400"; d="scan'208";a="285975991" Message-ID: <55ADF77E.1000909@citrix.com> Date: Tue, 21 Jul 2015 09:40:46 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Jeroen van der Ham CC: Subject: Re: Xen console on 10.1 DomU References: <4C92646F-4307-4A45-B35E-DFBD09A71313@dckd.nl> <55AD1C09.7040500@citrix.com> <59CA2328-4AC7-4098-8BCA-6A5A5E9A5929@dckd.nl> In-Reply-To: <59CA2328-4AC7-4098-8BCA-6A5A5E9A5929@dckd.nl> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 21 Jul 2015 07:40:51 -0000 Hello, El 20/07/15 a les 21.02, Jeroen van der Ham ha escrit: >> On 20 Jul 2015, at 18:04, Roger Pau Monné wrote: >> If it's a HVM guest (I'm only guessing here), you need to add >> serial='pty' to your xl configuration file and then follow >> https://www.freebsd.org/doc/handbook/serialconsole-setup.html. > > Thanks, that did the trick. > Now the question remains where to document this properly so that others will not be mislead by all the other advice out there? I guess https://wiki.freebsd.org/Xen is the most appropriate place, although a mention somewhere in the handbook would also be nice. Roger. From owner-freebsd-xen@freebsd.org Thu Jul 23 02:14:41 2015 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 B4A649A8472 for ; Thu, 23 Jul 2015 02:14:41 +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 A11821471 for ; Thu, 23 Jul 2015 02:14:41 +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 t6N2Efcf081787 for ; Thu, 23 Jul 2015 02:14:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 195978] Add vlan support to xen netfront Date: Thu, 23 Jul 2015 02:14:41 +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-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: matt.thyer@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 23 Jul 2015 02:14:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195978 matt.thyer@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matt.thyer@gmail.com --- Comment #9 from matt.thyer@gmail.com --- (In reply to Grischa Zengel from comment #8) Really missing is Jumbo Frame support with VLANs. After all, we want FreeBSD DomU to be able to saturate 10 gigE don't we? -- You are receiving this mail because: You are the assignee for the bug.