From owner-freebsd-virtualization@freebsd.org Mon Jul 4 14:31:50 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 7FDC1B9136D for ; Mon, 4 Jul 2016 14:31:50 +0000 (UTC) (envelope-from nbe@renzel.net) Received: from nijmegen.renzel.net (mx1.renzel.net [195.243.213.130]) by mx1.freebsd.org (Postfix) with ESMTP id 476022AA3 for ; Mon, 4 Jul 2016 14:31:49 +0000 (UTC) (envelope-from nbe@renzel.net) Received: from dublin.vkf.isb.de.renzel.net (unknown [10.0.0.80]) by nijmegen.renzel.net (smtpd) with ESMTP id B843F141486E for ; Mon, 4 Jul 2016 16:22:42 +0200 (CEST) Received: from asbach.renzel.net (unknown [172.18.96.1]) by dublin.vkf.isb.de.renzel.net (Postfix) with ESMTP id AFDDAAC635 for ; Mon, 4 Jul 2016 16:22:42 +0200 (CEST) From: Nils Beyer To: freebsd-virtualization@freebsd.org Subject: bhyve: UEFI - preserve NVRAM between host system reboots? Date: Mon, 04 Jul 2016 16:22:42 +0200 Message-ID: <3164202.pIQMtlYQLk@asbach.renzel.net> Organization: VKF Renzel GmbH User-Agent: KMail/4.14.10 (FreeBSD/11.0-ALPHA6; KDE/4.14.10; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Virus-Scanned: clamav-milter 0.98 at nijmegen.renzel.net X-Virus-Status: Clean X-Spam-Status: No, score=-8.0 required=7.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on nijmegen.renzel.net X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 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 Jul 2016 14:31:50 -0000 Hi, is it somehow possible to preserve the contents of the NVRAMs of the VMs bet- ween host system reboots? "bhyvectl --destroy" kills them, too... Thanks in advance and regards, Nils