From owner-freebsd-virtualization@freebsd.org Thu Nov 15 09:23:16 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 0899D112FB3F; Thu, 15 Nov 2018 09:23:16 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC0538C0B2; Thu, 15 Nov 2018 09:23:14 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id 06E1B3C5; Thu, 15 Nov 2018 09:23:06 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1542273786; bh=NaXaaOQ5mnO4caVA9EZmzve7s6nZghcAaswJLwS6bbM=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=jFpESlwyQuAOToqIlamFm6bcHXRntgntPgbkS/1yyV3qZHA+Ms2Ruy+VlEE4UmaRu Sew5yvdeem3WQrBhAlkF5s427nUpLJHa3yK3ASLt9r6gLT25xSr/2fHeLXHM/s1j3e EqLUGALYQvFVWFT4jF43GgKA0pQeZpyEK8ZNT0Ew= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Thu, 15 Nov 2018 09:23:05 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Thu, 15 Nov 2018 09:23:05 +0000 From: Matt Churchyard To: Warner Losh , Kyle Evans CC: FreeBSD Current , "Rodney W. Grimes" , "freebsd-virtualization@freebsd.org" Subject: RE: UEFI GOP: screen goes blank during boot after loader is finished Thread-Topic: UEFI GOP: screen goes blank during boot after loader is finished Thread-Index: AQHUexgNTIRUUtU5ZEW3drb1EFLC0aVN1uiAgAAFPoCAAAe9gIAAc0IAgAAtcoCAACBkgIAAlayAgAAt/YCAAAUugIAAWw0AgAAAb4CAAAzgAIAABNaAgAACLICAAADCAIAABhUAgAAA2oCAAEKrAIAAaRfg Date: Thu, 15 Nov 2018 09:23:04 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Rspamd-Queue-Id: DC0538C0B2 X-Spamd-Result: default: False [-2.51 / 200.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[userve.net]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.973,0]; NEURAL_HAM_LONG(-0.99)[-0.990,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[userve.net]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[userve.net:+]; MX_GOOD(-0.01)[av-smtp-in2.userve.net,av-smtp-in1.userve.net]; RCVD_IN_DNSWL_NONE(0.00)[22.1.196.217.list.dnswl.org : 127.0.10.0]; NEURAL_HAM_SHORT(-0.22)[-0.222,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-0.02)[country: GB(-0.10)]; ASN(0.00)[asn:20652, ipnet:217.196.0.0/20, country:GB] X-Rspamd-Server: mx1.freebsd.org 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: Thu, 15 Nov 2018 09:23:16 -0000 -----Original Message----- From: owner-freebsd-virtualization@freebsd.org On Behalf Of Warner Losh Sent: 15 November 2018 02:57 To: Kyle Evans Cc: FreeBSD Current ; Rodney W. Grimes ; freebsd-virtualization@freebsd.org Subject: Re: UEFI GOP: screen goes blank during boot after loader is finish= ed On Wed, Nov 14, 2018 at 4:00 PM Kyle Evans wrote: > On Wed, Nov 14, 2018 at 4:55 PM Subbsd wrote: > > > > On Thu, Nov 15, 2018 at 1:33 AM Kyle Evans wrote: > > > > > > On Wed, Nov 14, 2018 at 4:30 PM Kyle Evans wrote= : > > > > > > > > On Wed, Nov 14, 2018 at 4:23 PM Subbsd wrote: > > > > > > > > > > On Thu, Nov 15, 2018 at 1:05 AM Subbsd wrote: > > > > > > > > > > > > On Thu, Nov 15, 2018 at 12:21 AM Rebecca Cran < > rebecca@bluestop.org> wrote: > > > > > > > > > > > > > > On November 14, 2018 at 2:18:04 PM, Subbsd=20 > > > > > > > (subbsd@gmail.com) > wrote: > > > > > > >> > > > > > > >> > > > > > > >> My current host: FreeBSD 13.0-CURRENT r340319 and the=20 > > > > > > >> problem > is > > > > > > >> still present. > > > > > > > > > > > > > > Rod was asking about the guest OS version, not the host thoug= h. > > > > > > > > > > > > > > > > > > > > > > > > > > I apologize, it seemed to me that I wrote earlier) Guest versio= n: > > > > > > > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0 > /FreeBSD-13.0-CURRENT-amd64-20181101-r339979-disc1.iso.xz > > > > > > > > > > Hm, it seems the problem is 'boot_serial' which is sets to YES=20 > > > > > by > default in gop > > > > > > > > > > set boot_serial=3DNO > > > > > boot > > > > > > > > > > solve this issue > > > > > > > > Huh? This is perhaps going to be a stupid question, but where is=20 > > > > boot_serial=3DYES getting set? Loader will not set it by itself=20 > > > > and > UEFI > > > > doesn't respect /boot.config, so this must be explicitly set in=20 > > > > /boot/loader.conf or /boot/defaults/loader.conf, but it's not=20 > > > > clear > to > > > > me what's putting it there. > > > > > > > http://src.illumos.org/source/xref/freebsd-head/usr.sbin/bhyveload/bhy > veload.c#832 > > > is the only place I can see immediately that this might be=20 > > > happening, but do UEFI boots go through bhyveload? I'm ignorant here. > > > > This is UEFI GOP methodvia bootrom/uefi-firmware, no bhyveload: > > > > bhyve -AHP -s 0:0,hostbridge -s 31:0,lpc -s=20 > > 4:0,ahci-cd,/tmp/FreeBSD-13.0-CURRENT-amd64-20181101-r339979-disc1.i > > so -c 1 -m 1024M -s 29,fbuf,tcp=3D0.0.0.0:5900,w=3D1024,h=3D768,wait -l= =20 > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd freebsd1 > > > > https://snag.gy/0MH7zU.jpg > > https://snag.gy/kF5cxZ.jpg > > https://snag.gy/htHMG0.jpg > > https://snag.gy/vK1ALN.jpg > > https://snag.gy/qKNPGU.jpg > > What does your /boot/loader.conf look like? > >What is the ConOut evifar look like? We set serial when the UEFI env says = to do so. >Warner I can confirm that 11.2-REL boots fine but 12.0-BETA4 goes blank just after= the loader, using the exact same bhyve configuration. (This is on an 11.2 = host) A few lines are output just before going blank but I can't catch what they = say. I'm using the official ISO files with no other configuration so it does see= m that 12.0 will currently not boot under UEFI-GOP bhyve. I can check the efivars if someone lets me know how. Matt _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/m= ailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org"