From owner-freebsd-virtualization@freebsd.org Mon Nov 2 17:47:55 2015 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 38307A2455A for ; Mon, 2 Nov 2015 17:47:55 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-lf0-x243.google.com (mail-lf0-x243.google.com [IPv6:2a00:1450:4010:c07::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A76461CD8 for ; Mon, 2 Nov 2015 17:47:54 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by lfgh9 with SMTP id h9so1968765lfg.0 for ; Mon, 02 Nov 2015 09:47:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=SxmRerEK6PxSPKZkXwBwOnvV5cLmUyYHpiriwNJPm88=; b=ANwDsAhblI3oApeATQyNSYK7FBF2vHmAoFLmiwrMXbjKy/aflHTBXUjzlS3MGYHwE6 eXv8iJpBwuTB0HW82vfb8b0UQmdzrTlb5lkGFE3Gt0f8Pu19yT/Zk+xoSXl12M4qDH+h KX+KUOVauRTmbVMv1f+bpURDkrPYkAIsZ8hoSuy4/w9770d/kHwiWAcTuRWYySkjabfA vLqdxNGIA7ijYjwluR84pAjvBqWXJOgAISeka8hauKoMcNQMBD6rqpgwR3lMAsS5CY0r UPTiM1B5DnDe/bUHuSFn0/WyzeZoZXelqHYkUPbFJhyqILn+UjgwU0+wLLCCTsXUQN0Z gAyA== X-Received: by 10.25.152.131 with SMTP id a125mr7334003lfe.13.1446486472783; Mon, 02 Nov 2015 09:47:52 -0800 (PST) Received: from kloomba.lvv.mirantis.net ([217.65.211.58]) by smtp.gmail.com with ESMTPSA id m124sm1584499lfd.40.2015.11.02.09.47.51 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Nov 2015 09:47:52 -0800 (PST) Sender: Roman Bogorodskiy Date: Mon, 2 Nov 2015 20:47:49 +0300 From: Roman Bogorodskiy To: Trent Thompson Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve -l bootrom problem Message-ID: <20151102174748.GC18899@kloomba.lvv.mirantis.net> References: <20151102171356.GB18899@kloomba.lvv.mirantis.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eHhjakXzOLJAF9wJ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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, 02 Nov 2015 17:47:55 -0000 --eHhjakXzOLJAF9wJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Trent Thompson wrote: > According to the bhyve/Windows wiki: https://wiki.freebsd.org/bhyve/Windo= ws > The lpc slot needs to be in slot 31, and the block devices bust be in 3, = 4, > 5, and 6. > I have had luck* booting into the Debian install environment using this > method, as long as you pass "console=3DttyS0" to grub at boot time. I bel= ieve > you must do the same as well on FreeBSD, with adding the ability to use a > console in /boot/loader.conf >=20 > *I have installed Debian VMs utilizing UEFI, however I have not had succe= ss > after destroying the VM. > They fail to boot and drop you to that fancy EFI shell. Hm... changing pci slot numbers doesn't seem to change anything: sudo /usr/sbin/bhyve -l bootrom,/home/novel/uefi/BHYVE_UEFI_20151002.fd -c 2 -m 512 -A -I -u -H -P -s 0:0,hostbridge -s 3:0,ahci-hd,/home/novel/bhyve_freebsd.img.bak -s 31,lpc -l com1,/dev/nmdm0A testvm=20 and I get: Boot Failed. EFI Hard Drive However, when I do: sudo bhyveload -m 512 -d /home/novel/bhyve_freebsd.img.bak testvm and then: sudo /usr/sbin/bhyve -c 2 -m 512 -A -I -u -H -P -s 0:0,hostbridge -s 3:0,ahci-hd,/home/novel/bhyve_freebsd.img.bak -s 31,lpc -l com1,/dev/nmdm0A testvm I can see a console: (It fails to mount root though because my image is configured to virtio, but I guess it's not relevant to this situation). >=20 > On Mon, Nov 2, 2015 at 10:13 AM, Roman Bogorodskiy > wrote: >=20 > > Hi, > > > > I'm facing a strange problem with -l bootrom. > > > > I try to boot a VM this way: > > > > sudo /usr/sbin/bhyve -l bootrom,/home/novel/uefi/BHYVE_UEFI_20151002.fd > > -c 2 -m 214 -A -I -u -H -P -s 0:0,hostbridge -s > > 2:0,virtio-net,tap0,mac=3D52:54:00:56:9a:77 -s > > 3:0,ahci-hd,/home/novel/FreeBSD-11.0-CURRENT-amd64.raw -s 1,lpc -l > > com1,/dev/nmdm0A testvm > > > > BHYVE_UEFI_20151002.fd is downloaded from [1]. > > FreeBSD-11.0-CURRENT-amd64.raw is downloaded from [2]. > > > > VMs fail to boot with 'Boot Failed. EFI Hard Drive' and brings into UEFI > > shell. > > > > Changing ahci-hd to virtio-blk changes error message to: > > > > 'Boot Failed. EFI Misc Device'. > > > > Dropping 'hostbridge' and 'virtio-net' doesn't seem to change anything. > > > > Also, before trying FreeBSD-11.0-CURRENT-amd64.raw I tried my old images > > I used with bhyveload and they fail in the same way, though they're > > still booting using bhyveload. > > > > I'm running -CURRENT updated last weekend on Intel i5-2310. > > > > What could be wrong with this? > > > > 1: http://people.freebsd.org/~grehan/bhyve_uefi/BHYVE_UEFI_20151002.fd > > 2: > > > > http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/11.0-CURRENT/amd= 64/Latest/FreeBSD-11.0-CURRENT-amd64.raw.xz > > > > Roman Bogorodskiy > > Roman Bogorodskiy --eHhjakXzOLJAF9wJ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWN6HEAAoJEMltX/4IwiJqlIwH/3uR3WVmXmUDuU6pbIk8dDMG vVS7UVcYTwdSyw3NzD6s22iBCUNOdTu/SyFsr5mpzR3gQ72/kSIuFReG7KVDW50K DUCKZ4DCRbV1DblHb9KbBQe2SN1x8QJTMOzNmgxzYvpFUOJgNcWm7wZMR1Lb+e27 f9PApkTH56sw459HepP5C713d/HdQerrByhyUG1QokRmSuidNFwMLjlcKKkXjbkF TqT28osStJmJbGm+T3EOqVCBqOM/NSTz8IO4fIh6fI+71JUQFOJze68Ch/+QH5FN eovUJ5pK9WpapHP0kn+ay11jCqdKK1xxp30AQ/vM8rbQ1xhN57Ka7Yu7j4L0cwg= =b2Lh -----END PGP SIGNATURE----- --eHhjakXzOLJAF9wJ--