From owner-freebsd-virtualization@freebsd.org Sun Apr 3 14:26:19 2016 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 C9E0FB006BD for ; Sun, 3 Apr 2016 14:26:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B94E11A3D for ; Sun, 3 Apr 2016 14:26:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u33EQJ8j093042 for ; Sun, 3 Apr 2016 14:26:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 203820] kernel panic when trying to unload vmm(4) and VirtualBox VMs are running Date: Sun, 03 Apr 2016 14:26:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nospam@ofloo.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.21 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, 03 Apr 2016 14:26:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203820 nospam@ofloo.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nospam@ofloo.net --- Comment #7 from nospam@ofloo.net --- FreeBSD 10.2-RELEASE-p14 #13 r296979 I have had the same issue running kldunload vmm crashed my server and I'm running virtualbox as well. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sun Apr 3 21:00:55 2016 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 4E456B00BB4 for ; Sun, 3 Apr 2016 21:00:55 +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 2D2041765 for ; Sun, 3 Apr 2016 21:00:55 +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 u33L01wv097496 for ; Sun, 3 Apr 2016 21:00:55 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201604032100.u33L01wv097496@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, 03 Apr 2016 21:00:55 +0000 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 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, 03 Apr 2016 21:00:55 -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 ------------+-----------+--------------------------------------------------- In Progress | 202321 | [bhyve,patch] More verbose error reporting in bhy New | 202322 | [bhyve,patch] add option to have bhyve write its 2 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Mon Apr 4 17:19:12 2016 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 E415DB036BF for ; Mon, 4 Apr 2016 17:19:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D413F1068 for ; Mon, 4 Apr 2016 17:19:12 +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 u34HJC6w080841 for ; Mon, 4 Apr 2016 17:19:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 203820] kernel panic when trying to unload vmm(4) and VirtualBox VMs are running Date: Mon, 04 Apr 2016 17:19:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhb@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.21 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, 04 Apr 2016 17:19:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203820 --- Comment #8 from John Baldwin --- To be clear, yes, this is not a supported configuration (having both vmm.ko= and virtualbox's module loaded at the same time, much less unloading one while = the other is running). I don't expect there to be a "fix" for this anytime soo= n, but if there is one it will consist of making vmm.ko fail to load if virtual box is loaded and vice versa. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 4 17:21:02 2016 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 2CF8CB03735 for ; Mon, 4 Apr 2016 17:21:02 +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 1D74D11F8 for ; Mon, 4 Apr 2016 17:21:02 +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 u34HL1Iv084804 for ; Mon, 4 Apr 2016 17:21:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 203820] kernel panic when trying to unload vmm(4) and VirtualBox VMs are running Date: Mon, 04 Apr 2016 17:21:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nospam@ofloo.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 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, 04 Apr 2016 17:21:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203820 --- Comment #9 from nospam@ofloo.net --- What about loading virtualboxes into bhyve kernels? I haven't tried it but would that be acceptable? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 4 18:35:41 2016 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 CF96FB02D44 for ; Mon, 4 Apr 2016 18:35:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BEB5415E8 for ; Mon, 4 Apr 2016 18:35:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u34IZfIL034835 for ; Mon, 4 Apr 2016 18:35:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 203820] kernel panic when trying to unload vmm(4) and VirtualBox VMs are running Date: Mon, 04 Apr 2016 18:35: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: 10.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ilavsky.martin@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: 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.21 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, 04 Apr 2016 18:35:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203820 --- Comment #10 from martin ilavsky --- >From my point of view it was important to know why it crashed. Deeper investigation showed where and why. That was important to me.=20 Kernel level API like on OS X would be appreciated feature .. but I get that priority is somewhere else. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 4 22:53:27 2016 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 7E527B03791 for ; Mon, 4 Apr 2016 22:53:27 +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 6EA3113AC for ; Mon, 4 Apr 2016 22:53:27 +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 u34MrRZO051030 for ; Mon, 4 Apr 2016 22:53:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 203820] kernel panic when trying to unload vmm(4) and VirtualBox VMs are running Date: Mon, 04 Apr 2016 22:53:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhb@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.21 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, 04 Apr 2016 22:53:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203820 --- Comment #11 from John Baldwin --- (In reply to nospam from comment #9) Do you mean kldloading virtual box in an instance of FreeBSD running in a b= hyve VM? I think that will just not work as bhyve doesn't let the guest see any= of the VT-x capabilities of the CPU since it doesn't support nested VT-x. The reverse might work if VirtualBox supports nested VT-x (I haven't tried). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 5 08:17:11 2016 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 ED315B03704 for ; Tue, 5 Apr 2016 08:17:11 +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 DDAD61259 for ; Tue, 5 Apr 2016 08:17:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u358HBXV026642 for ; Tue, 5 Apr 2016 08:17:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 203820] kernel panic when trying to unload vmm(4) and VirtualBox VMs are running Date: Tue, 05 Apr 2016 08:17:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nospam@ofloo.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 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, 05 Apr 2016 08:17:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203820 --- Comment #12 from nospam@ofloo.net --- No I've tried the reverse because when I wanted to play with bhyve, I insta= lled virtualbox to do so, but that didn't work at all. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Apr 7 07:08:41 2016 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 6043BB0630B for ; Thu, 7 Apr 2016 07:08:41 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 3E02E10A7 for ; Thu, 7 Apr 2016 07:08:41 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id AB05F15BBD; Thu, 7 Apr 2016 07:08:40 +0000 (UTC) Date: Thu, 7 Apr 2016 07:08:40 +0000 To: freebsd-virtualization@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D5291+333+9e687f0ec04aca99@reviews.freebsd.org Subject: [Differential] [Abandoned] D5291: hyperv/vmbus: Select an IDT vector has lower priority than LAPIC timer and IPIs vectors Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D5291: hyperv/vmbus: Select an IDT vector has lower priority than LAPIC timer and IPIs vectors X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: M2VhMjA1ZWQ4ODNjZTIxMmJiYjJmZGJiYWNkIFcGB3g= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 07:08:41 -0000 sepherosa_gmail.com abandoned this revision. REVISION DETAIL https://reviews.freebsd.org/D5291 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, adrian, delphij, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, royger Cc: freebsd-virtualization-list From owner-freebsd-virtualization@freebsd.org Thu Apr 7 22:28:37 2016 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 6E42AB08EAA for ; Thu, 7 Apr 2016 22:28:37 +0000 (UTC) (envelope-from luislupe@gmail.com) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D4641356 for ; Thu, 7 Apr 2016 22:28:37 +0000 (UTC) (envelope-from luislupe@gmail.com) Received: by mail-ig0-x22e.google.com with SMTP id f1so551979igr.1 for ; Thu, 07 Apr 2016 15:28:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=2Ypns8eA5VFSktMbhIU9EdT8zPz0rdMeL2WR+Qvr1/Q=; b=fulnvxgA6rAteZV8Z4mbcYDuVkQeX0xWJpivkx9JiTEqh3jR8nt+r47bonL8dMtGW1 tIGx1Fs9cByYHiHx5/M7ez7RFcRYzDL3WvyupREKHJB+frOPyxWCSqvf3AgoJ/2IDfJS JHngsXOII2Va7HSFfuvptr/oIpUuynVOfmLLkBiK+Y9jxOGN2352TZibbS7L0iuvcOS/ 7p0LjspoPWJAjo6EA53W4L3GeBk6gvOz2n2sTEgxtg4V9xMODugXFYjM8xbcl9Gbswqd 2BzP2yyCb7lQAjWCK5HxHf9Tf2gKS/XStSu81imbf1KtIBYVuSsZ/DWJ2fkNst4iCDrr FBnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=2Ypns8eA5VFSktMbhIU9EdT8zPz0rdMeL2WR+Qvr1/Q=; b=GDcn9zgPQ8xBY5B0v+YapgNdiDmy6ENPWcapglpuaAiOcMJWoYM4g2YLPtUt9mw2rT DuupgKrOCkxABjR0IG3UCubOYbO2jzi1ay0uO68MbRJYdOgCPManA++KwqQWNvF94fEo mUsmM/6D1CL1R/KIPFH5/0+nCWRouXEPvwcI2SBg6qn6abCTqi8XL6s9Z+TAp0Y3UzCR 5N88KSQR6Eu9prU1vT62v7tuze/3ySv6K8VBPSdMRLm5iPwaPx3dwZKFX/YJV9UqLPhS 1tvu0sBDkS77CRa6p61jsh1dR0J+wLmvdhM3UlCscoMYlZEL+5xm5FqW0TwsIHr7bO8K coSQ== X-Gm-Message-State: AD7BkJI6pI1/1QoZVKr5aBzDnhtOcbLsTUtGWp5P0ZPT+coxB0ts/ZiROnaT9AcNVdXEHmHE6pt95Y0oDZileA== MIME-Version: 1.0 X-Received: by 10.50.8.101 with SMTP id q5mr133588iga.22.1460068116623; Thu, 07 Apr 2016 15:28:36 -0700 (PDT) Received: by 10.36.123.19 with HTTP; Thu, 7 Apr 2016 15:28:36 -0700 (PDT) Date: Thu, 7 Apr 2016 23:28:36 +0100 Message-ID: Subject: bhyve with Linuxes as guests - shared filesystem From: "Luis P. Mendes" To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 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, 07 Apr 2016 22:28:37 -0000 Hi, In a FreeBSD host, I'm running a Slackware Linux guest. I'd like to share a `zfs` filesystem between those two OSes and with one other Ubuntu Linux system to be installed. There are three options that I can think of: 1. Have a `virtio-blk` option to `bhyve` and loading `zfs` modules for the Linux OSes. 2. Share the filesystem through `nfs` 3. Share it through `samba` For `1.`, the disadvantages I see are: a. `zfs` would have to run in the two Linux OSes in user mode. b. it would consume much RAM to have three `zfs` managers running at the same time. For `2.`, I don't see any disadvantage. Regarding `3.`, as I don't use Windows, it doesn't seem to offer any advantage over `2.`. Hence my question: regarding the experience many of you have with shared file systems between FreeBSD and Linux systems, what do you have to say about reliability (locks, ...) and performance(1) of the options presented, or even of other ones. Luis PS (1). I know I should do performance tests myself but would like to hear from your experience. From owner-freebsd-virtualization@freebsd.org Thu Apr 7 22:40:57 2016 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 DCC7BB0715E for ; Thu, 7 Apr 2016 22:40:57 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-ob0-x241.google.com (mail-ob0-x241.google.com [IPv6:2607:f8b0:4003:c01::241]) (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 AD07E1829 for ; Thu, 7 Apr 2016 22:40:57 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-ob0-x241.google.com with SMTP id js7so4501233obc.0 for ; Thu, 07 Apr 2016 15:40:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=h8wTVq2I2at1bGd6Zdj2Tk6k2i/VNlaEZgiRpUHzYwM=; b=O7TnjDIQeVR8gLkliizBEHZWZ/olQinnSAgA/ebDjvLtOsG0E1UTo32D5XjK2e/lPo t01Cbrj0GHNBcL1h+kS3IdCgYdxT42DecPnTC2AJb+Btva6E29fdPNHytm22YsMItv0w oYvyBBS2QHR07JHXFbYNAMPYZW9tR5SrTMOptBqDgYPzI80i+LqJAsfO/No+FsXXuAbV oKcPmO5tkR/5iXvS9LioOBH2BoDLHeogBvJN5/kdzNacWfI1MCoVCjs7cvUevvPGCjJK 0PsM7EMx/wCXe5NZZGsqT4W3c3pnggZfA8KTySEk3gjs1VvKnXRVUCfhX2x/nv2lYwXd 8jew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=h8wTVq2I2at1bGd6Zdj2Tk6k2i/VNlaEZgiRpUHzYwM=; b=EAnvbTLx5sknNscin330Ga9tkt9Cb4JhguzFj0Q2PuEtJUgnLLX4mNqod1X+yLwYIZ SAt5r8Lt7ASFYCprFYxlB0zuUTphWHa44gm6tggebPCv2/pjrFQxRgJzJuzckXXQFPQe ggdqQTDVT26nSAWJ6+zJ1WeEFBdLWaJdVDecwbp3MIgJuJ+bkutIivX5k/Nybg96s8rN mX02vwm1xcu5WBU66nr95aE5FPVf9ikf8hDJenRE0aUJxt6fcF1fOZFNQXo+aNkQlkXZ oolceVH2g2ey/5dXo7FKEV2CX3pS7wLR98O8mILnwc0cF9XzZ9Z8evDZjzQN68Z+f2A5 FxWg== X-Gm-Message-State: AD7BkJIgOH0vgENs34eDcavW3nf7pQKJAk8XDBPDrmQEnU91uHEQJ9teO3ovd0TeRjdPg8hLLP4rYYl/5X6FRg== X-Received: by 10.182.49.168 with SMTP id v8mr2790938obn.48.1460068857042; Thu, 07 Apr 2016 15:40:57 -0700 (PDT) MIME-Version: 1.0 Sender: jtubnor@gmail.com Received: by 10.202.206.202 with HTTP; Thu, 7 Apr 2016 15:40:37 -0700 (PDT) In-Reply-To: References: From: Jason Tubnor Date: Fri, 8 Apr 2016 08:40:37 +1000 X-Google-Sender-Auth: YqojMplrXATuj5PJFmOkjbPhjGI Message-ID: Subject: Re: bhyve with Linuxes as guests - shared filesystem To: "Luis P. Mendes" Cc: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 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, 07 Apr 2016 22:40:58 -0000 1. Won't work if you want them to access concurrently (unless there is some new funky cluster feature I'm not aware of) 2. Probably best option for compatibility across the board without 'extra' drivers needed, maybe an issue if you have a Windows guest later on. Performance considerations needed if there is high IO expected. 3. Yeah, samba, hmm, unless you are doing Windows, I'd stay away. Cheers, Jason. On 8 April 2016 at 08:28, Luis P. Mendes wrote: > Hi, > > In a FreeBSD host, I'm running a Slackware Linux guest. I'd like to > share a `zfs` filesystem between those two OSes and with one other > Ubuntu Linux system to be installed. There are three options that I > can think of: > > 1. Have a `virtio-blk` option to `bhyve` and loading `zfs` modules for > the Linux OSes. > 2. Share the filesystem through `nfs` > 3. Share it through `samba` > > For `1.`, the disadvantages I see are: > a. `zfs` would have to run in the two Linux OSes in user mode. > b. it would consume much RAM to have three `zfs` managers running at > the same time. > > For `2.`, I don't see any disadvantage. > Regarding `3.`, as I don't use Windows, it doesn't seem to offer any > advantage over `2.`. > > Hence my question: regarding the experience many of you have with > shared file systems between FreeBSD and Linux systems, what do you > have to say about reliability (locks, ...) and performance(1) of the > options presented, or even of other ones. > > > Luis > > PS (1). I know I should do performance tests myself but would like to > hear from your experience. > _______________________________________________ > 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" > > From owner-freebsd-virtualization@freebsd.org Fri Apr 8 22:28:22 2016 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 D7DDAB09136 for ; Fri, 8 Apr 2016 22:28:22 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 9FD0A133D for ; Fri, 8 Apr 2016 22:28:22 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 76BB94FB57; Fri, 8 Apr 2016 22:28:20 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u38MSJXV000724; Fri, 8 Apr 2016 22:28:19 GMT (envelope-from phk@phk.freebsd.dk) To: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= cc: Neel Natu , "freebsd-virtualization@freebsd.org" Subject: Re: -current host, 10.1 client loops In-reply-to: From: "Poul-Henning Kamp" References: <20918.1458052609@critter.freebsd.dk> <23329.1458077441@critter.freebsd.dk> <28223.1458163559@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <722.1460154499.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Fri, 08 Apr 2016 22:28:19 +0000 Message-ID: <723.1460154499@critter.freebsd.dk> X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 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, 08 Apr 2016 22:28:22 -0000 -------- In message , =3D?UTF-8?Q?Olivier_Cochard=3D2DLabb=3DC3=3DA9?=3D writes: With the host now running: FreeBSD 11.0-CURRENT #0 r297514M And (another) i386 guest running: FreeBSD 11.0-CURRENT #3 r297721M I do not see the problem. I'm going to try the 10.1/i386 guest over the weekend. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .