From owner-freebsd-virtualization@freebsd.org Sun Oct 21 16:01:54 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 F29BAFF7CB2 for ; Sun, 21 Oct 2018 16:01:53 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 805DD93EE2 for ; Sun, 21 Oct 2018 16:01:53 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9LG1n7T005685; Sun, 21 Oct 2018 09:01:49 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9LG1nFh005684; Sun, 21 Oct 2018 09:01:49 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810211601.w9LG1nFh005684@pdx.rh.CN85.dnsmgr.net> Subject: Re: bhyve uefi="csm" In-Reply-To: To: Jason Barbier Date: Sun, 21 Oct 2018 09:01:49 -0700 (PDT) CC: Victor Sudakov , freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 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, 21 Oct 2018 16:01:54 -0000 > Can you tell us a bit about your set up, like are you using helper scripts like libvirt? > To answer the question you asked when I run a vm with the CSM firmware it works for me. You should always be able to boot a vm that uses and boots with the non CSM uefi firmware with the CSM version of the firmware, failures may start to show up if your booting something that is either purely legacy, or efi aware but falls back to csm because it didnt like something. The older ED2K uefi that we are using and some of the hatchetry that was used to craft its CSM are in a poor state and could use some love. > > > > On Oct 20, 2018, at 10:39 PM, Victor Sudakov wrote: > > > > Dear Colleagues, > > > > Has anyone been able to boot *anything* with uefi="csm"? > > > > Can you please share at least one success story? > > > > -- > > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > > 2:5005/49@fidonet http://vas.tomsk.ru/ > > _______________________________________________ > > 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" > > _______________________________________________ > 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" > -- Rod Grimes rgrimes@freebsd.org