From owner-freebsd-virtualization@freebsd.org Mon Aug 19 09:06:42 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0DF02AE783 for ; Mon, 19 Aug 2019 09:06:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46Bp2T6hjyz4WG7 for ; Mon, 19 Aug 2019 09:06:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id E5CCAAE782; Mon, 19 Aug 2019 09:06:41 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E5985AE781 for ; Mon, 19 Aug 2019 09:06:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Bp2T5nF5z4WG5 for ; Mon, 19 Aug 2019 09:06:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A88E01844F for ; Mon, 19 Aug 2019 09:06:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7J96fNQ086357 for ; Mon, 19 Aug 2019 09:06:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7J96fkG086347 for virtualization@FreeBSD.org; Mon, 19 Aug 2019 09:06:41 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through Date: Mon, 19 Aug 2019 09:06:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: weh@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@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-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2019 09:06:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222996 --- Comment #25 from Wei Hu --- (In reply to Michael from comment #23) Can you share the 'pciconf -lvb' outputs when the passthrough NIC working a= nd not working? Also share /boot/loader.conf file. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Aug 20 01:57:40 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 68AC8C0480 for ; Tue, 20 Aug 2019 01:57:40 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46CDSy2rBPz3FG6 for ; Tue, 20 Aug 2019 01:57:37 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from disco.vangyzen.net (unknown [70.97.188.230]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 959FE5649D for ; Mon, 19 Aug 2019 20:48:32 -0500 (CDT) To: freebsd-virtualization@freebsd.org From: Eric van Gyzen Subject: Inter-VM networking with FreeBSD under bhyve Message-ID: <5e50ec97-4a68-b6a5-b8f7-7e9b21028e14@vangyzen.net> Date: Mon, 19 Aug 2019 20:48:28 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46CDSy2rBPz3FG6 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of eric@vangyzen.net designates 2607:fc50:1000:7400:216:3eff:fe72:314f as permitted sender) smtp.mailfrom=eric@vangyzen.net X-Spamd-Result: default: False [-6.20 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DMARC_NA(0.00)[vangyzen.net]; NEURAL_HAM_SHORT(-0.98)[-0.985,0]; IP_SCORE(-2.92)[ip: (-6.93), ipnet: 2607:fc50:1000::/36(-3.73), asn: 36236(-3.87), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:2607:fc50:1000::/36, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 01:57:40 -0000 freebsd-virtualization: What is my best option for inter-VM networking with FreeBSD guests under bhyve? I'm only concerned with networking between VMs, not with the host or physical network. I imagine some form of netmap is my best bet, but what exactly? Thanks in advance, Eric From owner-freebsd-virtualization@freebsd.org Tue Aug 20 02:23:51 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B1FB2C129B for ; Tue, 20 Aug 2019 02:23:51 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from mx1.shrew.net (mx1.shrew.net [38.97.5.131]) (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 46CF3B5yPVz3GpT for ; Tue, 20 Aug 2019 02:23:50 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from mail.shrew.net (mail.shrew.prv [10.24.10.20]) by mx1.shrew.net (8.15.2/8.15.2) with ESMTP id x7K2NnUo050673; Mon, 19 Aug 2019 21:23:49 -0500 (CDT) (envelope-from mgrooms@shrew.net) Received: from [10.1.9.187] (unknown [136.49.22.229]) by mail.shrew.net (Postfix) with ESMTPSA id 0A615195F3C; Mon, 19 Aug 2019 21:23:44 -0500 (CDT) Date: Mon, 19 Aug 2019 21:23:42 -0500 Subject: Re: Inter-VM networking with FreeBSD under bhyve Message-ID: X-Android-Message-ID: In-Reply-To: <5e50ec97-4a68-b6a5-b8f7-7e9b21028e14@vangyzen.net> From: Matthew Grooms To: Eric van Gyzen Cc: freebsd-virtualization@freebsd.org Importance: Normal X-Priority: 3 X-MSMail-Priority: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx1.shrew.net [10.24.10.10]); Mon, 19 Aug 2019 21:23:49 -0500 (CDT) X-Rspamd-Queue-Id: 46CF3B5yPVz3GpT X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mgrooms@shrew.net designates 38.97.5.131 as permitted sender) smtp.mailfrom=mgrooms@shrew.net X-Spamd-Result: default: False [-1.79 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[shrew.net]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.95)[-0.951,0]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[131.5.97.38.list.dnswl.org : 127.0.10.0]; HAS_X_PRIO_THREE(0.00)[3]; MIME_HTML_ONLY(0.20)[]; IP_SCORE(-0.94)[ip: (-9.20), ipnet: 38.0.0.0/8(2.81), asn: 174(1.76), country: US(-0.05)]; MIME_BASE64_TEXT(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MISSING_MIMEOLE(2.00)[]; ASN(0.00)[asn:174, ipnet:38.0.0.0/8, country:US]; MIME_TRACE(0.00)[0:~] MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 02:23:51 -0000 From owner-freebsd-virtualization@freebsd.org Tue Aug 20 03:11:46 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 01510C26B0 for ; Tue, 20 Aug 2019 03:11:46 +0000 (UTC) (envelope-from andy@fud.org.nz) Received: from mail-io1-f45.google.com (mail-io1-f45.google.com [209.85.166.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46CG6T0FTvz3JwJ for ; Tue, 20 Aug 2019 03:11:43 +0000 (UTC) (envelope-from andy@fud.org.nz) Received: by mail-io1-f45.google.com with SMTP id 18so9032409ioe.10 for ; Mon, 19 Aug 2019 20:11:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pI/j2OvE2yn3c+jG3mcgKeZAu3wOSXrhMr6YxEE7bbE=; b=IIgiOquRwZCYOaDpwilDU1KbOs3Ck8ETkHLHVzLRVjBnI8Ip+kaQWWumEpbjxzoQzz kD+ZNEdfOuzGB5Uz8rHIscvJSkTamKTqQv3VETRw+7ilxvO0cNwAZhkeWVpY0lRboh26 qf2l0U+6UExTMZztOxiH6Dk3tfjhs68rS3ATykraDrYII2WeWMkLHpEtWnzd6NpXS7Fk vkPunMKCy1437ZuIkD6EdEW8GzC38wRyPWCnx6X+OdmBruH6LjdV712bagNp2aa7RWhm al+0It2t/R8RJI2GPjvf191rHUAakYdVGefOih4sD+/Kss0eMrsGveEViZIyDbK2Z1dM gGZQ== X-Gm-Message-State: APjAAAW5OpFk1wLZp16DR5l8CVhP2HRDzYv8l6czpJcg2P88zOVlGdUc lFZ7rgTZetAkDBUmzBnD9NbTOejGIi4+pn9cBRnesQ== X-Google-Smtp-Source: APXvYqyGIMgq1xwM4ZCdYb0J7gaL2yJgszzIsBtUAd9Ib4lweUnA+WT6G5Lkw9qCNitn9oRJMtCSaZcVSpavviCLXVQ= X-Received: by 2002:a02:4881:: with SMTP id p123mr1282378jaa.69.1566270702059; Mon, 19 Aug 2019 20:11:42 -0700 (PDT) MIME-Version: 1.0 References: <5e50ec97-4a68-b6a5-b8f7-7e9b21028e14@vangyzen.net> In-Reply-To: <5e50ec97-4a68-b6a5-b8f7-7e9b21028e14@vangyzen.net> From: Andrew Thompson Date: Tue, 20 Aug 2019 15:11:29 +1200 Message-ID: Subject: Re: Inter-VM networking with FreeBSD under bhyve To: Eric van Gyzen Cc: freebsd-virtualization@freebsd.org X-Rspamd-Queue-Id: 46CG6T0FTvz3JwJ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of andy@fud.org.nz has no SPF policy when checking 209.85.166.45) smtp.mailfrom=andy@fud.org.nz X-Spamd-Result: default: False [-3.10 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.988,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(-2.33)[ip: (-5.86), ipnet: 209.85.128.0/17(-3.36), asn: 15169(-2.37), country: US(-0.05)]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; AUTH_NA(1.00)[]; URI_COUNT_ODD(1.00)[3]; NEURAL_HAM_LONG(-1.00)[-0.997,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.985,0]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[45.166.85.209.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[thompsa@freebsd.org,andy@fud.org.nz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[thompsa@freebsd.org,andy@fud.org.nz]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 03:11:46 -0000 On Tue, 20 Aug 2019 at 13:57, Eric van Gyzen wrote: > freebsd-virtualization: > > What is my best option for inter-VM networking with FreeBSD guests under > bhyve? I'm only concerned with networking between VMs, not with the > host or physical network. I imagine some form of netmap is my best bet, > but what exactly? There was a presentation by Sean last year for a inter-VM networking framework here, https://www.bsdcan.org/2018/schedule/events/969.en.html I am not sure what has happened to this project. Andrew From owner-freebsd-virtualization@freebsd.org Tue Aug 20 06:50:09 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 92CFAC767A for ; Tue, 20 Aug 2019 06:50:09 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46CLyS5DScz3yCs for ; Tue, 20 Aug 2019 06:50:08 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id x7K6nmFu074525 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 Aug 2019 23:49:48 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id x7K6nm7C074524; Mon, 19 Aug 2019 23:49:48 -0700 (PDT) (envelope-from jmg) Date: Mon, 19 Aug 2019 23:49:48 -0700 From: John-Mark Gurney To: Eric van Gyzen Cc: freebsd-virtualization@freebsd.org Subject: Re: Inter-VM networking with FreeBSD under bhyve Message-ID: <20190820064948.GM2342@funkthat.com> Mail-Followup-To: Eric van Gyzen , freebsd-virtualization@freebsd.org References: <5e50ec97-4a68-b6a5-b8f7-7e9b21028e14@vangyzen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5e50ec97-4a68-b6a5-b8f7-7e9b21028e14@vangyzen.net> X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Mon, 19 Aug 2019 23:49:48 -0700 (PDT) X-Rspamd-Queue-Id: 46CLyS5DScz3yCs X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jmg@gold.funkthat.com has no SPF policy when checking 208.87.223.18) smtp.mailfrom=jmg@gold.funkthat.com X-Spamd-Result: default: False [-2.53 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(-0.88)[ip: (-2.28), ipnet: 208.87.216.0/21(-1.14), asn: 32354(-0.91), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[funkthat.com]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-0.996,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.86)[-0.862,0]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[jmg@funkthat.com,jmg@gold.funkthat.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:32354, ipnet:208.87.216.0/21, country:US]; FROM_NEQ_ENVFROM(0.00)[jmg@funkthat.com,jmg@gold.funkthat.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 06:50:09 -0000 Eric van Gyzen wrote this message on Mon, Aug 19, 2019 at 20:48 -0500: > What is my best option for inter-VM networking with FreeBSD guests under > bhyve? I'm only concerned with networking between VMs, not with the > host or physical network. I imagine some form of netmap is my best bet, > but what exactly? Same host? If so, netmap+vale is interesting, and more info at: https://www.bsdcan.org/2017/schedule/events/814.en.html -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-virtualization@freebsd.org Tue Aug 20 15:47:46 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A0AA1D4C44 for ; Tue, 20 Aug 2019 15:47:46 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46CZtn3s0Fz4Tb3 for ; Tue, 20 Aug 2019 15:47:44 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x7KFlfrE049669; Tue, 20 Aug 2019 08:47:41 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x7KFlfgO049668; Tue, 20 Aug 2019 08:47:41 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201908201547.x7KFlfgO049668@gndrsh.dnsmgr.net> Subject: Re: Inter-VM networking with FreeBSD under bhyve In-Reply-To: <5e50ec97-4a68-b6a5-b8f7-7e9b21028e14@vangyzen.net> To: Eric van Gyzen Date: Tue, 20 Aug 2019 08:47:41 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46CZtn3s0Fz4Tb3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [0.02 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.45)[-0.452,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.33)[-0.334,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.14)[-0.136,0]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.04)[ip: (0.15), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.05), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 15:47:46 -0000 > freebsd-virtualization: > > What is my best option for inter-VM networking with FreeBSD guests under > bhyve? I'm only concerned with networking between VMs, not with the > host or physical network. I imagine some form of netmap is my best bet, > but what exactly? > > Thanks in advance, Do you have any desired parameters? Performance Driven? Simplicity? netmap would probably be the most performant solution, A host bridge device with taps per guest with a vtnet device in the guest would probably be the simplist. By not attaching the bridge to a host adapter and not giving it an IP on the host the host is left out of the communications, BUT it can debug most any of it with tcpdump. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Tue Aug 20 20:32:41 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 15E38DF497 for ; Tue, 20 Aug 2019 20:32:41 +0000 (UTC) (envelope-from list+org.freebsd.virtualization@io7m.com) Received: from mail.io7m.com (mail.io7m.com [45.77.76.92]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.io7m.com", Issuer "arc7 CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46CjCX06xHz3yQ3 for ; Tue, 20 Aug 2019 20:32:39 +0000 (UTC) (envelope-from list+org.freebsd.virtualization@io7m.com) Received: from almond.int.arc7.info (cust187-dsl61.idnet.net [212.69.61.187]) by mail.io7m.com (Postfix) with ESMTPSA id 4F68C30AAA for ; Tue, 20 Aug 2019 20:26:46 +0000 (UTC) Date: Tue, 20 Aug 2019 21:26:36 +0100 From: Mark Raynsford To: freebsd-virtualization@freebsd.org Subject: Severely broken bhyve console Message-ID: <20190820212636.63f08db2@almond.int.arc7.info> Organization: io7m.com OpenPGP: id=E379595716131DB4E7AB87DD67B18CC1F9ACE345; url=https://io7m.com/pgp/E379_5957_1613_1DB4_E7AB_87DD_67B1_8CC1_F9AC_E345.key MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/fiwrxqWyrn.YNb8ZeB57c8j"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-Queue-Id: 46CjCX06xHz3yQ3 X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.91 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[io7m.com:s=mail]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.983,0]; DKIM_TRACE(0.00)[io7m.com:+]; DMARC_POLICY_ALLOW(-0.50)[io7m.com,quarantine]; NEURAL_HAM_SHORT(-0.74)[-0.735,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-0.09)[asn: 20473(-0.40), country: US(-0.05)]; ASN(0.00)[asn:20473, ipnet:45.77.76.0/22, country:US]; TAGGED_FROM(0.00)[org.freebsd.virtualization]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 20:32:41 -0000 --Sig_/fiwrxqWyrn.YNb8ZeB57c8j Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello! For reasons I'm unable to explain, my ability to access the nmdm consoles of bhyve guests has suddenly broken. It may have been caused by a recent 11.2 update - I keep this machine on 11.2-RELEASE plus freebsd-update patches but, as it's not a publically accessible machine, I rarely reboot for updates unless absolutely necessary. I can use "sudo cu -l /dev/nmdm*B" to connect to a particular bhyve guest's console, but as this video shows, the console is effectively unusable: https://ataxia.io7m.com/2019/08/20/broken_terminal.ogv In that video, I connect to /dev/nmdm57B when the guest is shut down. I start the guest in a separate terminal (not pictured) and wait for it to boot into the Debian installer. I don't touch the keys until the title bar becomes visible. At that point, touching the arrow keys or the return key results in chaos. It doesn't seem to be terminal-specific; I'm ssh'd into the host machine, and have tried various different terminals and $TERM settings to no effect. It doesn't seem to be guest-specific; I'm running FreeBSD, Debian, and OpenBSD guests and they now all show this behaviour. The guests themselves don't appear to be in any distress, I can ssh into the guests and everything is working correctly. The host: # uname -a FreeBSD cranberry.int.arc7.info 11.2-RELEASE-p13 FreeBSD 11.2-RELEASE-p13 #0: Tue Aug 6 06:41:33 UTC 2019 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I'd appreciate any help on this. --=20 Mark Raynsford | http://www.io7m.com --Sig_/fiwrxqWyrn.YNb8ZeB57c8j Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQTjeVlXFhMdtOerh91nsYzB+azjRQUCXVxXfAAKCRBnsYzB+azj RXAcAP4xFUjB8KGxYZ6sPRUv9dxhQrPZkCTwNzALKoAinumBHwD/c9tlChYDmX6j kImMLJ9NxWB3ofQnWelozTRHAjvz7AE= =ZubK -----END PGP SIGNATURE----- --Sig_/fiwrxqWyrn.YNb8ZeB57c8j-- From owner-freebsd-virtualization@freebsd.org Tue Aug 20 21:34:14 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3A3FAE1419 for ; Tue, 20 Aug 2019 21:34:14 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46CkZX6LVHz457V for ; Tue, 20 Aug 2019 21:34:12 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x7KLY2ic051161; Tue, 20 Aug 2019 14:34:02 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x7KLY2JZ051160; Tue, 20 Aug 2019 14:34:02 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201908202134.x7KLY2JZ051160@gndrsh.dnsmgr.net> Subject: Re: Severely broken bhyve console In-Reply-To: <20190820212636.63f08db2@almond.int.arc7.info> To: Mark Raynsford Date: Tue, 20 Aug 2019 14:34:02 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46CkZX6LVHz457V X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [0.15 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.06)[-0.059,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.04)[ip: (0.15), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.05), country: US(-0.05)]; TAGGED_RCPT(0.00)[org.freebsd.virtualization]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.61)[-0.612,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.13)[-0.127,0]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 21:34:14 -0000 > Hello! > > For reasons I'm unable to explain, my ability to access the nmdm > consoles of bhyve guests has suddenly broken. It may have been caused > by a recent 11.2 update - I keep this machine on 11.2-RELEASE plus > freebsd-update patches but, as it's not a publically accessible machine, > I rarely reboot for updates unless absolutely necessary. > > I can use "sudo cu -l /dev/nmdm*B" to connect to a particular bhyve > guest's console, but as this video shows, the console is effectively > unusable: > > https://ataxia.io7m.com/2019/08/20/broken_terminal.ogv > > In that video, I connect to /dev/nmdm57B when the guest is shut down. I > start the guest in a separate terminal (not pictured) and wait for it > to boot into the Debian installer. I don't touch the keys until the > title bar becomes visible. At that point, touching the arrow keys or > the return key results in chaos. > > It doesn't seem to be terminal-specific; I'm ssh'd into the host > machine, and have tried various different terminals and $TERM settings > to no effect. It doesn't seem to be guest-specific; I'm running > FreeBSD, Debian, and OpenBSD guests and they now all show this > behaviour. The guests themselves don't appear to be in any distress, I > can ssh into the guests and everything is working correctly. > > The host: > > # uname -a > FreeBSD cranberry.int.arc7.info 11.2-RELEASE-p13 FreeBSD > 11.2-RELEASE-p13 #0: Tue Aug 6 06:41:33 UTC 2019 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > I'd appreciate any help on this. I see this often, but normally I have a shell prompt and can clear the problem with a resizewin command or a stty sane Other things to try are clear, reset, tset. But none of that is going to work inside a grub> prompt. What it looks as if is happened is you have disconnected from a session while it was in grub and had sent specific control sequences, possibly even expecting scroll regions and such set up in the terminal. Now when you reconnect from a newly initialzed terminal that has none of this setup things go very wrong. This can happen on real hardware if you power down your vt320, and then power it back up while something has done a lot of "special" stuff to setup the screen. One solution is to use the graphics console, that does not suffer from these tty type issues, its a bit sluggish if you do not have a good high speed network path to the bhyve host though. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Wed Aug 21 08:51:49 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 458F7C0506 for ; Wed, 21 Aug 2019 08:51:49 +0000 (UTC) (envelope-from list+org.freebsd.virtualization@io7m.com) Received: from mail.io7m.com (mail.io7m.com [IPv6:2001:19f0:5:752:f000::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.io7m.com", Issuer "arc7 CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46D1cN2tH5z3BsR for ; Wed, 21 Aug 2019 08:51:48 +0000 (UTC) (envelope-from list+org.freebsd.virtualization@io7m.com) Received: from almond.int.arc7.info (cust187-dsl61.idnet.net [212.69.61.187]) by mail.io7m.com (Postfix) with ESMTPSA id 9FA557DA9; Wed, 21 Aug 2019 08:51:45 +0000 (UTC) Date: Wed, 21 Aug 2019 09:51:33 +0100 From: Mark Raynsford To: "Rodney W. Grimes" Cc: freebsd-virtualization@freebsd.org Subject: Re: Severely broken bhyve console Message-ID: <20190821095133.29344da4@almond.int.arc7.info> In-Reply-To: <201908202134.x7KLY2JZ051160@gndrsh.dnsmgr.net> References: <20190820212636.63f08db2@almond.int.arc7.info> <201908202134.x7KLY2JZ051160@gndrsh.dnsmgr.net> Organization: io7m.com OpenPGP: id=E379595716131DB4E7AB87DD67B18CC1F9ACE345; url=https://io7m.com/pgp/E379_5957_1613_1DB4_E7AB_87DD_67B1_8CC1_F9AC_E345.key MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/Ig9_L7WRDbnquDl2heTjklD"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-Queue-Id: 46D1cN2tH5z3BsR X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.54 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[io7m.com:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[io7m.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[io7m.com,quarantine]; NEURAL_HAM_SHORT(-0.93)[-0.927,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-0.52)[ipnet: 2001:19f0::/38(-2.13), asn: 20473(-0.41), country: US(-0.05)]; ASN(0.00)[asn:20473, ipnet:2001:19f0::/38, country:US]; TAGGED_FROM(0.00)[org.freebsd.virtualization]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2019 08:51:49 -0000 --Sig_/Ig9_L7WRDbnquDl2heTjklD Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On 2019-08-20T14:34:02 -0700 "Rodney W. Grimes" wrote: > > What it looks as if is happened is you have disconnected from > a session while it was in grub and had sent specific control > sequences, possibly even expecting scroll regions and such > set up in the terminal. Now when you reconnect from a newly > initialzed terminal that has none of this setup things go > very wrong. Interesting. I don't remember this happening, but it's not inconceivable that it happened and I didn't notice it. What is kind of strange is that I appear to be partly in the grub prompt and partly in the Debian installer; I see output and responses from both interleaved. > One solution is to use the graphics console, that does not suffer > from these tty type issues, its a bit sluggish if you do not have > a good high speed network path to the bhyve host though. It's a 1Gbps LAN, so I assume that's fast enough. However: Is there some way I can reset the nmdm device? --=20 Mark Raynsford | http://www.io7m.com --Sig_/Ig9_L7WRDbnquDl2heTjklD Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQTjeVlXFhMdtOerh91nsYzB+azjRQUCXV0GFQAKCRBnsYzB+azj RUL2AQC9o8t9ikolCQkbERHrpZ9MBMgJF9GD2nvP0aR5dLYikgD8C+pyhdZRQ6ev r+kWFCcBUqA2srSN7KvjcLb+2MWsbAQ= =g52h -----END PGP SIGNATURE----- --Sig_/Ig9_L7WRDbnquDl2heTjklD-- From owner-freebsd-virtualization@freebsd.org Wed Aug 21 14:35:16 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 768EBCA14B for ; Wed, 21 Aug 2019 14:35:16 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46D9Dg362Jz41wV for ; Wed, 21 Aug 2019 14:35:15 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from disco.vangyzen.net (unknown [70.97.188.230]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 47E905649D for ; Wed, 21 Aug 2019 09:35:08 -0500 (CDT) Subject: Re: Inter-VM networking with FreeBSD under bhyve References: <201908201547.x7KFlfgO049668@gndrsh.dnsmgr.net> From: Eric van Gyzen To: freebsd-virtualization@freebsd.org Message-ID: <099cc2bb-2647-d012-ca27-f57a99b49010@vangyzen.net> Date: Wed, 21 Aug 2019 09:35:07 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <201908201547.x7KFlfgO049668@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46D9Dg362Jz41wV X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of eric@vangyzen.net designates 2607:fc50:1000:7400:216:3eff:fe72:314f as permitted sender) smtp.mailfrom=eric@vangyzen.net X-Spamd-Result: default: False [-6.24 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DMARC_NA(0.00)[vangyzen.net]; NEURAL_HAM_SHORT(-0.99)[-0.986,0]; IP_SCORE(-2.96)[ip: (-7.09), ipnet: 2607:fc50:1000::/36(-3.79), asn: 36236(-3.87), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:2607:fc50:1000::/36, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2019 14:35:16 -0000 Thanks for the replies, everyone. > Do you have any desired parameters? > Performance Driven? Simplicity? I failed to mention that. I'm interested in performance, especially low CPU overhead. I had tried vale+tap on a stable/12 host, but it wouldn't pass traffic, so I started this thread as a feeler for what was expected to work on which branches. Since then, I updated the host to head, and vale+tap works. I'm very interested in vale+ptnetmap. It seems to be partially committed to head, but not entirely. Is that right? Thanks again. Eric From owner-freebsd-virtualization@freebsd.org Wed Aug 21 15:48:31 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 04879CBDC1 for ; Wed, 21 Aug 2019 15:48:31 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46DBs93xtWz45n1 for ; Wed, 21 Aug 2019 15:48:28 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x7LFmOw0054359; Wed, 21 Aug 2019 08:48:24 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x7LFmOua054358; Wed, 21 Aug 2019 08:48:24 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201908211548.x7LFmOua054358@gndrsh.dnsmgr.net> Subject: Re: Severely broken bhyve console In-Reply-To: <20190821095133.29344da4@almond.int.arc7.info> To: Mark Raynsford Date: Wed, 21 Aug 2019 08:48:24 -0700 (PDT) CC: "Rodney W. Grimes" , freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46DBs93xtWz45n1 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [0.98 / 15.00]; ARC_NA(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; TAGGED_RCPT(0.00)[org.freebsd.virtualization]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.53)[0.529,0]; NEURAL_HAM_LONG(-0.35)[-0.351,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.04)[ip: (0.15), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.05), country: US(-0.05)]; NEURAL_HAM_SHORT(-0.14)[-0.145,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2019 15:48:31 -0000 > On 2019-08-20T14:34:02 -0700 > "Rodney W. Grimes" wrote: > > > > What it looks as if is happened is you have disconnected from > > a session while it was in grub and had sent specific control > > sequences, possibly even expecting scroll regions and such > > set up in the terminal. Now when you reconnect from a newly > > initialzed terminal that has none of this setup things go > > very wrong. > > Interesting. I don't remember this happening, but it's not > inconceivable that it happened and I didn't notice it. Is it possible the VM guest dropped out to grub, or is in a failed reboot state, or in a partial boot state? If grub started up while you had no console attached it may of output a bunch of control sequences that now went into the bit bucket that are need to set the scroll regions, reverse video, etc. Is there a way to tell grub it is using a dumb terminal and not a PC console, or vt100, or xterm. Just a dumb old tty (/etc/termcap calls this "dumb".) Using that as the console type may resolve these issues. > What is kind of strange is that I appear to be partly in the grub > prompt and partly in the Debian installer; I see output and responses > from both interleaved. I agree that is very odd, is it possible the same nmdm device somehow has been attached to multip vm's? I am not even sure if that is possible. Traditional tty's can be open by more than one process so I think it might be possible to do that, and this would lead to a mess as well. > > One solution is to use the graphics console, that does not suffer > > from these tty type issues, its a bit sluggish if you do not have > > a good high speed network path to the bhyve host though. > > It's a 1Gbps LAN, so I assume that's fast enough. > > However: Is there some way I can reset the nmdm device? The problem is not that you need to reset the nmdm device, the problem is what ever is running on the inside the guest talking to the console believes the device to be in a different state than what your device is in, and there is no convienient way to get your device in the expected state. In the situation of a shell prompt you can get the 2 states alligned by issueing a terminal reset command of some form, I have no idea how to do that at a grub prompt. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Wed Aug 21 16:00:47 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 72318CC287 for ; Wed, 21 Aug 2019 16:00:47 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46DC7L3xdRz46w7 for ; Wed, 21 Aug 2019 16:00:46 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x7LG0ioA054419; Wed, 21 Aug 2019 09:00:44 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x7LG0iup054418; Wed, 21 Aug 2019 09:00:44 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201908211600.x7LG0iup054418@gndrsh.dnsmgr.net> Subject: Re: Inter-VM networking with FreeBSD under bhyve In-Reply-To: <099cc2bb-2647-d012-ca27-f57a99b49010@vangyzen.net> To: Eric van Gyzen Date: Wed, 21 Aug 2019 09:00:44 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46DC7L3xdRz46w7 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [1.10 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.31)[-0.314,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.61)[0.606,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.14)[-0.138,0]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.04)[ip: (0.15), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.05), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2019 16:00:47 -0000 > Thanks for the replies, everyone. > > > Do you have any desired parameters? > > Performance Driven? Simplicity? > I failed to mention that. I'm interested in performance, especially low > CPU overhead. Then a netmap based solution is probably in line with your goal. > I had tried vale+tap on a stable/12 host, but it wouldn't pass traffic, > so I started this thread as a feeler for what was expected to work on > which branches. Since then, I updated the host to head, and vale+tap works. > > I'm very interested in vale+ptnetmap. It seems to be partially > committed to head, but not entirely. Is that right? I am not well informed as to the state of this. > Thanks again. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Fri Aug 23 04:55:43 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4F464DA426 for ; Fri, 23 Aug 2019 04:55:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46F8H31RX6z4JQj for ; Fri, 23 Aug 2019 04:55:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 2F59ADA425; Fri, 23 Aug 2019 04:55:43 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2DED1DA424 for ; Fri, 23 Aug 2019 04:55:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46F8H30FWXz4JQh for ; Fri, 23 Aug 2019 04:55:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DA3A8F7F5 for ; Fri, 23 Aug 2019 04:55:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7N4tgrm041727 for ; Fri, 23 Aug 2019 04:55:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7N4tg0K041726 for virtualization@FreeBSD.org; Fri, 23 Aug 2019 04:55:42 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 240050] Keyboard Function Lost Post Kernel Intense Swapping after Application Process Killed by Kernel Date: Fri, 23 Aug 2019 04:55:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bhyve X-Bugzilla-Version: 11.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jlmales@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: 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-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 04:55:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240050 Bug ID: 240050 Summary: Keyboard Function Lost Post Kernel Intense Swapping after Application Process Killed by Kernel Product: Base System Version: 11.3-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: jlmales@gmail.com Created attachment 206810 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D206810&action= =3Dedit Various Information On Clean Boot of System I am not new to Unix having used Unix since 1995, and as my only OS since 1= 999. I am new to FreeBSD mostly since mid July 2019, and on/off attempts over l= ast 15 years. This problem is serious, but likely I or only a few unique types of users w= ill experience this serious problem. What makes this bug unique from information gathering and debugging point of view is the complete loss of the keyboard. Complete loss does mean no input from the keyboard is accepted not is any input from the keyboard result in a beep. At the time of this FreeBSD Kernel condition I had been and still was in my XFCE4 DE environment. The mouse was responsive and applications would resp= ond to the mouse, but application would respond to any keyboard input. The CTL-Alt-Fn keyboard sequence was also unresponsive. For reasons unknown the only XFCE4 functions not greyed out was "Log Out". Various applications were successfully and normally exited via the use of t= he DE mouse by selecting the application menu to exit the application. Upon "Log Out" of XFCE DE the command line appeared as is how my system is = so configured. I did not install SLIM nor any other DE GUI based login manage= r.=20 The command line would not accept any keyboard input and likewise no error messages not keyboard beeps. Two additional observations were also made. The first and most important is I believe the condition of the keyboard was directly related to the FreeBSD Kernel in a intense swap file activity for about 15 minutes before the base system killed Firefox as the almost certain object of the intense swap file activity. Be aware I have far more than li= kely to ever be needed at present of swap file space. That means the swap file capacity would not have been reached. At the time of the intense swap acti= vity about 4.78GB of swap was being used as it so happens htop was already runni= ng on a terminal as well as XOSview at time of intense swap file use. When the base system killed firefox the swap file use dropped to about 678Mb per hto= p.=20 htop could not be exited via the keyboard "q" normally used to exit htop. The second by pure chance of circumstance occurred at the terminal prompt a= fter the successful exit from XFCE DE unresponsive to any keyboard input. I happened to plug my phone in to charge via USB cable left in the laptop ong= oing for that purpose. The Android phone in question has no USB access by desig= n of the phone (long story, but Samsung disabled any USB access on this specific version of the phone). Despite the phone not having USB access to files on= the phone FreeBSD Kernel did issue messages to the terminal when the phone was connected to the USB port. I tried the keyboard again out of curiosity, and found he keyboard was responsive! This allowed me to shutdown FreeBSD norm= ally vs the only other option I did not wish to use being a power off. Despite issuing a "poweroff" command and then powering on the laptop after there appeared to be a number of file system repairs done, but I have not b= een able to find where FreeBSD keeps the messages that flash by on the booting = of the FreeBSD kernel to save those messages and look at them in more detail. I had a long career in IT and much of that career was working on bugs that = were often very difficult to find, including difficult to duplicate. So I know = more information will be needed for when this FreeBSD Kernel bug occurs again. I know it will, but I do not know when. In the process of first sorts of software I like to have on a Unix system=20 bsdsar was at top of list after some basic research. Sadly bsdsar seems to have been an inactive project for a long time. I have been unable to find a alternative to bsdsar that would have at least provided some metrics on th paging activity, extent, how much and how long before firefox was killed by= the base system. Wat I need to know is based on the likely limitation of no keyboard access what can I do that will collect information about this issue that can be looked at even after I may have to hard power off the laptop vs using "shutdown" or "poweroff" or "reboot" CLI commands? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Aug 23 05:47:30 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0BD76DAEF8 for ; Fri, 23 Aug 2019 05:47:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46F9Qn6SLFz4Lqv for ; Fri, 23 Aug 2019 05:47:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id DD976DAEF7; Fri, 23 Aug 2019 05:47:29 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DD5A5DAEF6 for ; Fri, 23 Aug 2019 05:47:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46F9Qn5Sjhz4Lqt for ; Fri, 23 Aug 2019 05:47:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9D5D0180EB for ; Fri, 23 Aug 2019 05:47:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7N5lT8e078229 for ; Fri, 23 Aug 2019 05:47:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7N5lTBp078228 for virtualization@FreeBSD.org; Fri, 23 Aug 2019 05:47:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 240050] Keyboard Function Lost Post Kernel Intense Swapping after Application Process Killed by Kernel Date: Fri, 23 Aug 2019 05:47:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bhyve X-Bugzilla-Version: 11.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jlmales@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 05:47:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240050 John changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlmales@gmail.com --- Comment #1 from John --- Created attachment 206812 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D206812&action= =3Dedit dmesg from just prior to firefox killed by base system, poweroff CLI, to fi= rst few messages after Power On laptop This is the dmesg from just before FreeBSD Kernel base system killed firefox after intense swap file activity by firefox for about 15 minutes to when ab= le to issue CLI "poweroff" command after by chance phone enabled keyboard acce= ss again to first few dmesg after powered on laptop after CLI "poweroff" comma= nd. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Aug 23 05:58:01 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 699F0DB15A for ; Fri, 23 Aug 2019 05:58:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46F9fx291nz4M9w for ; Fri, 23 Aug 2019 05:58:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 474CEDB159; Fri, 23 Aug 2019 05:58:01 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 45DE7DB158 for ; Fri, 23 Aug 2019 05:58:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46F9fx0r8Zz4M9v for ; Fri, 23 Aug 2019 05:58:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id EE3A3182B8 for ; Fri, 23 Aug 2019 05:58:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7N5w0qj006354 for ; Fri, 23 Aug 2019 05:58:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7N5w0sZ006351 for virtualization@FreeBSD.org; Fri, 23 Aug 2019 05:58:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 240050] Keyboard Function Lost Post Kernel Intense Swapping after Application Process Killed by Kernel Date: Fri, 23 Aug 2019 05:58: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: 11.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jlmales@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: component 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-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 05:58:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240050 John changed: What |Removed |Added ---------------------------------------------------------------------------- Component|bhyve |kern --- Comment #2 from John --- I am new to FreeBSD and found the bug was assigned to virtualization@FreeBSD.org as I choose bhyve as "Component". This is not a virtualization bug at all. I am was just trying to select a "Component" for base system and not sources that some of the "Component" indicated as the "Component". I am going to try "kern" for "Component" even tough I never b= uilt the FreeBSD kernel from source. I just installed the stable FreeBSD Kernel thjat has not been updated since I installed FreeBSD mid July 2019. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Aug 23 17:03:30 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DB4AEC9FB4 for ; Fri, 23 Aug 2019 17:03:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46FSQp5S3tz40WQ for ; Fri, 23 Aug 2019 17:03:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id B9349C9FB2; Fri, 23 Aug 2019 17:03:30 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B8F4AC9FB1 for ; Fri, 23 Aug 2019 17:03:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46FSQp4Lk7z40WP for ; Fri, 23 Aug 2019 17:03:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 76F3D1FBDA for ; Fri, 23 Aug 2019 17:03:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7NH3Uja074142 for ; Fri, 23 Aug 2019 17:03:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7NH3UjH074141 for virtualization@FreeBSD.org; Fri, 23 Aug 2019 17:03:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 240050] Keyboard Function Lost Post Kernel Intense Swapping after Application Process Killed by Kernel Date: Fri, 23 Aug 2019 17:03: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: 11.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pete@nomadlogic.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@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-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 17:03:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240050 pete@nomadlogic.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pete@nomadlogic.org --- Comment #3 from pete@nomadlogic.org --- (In reply to John from comment #2) Since this is an old'ish stable system would it be possible to reproduce th= is either on a fresh stable build, or try to reproduce this behavior on a rele= ase? having said that I have certainly seen issues where firefox will swap like crazy and user input will become very slow while a core file for firefox is being generated due to a crash. generally after the intensive i/o is done = the system becomes responsive again. also, are you able to ssh into this system when the problem occurs? if so, what processes are running - the systat(1)= and procstat(1) man pages will be helpful here. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Aug 23 18:45:54 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 00556CBC07 for ; Fri, 23 Aug 2019 18:45:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46FVhx6F1vz44dF for ; Fri, 23 Aug 2019 18:45:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id D4228CBC06; Fri, 23 Aug 2019 18:45:53 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D3E49CBC05 for ; Fri, 23 Aug 2019 18:45:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46FVhx5DYbz44dD for ; Fri, 23 Aug 2019 18:45:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9125020DCD for ; Fri, 23 Aug 2019 18:45:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7NIjrsc006746 for ; Fri, 23 Aug 2019 18:45:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7NIjr1V006745 for virtualization@FreeBSD.org; Fri, 23 Aug 2019 18:45:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 240050] Keyboard Function Lost Post Kernel Intense Swapping after Application Process Killed by Kernel Date: Fri, 23 Aug 2019 18:45:53 +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: 11.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jlmales@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@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-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 18:45:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240050 --- Comment #4 from John --- (In reply to pete from comment #3) Pete, Thanks for reply and information. I have a few questions. I installed FreeBSD just after the 11.3 release. I used the USB image and installed all but the sources. I was expecting the base system and kernel updates would occur via updates. So far that appears not to occur assuming= no base/kernel updates since the release of 11.3. I have used pkg update/upgrade that appears to keep the installed packages = up to date. About 4 weeks ago I looked into if and why the FreeBSD kernel is or not upgraded. I ave not determined yet if there have been base/kernel updates s= ince the 11.3 release. Should I have installed sources? Are sources needed for base/kernel updates? Why if not needed for installing FreeBSD? I choose n= ot to install sources as I did not feel I would have a need to customized the FreeBSD kernel. I had for many reasons had to many times (usually about 4-8 times a year, sometimes many more) configure and compile the Linux Kernel m= any many times over the past 20 years. I assumed stable FreeBSD kernel meant stable and stable updates would occur. I sense I am incorrect with that assumption, but not certain what the best approach is for FreeBSD kernel updates while not destabilizing my DE and installed packages. My last atte= mpt at FreeBSD as test system a couple years ago updates to packages and kernel would cause frequent issues and I could not access any X, DE and/or key DE = apps for months at time. One very very creative effort taking lots of timet dug = me out of one of those instances of many months of no access beyond CLI after boot. I have always favoured CLI after boot by choice so I can then choose what to do next. Is there a safe approach to update kernel/base so the packaged installed are not out of sync with the kernel/base? If so where d= o I look to find this. I have felt safe enough thus far to allow me to use Fre= eBSD as my primary system. Long term ideal is o find a way to create a LiveCD FreeBSD like OliveBSD for stability handful of systems I have that run 24/7= /365 from another Kernel common to LiveCD images.=20 I believe the core issue is FreeBSD decided there was too much time and swap activity being used by Firefox so FreeBSD killed firefox. The core dump wh= ich I have not looked for nor care about does not take long to create. The sys= tem was responsive for that 15+ minutes of intense swap activity I am certain w= as all due to Firefox. As I mentioned swap file used dropped to basically no = swap file space once Firefox was killed by FreeBSD. I have had a few of these events of intense swap file activity for a shorter time period where FreeBSD kills firefox, but this is first time after such an set of similar events h= as the keyboard been dead from FreeBSD kernel perspective, let alone carry to = the CLI after DE is shut down via mouse still active. For moment I think to keep all things equal I like to stay with the version= of the FreeBSD kernel I have for one key reason. The less variables I change = the better it is to isolate the issue. I believe that once the issue is isolat= ed then it can be determined with ease if this issue still exists with more current versions of the FreeBSD Kernel/Base. The reason I favour this appr= oach is based on my extensive past professional experience working with bugs that are difficult to duplicate as well as being complex in factors that are cau= se is the less that is changed the better and often such issues become more difficult to try to duplicate with newer versions as the underlying bug see= ms for indirect reasons to become deeper to reach ergo much more difficult to isolate/duplicate. I do not know if there are any Free BSD sandboxes where I can attempt to duplicate the issue only needed CLI based environment that allows me to ins= tall other CLI applications that may help in my duplicating and collecting system information about the bug. If there is many that is an option to consider = for this issue. This issue needs to be done bare metal and not via a VM for rea= sons I will skip other than to say if it was IBM VM then via VM would be just fi= ne, but X86 based VM is nowhere close to IBM VM of 1980s, let alone the even mo= re refined IBM VM of current day. Suffice to say I have lots of systems and VM experience dating back to the 1980s and onward for some years agmonst other= s. I looked into and tried systat(1) and procstat(1) you suggested. systat al= lows some vmstat information to be displayed, but in awkward manner. Awkward meaning not compatible with a table or CSV format of data such as dstat ( or sar in Linux create that I suspect bsdsar would also provide. I used sar via systat in Linux and I used dstat alot of time Linux to document what was almost always a similar set of conditions, but caused different variations of issues with the Linux Kernel= .=20 vmstat -s in my opinion produces the type of information for sure needed for this FreeBSD issue, but again not in a table or CSV format that can be iter= ated over an interval of time. This means I am still at basic loss of how I can collect information proactively as once the bug occurs I cannot enter any commands at all inclu= ding vmstat, systat, procstat, et al to get a sense of the FreeBSD Kernel bug. = It means I have to run commands that can just run and collect information with timestamps proactive so these are running and ideally still able to log the= ir information when this FreeBSD Kernel bug occurs. --=20 You are receiving this mail because: You are the assignee for the bug.=