From owner-freebsd-virtualization@freebsd.org Mon Feb 12 19:08:40 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2621F13707 for ; Mon, 12 Feb 2018 19:08:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 405EC87DCA for ; Mon, 12 Feb 2018 19:08: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7D5E41D26A for ; Mon, 12 Feb 2018 19:08:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1CJ8dlW097736 for ; Mon, 12 Feb 2018 19:08:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1CJ8d4A097735 for freebsd-virtualization@FreeBSD.org; Mon, 12 Feb 2018 19:08:39 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225558] [bhyve][patch] Add option to specify emulated NIC in vmrun.sh Date: Mon, 12 Feb 2018 19:08:39 +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: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: rgrimes@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.25 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, 12 Feb 2018 19:08:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225558 --- Comment #7 from commit-hook@freebsd.org --- A commit references this bug: Author: rgrimes Date: Mon Feb 12 19:08:17 UTC 2018 New revision: 329179 URL: https://svnweb.freebsd.org/changeset/base/329179 Log: MFC: r328695,r328720,r328784,r328795 share/examples/bhyve/vmrun.sh addit= ions and cleanups r328695: Add option '-n' network device emulation type which has a default of virtio-net PR: 225558 Submitted by: Johannes Lundberg r328720: Add -n to usage synopsis forgotten in r328695. Fix long lines in usage. Consistently use "default:" rather than "default is" r328784: Clean up long lines. r328795: Fold constants and unify vnc variable names. Approved by: grehan (mentor) PR: 225558 Changes: _U stable/11/ stable/11/share/examples/bhyve/vmrun.sh --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Feb 12 19:08:42 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF867F1371D for ; Mon, 12 Feb 2018 19:08:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D67F87DD9 for ; Mon, 12 Feb 2018 19:08:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B0AC11D26E for ; Mon, 12 Feb 2018 19:08:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1CJ8fKm097786 for ; Mon, 12 Feb 2018 19:08:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1CJ8f3D097785 for freebsd-virtualization@FreeBSD.org; Mon, 12 Feb 2018 19:08:41 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225558] [bhyve][patch] Add option to specify emulated NIC in vmrun.sh Date: Mon, 12 Feb 2018 19:08:41 +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: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: rgrimes@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.25 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, 12 Feb 2018 19:08:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225558 --- Comment #8 from commit-hook@freebsd.org --- A commit references this bug: Author: rgrimes Date: Mon Feb 12 19:08:17 UTC 2018 New revision: 329179 URL: https://svnweb.freebsd.org/changeset/base/329179 Log: MFC: r328695,r328720,r328784,r328795 share/examples/bhyve/vmrun.sh addit= ions and cleanups r328695: Add option '-n' network device emulation type which has a default of virtio-net PR: 225558 Submitted by: Johannes Lundberg r328720: Add -n to usage synopsis forgotten in r328695. Fix long lines in usage. Consistently use "default:" rather than "default is" r328784: Clean up long lines. r328795: Fold constants and unify vnc variable names. Approved by: grehan (mentor) PR: 225558 Changes: _U stable/11/ stable/11/share/examples/bhyve/vmrun.sh --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Feb 13 00:22:50 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1E1FF0752B for ; Tue, 13 Feb 2018 00:22:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E4BE76AA4 for ; Tue, 13 Feb 2018 00:22:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 67F9F1FF4A for ; Tue, 13 Feb 2018 00:22:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1D0MnTo066672 for ; Tue, 13 Feb 2018 00:22:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1D0MnX0066671 for freebsd-virtualization@FreeBSD.org; Tue, 13 Feb 2018 00:22:49 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225794] VM images for 12.0-CURRENT have problem with USB 3.0 ports Date: Tue, 13 Feb 2018 00:22:49 +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: regression 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 keywords 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.25 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, 13 Feb 2018 00:22:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225794 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org Keywords| |regression --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Feb 13 00:23:37 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E55FF076D2 for ; Tue, 13 Feb 2018 00:23:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ADBFF76BB4 for ; Tue, 13 Feb 2018 00:23:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id ED3551FF52 for ; Tue, 13 Feb 2018 00:23:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1D0NZOJ067903 for ; Tue, 13 Feb 2018 00:23:35 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1D0NZ9V067902 for freebsd-virtualization@FreeBSD.org; Tue, 13 Feb 2018 00:23:35 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225791] ena driver causing kernel panics on AWS EC2 Date: Tue, 13 Feb 2018 00:23:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE 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.25 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, 13 Feb 2018 00:23:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225791 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 Tue Feb 13 17:09:10 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7CEF9F11E15 for ; Tue, 13 Feb 2018 17:09:10 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 ECA44846F8 for ; Tue, 13 Feb 2018 17:09:09 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id EF25D2159E for ; Tue, 13 Feb 2018 12:09:08 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 13 Feb 2018 12:09:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=rdPGd4Vf7339dFLBpn28JUlU1q7U3CaO6IjRHU26Bss=; b=DL//wA+O vz3Fk0mQjSwJMrdrBGWIhRVRLG7kokTqClwSUzJI3t8jEHwOlW9+BXFBqUMRWS4P NinkHTP1FpWJFRyrs7xHcZMwhHFwEuNTke/edeMfSicq8KlSL+c9ftO2+vIei5uQ s9Ui5WEcd56T/qJqiwTxETVnC6jIQHJMUdxMKaNeCDbFYZTjmp7laIqNmhxW3fWM U3m2nDQLrmAXGCKjQSUg1InBTua71IxsQbhKwS2umnnr5RtejQgu9xRTRcEnpoeI gP/FbNly3wIgpgsZ2l4LYcKB6Uq0YG9sb36iDqp6+pRcSwSviDZ4gI4FfIPZKOLc AtGtfUK4+rvGTg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=rdPGd4Vf7339dFLBpn28JUlU1q7U3 CaO6IjRHU26Bss=; b=RFjP8LKKzdvHn7c8A/8tCKIs+5u4Y7SzYRUTCjcFa+kbf /TcCpMN1rJyHbQWS3lMcDbWZ/ILVAXHu6uKNqUxD7u1DMRu7OhA+4SvEXenGOBt7 X4xkZ0GMfs7vmPKJBaRiDwZLaIY+t4cz9c57PAbLtW6nUh9GbYoJhQxMyNQ6olA6 o2f9664RlEQABv9f+zMy8tITji+EKuGhKTShPU5FC3d0v5FaN4BCejByVIGpr0UH Aa6C6siTf+d15DKG31rXELO1v0SjGOxAUnQYbLgR47pdNtS218Rb7FvOGMfbfgcP Luphe8roR7D4TJTRN2IfNSQ1HjO7W+1V7aPyKZx5w== X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 8792B24610 for ; Tue, 13 Feb 2018 12:09:08 -0500 (EST) To: freebsd-virtualization@freebsd.org From: tech-lists Subject: bhyve and contention Message-ID: <61adce39-e393-f533-3772-6503a72972af@zyxst.net> Date: Tue, 13 Feb 2018 17:09:07 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 13 Feb 2018 17:09:11 -0000 Hello virtualizations, Please can anyone tell me what happens in the following scenarios: 1. freebsd-11 server, 5x freebsd-11 guests The server has 32GB ram installed. it's an i7 so 8 cores. There's 64GB swap. Each guest that bhyve loads is with m 8192M, so ram is overcommitted by 6GB. What happens to the guests and the server? Do either (or both) crash? Or is there something in bhyve that will make memory allocated on a best-effort basis? 2. In the following context, the server is the same but this time all five guests have -c 4 per guest, so bhyve is asking 12 more cores than that existing in hardware. Does the guest fail to load, do either guest or server crash? thanks, -- J. From owner-freebsd-virtualization@freebsd.org Tue Feb 13 18:07:09 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56586F16A83 for ; Tue, 13 Feb 2018 18:07:09 +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 B15EC87D68 for ; Tue, 13 Feb 2018 18:07:08 +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 w1DI6xPI049910; Tue, 13 Feb 2018 10:06:59 -0800 (PST) (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 w1DI6xp7049909; Tue, 13 Feb 2018 10:06:59 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201802131806.w1DI6xp7049909@pdx.rh.CN85.dnsmgr.net> Subject: Re: bhyve and contention In-Reply-To: <61adce39-e393-f533-3772-6503a72972af@zyxst.net> To: tech-lists Date: Tue, 13 Feb 2018 10:06:59 -0800 (PST) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 13 Feb 2018 18:07:09 -0000 > Hello virtualizations, > > Please can anyone tell me what happens in the following scenarios: I can speculate on some of what may happen, this may not be exact, but should give you an idea. > 1. > freebsd-11 server, 5x freebsd-11 guests > The server has 32GB ram installed. it's an i7 so 8 cores. There's 64GB > swap. Each guest that bhyve loads is with m 8192M, so ram is > overcommitted by 6GB. 5 x 8G == 40G, 32G ram, so 8G overcommit, not 6. Further more you have base sytem memory which includes such things as kernel, page tables, loaded modules, buffer cache, possibly ZFS arc cache since you dont mention that. ZFS arc cache will attempt to grow to something like 95% of memory, so you can actually be in full 40G over commit situation on memory. > What happens to the guests and the server? Do either (or both) crash? Or > is there something in bhyve that will make memory allocated on a > best-effort basis? With 64G of swap space avaliable, and assuming your either not running ZFS or have limited zfs arc cache to say 2G or 4G the system should not crash. You however are in a memory overcommit and things are likely to be sluggish and may even appear crashed. Bhyve uses swap backed annonymous vm so the vm system shall apply best effort to meet the demands. Swapping vm guest memory pages though not idea does work, but as I said, things are going to get very sluggish both on the host and the guest. > 2. > In the following context, the server is the same but this time all five > guests have -c 4 per guest, so bhyve is asking 12 more cores than that > existing in hardware. Does the guest fail to load, do either guest or > server crash? The is core over commit, very common in the virtualization world, bhyve does its best effort to give the guests cores as needed. I am typing this on a system with a 4 core CPU (2 real x 2 thread) that is running 10 bhyve VM's, each just single core. My host load average is: 6:01PM up 3 days, 16:01, 7 users, load averages: 3.77, 3.34, 3.22 One of those guests is running a stable/10 make world in a memory contrained situation (512MB). The host system is responsive and working fine, as are the guests. I am fine with CPU over commit, but I watch the memory situation like a hawk. I only have 12GB of memory, I have restricted ZFS arc cache to 6G The sums of the memory of all the running VM's is about 2G This leaves me about 4G of fiddle around room on the host for occasional VM spin up, or other memory heavy things. I run all my VM's with the wired memory option. > > thanks, > -- > J. > _______________________________________________ > 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 Tue Feb 13 23:49:05 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59CC2F0C67E for ; Tue, 13 Feb 2018 23:49:05 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id BB6D678EAF for ; Tue, 13 Feb 2018 23:49:04 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id CFF1620B4D34 for ; Wed, 14 Feb 2018 09:49:01 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id C647E281F1F for ; Wed, 14 Feb 2018 09:49:01 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id sRzo1bk7CNro for ; Wed, 14 Feb 2018 09:49:01 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (96-82-80-65-static.hfc.comcastbusiness.net [96.82.80.65]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 2FD32280AB0; Wed, 14 Feb 2018 09:48:59 +1000 (AEST) Subject: Re: bhyve and contention To: "Rodney W. Grimes" , tech-lists Cc: freebsd-virtualization@freebsd.org References: <201802131806.w1DI6xp7049909@pdx.rh.CN85.dnsmgr.net> From: Peter Grehan Message-ID: Date: Tue, 13 Feb 2018 15:48:57 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201802131806.w1DI6xp7049909@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=KPZ08mNo c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=IkcTkHD0fZMA:10 a=Op4juWPpsa0A:10 a=RbfNA_8WEnTZXyLG25AA:9 a=QEXdDO2ut3YA:10 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 13 Feb 2018 23:49:05 -0000 >> 2. >> In the following context, the server is the same but this time all five >> guests have -c 4 per guest, so bhyve is asking 12 more cores than that >> existing in hardware. Does the guest fail to load, do either guest or >> server crash? > > The is core over commit, very common in the virtualization world, > bhyve does its best effort to give the guests cores as needed. To add to what Rod said - bhyve uses a thread for each vCPU. It's up to the FreeBSD scheduler to determine where/when these threads run. It is possible for a guest to fail, for example if a spinlock times out due to vCPUs not being able to run to release a lock. This is a general problem with virtualization and can occur even on VMWare ESXi with heavy oversubscription. That being said, there is certainly scope to provide more information to the FreeBSD scheduler so it can make better decisions when running VM guests. later, Peter. From owner-freebsd-virtualization@freebsd.org Wed Feb 14 03:23:32 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D6F4F1D052 for ; Wed, 14 Feb 2018 03:23:32 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by mx1.freebsd.org (Postfix) with ESMTP id 8879281020 for ; Wed, 14 Feb 2018 03:23:30 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from unknown (HELO leader.local) ([118.211.61.252]) by ipmail07.adl2.internode.on.net with ESMTP; 14 Feb 2018 13:48:19 +1030 Subject: Re: bhyve and contention To: tech-lists Cc: freebsd-virtualization@freebsd.org References: <201802131806.w1DI6xp7049909@pdx.rh.CN85.dnsmgr.net> From: Shane Ambler Message-ID: Date: Wed, 14 Feb 2018 13:48:17 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 14 Feb 2018 03:23:32 -0000 On 14/02/2018 10:18, Peter Grehan wrote: >>> 2. >>> In the following context, the server is the same but this time all five >>> guests have -c 4 per guest, so bhyve is asking 12 more cores than that >>> existing in hardware. Does the guest fail to load, do either guest or >>> server crash? >> >> The is core over commit, very common in the virtualization world, >> bhyve does its best effort to give the guests cores as needed. > >  To add to what Rod said - bhyve uses a thread for each vCPU. It's up to > the FreeBSD scheduler to determine where/when these threads run. > >  It is possible for a guest to fail, for example if a spinlock times out > due to vCPUs not being able to run to release a lock. This is a general > problem with virtualization and can occur even on VMWare ESXi with heavy > oversubscription. There are some bhyve options you need to check - You want to use the -H option which prevents the guest keeping 100% cpu. Be sure not to pass the -S option to bhyve as it wires the guest memory. This was seen recently as sysutils/chyves uses it by default. https://www.mail-archive.com/freebsd-virtualization@freebsd.org/msg05665.html If you use zfs, you may want to set the arc_max. One thing that I have noticed, as a guest allocates ram, the host allocates ram to its bhyve instance, but when the guest releases it, the host is unaware of the ram now being free. Apparently there is work on getting the guest to notify the host of released ram. Until that is available you may want to restart guests that temporarily allocate large amounts of ram. -- FreeBSD - the place to B...Sharing Devices Shane Ambler From owner-freebsd-virtualization@freebsd.org Wed Feb 14 16:25:09 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D63B7F0BAE8 for ; Wed, 14 Feb 2018 16:25:09 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 7B4928055D for ; Wed, 14 Feb 2018 16:25:09 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B8AC720C0D for ; Wed, 14 Feb 2018 11:25:03 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 14 Feb 2018 11:25:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=vw6deRJhvaQpHtt3Kk8VqgBe6toE6 67ezGpE9yrPUv4=; b=uqVdpOEdJOw1caUl4hc5GP/tc0lHVdaW4tHm/6PB3rAVy jBeNBna73egC5p+KDIhRm1KpJ+zRVQRffWslO2zs/tEnBvGeJHCRhv7rQRXQf0Su 1QN3JsElzkAz5gSpLiOz2fXVkf7xZt6IlPjQ260lmkSvoZTU40piF+KVMdlFjfKW 8Ow9qPQ5KMEZOqPlX4xf9PN0cKy1vyBPTIKLnXBPSqPaR90OzMm8+l39uyP1C5iU C1LNONI73frdrWE8ihOcwR0hXpqcQqXy8axdfxZhGPDogrPnFKbwMXhsN/ubEh+Z Gu63NjNaZgwTjscmQH3Ysx6bqQNCO8j+NYDGJsJjA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=vw6deR JhvaQpHtt3Kk8VqgBe6toE667ezGpE9yrPUv4=; b=WxdFg4LYPRxtbrLvFeSdGS 8vpToTDIekZwKYWRKmO6treY9kzl8Amq0Jp0k8xyB0oLa8hQaevrrjjneRyzfKPZ ZgPEgqAsK9jfv4MsRlk/JgIm0kVki9vnNyw/G6iJ58vwfjYf5T4Su2qi7QRnzSPr KhkJB8MzFfcdJHPBxNjSJIJt1ZzTn2kIl/O/DdeDw697eqPM/ChQf0pNQyImXytd O680ktIl4p2nSHrGSpDykc1709gWI2ANqkjo1hln0SiyDECSAIBa8Pld9wKr7rOW 0sA1wwolpKb7gc2BqRpvNP56dSZVyihU/JIwjkcuRgC/82r+OVGNTzgj5GXYkN2Q == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 98250245A8 for ; Wed, 14 Feb 2018 11:25:02 -0500 (EST) Subject: Re: bhyve and contention References: <201802131806.w1DI6xp7049909@pdx.rh.CN85.dnsmgr.net> To: freebsd-virtualization@freebsd.org From: tech-lists Message-ID: <91161d55-e88e-9a06-1733-f2976498bfaa@zyxst.net> Date: Wed, 14 Feb 2018 16:25:01 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201802131806.w1DI6xp7049909@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 14 Feb 2018 16:25:10 -0000 Thanks everyone for answering my query -- J. From owner-freebsd-virtualization@freebsd.org Wed Feb 14 19:27:17 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34A7AF195BF for ; Wed, 14 Feb 2018 19:27:17 +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 A2A8469152 for ; Wed, 14 Feb 2018 19:27:16 +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 w1EJANsW054511; Wed, 14 Feb 2018 11:10:23 -0800 (PST) (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 w1EJAMQi054510; Wed, 14 Feb 2018 11:10:22 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201802141910.w1EJAMQi054510@pdx.rh.CN85.dnsmgr.net> Subject: Re: bhyve and contention In-Reply-To: To: Shane Ambler Date: Wed, 14 Feb 2018 11:10:22 -0800 (PST) CC: tech-lists , 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.25 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, 14 Feb 2018 19:27:17 -0000 [ Charset UTF-8 unsupported, converting... ] > On 14/02/2018 10:18, Peter Grehan wrote: > >>> 2. > >>> In the following context, the server is the same but this time all five > >>> guests have -c 4 per guest, so bhyve is asking 12 more cores than that > >>> existing in hardware. Does the guest fail to load, do either guest or > >>> server crash? > >> > >> The is core over commit, very common in the virtualization world, > >> bhyve does its best effort to give the guests cores as needed. > > > > ?To add to what Rod said - bhyve uses a thread for each vCPU. It's up to > > the FreeBSD scheduler to determine where/when these threads run. > > > > ?It is possible for a guest to fail, for example if a spinlock times out > > due to vCPUs not being able to run to release a lock. This is a general > > problem with virtualization and can occur even on VMWare ESXi with heavy > > oversubscription. > > There are some bhyve options you need to check - > > You want to use the -H option which prevents the guest keeping 100% cpu. Very true, this yields the vCPU when a halt is executed. > Be sure not to pass the -S option to bhyve as it wires the guest memory. > This was seen recently as sysutils/chyves uses it by default. This should be evaluated, if you do not pass -S you run into the possible performance impact of swapping guest memory, which does infact allow you more over commit, but at a pretty large performance penality. You need swap space if you are going to not pass -S and over commit, if you do not have enough swap space for the over commit your system runs out of swap and usually ends up killing random processes, and random usually means the most important things you are running! > https://www.mail-archive.com/freebsd-virtualization@freebsd.org/msg05665.html > > If you use zfs, you may want to set the arc_max. This is not a may, if you use ZFS you must restrict its buffer cache, or expect unstable systems. ZFS's default situation is to use up to 95% of memory, that leaves almost nothing for a running VM. > One thing that I have noticed, as a guest allocates ram, the host > allocates ram to its bhyve instance, but when the guest releases it, the > host is unaware of the ram now being free. Apparently there is work on > getting the guest to notify the host of released ram. Until that is > available you may want to restart guests that temporarily allocate large > amounts of ram. Correct, we need an implementation of what is called a memory ballon driver so that the guest can pass back to the host un used memory. > -- > FreeBSD - the place to B...Sharing Devices > Shane Ambler -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Thu Feb 15 06:21:25 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E5EDF00909 for ; Thu, 15 Feb 2018 06:21:25 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmailnode02.adl6.internode.on.net (ipmailnode02.adl6.internode.on.net [150.101.137.148]) by mx1.freebsd.org (Postfix) with ESMTP id 739FB84A5A for ; Thu, 15 Feb 2018 06:21:23 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from unknown (HELO leader.local) ([118.211.9.187]) by ipmail02.adl6.internode.on.net with ESMTP; 15 Feb 2018 16:46:12 +1030 Subject: Re: bhyve and contention To: "Rodney W. Grimes" Cc: tech-lists , freebsd-virtualization@freebsd.org References: <201802141910.w1EJAMQi054510@pdx.rh.CN85.dnsmgr.net> From: Shane Ambler Message-ID: <6fc388d9-388f-1cd3-ee8b-16d8e9204447@ShaneWare.Biz> Date: Thu, 15 Feb 2018 16:46:11 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <201802141910.w1EJAMQi054510@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 15 Feb 2018 06:21:25 -0000 On 15/02/2018 05:40, Rodney W. Grimes wrote: > [ Charset UTF-8 unsupported, converting... ] >> On 14/02/2018 10:18, Peter Grehan wrote: >> Be sure not to pass the -S option to bhyve as it wires the guest memory. >> This was seen recently as sysutils/chyves uses it by default. > > This should be evaluated, if you do not pass -S you run into the > possible performance impact of swapping guest memory, which does > infact allow you more over commit, but at a pretty large > performance penality. The original question specified having 5 guests with 8G each on a host with 32G, so overcommitting ram was expected, wiring each guest in this setup will cause panics not swapping. > You need swap space if you are going to not pass -S and over commit, > if you do not have enough swap space for the over commit your system > runs out of swap and usually ends up killing random processes, and > random usually means the most important things you are running! The host has 64G swap setup. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-virtualization@freebsd.org Thu Feb 15 17:10:20 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E35BF08B32 for ; Thu, 15 Feb 2018 17:10:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3380382F13 for ; Thu, 15 Feb 2018 17:10:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 578A422313 for ; Thu, 15 Feb 2018 17:10:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1FHAJfO011647 for ; Thu, 15 Feb 2018 17:10:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1FHAJbn011646 for freebsd-virtualization@FreeBSD.org; Thu, 15 Feb 2018 17:10:19 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 215972] Bhyve crash more then 1 cpu AMD Date: Thu, 15 Feb 2018 17:10:18 +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 Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@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.25 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, 15 Feb 2018 17:10:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215972 --- Comment #37 from commit-hook@freebsd.org --- A commit references this bug: Author: avg Date: Thu Feb 15 17:09:48 UTC 2018 New revision: 329320 URL: https://svnweb.freebsd.org/changeset/base/329320 Log: MFC r328622: vmm/svm: post LAPIC interrupts using event injection PR: 215972 Changes: _U stable/11/ stable/11/sys/amd64/vmm/amd/svm.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Feb 15 17:11:26 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9114EF08F6D for ; Thu, 15 Feb 2018 17:11:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 12EA7832BE for ; Thu, 15 Feb 2018 17:11:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D72D322353 for ; Thu, 15 Feb 2018 17:11:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1FHBOdB016782 for ; Thu, 15 Feb 2018 17:11:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1FHBOho016781 for freebsd-virtualization@FreeBSD.org; Thu, 15 Feb 2018 17:11:24 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 215972] Bhyve crash more then 1 cpu AMD Date: Thu, 15 Feb 2018 17:11:24 +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 Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@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.25 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, 15 Feb 2018 17:11:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215972 --- Comment #38 from commit-hook@freebsd.org --- A commit references this bug: Author: avg Date: Thu Feb 15 17:10:42 UTC 2018 New revision: 329321 URL: https://svnweb.freebsd.org/changeset/base/329321 Log: MFC r328622: vmm/svm: post LAPIC interrupts using event injection PR: 215972 Changes: _U stable/10/ stable/10/sys/amd64/vmm/amd/svm.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Feb 15 17:16:19 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C9C7F096D8 for ; Thu, 15 Feb 2018 17:16:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2F438385F for ; Thu, 15 Feb 2018 17:16:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 01B522249D for ; Thu, 15 Feb 2018 17:16:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1FHGHgk039338 for ; Thu, 15 Feb 2018 17:16:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1FHGHmb039337 for freebsd-virtualization@FreeBSD.org; Thu, 15 Feb 2018 17:16:17 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 215972] Bhyve crash more then 1 cpu AMD Date: Thu, 15 Feb 2018 17:16: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 Many People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution 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.25 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, 15 Feb 2018 17:16:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215972 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Feb 16 01:00:23 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1ECFEF047F3; Fri, 16 Feb 2018 01:00:23 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 DE8CD796D6; Fri, 16 Feb 2018 01:00:19 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id F1E9420D7D; Thu, 15 Feb 2018 20:00:18 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 15 Feb 2018 20:00:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=Lf/pY97HnoU5QTlCncOgVnA729ais0izgQ78X2Hd+jA=; b=gvBifQfS oLPAZuOVTo/bjBG5/GZ1T+zadvv4HOb3GRDbM7vIGpntNlLH5a3jK7dXFO1HiTjf g+YhcvVTkTTuz+NS5FXffFyA3OgBfidhcoz7oqjlIa20GyV6fUMO5x8iSAAsrjL9 3WsffI/MQYNEWpMTuti5Fp2g9tCGR4forLyHiTtyhLFJ4wDTp487B3x3zSNEbQJc SvuJm3274LDSYHP41etWgp+awDoRqxurPSl43YCVDP5JxzTsuStvfnAgxIkyy1VP iUCzuLdzxEXNw5hjz6LiO94iG3fmHLei7ybQa+dt5j0/zLRPSGP49DLmTkwtjnxq qJZ2cPoQWvM+Pw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Lf/pY97HnoU5QTlCncOgVnA729ais 0izgQ78X2Hd+jA=; b=BvCrdwc0vSbiYd7bbur/N6V8x0qwcaqj3prhUJAfybteS VDHvG5bIwvP2dANcElRipGk+7QrER+mfnbgCPIU2AfUAGXCFyKtk0WdFYHhBZwtN 9aRzzN9jv4roHcpU2Lei96lWA5C4XaYKlrGcMGSwfXRXtjabMatFvHWap4XnUkXy hTZ6l45fxXZEwFTaVz1STLWFcPqnu3RG8q94a0jolsbjYsjzDykQ5eKsvdo7IyGF s1e4oJBThkh/BevsClIbfjKgKMi82MaRBgBBrvfxpim41DqfKNihFKiW7ZtcuTYW 1T2f9VdCfjiCxlrkRtd3DQfVzufdmXpwnXzCak1AQ== X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 7DE80246D0; Thu, 15 Feb 2018 20:00:18 -0500 (EST) From: tech-lists Subject: is it possible to chroot into arm64 from amd64? To: freebsd-virtualization@freebsd.org Cc: freebsd-stable@freebsd.org Message-ID: <30cfa8a3-76e4-73ac-3b2a-2d64ed24aef8@zyxst.net> Date: Fri, 16 Feb 2018 01:00:16 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 16 Feb 2018 01:00:23 -0000 Hi, Is it possible to have on an amd64 system, a chrooted or jailed arm64 environment? It's possible to cross-compile an arm6 environment on amd64 and then chroot into the arm6 environment - is the same possible for arm64? I can cross-compile arm64 like this: # SYSROOT=/crossbuild/arm64 # cd /usr/src # make -j32 TARGET=arm64 TARGET_ARCH=aarch64 buildworld # make DESTDIR=$SYSROOT TARGET=arm64 TARGET_ARCH=aarch64 installworld # make DESTDIR=$SYSROOT TARGET=arm TARGET_ARCH=armv6 distribution # cp /usr/local/bin/qemu-aarch64-static $SYSROOT/sbin # /usr/sbin/binmiscctl add arm64 --interpreter "/usr/local/bin/qemu-aarch64" \ --magic "\x7f\x45\x4c\x46\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00" \ --mask "\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff" \ --size 20 --set-enabled # mount -t devfs devfs ${DESTDIR}/dev then: # chroot -u root $SYSROOT then I get the following error: chroot: /bin/csh: No such file or directory # so looked at the chroot, and bin/csh is there! # ls -lah $SYSROOT/bin |less total 9144 drwxr-xr-x 2 root wheel 1.0K Feb 16 00:43 . drwxr-xr-x 18 root wheel 512B Feb 16 00:44 .. -r-xr-xr-x 2 root wheel 195K Feb 16 00:43 [ -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 cat -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 chflags -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 chio -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 chmod -r-xr-xr-x 1 root wheel 195K Feb 16 00:43 cp -r-xr-xr-x 2 root wheel 451K Feb 16 00:43 csh what am I doing wrong? -- J. From owner-freebsd-virtualization@freebsd.org Fri Feb 16 01:22:09 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDD61F0623E for ; Fri, 16 Feb 2018 01:22:09 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 8134A7AA17 for ; Fri, 16 Feb 2018 01:22:08 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-qt0-x22c.google.com with SMTP id d14so2104317qtg.1 for ; Thu, 15 Feb 2018 17:22:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Rdb5CyqeVz87BXb6WhLJ5Jb1QcugWr1f3khKG5wF6xA=; b=XUXCfn1maab59IMouOl0Ag+5iz77rh8r8Q2kYtMJeTQ7IHhQgAcGEv6chcrpj5OYIM MsCfGyVJAAgm5d+Vj08iHzYltFM3TxAwJSN4Xm7OP1Mr5wP8+cFcr1hfgxUYhOAS6KOK w6N5M0mjk/TMR8IebinsHVJDyogXjYaeKAPnfFbRHRMiZ5lLpmhZSCD+dtF1t1W1u0BO 1DL/rinPblwrL/nmoTPcsr9F9607pWPiIP8OSg1l87clBxPeVMzCoflOwHGy7IehgPeK uqYxq3mgDP8s4GaueqmKvT5qGc6OcIywSqvtWqUmJQDMH6+Tookz/tRXRkFz0YFMlpkh 6xNQ== 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=Rdb5CyqeVz87BXb6WhLJ5Jb1QcugWr1f3khKG5wF6xA=; b=AOzFEeFDrtm0D6psNeERviRc/g4irjrZ0DSC24sc9Kjl8M+AkyqN/RAFhgvrka6upd Gx3aVeZNbWueOJin/NMeBZ5YHE6bCZ85vuTf0yP4AML508wX5HqwnHPYFPlZxzN1z2RK FevTOkzFv4J2fphMeYYtxPi65FSICFCNGTWsQ42bwOnjl9wcVV0zvYXTYLCBHzzBCAVv xa4isze1DTfGdvPNiZWNSLSvpyaQZZXhKuODJgamNcF7lODGWnWfyfzWeqvb8E68LnF7 XXkEgUo6Rth0UzeWfX3CaYPgTmtlbjhoJgeo2PHa5znrTWCFlnDiGRUDY+fx9eDgoagn GbgA== X-Gm-Message-State: APf1xPAWyw8XVTWpwatTr29jX1w3uR5BVNi4b01jmAXCuJif6tJy2Gih INRYUg26/0pJNN4yw16sNtz6Hjs/NiahmXQrqt4fxhwy X-Google-Smtp-Source: AH8x227ZFrq9ON8NW+bVQE+rt/Pm+KpIwSnj+4ImVcbVV/3GyVNZGCxBYUThUqiQ5oRpZ5TcEpkHf+KjinJaxMi08dI= X-Received: by 10.200.54.100 with SMTP id n33mr2393534qtb.271.1518744127695; Thu, 15 Feb 2018 17:22:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.80.241 with HTTP; Thu, 15 Feb 2018 17:22:07 -0800 (PST) X-Originating-IP: [203.99.129.1] In-Reply-To: <30cfa8a3-76e4-73ac-3b2a-2d64ed24aef8@zyxst.net> References: <30cfa8a3-76e4-73ac-3b2a-2d64ed24aef8@zyxst.net> From: Jonathan Chen Date: Fri, 16 Feb 2018 14:22:07 +1300 Message-ID: Subject: Re: is it possible to chroot into arm64 from amd64? To: tech-lists Cc: freebsd-virtualization@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 16 Feb 2018 01:22:10 -0000 On 16 February 2018 at 14:00, tech-lists wrote: > Hi, > > Is it possible to have on an amd64 system, a chrooted or jailed arm64 > environment? It's possible to cross-compile an arm6 environment on > amd64 and then chroot into the arm6 environment - is the same possible > for arm64? I can cross-compile arm64 like this: > > # SYSROOT=/crossbuild/arm64 > # cd /usr/src > # make -j32 TARGET=arm64 TARGET_ARCH=aarch64 buildworld > # make DESTDIR=$SYSROOT TARGET=arm64 TARGET_ARCH=aarch64 installworld > > # make DESTDIR=$SYSROOT TARGET=arm TARGET_ARCH=armv6 distribution > # cp /usr/local/bin/qemu-aarch64-static $SYSROOT/sbin > > # /usr/sbin/binmiscctl add arm64 --interpreter > "/usr/local/bin/qemu-aarch64" \ [...] You've copied qemu-aarch64-static to $SYSROOT/sbin. binmiscctl(8) should use /sbin/qemu-aarch64-static as its arm64 interpreter in the arm64-chroot. Cheers. -- Jonathan Chen From owner-freebsd-virtualization@freebsd.org Fri Feb 16 02:01:49 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54877F08BEC for ; Fri, 16 Feb 2018 02:01:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E71927C1C6 for ; Fri, 16 Feb 2018 02:01:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 387EE26E60 for ; Fri, 16 Feb 2018 02:01:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1G21m9x008673 for ; Fri, 16 Feb 2018 02:01:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1G21mts008672 for freebsd-virtualization@FreeBSD.org; Fri, 16 Feb 2018 02:01:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 213333] FreeBSD 11-RELEASE fails to boot under KVM/Qemu Date: Fri, 16 Feb 2018 02:01:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mpp302@gmail.com 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.25 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, 16 Feb 2018 02:01:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213333 Mateusz Piotrowski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpp302@gmail.com --- Comment #18 from Mateusz Piotrowski --- Same on FreeBSD 11.1 amd64. Switching to kvm64 or Opteron_G3 "fixes" this i= ssue for me. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Feb 16 11:25:53 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55DC2F09D9C; Fri, 16 Feb 2018 11:25:53 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 D2901743E5; Fri, 16 Feb 2018 11:25:52 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id EEBC420A8C; Fri, 16 Feb 2018 06:25:51 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Fri, 16 Feb 2018 06:25:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=2AXdReon5D2a++aEzy41xM+jETgcD I6Lv8uLxBFlioo=; b=SvcCGlsE8GFSvMdQDi9qmFGykAm7GOK6FjVLOLOf2G5cx +d0TcnRcAuo+kea2mC8ySXv5A17uUrrM/0S8BB64F8b0LuZqVY6TayF7OXq81qyy ThkTqC4CjjHztbJHXUfpkR/kGofei1hKI1UrguLGuxFJ5yxRgNoVuDaR1cwh/2BT umip5LDfzJbVeVzfFXJcarcrd67H2C2S0ZB84fbIcfolIRtFFWBgaYrL2t+zV95c bsxbYqWvVSxPHMyqZZLUFRlmQs8VF0xBFIGp2lbBYp/RHNwu1lIprdwA2VPvaVAQ hxik7X0uuAqT3Sfzvb78g5kIY8ZCb3DtkPNnrG3EA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=2AXdRe on5D2a++aEzy41xM+jETgcDI6Lv8uLxBFlioo=; b=W8cQBjfcrL17V50PfulBoa 77KYm7Cr/2ErVyvG0CBfXTsVpZQ1WPngje9ha/lwXUFFFSKCgFjyhOjMpEhxduvq X0LSqZQPXZgLm+pJ4gWlvvRhYri04n8aK9Fjqo0k7BEmTZz0q42JlP+3chuFgIMj JK0xB/qSoJmr6eh4AFh8PKBh7Vo31iWqbjlBFScNW0zuzO21QsQvTlJHrbt+I+mL 8BSOFpmgGtQ46VzuO3aeMb42ymZuAfWnQMDPhCR3pxmrBFxYFfYrBCOHikhCHfPK ORCdMbKfWKPEuIUn9lJiRZHxlypx4JidUeQH4XKTMyLzcqClmjkDwf6l0l/of/4A == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 51B2824550; Fri, 16 Feb 2018 06:25:51 -0500 (EST) Subject: Re: is it possible to chroot into arm64 from amd64? To: Jonathan Chen Cc: freebsd-stable@freebsd.org, freebsd-virtualization@freebsd.org References: <30cfa8a3-76e4-73ac-3b2a-2d64ed24aef8@zyxst.net> From: tech-lists Message-ID: <770ca572-657a-9cbf-4ab5-70804f07e1cc@zyxst.net> Date: Fri, 16 Feb 2018 11:25:50 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 16 Feb 2018 11:25:53 -0000 On 16/02/2018 01:22, Jonathan Chen wrote: > You've copied qemu-aarch64-static to $SYSROOT/sbin. binmiscctl(8) > should use /sbin/qemu-aarch64-static as its arm64 interpreter in the > arm64-chroot. arrrgh, thanks for spotting that. I'll try again -- J. From owner-freebsd-virtualization@freebsd.org Fri Feb 16 14:15:55 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88D44F176DC; Fri, 16 Feb 2018 14:15:55 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 2D4757BB87; Fri, 16 Feb 2018 14:15:55 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 88CEC2082A; Fri, 16 Feb 2018 09:15:54 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Fri, 16 Feb 2018 09:15:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=8qjWpMsb3HlUR0PMZfUhB2BOgyFjn dl+sOwqe63Fzb8=; b=Ks8FJx47nK5cm55Jf4EUh7TK23Y2HIqByycJXhyp8rwZl 1PYRZex6W+1EmY/zRhazctFKFLuwIf8Q+/etiJhIpY51o9qrrsLWwPhQR4/bJybh UOaRDsLSXhWn60yA8rqt6cRj7XKDYhBWAaxBzmUaWfq5pFB1eS23zFFmJpTOdMAw 4y75raqbP/Zb+Y9xZ334qjaeI7qmPLrxIpw9cUsy3dHwy86pKRFlpfA1CBXSpOil B1wm9FJeF/kpkmTqOQh8H7Hvt4fgBGX7FrqbaoM+eeAsIauH0N76NC/j1wCk5WVb Zbvvk6mXJ8saH9VVGQSeO20KlB160Tb21hlRWsx/A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=8qjWpM sb3HlUR0PMZfUhB2BOgyFjndl+sOwqe63Fzb8=; b=cPSRu0foPhjSGIHnbL8iD/ vC5j8I62yKk3h3sa8/GKvzjpe42YsBWVPDuaKkXCndWH8gkzEKKKSLaqZZp/bKMT zjuW0ePmI3CRh7OqJPz3angL7u+wZReW6PXThtQ6QgqnEF+iiUUpzjUfSbMpAreL kFOAc9sMve+KoEIMIspooo4cyej+QJ73M9Tbjg1zBzDgPtRD4H0LVGUz+U8jaPqy AqfBTvmJ47gkM/BWlGUhQl3ABG5V8HKyesyP6MjzBH2PztTNd7uq36gkCihMt9K7 suyW1yQPU6AB9KfnKj87X6WxOp+KSJb6wzUpF/BYi6nDM2m8NIl7NL7IFBIsY4qw == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id E361C24550; Fri, 16 Feb 2018 09:15:53 -0500 (EST) Subject: Re: is it possible to chroot into arm64 from amd64? To: =?UTF-8?Q?Mika=c3=abl_Urankar?= References: <30cfa8a3-76e4-73ac-3b2a-2d64ed24aef8@zyxst.net> Cc: freebsd-virtualization@freebsd.org, freebsd-stable@freebsd.org From: tech-lists Message-ID: Date: Fri, 16 Feb 2018 14:15:52 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 16 Feb 2018 14:15:55 -0000 On 16/02/2018 08:21, Mikaël Urankar wrote: > Put  /usr/local/bin/qemu-aarch64-static in > $SYSROOT/usr/local/bin/qemu-aarch64-static > you can use "service qemu_user_static start" to add the interpreter That did it! :D many thanks. I had a bit of a problem with ldconfig but it seems ok so far. Here's what I did from start to finish in case anyone else is interested: ### root@sm1:/# chflags -Rf noschg crossbuild/ root@sm1:/# rm -Rf crossbuild/* root@sm1:/# mkdir crossbuild/arm64 root@sm1:/# sh # SYSROOT=/crossbuild/arm64 # cd /usr/src # make -j96 cleandir && make -j96 clean && make -j96 clean # make -j96 TARGET=arm64 TARGET_ARCH=aarch64 buildworld # make DESTDIR=$SYSROOT TARGET=arm64 TARGET_ARCH=aarch64 installworld # make DESTDIR=$SYSROOT TARGET=arm64 TARGET_ARCH=aarch64 distribution # cp /usr/local/bin/qemu-aarch64-static $SYSROOT/usr/local/bin/qemu-aarch64-static cp: /crossbuild/arm64/usr/local/bin/qemu-aarch64-static: No such file or directory # cp /usr/local/bin/qemu-aarch64-static $SYSROOT/usr/local/bin/ cp: directory /crossbuild/arm64/usr/local/bin does not exist # ls -lah $SYSROOT/usr/local total 8 drwxr-xr-x 2 root wheel 512B Feb 16 12:28 . drwxr-xr-x 13 root wheel 512B Feb 16 12:28 .. # mkdir $SYSROOT/usr/local/bin # cp /usr/local/bin/qemu-aarch64-static $SYSROOT/usr/local/bin/ # service qemu_user_static start Cannot 'start' qemu_user_static. Set qemu_user_static_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'. # echo "qemu_user_static_enable="YES"" >>/etc/rc.conf # service qemu_user_static start # mount -t devfs devfs ${DESTDIR}/dev # chroot -u root $SYSROOT root@sm1:/ # root@sm1:~ # file /usr/bin/file /usr/bin/file: ELF 64-bit LSB executable, ARM aarch64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.1 (1101509), FreeBSD-style, stripped root@sm1:~ # service start ldconfig ps: empty file: Invalid argument start does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable root@sm1:~ # which ldconfig /sbin/ldconfig root@sm1:~ # /sbin/ldconfig root@sm1:~ # root@sm1:~ # exit # -- J. From owner-freebsd-virtualization@freebsd.org Sat Feb 17 02:02:03 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92081F02E53 for ; Sat, 17 Feb 2018 02:02:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2EC047EFB1 for ; Sat, 17 Feb 2018 02:02:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6AA5513CCF for ; Sat, 17 Feb 2018 02:02:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1H222jF076192 for ; Sat, 17 Feb 2018 02:02:02 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1H222nK076182 for freebsd-virtualization@FreeBSD.org; Sat, 17 Feb 2018 02:02:02 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225794] VM images for 12.0-CURRENT have problem with USB 3.0 ports Date: Sat, 17 Feb 2018 02:02:02 +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: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jdc@koitsu.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.25 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, 17 Feb 2018 02:02:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225794 Jeremy Chadwick changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdc@koitsu.org --- Comment #4 from Jeremy Chadwick --- freebsd-stable mailing list also has this, indicating an MFC has now caused this problem in -STABLE: https://lists.freebsd.org/pipermail/freebsd-stable/2018-February/088393.html "VM image for 11.1-STABLE began exhibiting same dislike for USB 3.0 ports as problem reported in PR 225794 for 12.0-CURRENT. Prior to FreeBSD-11.1-STABLE-amd64-20180215-r329320.vmdk.xz no such problem was observed." CAM status 0x44 refers to done_ccb->ccb_h.status per sys/cam/scsi/scsi_da.c, function dadone(). done_ccb is declared as "union ccb *done_ccb". Field c= cb_h is likely declared as "struct ccb_hdr ccb_h" (this is commonplace). Field status is therefore "u_int32_t status" per sys/cam/scsi/cam_ccb.h, which sh= ould correlate with the cam_status enum per sys/cam/scsi/cam.h. I had to write a small program to dump all the enum names and values because the ordering and mid-struct value assignments result in hard-to-read code. Text strings come directly from cam_status_table[] per sys/cam/cam.c, except for QFRZN, which comes from the .h file itself. 0x04 =3D CAM_REQ_CMP_ERR =3D CCB request completed with an error 0x40 =3D CAM_DEV_QFRZN =3D The DEV queue is frozen w/this err Suggest involving avg@, hselasky@, and emaste@ You will probably be asked = to try older commits to try and narrow down what exact commit broke things. stable/11 commits: http://www.freshbsd.org/search?branch=3DRELENG_11&project=3Dfreebsd HEAD commits: http://www.freshbsd.org/?branch=3DHEAD&project=3Dfreebsd --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sat Feb 17 23:39:43 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE2A7F1C061 for ; Sat, 17 Feb 2018 23:39:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 466B57348B for ; Sat, 17 Feb 2018 23:39:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 713A51F19B for ; Sat, 17 Feb 2018 23:39:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1HNdgm2024885 for ; Sat, 17 Feb 2018 23:39:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1HNdgac024884 for freebsd-virtualization@FreeBSD.org; Sat, 17 Feb 2018 23:39:42 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225794] VM images for 12.0-CURRENT have problem with USB 3.0 ports Date: Sat, 17 Feb 2018 23:39:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: David.Boyd49@twc.com 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.25 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, 17 Feb 2018 23:39:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225794 --- Comment #5 from David.Boyd49@twc.com --- Based on Jeremy's assessment, I looked for revisions from 4 weeks ago that = were MFC'd this week. I came up with r327996 which was MFC'd to 11.1-STABLE as r329316. I built 11.1-STABLE as of r329310 and the problem appears to be resolved. All of this is without any understanding of the intent of the original (r327996) fix. --=20 You are receiving this mail because: You are the assignee for the bug.=