From owner-freebsd-virtualization@freebsd.org  Fri Sep 28 17:10:21 2018
Return-Path: <owner-freebsd-virtualization@freebsd.org>
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 1AEDE10B51B7
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Fri, 28 Sep 2018 17:10:21 +0000 (UTC)
 (envelope-from ghislain@ghislain.net)
Received: from mail02.aqueos.net (mail02.aqueos.net [94.125.164.53])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A7B607A876
 for <freebsd-virtualization@freebsd.org>; Fri, 28 Sep 2018 17:10:20 +0000 (UTC)
 (envelope-from ghislain@ghislain.net)
Received: from localhost (localhost [127.0.0.1])
 by mail02.aqueos.net (Postfix) with ESMTP id EF7CC5CE7D7
 for <freebsd-virtualization@freebsd.org>;
 Fri, 28 Sep 2018 19:10:18 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mail02.aqueos.net
Received: from mail02.aqueos.net ([127.0.0.1])
 by localhost (mail02.aqueos.net [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id LjY_Ac_dmqdm for <freebsd-virtualization@freebsd.org>;
 Fri, 28 Sep 2018 19:10:18 +0200 (CEST)
Received: from [192.168.200.223] (adsl2.aqueos.com [81.56.195.31])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail02.aqueos.net (Postfix) with ESMTPSA id E11DD5CE744
 for <freebsd-virtualization@freebsd.org>;
 Fri, 28 Sep 2018 19:10:17 +0200 (CEST)
Subject: Re: New bhyve user
To: freebsd-virtualization@freebsd.org
References: <201809281630.w8SGUuB4078064@pdx.rh.CN85.dnsmgr.net>
From: ghislain <ghislain@ghislain.net>
Message-ID: <1f83e1d4-5356-beec-f67e-b0caa659ed78@ghislain.net>
Date: Fri, 28 Sep 2018 19:10:18 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <201809281630.w8SGUuB4078064@pdx.rh.CN85.dnsmgr.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: fr
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Sep 2018 17:10:21 -0000

> It is all a mater of Load, as long as your host load stays
> below the number of CPU threads you actually have things
> in this aspect tend to work just fine.  And if you do exceed
> this everyone slows down in a fairly fair fashion.
>

> well virtualisation is used for a lot of things but if you want to 
> isolate things you do not want a rogue VM taking all cpu so sharing 
> cpu in the current state is a risk as the policeman that is the kernel 
> do not seems to know bhyve guests :) (i speak conditionnal as i dont 
> use it myself i am just curious).


Ghislain.