From owner-freebsd-virtualization@freebsd.org Wed Feb 28 14:31:05 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 A3429F2A656 for ; Wed, 28 Feb 2018 14:31:05 +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 27CB27994F; Wed, 28 Feb 2018 14:31:04 +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 w1SEV1bq020478; Wed, 28 Feb 2018 06:31:01 -0800 (PST) (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 w1SEV1JC020477; Wed, 28 Feb 2018 06:31:01 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201802281431.w1SEV1JC020477@pdx.rh.CN85.dnsmgr.net> Subject: Re: Re[2]: Migrate from real server to virtual In-Reply-To: <1519797493.7978147.fd786v89@frv52.fwdcdn.com> To: wishmaster Date: Wed, 28 Feb 2018 06:31:01 -0800 (PST) CC: Peter Grehan , "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.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: Wed, 28 Feb 2018 14:31:05 -0000 > --- Original message --- > From: "Peter Grehan" > Date: 27 February 2018, 20:40:52 > > > > > > But I think the bigger problem is that this is an MBR disk > > > with Windows 7 in it, I > > > do not believe that bhyve can run Windows 7 at this time. So let me correct that statement with the new information. I do not believe that bhyve can run an MBR Windows 7 install at this time, as that would indicated the install is not UEFI bootable, and we can only boot Windows 7 64 bit in EFI mode. > > > > Bhyve has been able to run Win7 since 2015, though x64 only and in > > UEFI mode. > > > > Yes, Windows 7 is from the same "brunch" as Windows 2008. And I > think my problem is that hardware server has been installed > without UEFI, just in Legacy mode. > So, in this situation it is unable run this server in Bihyve with UEFI. > > Am I right? Yes, I do believe that is the correct conclusion to your current situation. The other part that could be at issue here is if this is a 32bit or 64bit version of windows. As Peter stated only 64 bit windows in UEFI mode. It might be possible to create a shim drive that has the Windows UEFI boot code on it, and set that shim drive up to load the copy of windows from your image file. This would be a experiment that might lead to a booting VM. It may also be possible to remove the legacy bootmgr files from the disk0.img and add the needed uefi files, I gave some commands in a prior email that would allow you to mount this disk on the FreeBSD system to facilitate this type of work. -- Rod Grimes rgrimes@freebsd.org