From owner-freebsd-virtualization@freebsd.org Sun Jul 16 21:00:50 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 7955FC79E0D for ; Sun, 16 Jul 2017 21:00: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 mx1.freebsd.org (Postfix) with ESMTPS id 5588766BF8 for ; Sun, 16 Jul 2017 21:00:50 +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 v6GL01nt002409 for ; Sun, 16 Jul 2017 21:00:50 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201707162100.v6GL01nt002409@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, 16 Jul 2017 21:00:50 +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, 16 Jul 2017 21:00:50 -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 Mon Jul 17 10:29:29 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 2948CD76E7E for ; Mon, 17 Jul 2017 10:29:29 +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 172C6800E2 for ; Mon, 17 Jul 2017 10:29:29 +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 v6HATSk3045598 for ; Mon, 17 Jul 2017 10:29:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 220790] [Hyper-V]Fail to install on Hyper-V GEN2 VM on win2012r2 or win2016 Date: Mon, 17 Jul 2017 10:29:29 +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 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: Mon, 17 Jul 2017 10:29:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220790 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 Mon Jul 17 20:13:33 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 B3D00D9F7D2 for ; Mon, 17 Jul 2017 20:13:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A1C866FBAC for ; Mon, 17 Jul 2017 20:13:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v6HKDXfd027838 for ; Mon, 17 Jul 2017 20:13:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 220790] [Hyper-V]Fail to install on Hyper-V GEN2 VM on win2012r2 or win2016 Date: Mon, 17 Jul 2017 20:13:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: decui@microsoft.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.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, 17 Jul 2017 20:13:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220790 --- Comment #1 from Dexuan Cui --- It looks the issue doesn't repro if the DVD is connected to the first SCSI adapter (this is the default configuration when we create a GEN2 VM). It only happens when the DVD is connected to the second SCSI adapter. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Jul 18 01:09:23 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 3361AC08ED5 for ; Tue, 18 Jul 2017 01:09:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2154D7DA09 for ; Tue, 18 Jul 2017 01:09:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v6I19ME7083098 for ; Tue, 18 Jul 2017 01:09:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 220790] [Hyper-V]Fail to install on Hyper-V GEN2 VM on win2012r2 or win2016 Date: Tue, 18 Jul 2017 01:09:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: honzhan@microsoft.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.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, 18 Jul 2017 01:09:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220790 --- Comment #2 from Hongjiang --- (In reply to Dexuan Cui from comment #1) Yes, in addition, if there is a SCSI Hard Disk attached before the DVD, the issue will not show up. I have a local fix for this issue. If it passed all tests, I'll create a co= de review. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Jul 18 03:01: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 E0CFFC7ACE6 for ; Tue, 18 Jul 2017 03:01: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 CEE3481E35 for ; Tue, 18 Jul 2017 03:01: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 v6I31q6V032234 for ; Tue, 18 Jul 2017 03:01:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 220790] [Hyper-V]Fail to install on Hyper-V GEN2 VM on win2012r2 or win2016 Date: Tue, 18 Jul 2017 03:01:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: honzhan@microsoft.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.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, 18 Jul 2017 03:01:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220790 --- Comment #3 from Hongjiang --- The patch is ready: https://reviews.freebsd.org/D11634 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Jul 18 11:06: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 7A128CFEB91 for ; Tue, 18 Jul 2017 11:06: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 5AC256A15E for ; Tue, 18 Jul 2017 11:06: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 v6IB5xJK019556 for ; Tue, 18 Jul 2017 11:06:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 212820] FreeBSD 10-STABLE from latest HEAD and 11-RELEASE-RC3 fail to boot in Hyper-V on Windows 10 Date: Tue, 18 Jul 2017 11:05:59 +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-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@unrelenting.technology X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? 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: Tue, 18 Jul 2017 11:06:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212820 Greg V changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |greg@unrelenting.technology --- Comment #29 from Greg V --- 11-STABLE works perfectly for me in a Gen 2 VM on Windows 10 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Jul 20 07:13:53 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 EC407DAA863 for ; Thu, 20 Jul 2017 07:13:53 +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 DA74E839E3 for ; Thu, 20 Jul 2017 07:13:53 +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 v6K7Dri1091485 for ; Thu, 20 Jul 2017 07:13:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 220790] [Hyper-V]Fail to install on Hyper-V GEN2 VM on win2012r2 or win2016 Date: Thu, 20 Jul 2017 07:13:54 +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 Only Me 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, 20 Jul 2017 07:13:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220790 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: sephe Date: Thu Jul 20 07:13:26 UTC 2017 New revision: 321286 URL: https://svnweb.freebsd.org/changeset/base/321286 Log: hyperv/storvsc: Force SPC3 for CDROM attached. This unbreaks the CDROM attaching on GEN2 VMs. On GEN1 VMs, CDROM is attached to emulated ATA controller. PR: 220790 Submitted by: Hongjiang Zhang MFC after: 3 days Sponsored by: Microsoft Differential Revision: https://reviews.freebsd.org/D11634 Changes: head/sys/dev/hyperv/storvsc/hv_storvsc_drv_freebsd.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Jul 20 08:13: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 750C0DABA29 for ; Thu, 20 Jul 2017 08:13: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 63643165F for ; Thu, 20 Jul 2017 08:13: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 v6K8Di9L052072 for ; Thu, 20 Jul 2017 08:13:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 220872] ixv driver 12.0 crash in AWS/EC2 Date: Thu, 20 Jul 2017 08:13: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: CURRENT 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 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, 20 Jul 2017 08:13:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220872 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org CC| |cperciva@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Jul 21 22:43:41 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 E058DC09836 for ; Fri, 21 Jul 2017 22:43:41 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 933311A28 for ; Fri, 21 Jul 2017 22:43:41 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id e131so24716768wme.0 for ; Fri, 21 Jul 2017 15:43:41 -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=NiM+Y5U/C6QqbErQBhYB6d8I1Lp8bWNT1yddVS285/Q=; b=DOMjBD7Z95Rsge8nLjfwHwzMxi5Qk4wwKWgBX0ha2j9qjaOJCCFt14Gl/VlVdsZIVm S+yCRp28KPKGqBoW3DYtP3HkgzUxw+4JHfg6OEtMkSTuRclffbE5J6To1e3PNiHNAZ1B I74BBIUj1zgSAWrAxIU215sDTNcHuN7b9rsPvKyhcdlhB5sKoxKlohXSYBTnq8QIybgT TNix3AB3zH9sxb0VINRLLf/Sk5TmOnRmQLWJQBpon2kVmtHaK7rYQKJNB8uu1X4uWZ9Z O1luMABWoI9gYmPHi5lha3mUT/Q+6f/x5z5FbZ4ooNy82jQbp1YuoniZomhTAW/mx8uw 0+Gw== 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=NiM+Y5U/C6QqbErQBhYB6d8I1Lp8bWNT1yddVS285/Q=; b=tpMWDZ2XkLhvA2n109qVOt+Bh8R2zW+pkj+YKDRSd4aJOLx2w+SChMkuY3KwrkHveg rOid8ZmmM52rFBeFIxDR6LcRn8JDWJJh6Z0ZF0WFTd0Td45FfydlPx6sbWRcIFhIuWJr IsUIlptOLDXdbZ7ZGySa9LrQECN+IHgEHs6bGP0LnRK+eNOO7iaN9vqqlTm3LAaNbgmT U5lmEG8vDyCssEfvC49xsIXOdifz9oc+me4peMINFhsGDpz+Qu2ob/FwRxVabZvkS5ev bCoWiqMp1zmkcy9mJ4WUx0R7JWKFRb49sF3VQCLVhk9totL/5bz3hNXs+MOPpX7R7McS Vomg== X-Gm-Message-State: AIVw111C5pqCCliqHAlvGoj3btNOFvmhTwhxO2RHtom7lyu5C0JESRtc yllqnQ34QbQs+IcxBKJ5wfKI3hAysA== X-Received: by 10.80.158.168 with SMTP id a37mr7059260edf.169.1500677019737; Fri, 21 Jul 2017 15:43:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.220.8 with HTTP; Fri, 21 Jul 2017 15:43:39 -0700 (PDT) From: Zaphod Beeblebrox Date: Fri, 21 Jul 2017 18:43:39 -0400 Message-ID: Subject: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) To: "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: Fri, 21 Jul 2017 22:43:42 -0000 Since I found out that I can't run a Samba directory server in a jail, I've had the setup of a bhyve on my list. I had toyed with Bhyve 6 or 8 months ago, and still had the images, so I zfs cloned one and set about a source upgrade. This ignomineously hung. So... I upgraded the host to 11.1-RC3, and I reinstalled a fresh guest from the 11.1-RC3 install CD. The guest uses UFS2 on a 40G disk, the server is an AMD 9590 with 32G RAM and a 40T ZFS array. After installation, I started the guest again with 1G ram, 4 processors (of the 8 on the source CPU) and tried a buildworld again. This time the guest crashed and rebooted. What should be next steps here? This is repeatable. The host is stable (it can makeworld -j32 in about 25 minutes ... so it's hardware seems good). Is this an AMD bug? Is it bad to use ZFS ZVols? From owner-freebsd-virtualization@freebsd.org Fri Jul 21 22:58: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 B0D41C09B48 for ; Fri, 21 Jul 2017 22:58:25 +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 720E41EB5 for ; Fri, 21 Jul 2017 22:58:25 +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 0F04720AE974 for ; Sat, 22 Jul 2017 08:58:18 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 00178281258 for ; Sat, 22 Jul 2017 08:58:17 +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 NEC8gytIPgoT for ; Sat, 22 Jul 2017 08:58:17 +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 5039F2809A8; Sat, 22 Jul 2017 08:58:16 +1000 (AEST) Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) To: Zaphod Beeblebrox References: Cc: "freebsd-virtualization@freebsd.org" From: Peter Grehan Message-ID: <490d70e2-ff8b-2a60-2eb7-669dadbcc2a9@freebsd.org> Date: Fri, 21 Jul 2017 15:58:12 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: 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.2 cv=XKlAcUpE c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=IkcTkHD0fZMA:10 a=G3gG6ho9WtcA:10 a=fCqCzJ7R-124FQafWwsA:9 a=QEXdDO2ut3YA:10 wl=host:3 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, 21 Jul 2017 22:58:25 -0000 Hi, > What should be next steps here? This is repeatable. The host is stable > (it can makeworld -j32 in about 25 minutes ... so it's hardware seems > good). Is this an AMD bug? Is it bad to use ZFS ZVols? ZVols are fine. Is the guest panic a spinlock timeout ? I believe this is a bug in bhyve/SVM. It appears somewhat related to processor speed (I can't repro on a 2.3GHz 8 CPU Opteron 6320, but can hit it after 15 mins or so on a Ryzen 1700, with/without SMT). Anish and I are currently chasing this and have repros. An experiment you could try is to run with the vCPUs pinned i.e. for a 4 vCPU guest, add the options "-p 0:1 -p 1:2 -p 2:3 -p 3:4". later, Peter. From owner-freebsd-virtualization@freebsd.org Fri Jul 21 22:59: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 5DFFCC09BCA for ; Fri, 21 Jul 2017 22:59:17 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::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 E69D31F60 for ; Fri, 21 Jul 2017 22:59:16 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id v139so6535825wmv.0 for ; Fri, 21 Jul 2017 15:59:16 -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; bh=REhIxiswUOib0qC6nFwRsYCvsbzgUlmjnbi57EVHR18=; b=B35J/uZNQQO+legb1bTJQ7u3pH7Qgzr1DoZdYS3/IXK7niweQ60lLdy9QbSINUUeas s+tlMQlZnvaaw5QfOtBFdX9fYdQ5q5xcV9ylUJP653eTfkhltDo5sdXi7ZrUG8WlvgKr x/JbWCYcgKEXX+tlzPhKGLsh40mXOJE/IQAueZQ8gRdhLnwq7ooe+1TXVcD7kR40rykb 0aK21rseX0M+xosX9E3SrsVv+Rbcme+y50B4ewj2Z4XvZU2JXWkuCxEKMgW+UKk1MwoT xz1L6yyBfq13Q3Sttjogp6VuReSeAiytfP36LV4tevnX2blNi+dxECB0K6ssx95vdY6/ /m+Q== 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; bh=REhIxiswUOib0qC6nFwRsYCvsbzgUlmjnbi57EVHR18=; b=keiX7Tyx62YZ51Uq1gLYfYxtwyj/POnBZmCaVtyKgHaz1rsftyQUBPBz1nS7Lzp9hn 4zyGrHKxl9C/cw4CyROX0YBIvCCiuKxtsGXUJmFxvGglukQnAj68j3pJD45RT1fIDNlu kNmmjRT2d+lbuyBP2ZdXmP++izA6N9F9qWT5ABuQXGsDBmjpBTxPXLfUFb1bvy723wdi nw7pX9b3ht9vY12tcDslOz5j4BU6BQABhwSVM9UjNyVrtsoRXqF6DDBn0bAlBRxCo/LZ UUxyFzfXFItiukv83+RK4XIeZizxBBPbd9WSJklGfQK5p1iHy8YDr48G2OpNc3c4362v neDg== X-Gm-Message-State: AIVw113zwbwg6romAU8MEHTkEDCDmB+G4hxV1iPEB8y8WIX9/t8nUk63 ial+DS8mCieMWWGQn1v7LmAnuDzykDSz X-Received: by 10.80.222.138 with SMTP id c10mr7333607edl.97.1500677955378; Fri, 21 Jul 2017 15:59:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.220.8 with HTTP; Fri, 21 Jul 2017 15:59:14 -0700 (PDT) In-Reply-To: References: From: Zaphod Beeblebrox Date: Fri, 21 Jul 2017 18:59:14 -0400 Message-ID: Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) To: "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: Fri, 21 Jul 2017 22:59:17 -0000 ... curiously, top running on the guest reveals (the point at which the bhyve wedges): 88722 root 1 52 0 109M 105M pfault 3 0:03 42.37% llvm-tblgen 88687 root 1 52 0 374M 347M pfault 2 0:04 38.24% llvm-tblgen 88668 root 1 52 0 236M 225M pfault 0 0:04 35.11% llvm-tblgen 88743 root 1 52 0 55460K 26392K pfault 3 0:00 10.23% cc ... where top on the host just shows 100% bhyve 100% busy on 4 threads. On Fri, Jul 21, 2017 at 6:43 PM, Zaphod Beeblebrox wrote: > Since I found out that I can't run a Samba directory server in a jail, > I've had the setup of a bhyve on my list. I had toyed with Bhyve 6 or 8 > months ago, and still had the images, so I zfs cloned one and set about a > source upgrade. > > This ignomineously hung. > > So... I upgraded the host to 11.1-RC3, and I reinstalled a fresh guest > from the 11.1-RC3 install CD. The guest uses UFS2 on a 40G disk, the > server is an AMD 9590 with 32G RAM and a 40T ZFS array. > > After installation, I started the guest again with 1G ram, 4 processors > (of the 8 on the source CPU) and tried a buildworld again. This time the > guest crashed and rebooted. > > What should be next steps here? This is repeatable. The host is stable > (it can makeworld -j32 in about 25 minutes ... so it's hardware seems > good). Is this an AMD bug? Is it bad to use ZFS ZVols? > From owner-freebsd-virtualization@freebsd.org Fri Jul 21 23:01: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 C6D61C09C70 for ; Fri, 21 Jul 2017 23:01:11 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c: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 5AB092157 for ; Fri, 21 Jul 2017 23:01:11 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id w191so18398763wmw.1 for ; Fri, 21 Jul 2017 16:01:11 -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; bh=MJDcpaS9pKVqmStnIzJQinweHSslmffPjiUSfrfmdY4=; b=h7ZdXeHTftde/g0WibFkLO7hvuS8ANNF/d5g/ArXqtq/eyHRFOn4mUgackCew4dQ0L d9/xCWix7XsNoMEo0OfbXnqsqzLnOfNQL3fRUg1C0pG6XnJGK8MpRfwhUUtmIn1wHUVc SsBoEZdMxKnFWmddPgpv58qLS3+jTVpJNsytm4AiNgMV//3fXm9jhvsWJjWKKAXH8vAq kv7NcHFQDfQ3EbmckSjzORf7DIx+1PZ3BW78WTzeJYUbW9YQi+/4EYyhmnRkM4AVY2qK vQih+8wuKbjJ9HtJVI8A1y66Zml9IqLddC2nyJ07a3puogE1weGPhhILDLBnlVmUQy1R K9xQ== 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; bh=MJDcpaS9pKVqmStnIzJQinweHSslmffPjiUSfrfmdY4=; b=NdHdZXSy4OH33h29hBz3H5M/LILZYmsrsj0Ptn23lPaDedJ7H8ggEAaqwQeUnHTMLz LObH2WrASGjknAYCTaB+fvUQPlXXzWe4Bt62I7sBk07rr/AOKRQYsQFV9NLwwDICGIoX j88V3Dv9tJW4J28I3JAFPKp7n+hHqDS2Xi3x/9t6N29X8Rfu1I7c6CfCGxwZV0cGrzMM WYAobOfiOgwfDZH1kOLoM+B/igAeoDIy4FjzYRzLZ2BcJU5jT9hLP25e2NECIcaStp3n dfE2q0q/UHyLrX6XHLQFaYpSur0tGvxMX5SBLVomY4AjfQDGvtEZ2ir5R0t525S9RRFn piQg== X-Gm-Message-State: AIVw111/X9axOYwui5G/zU6EhACwLAamjlSSVy3RtbTXImwf2pWbEXHj LQdNzBuAfLPKdfItrKIevVk1xwhcgYIK X-Received: by 10.80.158.168 with SMTP id a37mr7089102edf.169.1500678069355; Fri, 21 Jul 2017 16:01:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.220.8 with HTTP; Fri, 21 Jul 2017 16:01:08 -0700 (PDT) In-Reply-To: References: From: Zaphod Beeblebrox Date: Fri, 21 Jul 2017 19:01:08 -0400 Message-ID: Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) To: "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: Fri, 21 Jul 2017 23:01:11 -0000 oh ... and ... the console spit out: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4522, size: 8192 (swap is on a separate zVol). On Fri, Jul 21, 2017 at 6:59 PM, Zaphod Beeblebrox wrote: > ... curiously, top running on the guest reveals (the point at which the > bhyve wedges): > > 88722 root 1 52 0 109M 105M pfault 3 0:03 42.37% > llvm-tblgen > 88687 root 1 52 0 374M 347M pfault 2 0:04 38.24% > llvm-tblgen > 88668 root 1 52 0 236M 225M pfault 0 0:04 35.11% > llvm-tblgen > 88743 root 1 52 0 55460K 26392K pfault 3 0:00 10.23% cc > > ... where top on the host just shows 100% bhyve 100% busy on 4 threads. > > > On Fri, Jul 21, 2017 at 6:43 PM, Zaphod Beeblebrox > wrote: > >> Since I found out that I can't run a Samba directory server in a jail, >> I've had the setup of a bhyve on my list. I had toyed with Bhyve 6 or 8 >> months ago, and still had the images, so I zfs cloned one and set about a >> source upgrade. >> >> This ignomineously hung. >> >> So... I upgraded the host to 11.1-RC3, and I reinstalled a fresh guest >> from the 11.1-RC3 install CD. The guest uses UFS2 on a 40G disk, the >> server is an AMD 9590 with 32G RAM and a 40T ZFS array. >> >> After installation, I started the guest again with 1G ram, 4 processors >> (of the 8 on the source CPU) and tried a buildworld again. This time the >> guest crashed and rebooted. >> >> What should be next steps here? This is repeatable. The host is stable >> (it can makeworld -j32 in about 25 minutes ... so it's hardware seems >> good). Is this an AMD bug? Is it bad to use ZFS ZVols? >> > > From owner-freebsd-virtualization@freebsd.org Fri Jul 21 23:03:55 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 292B3C09E97 for ; Fri, 21 Jul 2017 23:03:55 +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 DD6E722B7 for ; Fri, 21 Jul 2017 23:03:54 +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 31BE9204092E for ; Sat, 22 Jul 2017 09:03:52 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 2AB86281C3B for ; Sat, 22 Jul 2017 09:03:52 +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 FAhvFj3Qjask for ; Sat, 22 Jul 2017 09:03:52 +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 7A394280F8B; Sat, 22 Jul 2017 09:03:51 +1000 (AEST) Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) To: Zaphod Beeblebrox References: From: Peter Grehan Cc: "freebsd-virtualization@freebsd.org" Message-ID: <792ad5df-9e03-a332-c9a1-0b04ba69786a@freebsd.org> Date: Fri, 21 Jul 2017 16:03:49 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: 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.2 cv=XKlAcUpE c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=IkcTkHD0fZMA:10 a=G3gG6ho9WtcA:10 a=fXAUDZ2eGBcBujxDsqUA:9 a=QEXdDO2ut3YA:10 wl=host:3 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, 21 Jul 2017 23:03:55 -0000 > oh ... and ... the console spit out: > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4522, size: 8192 > > (swap is on a separate zVol). Ok - you may have hit a separate issue. Is ZFS ARC limited on your setup ? If bhyve and ZFS (and other consumers) end up fighting for memory, everyone loses :( A general rule of thumb is to limit ARC to less than the bhyve VM usage + a few additional gig for the base system. The FreeBSD default of giving ZFS all memory minus 1GB doesn't work too well when running VMs. later, Peter. From owner-freebsd-virtualization@freebsd.org Sat Jul 22 00:48:36 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 39ADBC31C69 for ; Sat, 22 Jul 2017 00:48:36 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B912863BCD; Sat, 22 Jul 2017 00:48:35 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id w126so23641516wme.0; Fri, 21 Jul 2017 17:48:35 -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=Eel3XeLoh8Rykhh6HeXgnvWW+sZZzrt8LnMJQUzBjtc=; b=qSzcH9KlkWTpzkDW1H74DiI8CV00C0Lvss0NGCOfhRDMDsNV3QRlCPaWU2c08pAwE2 ElnBnGSlNMjSODOeBMouulcm5/JTXtBDhrARVel0MfXJFTxiFwSzIKPPziKcVt3iG4FF NXajWC2mv1wYnnJX7XNV8N+Q+X2I/Wkfk8ZjhTL5AtLYiWP0lsrjAHRksc1jHz3yoNKk /uEKwj8mHgVDVjMQi7fMxelZV7HC1ikV2u+T21nwnDC4Hk26JGxSnEwSvkXh32jzP7+j 1YiUJwKeaIVU3en3txJCESBKj3QfMO0cBaF0Be7CFKSCAPs0Sk0by3ZjnNG3c6rKk8A+ 6K8w== 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=Eel3XeLoh8Rykhh6HeXgnvWW+sZZzrt8LnMJQUzBjtc=; b=QS3n72JerarXFDFFFuNxc2WTysptqO8nshVoetU6KC3uWldTjy1ewo/Fkj8eYI7K4x aY06PPV+NFT0hFMpKjktNLLXuwGBuSU+unmS2mHyTxIc9T0spyWA/508kmBSUB7MLUUX qNH72rxue+s5we7kPJc573Q99B2D34smdpIrWD294wTvoHQBcYiicfPIbdriZySVu91F A8KJHNyT6SindG9VWbkKi3gNydcr3IEGPSszXl0964y7G8XxlwgxG5NedjqQc183rTnu +qXFqW53a5hnWpMjk1Tp/7cj8aHx+6uOTqmhGlzg8bAI9PAUOs3K3uPw02y85Lk9FOS5 HUnw== X-Gm-Message-State: AIVw111Dj+nkBacn/vEy+QOQVnf8qJucmQsRqVX9MEJ5+CbKAcksXjxi Rf2kFhbfwHPcoMkXthis2SZEf1DDPsPF X-Received: by 10.80.175.130 with SMTP id h2mr890327edd.193.1500684514087; Fri, 21 Jul 2017 17:48:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.220.8 with HTTP; Fri, 21 Jul 2017 17:48:33 -0700 (PDT) In-Reply-To: <490d70e2-ff8b-2a60-2eb7-669dadbcc2a9@freebsd.org> References: <490d70e2-ff8b-2a60-2eb7-669dadbcc2a9@freebsd.org> From: Zaphod Beeblebrox Date: Fri, 21 Jul 2017 20:48:33 -0400 Message-ID: Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) To: Peter Grehan 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: Sat, 22 Jul 2017 00:48:36 -0000 I tried the -p 0:1 -p 1:2 -p 2:3 -p 3:4 bit. If I may say, it felt a little "chunky" ... but that could have just been a perception. Anyways... still hung the guest. On Fri, Jul 21, 2017 at 6:58 PM, Peter Grehan wrote: > Hi, > > What should be next steps here? This is repeatable. The host is stable >> (it can makeworld -j32 in about 25 minutes ... so it's hardware seems >> good). Is this an AMD bug? Is it bad to use ZFS ZVols? >> > > ZVols are fine. Is the guest panic a spinlock timeout ? > > I believe this is a bug in bhyve/SVM. It appears somewhat related to > processor speed (I can't repro on a 2.3GHz 8 CPU Opteron 6320, but can hit > it after 15 mins or so on a Ryzen 1700, with/without SMT). > > Anish and I are currently chasing this and have repros. An experiment you > could try is to run with the vCPUs pinned i.e. for a 4 vCPU guest, add the > options "-p 0:1 -p 1:2 -p 2:3 -p 3:4". > > later, > > Peter. > From owner-freebsd-virtualization@freebsd.org Sat Jul 22 00:50:57 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 31AB5C31D37 for ; Sat, 22 Jul 2017 00:50:57 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B90A263C82; Sat, 22 Jul 2017 00:50:56 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id w126so23660548wme.0; Fri, 21 Jul 2017 17:50:56 -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=+VZgIKdWSUgngl5pJjtNQhVontGunUJ2E1ds1wQP3JQ=; b=Mgel6c5bgIGjQssBKf2tCSPherHEV7qZCe6GDLIWT0mV81EELfeivAvV/DmOTkn9VD nlkyUBwDe4363TENz8HvReoPdjqDFNIRHQj1SmgBlsKPTYRESTntZNC33zRn6dM6o3j9 S7fn7oH+jPn/1n8GvOAvoeZUeLIe9PKq89liDKO/imTbOpDJANfABcG9MMj0IDMQwvK2 cEzJyAUQIQ9rfPUY8IvY1SGP8sUhNl/hMT2lQOfB+ZJhsn5Y4BwnBJ2RB6w2V91KlaBq KPC5KcmEitTCqRooo/gb0oJ0rwq0Dczw0ZxqXLI5N1y6aWG5KEM9uSK6dn5thzVCzBAi V6Dg== 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=+VZgIKdWSUgngl5pJjtNQhVontGunUJ2E1ds1wQP3JQ=; b=cxyEIlmO7DSq7ZxWCg0ReDOjtjcuUSOoYaLTKKLIssjj7anI+WbhvwgaOF+WscXjCc aOLbPpu94LSYvu+/b5/kYhxrLfDtSZCGZqG11PQ2mLrXKs/1ZAsWuS/FW/vmU1i6MTKS LVLGIy4loltAtkLGBGTNhm3OZ12C0rQagiWgGUzHXzkb6jgVJmGm7r2woHPP/NPdgQju AEKhc8KvbW4bziPGiWB68SCcuj6jHWowGDpKs3Nf+0EPTaeEunvuD4gXnWrpAIl2EGK5 OclY/mx3qDJ9Lqz6ofeaZIILc6ols9wFeHuMULHTccC/8AUDaYmCO9VntmjZT69GGN1G WORw== X-Gm-Message-State: AIVw111/FGdoV7e+HaAGIrlF4Dk90dd+2VAwLWvPhfGD+1GKGhzIFSnT blvizM0DtsflAqJJ2fD5vrHIqqvwxvek X-Received: by 10.80.154.131 with SMTP id p3mr7285043edb.181.1500684655221; Fri, 21 Jul 2017 17:50:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.220.8 with HTTP; Fri, 21 Jul 2017 17:50:54 -0700 (PDT) In-Reply-To: <792ad5df-9e03-a332-c9a1-0b04ba69786a@freebsd.org> References: <792ad5df-9e03-a332-c9a1-0b04ba69786a@freebsd.org> From: Zaphod Beeblebrox Date: Fri, 21 Jul 2017 20:50:54 -0400 Message-ID: Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) To: Peter Grehan 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: Sat, 22 Jul 2017 00:50:57 -0000 remember that the quoted problem is spit out by the guest, not the host. That said, the 'top' line on the frozen bhyve was: 29380 root 22 20 0 1060M 928M kqread 5 218:32 399.30% bhyve ... indicating that the bhyve had almost all it's memory... and the system had also 500M free when I checked it. On Fri, Jul 21, 2017 at 7:03 PM, Peter Grehan wrote: > oh ... and ... the console spit out: >> >> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4522, size: 8192 >> >> (swap is on a separate zVol). >> > > Ok - you may have hit a separate issue. Is ZFS ARC limited on your setup > ? If bhyve and ZFS (and other consumers) end up fighting for memory, > everyone loses :( A general rule of thumb is to limit ARC to less than the > bhyve VM usage + a few additional gig for the base system. > > The FreeBSD default of giving ZFS all memory minus 1GB doesn't work too > well when running VMs. > > later, > > Peter. > From owner-freebsd-virtualization@freebsd.org Sat Jul 22 00:55:01 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 C9F5FC31F7D for ; Sat, 22 Jul 2017 00:55:01 +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 82D6963F64 for ; Sat, 22 Jul 2017 00:55:01 +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 C54522040930 for ; Sat, 22 Jul 2017 10:54:58 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id BB0C32809DB for ; Sat, 22 Jul 2017 10:54:58 +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 KfU14nTjZT99 for ; Sat, 22 Jul 2017 10:54:58 +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 084342808FF; Sat, 22 Jul 2017 10:54:57 +1000 (AEST) Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) To: Zaphod Beeblebrox Cc: "freebsd-virtualization@freebsd.org" References: <792ad5df-9e03-a332-c9a1-0b04ba69786a@freebsd.org> From: Peter Grehan Message-ID: Date: Fri, 21 Jul 2017 17:54:54 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: 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.2 cv=XKlAcUpE c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=IkcTkHD0fZMA:10 a=G3gG6ho9WtcA:10 a=v-JuLcLaPmpdCNLVT_EA:9 a=QEXdDO2ut3YA:10 wl=host:3 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, 22 Jul 2017 00:55:01 -0000 > remember that the quoted problem is spit out by the guest, not the host. > > That said, the 'top' line on the frozen bhyve was: > > 29380 root 22 20 0 1060M 928M kqread 5 218:32 399.30% bhyve > > ... indicating that the bhyve had almost all it's memory... and the > system had also 500M free when I checked it. Are you using a "-j" option to buildworld in the guest ? You'd need at least 1G for each vCPU when doing parallel builds (and preferably a bit more) or you will swap heavily. later, Peter. From owner-freebsd-virtualization@freebsd.org Sat Jul 22 01:21:14 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 13008C78E40 for ; Sat, 22 Jul 2017 01:21:14 +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 C5E7664BAC for ; Sat, 22 Jul 2017 01:21:13 +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 2C0A2204042B for ; Sat, 22 Jul 2017 11:21:12 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 23DB1280F8B for ; Sat, 22 Jul 2017 11:21:12 +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 MHciA1-uV-ED for ; Sat, 22 Jul 2017 11:21:12 +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 22A972809A2; Sat, 22 Jul 2017 11:21:10 +1000 (AEST) Subject: Re: Bhyve Broken: whose fault (AMD, FreeBSD, ZFS ...?) From: Peter Grehan To: Zaphod Beeblebrox Cc: "freebsd-virtualization@freebsd.org" References: <792ad5df-9e03-a332-c9a1-0b04ba69786a@freebsd.org> Message-ID: <50047e9f-de8d-e94a-35d1-e3a7bcf7a0fd@freebsd.org> Date: Fri, 21 Jul 2017 18:21:06 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: 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.2 cv=XKlAcUpE c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=IkcTkHD0fZMA:10 a=G3gG6ho9WtcA:10 a=fkTWZIAttzpCodc6tDkA:9 a=QEXdDO2ut3YA:10 wl=host:3 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, 22 Jul 2017 01:21:14 -0000 On 7/21/17 5:54 PM, Peter Grehan wrote: >> remember that the quoted problem is spit out by the guest, not the host. >> >> That said, the 'top' line on the frozen bhyve was: >> >> 29380 root 22 20 0 1060M 928M kqread 5 218:32 399.30% >> bhyve >> >> ... indicating that the bhyve had almost all it's memory... and the >> system had also 500M free when I checked it. > > Are you using a "-j" option to buildworld in the guest ? You'd need at > least 1G for each vCPU when doing parallel builds (and preferably a bit > more) or you will swap heavily. I should add: I'm not saying this will fix the problem, but if it is an issue with the guest swapping, giving the guest more RAM is a workaround. later, Peter.