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.