From owner-freebsd-virtualization@freebsd.org Sun May 14 01:34:12 2017 Return-Path: Delivered-To: freebsd-virtualization@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 794CBD6C25B for ; Sun, 14 May 2017 01:34:12 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (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 50CAA159F for ; Sun, 14 May 2017 01:34:12 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-oi0-x242.google.com with SMTP id m17so14174665oik.2 for ; Sat, 13 May 2017 18:34:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=eXAV9SlNRO2uZjenJP207D4mV4IwVkYmfzD/qTJ4wSY=; b=E7UIV9doy8IQct6wAyaa9Hb54lWbEnlcIPNeF4GNoVrGYZ68K3LGTwihAPwCbMqXEg xIZQ+5dekBx049Ve23lxa1AXX2nDPQfrdAD+K7C4ytEb23cPdPQ60hPnhgr1WY22v4/O XRuOD/L242JneEr64FFCyOt0QETLfDcB2rZh/MAjO0WJvWVr54qHiJyMcHmehmmTS4aT byk+7fFoqMuqN6/lfKPW4djIGwZpPqVNyoJUuz6aT7eXpR94rQo/YwFX4+GuwD2UISRE 7aEYJzfeWMMZQgw4w3x4MB5ImXtEBucxqnmDtW1o+AtDB4kecObuGK3DYA4u5iuew2/4 XJRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=eXAV9SlNRO2uZjenJP207D4mV4IwVkYmfzD/qTJ4wSY=; b=PILuW21gDXQV5kpjropBTHdeIQpJaKTbDS9rnMsU74R1KoWrMlap0ooTkKajoyhTwF Q1fk+5DU4K1WRdRQm5Va9SdApyitBSZU2DyrPOQgRL6To6+weDmBXM8gHQTzzb7MMQlF sZwElrvW0gnYZ4TknWkPMRKodXk7PGcolcLvcCOMu9+xcJM1l65A4ZYYyaYmK7CjrbqA LdlCLqExahykWLQHKlFuSsSpRXPLoHq0Ins8YlnIBo1K03BCR9Weu29JnT8cWqsp2fR6 zSy2uXxe5OmRo+AmPoRoU3rvTzUqsfsJ8z8bex2H8nnvmwPLRQ6i1foOEZKUozSoVofX IGew== X-Gm-Message-State: AODbwcDvfx04k18c3G37rVq3OTJgoVHaDfQ8CYAF/U6Rs06wevYHxe9b M/q0ZIt6UWT1jXK7DYE= X-Received: by 10.157.1.195 with SMTP id e61mr5955204ote.234.1494725651103; Sat, 13 May 2017 18:34:11 -0700 (PDT) Received: from ?IPv6:2601:2c2:200:24bb:80e5:eed3:7a84:e697? ([2601:2c2:200:24bb:80e5:eed3:7a84:e697]) by smtp.gmail.com with ESMTPSA id r203sm3684067oif.15.2017.05.13.18.34.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 13 May 2017 18:34:10 -0700 (PDT) To: freebsd-virtualization@freebsd.org From: Rajil Saraswat Subject: PCIE card with USB ports Message-ID: <3c9b9b8f-1d88-bc87-64eb-a974b6f30151@gmail.com> Date: Sat, 13 May 2017 20:34:10 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 14 May 2017 01:34:12 -0000 Hello, I am looking for a recommendation for an out-of-the-box working PCIE card with USB controller. Thanks From owner-freebsd-virtualization@freebsd.org Sun May 14 16:05:35 2017 Return-Path: Delivered-To: freebsd-virtualization@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 1F2BED6C73E for ; Sun, 14 May 2017 16:05:35 +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 0D38F111A for ; Sun, 14 May 2017 16:05:35 +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 v4EG5Y3J065395 for ; Sun, 14 May 2017 16:05:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 211136] [Hyper-V]mount root may fail because vfs' mount starts early than VMBUS Date: Sun, 14 May 2017 16:05:34 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: dave@freedave.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.23 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: Sun, 14 May 2017 16:05:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211136 David Marker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dave@freedave.net --- Comment #2 from David Marker --- Created attachment 182594 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D182594&action= =3Dedit fix mountroot hyper-v in 11-stable --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sun May 14 16:08:08 2017 Return-Path: Delivered-To: freebsd-virtualization@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 EF046D6C7B6 for ; Sun, 14 May 2017 16:08:08 +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 DE50C119B for ; Sun, 14 May 2017 16:08:08 +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 v4EG8802068558 for ; Sun, 14 May 2017 16:08:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 211136] [Hyper-V]mount root may fail because vfs' mount starts early than VMBUS Date: Sun, 14 May 2017 16:08:09 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: dave@freedave.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.23 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: Sun, 14 May 2017 16:08:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211136 --- Comment #3 from David Marker --- I had the same problem in 11-stable. The issue is that storvsc root_mount_hold() happens after ZFS tried to mount root. Adding it to the bus fixed it (see patch). I found this a little more satisfying than the busy wait suggested in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sun May 14 17:46:43 2017 Return-Path: Delivered-To: freebsd-virtualization@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 398F1D6D326 for ; Sun, 14 May 2017 17:46:43 +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 192EB1DAD for ; Sun, 14 May 2017 17:46:42 +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 v4EHe5Ax058141 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 14 May 2017 10:40:06 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id v4EHe5vG058140; Sun, 14 May 2017 10:40:05 -0700 (PDT) (envelope-from jmg) Date: Sun, 14 May 2017 10:40:05 -0700 From: John-Mark Gurney To: Rajil Saraswat Cc: freebsd-virtualization@freebsd.org Subject: Re: PCIE card with USB ports Message-ID: <20170514174005.GY2042@funkthat.com> References: <3c9b9b8f-1d88-bc87-64eb-a974b6f30151@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3c9b9b8f-1d88-bc87-64eb-a974b6f30151@gmail.com> 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]); Sun, 14 May 2017 10:40:06 -0700 (PDT) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 14 May 2017 17:46:43 -0000 Rajil Saraswat wrote this message on Sat, May 13, 2017 at 20:34 -0500: > I am looking for a recommendation for an out-of-the-box working PCIE > card with USB controller. They all should just work. The driver interface is standardized and should just work no mater what card you pick. -- 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 Sun May 14 21:00:12 2017 Return-Path: Delivered-To: freebsd-virtualization@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 11821D6C129 for ; Sun, 14 May 2017 21:00:12 +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 E215514EA for ; Sun, 14 May 2017 21:00:11 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4EL01tV029899 for ; Sun, 14 May 2017 21:00:11 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201705142100.v4EL01tV029899@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-virtualization@FreeBSD.org Subject: Problem reports for freebsd-virtualization@FreeBSD.org that need special attention Date: Sun, 14 May 2017 21:00:11 +0000 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 14 May 2017 21:00:12 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 212820 | FreeBSD 10-STABLE from latest HEAD and 11-RELEASE 1 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Sun May 14 21:03:11 2017 Return-Path: Delivered-To: freebsd-virtualization@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 6716BD6CA29 for ; Sun, 14 May 2017 21:03:11 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::22d]) (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 371B41E93 for ; Sun, 14 May 2017 21:03:11 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-pg0-x22d.google.com with SMTP id q125so31250563pgq.2 for ; Sun, 14 May 2017 14:03:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=7otZJURGqWrjwDpYnIIhnSYvD6i4KLQXQwvITn/o+tY=; b=Pk64G1YtyvBHSrmMiBTzC+IKeh/vBYRDNkGhke88Ca0Eilx053FsPLqsKTGedhz3uM UMMGNfmyVhmxrFMb2r+ue6NBe7lZldES4ikPqxV+FsVdSVriB+DvJ2c8lOSKNAWBo0J4 USWx4yQeFDoD1eCv9NNT5sddtWUcA2hDAMN7m9IP+sfW2qujJO6pdRSMOuRPjajqXa7l yEyKY+/R53TGfVioeLUPo8U1D7SVmAZD0uvAAkoC5FEiOIL2Hts+tV/s9KQRlHGwkvp8 PlW+CvSc6LhHnPb6jHZB6zpT0WghiUsJXTZLsWZvHldOJt5F8YotxGgx9R7NkZDeYAzu 8oIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=7otZJURGqWrjwDpYnIIhnSYvD6i4KLQXQwvITn/o+tY=; b=iE27dTChY3+CCPngwEyEubhJNgKqEfGWP3J91tpXqj46e3hmLpXUPTVsq2/1V9vNzq qZuRoakCncSdqyzTO6HfrMjBMIfuO/NFwCGdRSU0VC32aXwH98uA8MR5EwH19H9aaphj dFGhIcC6VCuO7qbMlFYrR1fsOkO6Ij2toen/TcuzOMz1zflS5JYXmmNyeYqk08frdHyY f2rxp0LtrjF7q7XYGoBoa3lvIrwkIjs/WhsFEQOZeLStjCSXA0boz9w73EVSNANHdeeO w+fBq1Yx4/e9bFKhcuITFcfYFdexgKLGRS0FfguOkNqC3Mlv/5d0KOhIuXEDsghgloX2 pmVg== X-Gm-Message-State: AODbwcB8IijJz5+NSJOPcsgLMfcaIs7KP72YvRJeVF2oXuuLRxOVgYRs /Ity/yV+FhDf5lGbNwc= X-Received: by 10.99.189.2 with SMTP id a2mr2904137pgf.85.1494795790481; Sun, 14 May 2017 14:03:10 -0700 (PDT) Received: from ?IPv6:2601:2c2:200:24bb:80e5:eed3:7a84:e697? ([2601:2c2:200:24bb:80e5:eed3:7a84:e697]) by smtp.gmail.com with ESMTPSA id b90sm16270529pfj.19.2017.05.14.14.03.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 14 May 2017 14:03:10 -0700 (PDT) Subject: Re: PCIE card with USB ports To: freebsd-virtualization@freebsd.org References: <3c9b9b8f-1d88-bc87-64eb-a974b6f30151@gmail.com> <20170514174005.GY2042@funkthat.com> From: Rajil Saraswat Message-ID: <8726d7e3-38ae-76a7-7489-2d46f26cc1a3@gmail.com> Date: Sun, 14 May 2017 16:03:08 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170514174005.GY2042@funkthat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 14 May 2017 21:03:11 -0000 On 05/14/2017 12:40 PM, John-Mark Gurney wrote: > Rajil Saraswat wrote this message on Sat, May 13, 2017 at 20:34 -0500: >> I am looking for a recommendation for an out-of-the-box working PCIE >> card with USB controller. > They all should just work. The driver interface is standardized and > should just work no mater what card you pick. > I came across the following post wherein there was some issue with a card. Is that no longer the problem in FreeBSD-11? https://lists.freebsd.org/pipermail/freebsd-virtualization/2015-February/003371.html From owner-freebsd-virtualization@freebsd.org Mon May 15 00:16:40 2017 Return-Path: Delivered-To: freebsd-virtualization@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 8AC1AD6C1BD for ; Mon, 15 May 2017 00:16:40 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50E7818B5; Mon, 15 May 2017 00:16:40 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-pg0-x233.google.com with SMTP id x64so32280075pgd.3; Sun, 14 May 2017 17:16:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ioRLZgYziDSYzx0HnLuNTppPnel6oVqOiPpqnMiHGeI=; b=cSq/sGC5jcamfjuMNuoqhMchiICjA84kBehTGaLqtnlX4IC52980L/+PIqVCmHRZbs UstVAS/zZ+M2W8JFCDhFFtPyR6sREOtEgjVjfmBINL6SbzsHqWI9y79OsSXBlM6+GJUd dqoBGLoGPCw4E3B5F3ic2yRj0qFIq1MUVB8ysLx6p+Y758doJPxPZ/Co+kLOI5OYDalk RThPxNBhstjO67HxceDVSqrVxd6YFw+pjrp8ZKvm3iKQLR505uoO1wrz1tAqIlOwGYln WP+AHhzmbPkWeNW5TQkvW3wD9FV1avkQl0wi9ZotSutOH2okThu+aAYxIVlpm1RcVG+i Nzag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ioRLZgYziDSYzx0HnLuNTppPnel6oVqOiPpqnMiHGeI=; b=bMKi/pSgROZWKTYyTljsMv2drDfJWF5MFALJCLkAE7Z8mwiSgFq7TdctIozzPcioYz C4jCf+UANAGPh7t0vz3LatYoUKhJL1IZDu3sw9ka4WS5TGZtUBVylCW1DK4f74sBP2gk aTeaHzjpMfIcGebYRW29tSTvzFXYOfzgYf1m8dARfGBeg5CZ7dqME6xn7tv10X6XvOwC sLa8aQWq/p9XHGoW26i+b3jZ25FO0zAYuntXKgO3W54T5X06wrrz25FZL84ca7oQK7to ghzfOXQtTb88MhTbUZKQQKc2xYZKeFPTOKWr0QHL0p76yg68s3cB99izn0cT1VZwncA9 P9HQ== X-Gm-Message-State: AODbwcAHf/84YIf1DYcq5TE21+rgWOZzjc2L9VmwAzZPFqGjHBYqUcaV ZntgT8sIJujojJDuIsw= X-Received: by 10.99.109.141 with SMTP id i135mr3389625pgc.33.1494807399292; Sun, 14 May 2017 17:16:39 -0700 (PDT) Received: from ?IPv6:2601:2c2:200:24bb:80e5:eed3:7a84:e697? ([2601:2c2:200:24bb:80e5:eed3:7a84:e697]) by smtp.gmail.com with ESMTPSA id o89sm5198267pfj.88.2017.05.14.17.16.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 14 May 2017 17:16:38 -0700 (PDT) Subject: Re: PCIE card with USB ports To: freebsd-virtualization@freebsd.org References: <3c9b9b8f-1d88-bc87-64eb-a974b6f30151@gmail.com> <20170514174005.GY2042@funkthat.com> From: Rajil Saraswat Message-ID: <1c398033-a2aa-0060-6122-93f46de04bbe@gmail.com> Date: Sun, 14 May 2017 19:16:37 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170514174005.GY2042@funkthat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 15 May 2017 00:16:40 -0000 On 05/14/2017 12:40 PM, John-Mark Gurney wrote: > Rajil Saraswat wrote this message on Sat, May 13, 2017 at 20:34 -0500: >> I am looking for a recommendation for an out-of-the-box working PCIE >> card with USB controller. > They all should just work. The driver interface is standardized and > should just work no mater what card you pick. > Peter, Following is the list from xhci_pci.c. Any recommended card? case 0x01941033: /* NEC uPD720200 USB 3.0 controller */ case 0x00141912: /* NEC uPD720201 USB 3.0 controller */ /* Don't use 64-bit DMA on these controllers. */ usedma32 = 1; break; case 0x10001b73: /* FL1000G */ /* Fresco Logic host doesn't support MSI. */ usemsi = 0; break; case 0x0f358086: /* BayTrail */ case 0x9c318086: /* Panther Point */ case 0x1e318086: /* Panther Point */ case 0x8c318086: /* Lynx Point */ case 0x8cb18086: /* Wildcat Point */ case 0x9cb18086: /* Broadwell Mobile Integrated */ PS: Renesas uPD720201 based cards seem to be cheapest on Amazon. Thanks From owner-freebsd-virtualization@freebsd.org Mon May 15 15:50:45 2017 Return-Path: Delivered-To: freebsd-virtualization@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 140E2D6E0E2 for ; Mon, 15 May 2017 15:50:45 +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 E8FDCEAF for ; Mon, 15 May 2017 15:50:44 +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 v4FFoh6A075341 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 15 May 2017 08:50:43 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id v4FFohPe075340; Mon, 15 May 2017 08:50:43 -0700 (PDT) (envelope-from jmg) Date: Mon, 15 May 2017 08:50:43 -0700 From: John-Mark Gurney To: Rajil Saraswat Cc: freebsd-virtualization@freebsd.org Subject: Re: PCIE card with USB ports Message-ID: <20170515155043.GA2042@funkthat.com> References: <3c9b9b8f-1d88-bc87-64eb-a974b6f30151@gmail.com> <20170514174005.GY2042@funkthat.com> <8726d7e3-38ae-76a7-7489-2d46f26cc1a3@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8726d7e3-38ae-76a7-7489-2d46f26cc1a3@gmail.com> 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, 15 May 2017 08:50:43 -0700 (PDT) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 15 May 2017 15:50:45 -0000 Rajil Saraswat wrote this message on Sun, May 14, 2017 at 16:03 -0500: > On 05/14/2017 12:40 PM, John-Mark Gurney wrote: > > Rajil Saraswat wrote this message on Sat, May 13, 2017 at 20:34 -0500: > >> I am looking for a recommendation for an out-of-the-box working PCIE > >> card with USB controller. > > They all should just work. The driver interface is standardized and > > should just work no mater what card you pick. > > > I came across the following post wherein there was some issue with a > card. Is that no longer the problem in FreeBSD-11? > > https://lists.freebsd.org/pipermail/freebsd-virtualization/2015-February/003371.html Yes, it has been fixed/addressed and was committed before 11: https://svnweb.freebsd.org/base/head/usr.sbin/bhyve/pci_passthru.c?revision=297932&view=markup -- 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 Mon May 15 17:53:30 2017 Return-Path: Delivered-To: freebsd-virtualization@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 6B63AD6E7CA for ; Mon, 15 May 2017 17:53:30 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (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 2173614F for ; Mon, 15 May 2017 17:53:30 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-ua0-x22b.google.com with SMTP id e55so85133130uaa.2 for ; Mon, 15 May 2017 10:53:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XqSFaPuThTMLvcE4azZ7wtxNi8G3taJeCaFifkrEWO8=; b=jYMC1hfWtCout2MK3u473V5uDhRgo3qWN2+SqM19lCire9a9exabrohlVWAfU0rLZf McRJ50K25TgDxO/yMC6cfkCcLrdMx12UjY9VH5UT2YJ5kbShO0G2ro4V18a1PWfYpKhp aE9+EhrzHzMZtPzg8G9jMjb4ivJM1d8P4YM6b8jjZMKuLguqWKdcdrvclj2Kf8U+1LVs 9il/RMN429Oxko/vdXtdST3r65KcyG1DHUvszWEJkDna6qDid1tEr+EcPnepKtJhqHsk srN7ONVAleIII62J4i2OZeOf9nF6YgdWiQLbOgthFeWl4wpSG6wyG/44wFlQn9Szs23G y5NA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XqSFaPuThTMLvcE4azZ7wtxNi8G3taJeCaFifkrEWO8=; b=gMRcONmLGw/bdg+JGCwkn1ak5zIBSiunx9kp66wHFgknCDviPdy2AygUAPuymBD5N2 /8Oz2nMp9nzNC3OrIJUyhPHAl8JS4PyAApuoP0ilVb2zBU4r5EnSMoBFWlvhRp9mdoiK ou7797u6GKmk+cNgI7stJOJIjSrp9lyR99Yi//5t6ARTF5b0i9WaE+xdrYsgbNfCHxuL a4fVbJmgfZiwZGTXroH0IAW7lsTLXfIKiBlYDVtEe5zKmmXmJuSh+ckNPxgp3FVSri7o pULC6+m3FmZCpMvJnuy8L/BBKR4+lIr+K5DN2pa1sRuIlAL34OV8I4dqItLa8oztYbQA SKgQ== X-Gm-Message-State: AODbwcD9hEvz7SNuk7XF/+HAyMVi361v/8+Dxk9podHG8/s4EDd8k9sN TEtxG+6F5vzetJaxGyDjOnWyKbovoT+7 X-Received: by 10.176.85.145 with SMTP id v17mr3798490uaa.148.1494870809212; Mon, 15 May 2017 10:53:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.84.142 with HTTP; Mon, 15 May 2017 10:53:28 -0700 (PDT) Received: by 10.176.84.142 with HTTP; Mon, 15 May 2017 10:53:28 -0700 (PDT) In-Reply-To: <20170515155043.GA2042@funkthat.com> References: <3c9b9b8f-1d88-bc87-64eb-a974b6f30151@gmail.com> <20170514174005.GY2042@funkthat.com> <8726d7e3-38ae-76a7-7489-2d46f26cc1a3@gmail.com> <20170515155043.GA2042@funkthat.com> From: Rajil Saraswat Date: Mon, 15 May 2017 12:53:28 -0500 Message-ID: Subject: Re: PCIE card with USB ports To: John-Mark Gurney Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 15 May 2017 17:53:30 -0000 On May 15, 2017 10:50 AM, "John-Mark Gurney" wrote: Rajil Saraswat wrote this message on Sun, May 14, 2017 at 16:03 -0500: > On 05/14/2017 12:40 PM, John-Mark Gurney wrote: > > Rajil Saraswat wrote this message on Sat, May 13, 2017 at 20:34 -0500: > >> I am looking for a recommendation for an out-of-the-box working PCIE > >> card with USB controller. > > They all should just work. The driver interface is standardized and > > should just work no mater what card you pick. > > > I came across the following post wherein there was some issue with a > card. Is that no longer the problem in FreeBSD-11? > > https://lists.freebsd.org/pipermail/freebsd-virtualization/2015-February/ 003371.html Yes, it has been fixed/addressed and was committed before 11: https://svnweb.freebsd.org/base/head/usr.sbin/bhyve/pci_ passthru.c?revision=297932&view=markup -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." Good to know! From owner-freebsd-virtualization@freebsd.org Mon May 15 20:15:25 2017 Return-Path: Delivered-To: freebsd-virtualization@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 A9759D6EC0B for ; Mon, 15 May 2017 20:15:25 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E12E1FC5 for ; Mon, 15 May 2017 20:15:25 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v4FKFOe7054597; Mon, 15 May 2017 13:15:24 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v4FKFOFW054596; Mon, 15 May 2017 13:15:24 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201705152015.v4FKFOFW054596@pdx.rh.CN85.dnsmgr.net> Subject: Re: PCIE card with USB ports In-Reply-To: <20170515155043.GA2042@funkthat.com> To: John-Mark Gurney Date: Mon, 15 May 2017 13:15:24 -0700 (PDT) CC: Rajil Saraswat , 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-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 15 May 2017 20:15:25 -0000 > Rajil Saraswat wrote this message on Sun, May 14, 2017 at 16:03 -0500: > > On 05/14/2017 12:40 PM, John-Mark Gurney wrote: > > > Rajil Saraswat wrote this message on Sat, May 13, 2017 at 20:34 -0500: > > >> I am looking for a recommendation for an out-of-the-box working PCIE > > >> card with USB controller. > > > They all should just work. The driver interface is standardized and > > > should just work no mater what card you pick. > > > > > I came across the following post wherein there was some issue with a > > card. Is that no longer the problem in FreeBSD-11? > > > > https://lists.freebsd.org/pipermail/freebsd-virtualization/2015-February/003371.html > > Yes, it has been fixed/addressed and was committed before 11: > https://svnweb.freebsd.org/base/head/usr.sbin/bhyve/pci_passthru.c?revision=297932&view=markup One still must be very carefull about picking cards for pci passthru usage, it has far tighter restrictions than "cards that just work with FreeBSD". The card must have BAR's that are page aligned, and iirc of integral multiple of page in size. Many cards fail this restriction. When I was doing the AMD/IOmmu code testing for Anish about 50% of the cards I grabed to test with failed because of these contrataints. These cards worked fine with FreeBSD using them native. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Tue May 16 21:23:52 2017 Return-Path: Delivered-To: freebsd-virtualization@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 22A34D70EB7; Tue, 16 May 2017 21:23:52 +0000 (UTC) (envelope-from avv314@gmail.com) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (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 D1F4516B6; Tue, 16 May 2017 21:23:51 +0000 (UTC) (envelope-from avv314@gmail.com) Received: by mail-yw0-x231.google.com with SMTP id b68so59427696ywe.3; Tue, 16 May 2017 14:23:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=4q/cw3bDKIbWzwT3ItU20Dmmin/7ZzxXZqUwl2lExHM=; b=g7HtTpGvS/lPBpkgQbDsM6QizxpCQBI97kZ3LFbG1quBtKhWFp8au0mKYBiJmJN/UY S4BEPbwHBI/FcFDWLkWO8jbLbni2LgkltFweEI6/vnoQdzGFw55rQjdJ4jWmt0FYmlOO c5Q7Nph1XYEcffVsKWnHVkKDv55r+n0I/83J54QFq4EVX3ZGY2Kq9Xl6PDRk6oDcceI7 EERpH27aWpekfWZpINaBaDlIqDx3XlIFJPArySHyQbCYybjH/DisoO07QPkLqnrebJQK 3J1SFTETpJNKl6S7e8wYK3q44jAU4zNkVu7BsZCkiY6j4Wb3xIV9c5p+nHYfxYm3Mlut vkkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=4q/cw3bDKIbWzwT3ItU20Dmmin/7ZzxXZqUwl2lExHM=; b=acB26KSW08163Ox0lAc7bcEXecdBNnfU+HITpGbq5h23YsDPsEd2yGk58L+MdK3xBX kUJO+ZZ+CBNO/iBE4CvoW3/7y7be3bRSg8NUKciZmY3anygrY0KbhcUelxUxAr2WxwET isiTO6IgpOIYVKtlUSu5HjGkhueBiHyrem6dlQKogs+ZaDksLrQxd2Ai/DyXrRHHClMf pLwOBFPCtn3n/8dmfsRUIjm0ug+/UjA41QQXepnI32KtlQkrTLBJ9IgNrpWo06UVbUHH GBQ7j3afYQmEH2omQmCaTOxMU8MoDByHyz3bMqfBOSEmpnmIsVBotSLPor43w95kV2E3 chgg== X-Gm-Message-State: AODbwcDYC3LVtfJkbQDevAgJ9lWFdymN0piSsdCzqpSg+wdNjsbGPEez WmLpxC3GM+Ebnb0mHwNYUEIy/wShNw3g X-Received: by 10.13.235.86 with SMTP id u83mr28253ywe.226.1494969830573; Tue, 16 May 2017 14:23:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.253.133 with HTTP; Tue, 16 May 2017 14:23:50 -0700 (PDT) From: Andrew Vylegzhanin Date: Wed, 17 May 2017 00:23:50 +0300 Message-ID: Subject: vmx bug? To: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 16 May 2017 21:23:52 -0000 Hi! Recently I found a bug with numbering four (and probably more) vmxnet3 interfaces under ESXi 6.5 (FreeBSD 11.0-RELASE, 10.0-RELEASE and ESXi 5.5U1 reproduced). It seems that this is an old bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406 : ====> Just reproduced this bug on ESXi 6.5 with FreeBSD 11.0-RELEASE-p9 with four vmxnet3 interfaces Obviously problem goes from wrong FreeBSD vmx interface numbering in compare to VM ethernet interface order. In my case mapping was follows: ethernet0 -> vmx1 ethernet1 -> vmx2 ethernet2 -> vmx3 ethernet3 -> vmx0 I think something goes wrong on PCI probing/mapping stage. I've tried (not all options) to change pci bus numbers for ethernet interfaces in vmx config but without success. ====> Is any chance to fix it? If I fix it by taking into account vmx renumbering, VM migration will problem in future, if this is pci probe issue. WBR, -- Andrew From owner-freebsd-virtualization@freebsd.org Wed May 17 00:49:40 2017 Return-Path: Delivered-To: freebsd-virtualization@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 2D5D9D702EF for ; Wed, 17 May 2017 00:49:40 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (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 E490D10D3 for ; Wed, 17 May 2017 00:49:39 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-oi0-x234.google.com with SMTP id h4so46297848oib.3 for ; Tue, 16 May 2017 17:49:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=RYZHvseIt4n2+3WQI9xRvKoVu1SK0Mgx8K6RaxSubdU=; b=g8Sc5/351rZlUark0e4DjPMmNN97w60xPNl2eYuukY8KdZTbrm/8wzFZvlRXDomRl/ yQ8KsLcYIeYNie/KFUVXb6nVEWDam8lu3bLAZHTE0pOwyiirqbo4OrYUA2KM3hiqFrAm V+vLjmTnr5FU3hpZCWZrFHVbw79sx/of0DASEdMc/M5lzH4aOEoaSv2kH+b6sp4K4ZAn P2rXlIDDGUgNhH9x63CxBHWIe+fspzpGdgYeGOwLKjXzuuFwuPUsYX3HuXZ9DRAw6hvp OlXAzIyGcmOp5pAEwo6//8LVmPBihEcpHloGnCADRlc6k23nan7OlGszcbIpEXs9clG9 aTOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=RYZHvseIt4n2+3WQI9xRvKoVu1SK0Mgx8K6RaxSubdU=; b=pht8e2GEZRWpSLMW1aTT/FtAabM/T7PS+T1qAaVBqM2wnhyni+4Jj1JRn4niBzsPdH QYvttb3Zm3wW5u3y3fGTOvJff8iB9N3lT/MNIdKWlZ34R70OyEJKI9zWNiksIgp0T4UH ah1KnEq8ETyO7C9LuoZ2Vk3H3WHW1MCLC30+yAW6BOJeoPSxd26IUpD5YZZx+rS0r/mW X+MFKSEZLtGPyArEVLAWQ58REnNdkmQsQhMaou/ZOhw4HErMEP+3Pmo3J6HbZpd2LcRb oNjCC+dWM2YEAJPaVRcryeOYkZ1jTFo/4T7n/UhkA5TLACwf4L1D4EL5vmpIlMpuQqJO KAkQ== X-Gm-Message-State: AODbwcDGVtoLWhDqAlGqTSTB4aNjz2Xam8OyXpFFE7Gx/IhegpYOTMDJ ELwUy3x11WmaJs0NltQ= X-Received: by 10.202.6.196 with SMTP id 187mr454918oig.58.1494982179129; Tue, 16 May 2017 17:49:39 -0700 (PDT) Received: from ?IPv6:2601:2c2:200:24bb:80e5:eed3:7a84:e697? ([2601:2c2:200:24bb:80e5:eed3:7a84:e697]) by smtp.gmail.com with ESMTPSA id w197sm253865oie.8.2017.05.16.17.49.38 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 May 2017 17:49:38 -0700 (PDT) Subject: Re: PCIE card with USB ports To: freebsd-virtualization@freebsd.org References: <201705152015.v4FKFOFW054596@pdx.rh.CN85.dnsmgr.net> From: Rajil Saraswat Message-ID: <8ef4d8db-3268-d12c-ef0c-b39ad1e4efbf@gmail.com> Date: Tue, 16 May 2017 19:49:37 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <201705152015.v4FKFOFW054596@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 17 May 2017 00:49:40 -0000 On 05/15/2017 03:15 PM, Rodney W. Grimes wrote: >> Rajil Saraswat wrote this message on Sun, May 14, 2017 at 16:03 -0500: >>> On 05/14/2017 12:40 PM, John-Mark Gurney wrote: >>>> Rajil Saraswat wrote this message on Sat, May 13, 2017 at 20:34 -0500: >>>>> I am looking for a recommendation for an out-of-the-box working PCIE >>>>> card with USB controller. >>>> They all should just work. The driver interface is standardized and >>>> should just work no mater what card you pick. >>>> >>> I came across the following post wherein there was some issue with a >>> card. Is that no longer the problem in FreeBSD-11? >>> >>> https://lists.freebsd.org/pipermail/freebsd-virtualization/2015-February/003371.html >> Yes, it has been fixed/addressed and was committed before 11: >> https://svnweb.freebsd.org/base/head/usr.sbin/bhyve/pci_passthru.c?revision=297932&view=markup > One still must be very carefull about picking cards for pci passthru usage, > it has far tighter restrictions than "cards that just work with FreeBSD". > The card must have BAR's that are page aligned, and iirc of integral > multiple of page in size. > > Many cards fail this restriction. When I was doing the AMD/IOmmu > code testing for Anish about 50% of the cards I grabed to test with > failed because of these contrataints. These cards worked fine with > FreeBSD using them native. > > I tried this Mailiya card (https://www.amazon.com/gp/product/B01G86538S) based on Renesas uPD720201 chipset and it worked fine. From owner-freebsd-virtualization@freebsd.org Wed May 17 20:05:02 2017 Return-Path: Delivered-To: freebsd-virtualization@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 345FBD7103E; Wed, 17 May 2017 20:05:02 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (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 F34311321; Wed, 17 May 2017 20:05:01 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-it0-x22d.google.com with SMTP id c15so88236196ith.0; Wed, 17 May 2017 13:05:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BpeFOn1CJ27S7Exzac76PYP/RskP0guPganmHYAQkR0=; b=AcahmKrqvTPo0VE3HM2qkPbWaUMxsCcVTEbNplJKopYLI3/feAqR5rwT1uNIWISbIl EcFaCafdrOlJ8+fzLSezqdFSj9TD1fWMqSKY9sBkhrP9vXhA7qa1uAqmXg/T2ml0CDRi bjhX1vRlEsoyMLZksspMOArIpAFkTf7h+WqwSmXxFDM9nqH+9U1xokxeZs28pQ0Lm1PJ sPhuS80mK6RrLd8xpcsQL9S6M/0D5w0mK9OQ/Fh0pYIZe7sUMOMAqbxbMy1EncMkFIHZ m8EEf/2n8GmiSIJxDB6aYJayKEV8Ey6Nj5zJ+JfzOn7G3tWXtfT1ybFU024zqMsxPKwd 70mQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BpeFOn1CJ27S7Exzac76PYP/RskP0guPganmHYAQkR0=; b=bDmLqj0/TwAt+5NWPglQc8mJIZ/8osiQx7ZVgJFBUhzJZRKuPGPvifYzBubdhC9Gn+ xsV5I/p6GMXJoyQ4SCLdBz3bT9bnmb1a2uInMmJK0XtY2o348T7p7RnlQ2klGb/V/R8a RfnHynGm2d+TeFm3WQujMtwtoVv8Pn8m9wyOeidbtUVgMQHozzmg/Ll9rzrKV2IBDGeI Q2qzsTIh10Y6WL27kU0VzJjtUNPpgDB7VEjVK0gt4A7X5H/FYurouDk6z0W+aI+FlpVJ x49jxu2vqzF3t/cwZ8LfPpjv+kui5Dz/iPpPeRTf1NdYmVw7lcqXwLSIdad4PqQZNqwV zNLg== X-Gm-Message-State: AODbwcC3E5uMHZaZaYTQsffvj7j/UGHWjDFb4tDuiHQg7vjdmE8FThYg W5F+9UUKBvNCkkmv2eC4RogEbqglTg== X-Received: by 10.36.98.21 with SMTP id d21mr649858itc.78.1495051501161; Wed, 17 May 2017 13:05:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.32.211 with HTTP; Wed, 17 May 2017 13:05:00 -0700 (PDT) In-Reply-To: References: From: Ryan Stone Date: Wed, 17 May 2017 16:05:00 -0400 Message-ID: Subject: Re: vmx bug? To: Andrew Vylegzhanin Cc: freebsd-net , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 17 May 2017 20:05:02 -0000 The bug that you refer to does not appear to be related to your issue. What does "pciconf -l" print in your FreeBSD VM? From owner-freebsd-virtualization@freebsd.org Wed May 17 23:32:42 2017 Return-Path: Delivered-To: freebsd-virtualization@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 46C8ED7115E; Wed, 17 May 2017 23:32:42 +0000 (UTC) (envelope-from avv314@gmail.com) Received: from mail-yb0-x233.google.com (mail-yb0-x233.google.com [IPv6:2607:f8b0:4002:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE7D61A8E; Wed, 17 May 2017 23:32:41 +0000 (UTC) (envelope-from avv314@gmail.com) Received: by mail-yb0-x233.google.com with SMTP id p143so6812457yba.2; Wed, 17 May 2017 16:32:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CnO/4wm1KmJhJ4xe0yqzBtZFXArI7MMnJQv8rprNYIE=; b=HDB1orujZq8L5Jx/PBZDOoCR7KXyG9qjyGvedVb899w1QaNrs3OUgRix//kuQmF6e4 rUrUHIx570prrg2xTbqVXmRfGVaPdWcz8+zNHOhUKbk/bmoDspyJc0rgFFPdT4SjbT0M pDd+I0Y0CAKBwHhHwbBWkNWKXqajl2WE+vP/ki+inPoWOT+YgKYXD3KrqIXT+MkAjMGo IN2g5SNTnTImD8Gc0VcjNDpErap+RJYya2yQKn6MPZZoSv4qrJF2vrFUAEI4MlwTEfKG K67MBcFAn2TM3MhFuyox3AJfHZgvgw8dOVuCbS7+8AcxQ+lR9eXc+WH1PdKq+CGDbS0K tbMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CnO/4wm1KmJhJ4xe0yqzBtZFXArI7MMnJQv8rprNYIE=; b=Hquangk1WPesrlx3FBLaJYoRpU2ax90RH1T6TQQidoojB0YysWwHTGEJ+8Jo2DCIbn au6r3m05W8braztZ1Sjgp7ATVAJ/Haclmd8U8MUAMUgOAWEBjeupV08sA6/m2+d9KfKc RgVxpT/Zc+96dFcjQsr3r8YHAMzHLeGl2pR/80FEFRa58t5j2llTkErZ3D+NYfObY71s kT9i9ViIDjNSDs+9HqVNcqJzU0dBa1nh3+b0dG2zD3oOs7oo1ukuAW7WT8JnAesfDkLA 2KAEdwQEt4d/Iw2ZFYlRq1mNMHcA3q4UdG0YfmyLyc64cnzPeK9eXARczfU7vJ3QlLWo pN3g== X-Gm-Message-State: AODbwcDx1LKBQ7JhFIHO0JeunQo8qwL3YFADsAMly4JUV3uxiGycE5sf f6/D5uPpYhCcMw+NGNI729qfDFVW5pBW X-Received: by 10.37.77.138 with SMTP id a132mr1080183ybb.170.1495063960224; Wed, 17 May 2017 16:32:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.253.133 with HTTP; Wed, 17 May 2017 16:32:39 -0700 (PDT) In-Reply-To: References: From: Andrew Vylegzhanin Date: Thu, 18 May 2017 02:32:39 +0300 Message-ID: Subject: Re: vmx bug? To: Ryan Stone Cc: freebsd-net , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 17 May 2017 23:32:42 -0000 Ok, but probably interface renumbering was not checked in those bug. Here is similar topic https://forum.pfsense.org/index.php?topic=95621.0 Here is pciconf: [root@freebsd11-template ~]# pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x197615ad chip=0x71908086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '440BX/ZX/DX - 82443BX/ZX/DX Host bridge' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x00000000 chip=0x71918086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '440BX/ZX/DX - 82443BX/ZX/DX AGP bridge' class = bridge subclass = PCI-PCI isab0@pci0:0:7:0: class=0x060100 card=0x197615ad chip=0x71108086 rev=0x08 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB/EB/MB PIIX4 ISA' class = bridge subclass = PCI-ISA atapci0@pci0:0:7:1: class=0x01018a card=0x197615ad chip=0x71118086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB/EB/MB PIIX4 IDE' class = mass storage subclass = ATA none0@pci0:0:7:3: class=0x068000 card=0x197615ad chip=0x71138086 rev=0x08 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB/EB/MB PIIX4 ACPI' class = bridge none1@pci0:0:7:7: class=0x088000 card=0x074015ad chip=0x074015ad rev=0x10 hdr=0x00 vendor = 'VMware' device = 'Virtual Machine Communication Interface' class = base peripheral vgapci0@pci0:0:15:0: class=0x030000 card=0x040515ad chip=0x040515ad rev=0x00 hdr=0x00 vendor = 'VMware' device = 'SVGA II Adapter' class = display subclass = VGA pcib2@pci0:0:17:0: class=0x060401 card=0x079015ad chip=0x079015ad rev=0x02 hdr=0x01 vendor = 'VMware' device = 'PCI bridge' class = bridge subclass = PCI-PCI pcib3@pci0:0:21:0: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib4@pci0:0:21:1: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib5@pci0:0:21:2: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib6@pci0:0:21:3: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib7@pci0:0:21:4: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib8@pci0:0:21:5: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib9@pci0:0:21:6: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib10@pci0:0:21:7: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib11@pci0:0:22:0: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib12@pci0:0:22:1: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib13@pci0:0:22:2: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib14@pci0:0:22:3: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib15@pci0:0:22:4: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib16@pci0:0:22:5: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib17@pci0:0:22:6: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib18@pci0:0:22:7: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib19@pci0:0:23:0: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib20@pci0:0:23:1: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib21@pci0:0:23:2: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib22@pci0:0:23:3: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib23@pci0:0:23:4: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib24@pci0:0:23:5: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib25@pci0:0:23:6: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib26@pci0:0:23:7: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib27@pci0:0:24:0: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib28@pci0:0:24:1: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib29@pci0:0:24:2: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib30@pci0:0:24:3: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib31@pci0:0:24:4: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib32@pci0:0:24:5: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib33@pci0:0:24:6: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI pcib34@pci0:0:24:7: class=0x060400 card=0x07a015ad chip=0x07a015ad rev=0x01 hdr=0x01 vendor = 'VMware' device = 'PCI Express Root Port' class = bridge subclass = PCI-PCI mpt0@pci0:3:0:0: class=0x010700 card=0x197615ad chip=0x00541000 rev=0x01 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SAS vmx0@pci0:4:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 hdr=0x00 vendor = 'VMware' device = 'VMXNET3 Ethernet Controller' class = network subclass = ethernet vmx1@pci0:11:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 hdr=0x00 vendor = 'VMware' device = 'VMXNET3 Ethernet Controller' class = network subclass = ethernet vmx2@pci0:19:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 hdr=0x00 vendor = 'VMware' device = 'VMXNET3 Ethernet Controller' class = network subclass = ethernet vmx3@pci0:27:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 hdr=0x00 vendor = 'VMware' device = 'VMXNET3 Ethernet Controller' class = network subclass = ethernet 2017-05-17 23:05 GMT+03:00 Ryan Stone : > > The bug that you refer to does not appear to be related to your issue. > > What does "pciconf -l" print in your FreeBSD VM? From owner-freebsd-virtualization@freebsd.org Thu May 18 01:33:22 2017 Return-Path: Delivered-To: freebsd-virtualization@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 E0452D708A6 for ; Thu, 18 May 2017 01:33:22 +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 CFEC21154 for ; Thu, 18 May 2017 01:33:22 +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 v4I1XKkX000255 for ; Thu, 18 May 2017 01:33:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 209385] [hyperv] negative group permissions Date: Thu, 18 May 2017 01:33:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.23 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: Thu, 18 May 2017 01:33:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209385 --- Comment #3 from commit-hook@freebsd.org --- A commit references this bug: Author: sephe Date: Thu May 18 01:32:51 UTC 2017 New revision: 318433 URL: https://svnweb.freebsd.org/changeset/base/318433 Log: MFC 317783 hyperv/kvp: Fix pool direcrory and file permission PR: 209385 Sponsored by: Microsoft Changes: _U stable/11/ stable/11/contrib/hyperv/tools/hv_kvp_daemon.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu May 18 01:43:32 2017 Return-Path: Delivered-To: freebsd-virtualization@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 2BEADD713D5 for ; Thu, 18 May 2017 01:43:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1B70C1B34 for ; Thu, 18 May 2017 01:43:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4I1hVgC024354 for ; Thu, 18 May 2017 01:43:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 209385] [hyperv] negative group permissions Date: Thu, 18 May 2017 01:43:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.23 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: Thu, 18 May 2017 01:43:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209385 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: sephe Date: Thu May 18 01:42:55 UTC 2017 New revision: 318435 URL: https://svnweb.freebsd.org/changeset/base/318435 Log: MFC 317783 hyperv/kvp: Fix pool direcrory and file permission PR: 209385 Sponsored by: Microsoft Changes: _U stable/10/ stable/10/contrib/hyperv/tools/hv_kvp_daemon.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu May 18 03:52:04 2017 Return-Path: Delivered-To: freebsd-virtualization@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 8254FD71D9F; Thu, 18 May 2017 03:52:04 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 450C91704; Thu, 18 May 2017 03:52:04 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id f102so21252258ioi.2; Wed, 17 May 2017 20:52:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=I7Egl3CQY5sYPgpLaJx55DaRRrFvoDQsHXkSxMFWq6Y=; b=t6BLmss802SJjExVZGGjIwSBJJ+aiLcUFrzZPCD3ZmbXxpwi/CNMxc0FTxvJoq1BVy 3Q5eVXmOG9qdOR739GGMkKLacc3UQfbVvt1TEawbcWbuO32NDdQsp09G/4TaXA28xJLA t2JQcMJrQzRubKWDdgNX0v0fZrMYkkoX/shMhhUCAXf39Y1eJ5DzQYpKFN2mTxIisz9h BpCc2CQLyVRIn0UOjCoCP7jGDgmi5g6eCgvgw81lehWvI/k3A/AcBFDT99I1kQDLTfz9 HsjlR0g/eefR/MeWI256/8wfquoCgeKehtlxVBjMJ2eJ/LyJ2PW0ZmzViPo5xZukt+kA BnRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=I7Egl3CQY5sYPgpLaJx55DaRRrFvoDQsHXkSxMFWq6Y=; b=jGgj+DDK3bZAsYMzPe00hIi4ocUySCFTg30aqabGTraEwNalNxv2nJJnFOVG6NlVuz TXriJAV57ZZ0g7uQPNlYRG4m97oUyJaXaQ3VQj4NViiJrDRFieRqky1OW86WwpFaI/3e RIGb/ahUI066rjfQVCDvEmKE5+p9Hp3cCAHNl/fl2HxosJgekXFxyc4b1BU/EGjZQwu6 IMSfACRMWxusT4WQ0wfnhHIIxt4dPkfwI1TamlEBrb9eXIN51lMi8kmt5MX4k6bz8MYv 0N6406adAqlV7sjafC7185CQN4gKLjsxi1Kuw6Qs+PgYHd4Y+lvofL5LIobxYgFZGLWe UEJw== X-Gm-Message-State: AODbwcBQtdVRISi2V3aYPmvZQlpSDIzNGtQB8wVKqJ60C635UnacEe/4 8Mt+tEaX5Jt9zDmYmsugMkKrb5IFzQ== X-Received: by 10.107.51.195 with SMTP id z186mr2427876ioz.126.1495079523548; Wed, 17 May 2017 20:52:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.32.211 with HTTP; Wed, 17 May 2017 20:52:03 -0700 (PDT) In-Reply-To: References: From: Ryan Stone Date: Wed, 17 May 2017 23:52:03 -0400 Message-ID: Subject: Re: vmx bug? To: Andrew Vylegzhanin Cc: freebsd-net , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 18 May 2017 03:52:04 -0000 On Wed, May 17, 2017 at 7:32 PM, Andrew Vylegzhanin wrote: > > vmx0@pci0:4:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 > hdr=0x00 > > vendor = 'VMware' > > device = 'VMXNET3 Ethernet Controller' > > class = network > > subclass = ethernet > > vmx1@pci0:11:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 > hdr=0x00 > > vendor = 'VMware' > > device = 'VMXNET3 Ethernet Controller' > > class = network > > subclass = ethernet > > vmx2@pci0:19:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 > hdr=0x00 > > vendor = 'VMware' > > device = 'VMXNET3 Ethernet Controller' > > class = network > > subclass = ethernet > > vmx3@pci0:27:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 > hdr=0x00 > > vendor = 'VMware' > > device = 'VMXNET3 Ethernet Controller' > > class = network > > subclass = ethernet > Everything appears to be enumerated in the proper order. Do other OSes, say Linux, somehow enumerate in a different order? From owner-freebsd-virtualization@freebsd.org Thu May 18 05:00:17 2017 Return-Path: Delivered-To: freebsd-virtualization@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 3C726D72B6C for ; Thu, 18 May 2017 05:00:17 +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 25F2619AF for ; Thu, 18 May 2017 05:00:17 +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 v4I50GCl096478 for ; Thu, 18 May 2017 05:00:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219355] Heavy disk activity in bhyve deadlocks host Date: Thu, 18 May 2017 05:00:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd-bugs@joe.mulloy.me X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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.23 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: Thu, 18 May 2017 05:00:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219355 Joseph Mulloy changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Thu May 18 05:39:25 2017 Return-Path: Delivered-To: freebsd-virtualization@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 EDE89D7277B; Thu, 18 May 2017 05:39:25 +0000 (UTC) (envelope-from avv314@gmail.com) Received: from mail-yb0-x22e.google.com (mail-yb0-x22e.google.com [IPv6:2607:f8b0:4002:c09::22e]) (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 AB7D41BD9; Thu, 18 May 2017 05:39:25 +0000 (UTC) (envelope-from avv314@gmail.com) Received: by mail-yb0-x22e.google.com with SMTP id 187so1737671ybg.0; Wed, 17 May 2017 22:39:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=miKpgBcl5+YiJHOPK5YxOLkGFvP/0v+o9Z9CuFX/FeQ=; b=epLgYfkn/vKna9VBr17kd/pUjlqDVLeTS8osvztQyihPxr4FfQQbB0P/e7JBZJMnkT ONa5o16kntwSnG6Q+9Vwm1aslTVgsa88Q411/Wvm6rezzKuQ3crvxaVwl4DYaXsSFHzl O6Q+G7OW8KHb7jF7h2qpW8S3dhKzgiuHTuTubnnSpH441bYzgWpE9EJFBm1xPjZZzZlQ 2Ht+HxTtOsEvigA7jtpCpI5kwjETfcJ9I1Si68s6EIjfPGVKMe03J2TFvrCIIbR+rigO /gSrh8A46DCjziWIk406l1hjPFStAlmc7NJCiVVv7yw+khQXEFUskYTYfET4Hy+UgLpn DHjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=miKpgBcl5+YiJHOPK5YxOLkGFvP/0v+o9Z9CuFX/FeQ=; b=TMhQHCh2+8Jwq1bI4OeFB2/4khdkQPuTDFXbc4y+C0dAy8XPyErE9m8ys4DZ094r/J YppisUTx/wf99V6f+EiSwFQ5LBR+8k4756WNtkLeEStlHGdaEcgkRS/dZbP1GffP9mv6 bBdD+1DvkOSkvy3+XAJLiJJPmkMGC7WFSlWBC7DoryxuJuGqu29sjwAgsbdzzkTjdCJT yYdy40TLoW4xIZ+4ugB9+sbiclWebmWUISnCBMfSfwq392jucXYKzBhW+cKz9P+yGAcO p90uVt2o596yg/9Xzfe8D8aW7VzsnmVZPZpLY2lO4giY3L7scNvh+l/+ovrb1ahqibZv Do0g== X-Gm-Message-State: AODbwcBalT9vDxQM0ttFsFIAwfP7LF8KXU7iKnGUaYfJGSiI5NPDVjzW hh8+tmhQ16gHt3JcjsKohCfcSFKd+w== X-Received: by 10.37.58.131 with SMTP id h125mr1968484yba.152.1495085964812; Wed, 17 May 2017 22:39:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.253.133 with HTTP; Wed, 17 May 2017 22:39:24 -0700 (PDT) In-Reply-To: References: From: Andrew Vylegzhanin Date: Thu, 18 May 2017 08:39:24 +0300 Message-ID: Subject: Re: vmx bug? To: Ryan Stone Cc: freebsd-net , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 18 May 2017 05:39:26 -0000 I will test this VM with Linux tomorrow. Just for information, here is part of .vmx file with pci related conifg: pciBridge0.present = "TRUE" pciBridge4.present = "TRUE" pciBridge4.virtualDev = "pcieRootPort" pciBridge4.functions = "8" pciBridge5.present = "TRUE" pciBridge5.virtualDev = "pcieRootPort" pciBridge5.functions = "8" pciBridge6.present = "TRUE" pciBridge6.virtualDev = "pcieRootPort" pciBridge6.functions = "8" pciBridge7.present = "TRUE" pciBridge7.virtualDev = "pcieRootPort" pciBridge7.functions = "8" pciBridge0.pciSlotNumber = "17" pciBridge4.pciSlotNumber = "21" pciBridge5.pciSlotNumber = "22" pciBridge6.pciSlotNumber = "23" pciBridge7.pciSlotNumber = "24" vmci0.pciSlotNumber = "33" ethernet0.pciSlotNumber = "192" ethernet1.pciSlotNumber = "224" ethernet2.pciSlotNumber = "256" ethernet3.pciSlotNumber = "1184" <== vmx0 !!! 2017-05-18 6:52 GMT+03:00 Ryan Stone : > > On Wed, May 17, 2017 at 7:32 PM, Andrew Vylegzhanin wrote: >> >> >> vmx0@pci0:4:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 hdr=0x00 >> >> vendor = 'VMware' >> >> device = 'VMXNET3 Ethernet Controller' >> >> class = network >> >> subclass = ethernet >> >> vmx1@pci0:11:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 hdr=0x00 >> >> vendor = 'VMware' >> >> device = 'VMXNET3 Ethernet Controller' >> >> class = network >> >> subclass = ethernet >> >> vmx2@pci0:19:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 hdr=0x00 >> >> vendor = 'VMware' >> >> device = 'VMXNET3 Ethernet Controller' >> >> class = network >> >> subclass = ethernet >> >> vmx3@pci0:27:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 hdr=0x00 >> >> vendor = 'VMware' >> >> device = 'VMXNET3 Ethernet Controller' >> >> class = network >> >> subclass = ethernet > > > Everything appears to be enumerated in the proper order. Do other OSes, say Linux, somehow enumerate in a different order? From owner-freebsd-virtualization@freebsd.org Thu May 18 08:17:52 2017 Return-Path: Delivered-To: freebsd-virtualization@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 ECF11D71032 for ; Thu, 18 May 2017 08:17:52 +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 DCA3612EE for ; Thu, 18 May 2017 08:17:52 +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 v4I8Hplw003856 for ; Thu, 18 May 2017 08:17:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219355] Heavy disk activity in bhyve deadlocks host Date: Thu, 18 May 2017 08:17:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fk@fabiankeil.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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.23 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: Thu, 18 May 2017 08:17:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219355 Fabian Keil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fk@fabiankeil.de --- Comment #1 from Fabian Keil --- Are you using geli for the swap device as well? This is known to cause deadlocks under memory pressure (which your top outp= ut indicates): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209759 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Thu May 18 09:38:49 2017 Return-Path: Delivered-To: freebsd-virtualization@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 49DBFD72886; Thu, 18 May 2017 09:38:49 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D2DFD1141; Thu, 18 May 2017 09:38:48 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v4I9ckUg065377; Thu, 18 May 2017 02:38:46 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v4I9ckIb065376; Thu, 18 May 2017 02:38:46 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201705180938.v4I9ckIb065376@pdx.rh.CN85.dnsmgr.net> Subject: Re: vmx bug? In-Reply-To: To: Andrew Vylegzhanin Date: Thu, 18 May 2017 02:38:46 -0700 (PDT) CC: Ryan Stone , freebsd-net , 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-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 18 May 2017 09:38:49 -0000 This is a long standing issue with VMware ESXi, it effects Linux as well as FreeBSD and Windows. A couple of googles for things like https://www.google.com/search?q=esxi+guest+ethernet++order&ie=utf-8&oe=utf-8 Well lead you to several articles talking about this issue. I did not find any solutions however. > I will test this VM with Linux tomorrow. > > Just for information, here is part of .vmx file with pci related conifg: > > pciBridge0.present = "TRUE" > > pciBridge4.present = "TRUE" > pciBridge4.virtualDev = "pcieRootPort" > pciBridge4.functions = "8" > pciBridge5.present = "TRUE" > pciBridge5.virtualDev = "pcieRootPort" > pciBridge5.functions = "8" > pciBridge6.present = "TRUE" > pciBridge6.virtualDev = "pcieRootPort" > pciBridge6.functions = "8" > pciBridge7.present = "TRUE" > pciBridge7.virtualDev = "pcieRootPort" > pciBridge7.functions = "8" > pciBridge0.pciSlotNumber = "17" > pciBridge4.pciSlotNumber = "21" > pciBridge5.pciSlotNumber = "22" > pciBridge6.pciSlotNumber = "23" > pciBridge7.pciSlotNumber = "24" > vmci0.pciSlotNumber = "33" > ethernet0.pciSlotNumber = "192" > ethernet1.pciSlotNumber = "224" > ethernet2.pciSlotNumber = "256" > ethernet3.pciSlotNumber = "1184" <== vmx0 !!! > > > > 2017-05-18 6:52 GMT+03:00 Ryan Stone : > > > > On Wed, May 17, 2017 at 7:32 PM, Andrew Vylegzhanin > wrote: > >> > >> > >> vmx0@pci0:4:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 > hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > >> > >> vmx1@pci0:11:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad > rev=0x01 hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > >> > >> vmx2@pci0:19:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad > rev=0x01 hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > >> > >> vmx3@pci0:27:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad > rev=0x01 hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > > > > > > Everything appears to be enumerated in the proper order. Do other OSes, > say Linux, somehow enumerate in a different order? > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Thu May 18 12:43:13 2017 Return-Path: Delivered-To: freebsd-virtualization@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 8392AD718B3; Thu, 18 May 2017 12:43:13 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 4F3CCD21; Thu, 18 May 2017 12:43:13 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dBKlr-000D95-9g; Thu, 18 May 2017 13:43:11 +0100 Date: Thu, 18 May 2017 13:43:11 +0100 From: Gary Palmer To: Andrew Vylegzhanin Cc: Ryan Stone , freebsd-net , freebsd-virtualization@freebsd.org Subject: Re: vmx bug? Message-ID: <20170518124311.GB89273@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 18 May 2017 12:43:13 -0000 On Thu, May 18, 2017 at 08:39:24AM +0300, Andrew Vylegzhanin wrote: > I will test this VM with Linux tomorrow. > > Just for information, here is part of .vmx file with pci related conifg: > > pciBridge0.present = "TRUE" > > pciBridge4.present = "TRUE" > pciBridge4.virtualDev = "pcieRootPort" > pciBridge4.functions = "8" > pciBridge5.present = "TRUE" > pciBridge5.virtualDev = "pcieRootPort" > pciBridge5.functions = "8" > pciBridge6.present = "TRUE" > pciBridge6.virtualDev = "pcieRootPort" > pciBridge6.functions = "8" > pciBridge7.present = "TRUE" > pciBridge7.virtualDev = "pcieRootPort" > pciBridge7.functions = "8" > pciBridge0.pciSlotNumber = "17" > pciBridge4.pciSlotNumber = "21" > pciBridge5.pciSlotNumber = "22" > pciBridge6.pciSlotNumber = "23" > pciBridge7.pciSlotNumber = "24" > vmci0.pciSlotNumber = "33" > ethernet0.pciSlotNumber = "192" > ethernet1.pciSlotNumber = "224" > ethernet2.pciSlotNumber = "256" > ethernet3.pciSlotNumber = "1184" <== vmx0 !!! Out of curiosity, if you install sysutils/dmidecode from ports and run dmidecode -t 41 does it help at all? Some PC vendors have taken to doing odd things with their PCI layout which produce unexpected results with device naming (so port 1 on the back of the server is not the first interface in the OS) and introduced DMI type 41 as a "fix" e.g. see https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf Regards, Gary > 2017-05-18 6:52 GMT+03:00 Ryan Stone : > > > > On Wed, May 17, 2017 at 7:32 PM, Andrew Vylegzhanin > wrote: > >> > >> > >> vmx0@pci0:4:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad rev=0x01 > hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > >> > >> vmx1@pci0:11:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad > rev=0x01 hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > >> > >> vmx2@pci0:19:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad > rev=0x01 hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > >> > >> vmx3@pci0:27:0:0: class=0x020000 card=0x07b015ad chip=0x07b015ad > rev=0x01 hdr=0x00 > >> > >> vendor = 'VMware' > >> > >> device = 'VMXNET3 Ethernet Controller' > >> > >> class = network > >> > >> subclass = ethernet > > > > > > Everything appears to be enumerated in the proper order. Do other OSes, > say Linux, somehow enumerate in a different order? > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@freebsd.org Thu May 18 12:52:00 2017 Return-Path: Delivered-To: freebsd-virtualization@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 25158D720A1 for ; Thu, 18 May 2017 12:52:00 +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 14AE11320 for ; Thu, 18 May 2017 12:52:00 +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 v4ICpxNp067121 for ; Thu, 18 May 2017 12:51:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219355] Heavy disk activity in bhyve deadlocks host Date: Thu, 18 May 2017 12:52:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: grehan@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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.23 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: Thu, 18 May 2017 12:52:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219355 Peter Grehan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grehan@FreeBSD.org --- Comment #2 from Peter Grehan --- Not sure if you've limited your ARC cache - you'll really want to do that o= r it will try and force out your bhyve guest. Judging by the amount of swap that= has been allocated, that may have already happened. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Thu May 18 21:23:07 2017 Return-Path: Delivered-To: freebsd-virtualization@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 153DDD6F1CA; Thu, 18 May 2017 21:23:07 +0000 (UTC) (envelope-from avv314@gmail.com) Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 CB26B39E; Thu, 18 May 2017 21:23:06 +0000 (UTC) (envelope-from avv314@gmail.com) Received: by mail-yw0-x22f.google.com with SMTP id l14so27109997ywk.1; Thu, 18 May 2017 14:23:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LOJmERTze14lHXXC1aykfnVLFm7X11tqYOTw2Cct6OQ=; b=pM8NQpth+T1dLm6r6EOfrS9Vyc02CYseXqpGhzTckvMeK5xW5tFr/J0NfuuLVnL/Jz xbk8q+cEYvUIYGEXD0EOPH76Y7zDoBwD4u3m7PfH0Vq73r4NHRFQ2X4UpQW1hSK+3HPV 9UzJhjSu79qjz0qAqWpohbrhAX5SWiEtyAl7tE5knwwmjgMdZsDdf06uREbmtOdnFrGI D+2rFs4ntjS5AYydCm7b2pEK0mobV3qBX4TUDVx6mk93apeFfTySW/1cApQS+4Vkzo9Z Sto3v8vueW3nIZvJyVJWOs+KTmBsazBdkiRf5mw5rSIcimFNPObnl6CfBwmd9d8WdElN SrTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LOJmERTze14lHXXC1aykfnVLFm7X11tqYOTw2Cct6OQ=; b=R6Ae1yZwUQt/BFWsEtINw9CSEMf6B3wmbNADVoexchWRPi0OBOW/xTHxRujmtj3JhN EgA2rwq0Pa0Ig98LXRaQDrUAhk4qgSQ63rGATZjm2K07JIAcQhTrvvwbyfeWOF7h+Jxe q2l70Pz8jlx0DC29fRZ+93prXDddnSmDWFsErLDyiCbSK6f/QrcfF0jATtSxmm5hkj6e nF0aAMwU7d8nB3tkBDPEUFvmi+idSQ243GesJKO6W7qXD1jlukobUFX+Lbxp0KMsPe1k 01+jvuZQmJVHyVdVByDrY6ZTPFAmqE6uJLQbCAbuHYi203FABNmcmSa7ZOW5HlqfodEI XKoA== X-Gm-Message-State: AODbwcBAkRgUrWKmZxcqgWr95jHTBUMR3CYFdFy89g/Z0MZbw1V3u+a0 JxQluzpLT+yIfDQUooqLBeRB42GnpQ== X-Received: by 10.13.235.86 with SMTP id u83mr5412615ywe.226.1495142585930; Thu, 18 May 2017 14:23:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.253.133 with HTTP; Thu, 18 May 2017 14:23:05 -0700 (PDT) In-Reply-To: <20170518124311.GB89273@in-addr.com> References: <20170518124311.GB89273@in-addr.com> From: Andrew Vylegzhanin Date: Fri, 19 May 2017 00:23:05 +0300 Message-ID: Subject: Re: vmx bug? To: Gary Palmer Cc: Ryan Stone , freebsd-net , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 18 May 2017 21:23:07 -0000 2017-05-18 15:43 GMT+03:00 Gary Palmer : > > Out of curiosity, if you install sysutils/dmidecode from ports and > run > > dmidecode -t 41 > > does it help at all? This table is empty on VM: [root@freebsd11-template ~]# dmidecode -t 41 # dmidecode 3.0 Scanning /dev/mem for entry point. SMBIOS 2.4 present. [root@freebsd11-template ~]# > > Some PC vendors have taken to doing odd things with their PCI layout > which produce unexpected results with device naming (so port 1 on the > back of the server is not the first interface in the OS) and introduced > DMI type 41 as a "fix" > > e.g. see https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf > > Regards, > > Gary > > From owner-freebsd-virtualization@freebsd.org Fri May 19 06:26:19 2017 Return-Path: Delivered-To: freebsd-virtualization@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 82777D7468C for ; Fri, 19 May 2017 06:26:19 +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 72155108 for ; Fri, 19 May 2017 06:26:19 +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 v4J6QJuh057126 for ; Fri, 19 May 2017 06:26:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219355] Heavy disk activity in bhyve deadlocks host Date: Fri, 19 May 2017 06:26:19 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd-bugs@joe.mulloy.me X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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.23 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, 19 May 2017 06:26:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219355 --- Comment #3 from Joseph Mulloy --- Swap is geli encrypted and I am not limiting my ARC. I could try limiting t= he ARC, but it doesn't seem like I use much swap before it stalls. I will try limiting the ARC and see if that works. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Fri May 19 08:01:45 2017 Return-Path: Delivered-To: freebsd-virtualization@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 18884D7486E for ; Fri, 19 May 2017 08:01:45 +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 0784A1584 for ; Fri, 19 May 2017 08:01:45 +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 v4J81iMG026905 for ; Fri, 19 May 2017 08:01:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 208931] [patch] [hyperv] [netvsc] hn network driver fails to initialize if_baudrate Date: Fri, 19 May 2017 08:01:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 19 May 2017 08:01:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208931 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |eugen@freebsd.org Status|New |Closed --- Comment #7 from Eugene Grosbein --- Patched and MFC'd long time ago. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri May 19 08:02:51 2017 Return-Path: Delivered-To: freebsd-virtualization@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 431ECD749CE for ; Fri, 19 May 2017 08:02:51 +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 329361680 for ; Fri, 19 May 2017 08:02:51 +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 v4J82nZX033612 for ; Fri, 19 May 2017 08:02:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 209385] [hyperv] negative group permissions Date: Fri, 19 May 2017 08:02:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution 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.23 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, 19 May 2017 08:02:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209385 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed CC| |eugen@freebsd.org Resolution|--- |FIXED --- Comment #5 from Eugene Grosbein --- Patched and MFC'd. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri May 19 14:53:46 2017 Return-Path: Delivered-To: freebsd-virtualization@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 C71E6D7318C for ; Fri, 19 May 2017 14:53:46 +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 B658F377 for ; Fri, 19 May 2017 14:53:46 +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 v4JErkKC013368 for ; Fri, 19 May 2017 14:53:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219355] Heavy disk activity in bhyve deadlocks host Date: Fri, 19 May 2017 14:53:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd-bugs@joe.mulloy.me X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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.23 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, 19 May 2017 14:53:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219355 --- Comment #4 from Joseph Mulloy --- I just tried again with the ARC limited to 12 GB (out of 32 GB) and it still crashes. This time I got a ton of "swap_pager: indefinite wait buffer" mess= ages on the console. From the output of top, which I have pasted below I can see that the ARC was on 5 GB but the wired memory is up to 30GB. The guest has = the -S flag (wire guest memory) on the bhyve command since that is the default = in chyves. I have tried without it before since I suspected a memory problem. I will try again without it. 471 processes: 1 running, 447 sleeping, 23 waiting CPU: 43.8% user, 0.0% nice, 29.5% system, 1.4% interrupt, 25.4% idle Mem: 1106M Active, 317M Inact, 30G Wired, 55M Cache, 18M Free ARC: 5135M Total, 2282K MFU, 40M MRU, 2680M Anon, 1510M Header, 903M Other Swap: 16G Total, 1221M Used, 15G Free, 7% Inuse, 12K In, 141M Out PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMA= ND 3091 88 25 20 0 460M 21832K select 0 0:19 85.90% mysqld 3593 88 143 20 0 604M 195M select 3 2:39 83.29% mysqld 39084 root 21 20 0 2127M 1969M kqread 2 3:12 4.43% bhyve 4256 zabbix 1 20 0 105M 4584K pfault 3 0:16 0.45% zabbix_server 4264 zabbix 1 20 0 105M 3272K sbwait 2 0:16 0.44% zabbix_server 4278 zabbix 1 20 0 105M 8292K nanslp 0 0:16 0.38% zabbix_server 4294 zabbix 1 20 0 105M 4732K nanslp 0 0:16 0.38% zabbix_server 4295 zabbix 1 20 0 105M 8396K sbwait 2 0:15 0.35% zabbix_server 4233 zabbix 1 20 0 102M 6948K nanslp 0 0:03 0.34% zabbix_server 1191 root 1 20 0 26264K 3716K CPU3 3 0:43 0.11% top 1158 jdmulloy2 1 20 0 51156K 5224K select 3 0:09 0.09% mosh-server 1170 root 1 20 0 22420K 3340K select 0 0:22 0.08% tmux 4266 zabbix 1 20 0 105M 4608K sbwait 2 0:15 0.03% zabbix_server 4240 zabbix 1 20 0 105M 2256K pfault 2 0:16 0.02% zabbix_server 2090 root 14 52 0 45048K 9464K uwait 1 0:06 0.02% fileb= eat 4544 root 11 52 0 43672K 9840K uwait 1 0:06 0.02% fileb= eat 3786 root 13 52 0 44984K 10312K uwait 3 0:07 0.02% fileb= eat 4257 zabbix 1 20 0 105M 8360K sbwait 1 0:16 0.01% zabbix_server 1889 root 14 52 0 44056K 10308K uwait 1 0:06 0.01% fileb= eat 1487 root 10 52 0 44600K 9372K uwait 3 0:06 0.01% fileb= eat 4247 zabbix 1 20 0 105M 4868K sbwait 3 0:16 0.01% zabbix_server 2367 root 12 20 0 42676K 8788K tx->tx 2 0:06 0.01% fileb= eat 4329 zabbix 1 20 0 105M 1952K nanslp 2 0:16 0.01% zabbix_server 772 zabbix 1 20 0 31004K 2300K nanslp 0 0:02 0.01% zabbix_agentd 1662 zabbix 1 20 0 31004K 1972K nanslp 2 0:02 0.01% zabbix_agentd 3373 zabbix 1 20 0 31004K 2412K nanslp 0 0:02 0.01% zabbix_agentd 2609 zabbix 1 20 0 31004K 2612K tx->tx 1 0:01 0.01% zabbix_agentd 3405 root 15 52 0 46232K 10464K uwait 1 0:06 0.01% fileb= eat 808 root 1 20 0 10436K 1260K select 0 0:03 0.01% powerd 2605 zabbix 1 20 0 31004K 2520K nanslp 3 0:02 0.01% zabbix_agentd 1461 zabbix 1 20 0 31004K 1984K nanslp 0 0:02 0.01% zabbix_agentd 2635 root 15 52 0 45240K 10552K uwait 1 0:07 0.01% fileb= eat 3984 root 12 20 0 42808K 10000K uwait 0 0:06 0.01% fileb= eat --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Sat May 20 14:39:24 2017 Return-Path: Delivered-To: freebsd-virtualization@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 63A16D759C8 for ; Sat, 20 May 2017 14:39: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 52D251645 for ; Sat, 20 May 2017 14:39: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 v4KEdOSv093863 for ; Sat, 20 May 2017 14:39:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219343] bhyve requires -w option to run FreeBSD guests on AMD A10 CPU Date: Sat, 20 May 2017 14:39:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.23 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: Sat, 20 May 2017 14:39:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219343 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sat May 20 14:39:40 2017 Return-Path: Delivered-To: freebsd-virtualization@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 682C5D75A5F for ; Sat, 20 May 2017 14:39: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 57B5B170C for ; Sat, 20 May 2017 14:39: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 v4KEdd4A094248 for ; Sat, 20 May 2017 14:39:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219355] Heavy disk activity in bhyve deadlocks host Date: Sat, 20 May 2017 14:39:40 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.23 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: Sat, 20 May 2017 14:39:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219355 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Sat May 20 20:51:51 2017 Return-Path: Delivered-To: freebsd-virtualization@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 1B83FD76D3B for ; Sat, 20 May 2017 20:51:51 +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 0AB63128 for ; Sat, 20 May 2017 20:51:51 +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 v4KKpoMQ048294 for ; Sat, 20 May 2017 20:51:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219343] bhyve requires -w option to run FreeBSD guests on AMD A10 CPU Date: Sat, 20 May 2017 20:51:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.23 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: Sat, 20 May 2017 20:51:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219343 Rodney W. Grimes changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rgrimes@FreeBSD.org --- Comment #1 from Rodney W. Grimes --- Thought it is not a final fix, you no longer well need to edit vmrun.sh to use your workaround, -w has been added to as an avaliable option on your vmrun.sh command to pass it to the bhyve command. I do believe some work is under way to fix some of the unimplemented instructions that are causing this issue. --=20 You are receiving this mail because: You are the assignee for the bug.=