From owner-freebsd-virtualization@freebsd.org Sun Mar 11 17:00:56 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 D6B01F3AC0C for ; Sun, 11 Mar 2018 17:00:55 +0000 (UTC) (envelope-from fabian.freyer@physik.tu-berlin.de) Received: from mail.physik.tu-berlin.de (mail.physik-pool.tu-berlin.de [130.149.50.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57DF773F03 for ; Sun, 11 Mar 2018 17:00:54 +0000 (UTC) (envelope-from fabian.freyer@physik.tu-berlin.de) Received: from [192.168.119.1] (wlan-141-23-171-244.tubit.tu-berlin.de [141.23.171.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.physik.tu-berlin.de (Postfix) with ESMTPSA id BC9B061FB2; Sun, 11 Mar 2018 17:00:44 +0000 (UTC) From: "Fabian Freyer" To: "Martin Lucina" Cc: rumpkernel-users@freelists.org, freebsd-virtualization@freebsd.org Subject: Re: rumpkernel and bhyve: triple faults Date: Sun, 11 Mar 2018 18:00:41 +0100 X-Mailer: MailMate (1.10r5443) Message-ID: <0A39950F-698C-4A2C-80D6-B35A5B254BAA@physik.tu-berlin.de> In-Reply-To: <20180310224607.wscuqebheq5bjxww@nodbug.lucina.net> References: <20180310224607.wscuqebheq5bjxww@nodbug.lucina.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_772233C2-4F3C-413C-9C3B-FC3F90578CA5_="; micalg=pgp-sha512; protocol="application/pgp-signature" 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: Sun, 11 Mar 2018 17:00:56 -0000 This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_772233C2-4F3C-413C-9C3B-FC3F90578CA5_= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10 Mar 2018, at 23:46, Martin Lucina wrote: > On Friday, 09.03.2018 at=C2=A018:45, Fabian Freyer wrote: >> On 6 Mar 2018, at 7:45, Fabian Freyer wrote: >>> I=E2=80=99m not sure where to go from here. Is this a bug in bhyve(4)= , should these >>> values be initialised somehow, or should I patch rumpkernel(7) to ski= p this check >>> when running on bhyve(4)? > > You probably want to use a serial console rather than VGA on bhyve in a= ny > case, so you'll want to add the appropriate checks to hypervisor.c and > cons.c. I=E2=80=99ve started on a patch, but the check should fail if bios_crtc_b= ase is unset anyways. >> A build on Linux (which boots fine) shows [bios_com1_base, bios_crtc_b= ase] not to >> be uninitialised: >> 00000000003e3480 g O .bss 0000000000000002 bios_com1_base >> 00000000003e44a0 g O .bss 0000000000000002 bios_crtc_base > > When you write "which boots fine", I presume you're referring to bootin= g on > bhyve? Yes. The rumprun kernel built on Linux boots fine (including serial outpu= t by default on Linux. The one built on FreeBSD triple faults, due to accessing 0x2. >> Further down the rabbit hole, this goes on in rumprun.o: >> >> On Linux, bios_crtc_base is not a local symbol: >> 0000000000000002 O *COM* 0000000000000002 bios_crtc_base >> 0000000000000002 O *COM* 0000000000000002 bios_com1_base >> >> While on FreeBSD, they are marked as local: >> 0000000000000002 l O *COM* 0000000000000002 bios_crtc_base >> 0000000000000002 l O *COM* 0000000000000002 bios_com1_base > > That seems wrong. Can you try and force the toolchain to use the more > recent GNU ld from devel/binutils and see if that fixes the problem? I=E2=80=99m using GNU Binutils from devel/binutils: pkg list binutils | grep /usr/local/bin/ld /usr/local/bin/ld /usr/local/bin/ld.bfd /usr/local/bin/ld.gold $(x86_64-rumprun-netbsd-gcc -print-prog-name=3Dld) -v GNU ld (GNU Binutils) 2.30 Fabian --=_MailMate_772233C2-4F3C-413C-9C3B-FC3F90578CA5_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQJWBAEBCgBAFiEEX6JoxdmEemcFacQZmealkcs85+YFAlqlYLkiHGZhYmlhbi5m cmV5ZXJAcGh5c2lrLnR1LWJlcmxpbi5kZQAKCRCZ5qWRyzzn5qeIEACjO1rhn9zI dpfoA4VsBwMFxIiN5hvNG4peSaGzDQSWknhxpN5Fx7EmnWm+iy1Dgym4ie2ia4bC 25Zy+EDREHx/WjGzYaBA8LPqk5ccJuF7zIhKwM7hShakrYQdaQ0C/EthArCNzkTA QbFc4GFd4ggKuSBSrTJapNmAx9rh+CVvcJEw4NrQbEaouf4M/ys/wiOeUDYP0XKG pkX22JsgR6uirXU1/+k8ubyAcloGqmYyOkKfIZmx/ejQdhX5i0XI3hUIf+zrA+7H YlR6Gk1BRQ5Az85KwkKv+D5qkS/SSpQe9vJy+Q2AD4qp0lZcTE5gm782KQ/6R8SZ +slpoKsS+AhwS0AlHj3yfqt3BIE+VF/1Ulu5R18KrJvTtY9bqY099DCoIVVGVnI7 LqWXGrBfwSO72kOpLGhk4LGbWAvzGnnHOJ7YiAoldRlfXNp99XoXIXUkGa/T9HoN byXNBmq3M7vDL62yzC0sGiEXwJaQk9wYM9lrujtTdB0IQCzTgDtIgET1N497LP+t 8+uY4Bb22ASCKTLSpSRpc/vhhzeNnkNO4o+h9Hp4d2qk/yhzUa+cxO2qvd1pRZeD DhaPJQ7DRvZIZmdFYD8AfU6YyrL9+3g1uDYvxHpWiC96cCaaqfXYBNxUWEcMm0Sj dl9mU3nP5iRSE20u1PFY2wqR2D+N8vnsUQ== =T7nM -----END PGP SIGNATURE----- --=_MailMate_772233C2-4F3C-413C-9C3B-FC3F90578CA5_=-- From owner-freebsd-virtualization@freebsd.org Sun Mar 11 21:00:10 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 ADF85F4E6D1 for ; Sun, 11 Mar 2018 21:00:10 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48C987E899 for ; Sun, 11 Mar 2018 21:00:10 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 724484A9A for ; Sun, 11 Mar 2018 21:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2BL09rJ095115 for ; Sun, 11 Mar 2018 21:00:09 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2BL09tQ095111 for freebsd-virtualization@FreeBSD.org; Sun, 11 Mar 2018 21:00:09 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201803112100.w2BL09tQ095111@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-virtualization@FreeBSD.org Subject: Problem reports for freebsd-virtualization@FreeBSD.org that need special attention Date: Sun, 11 Mar 2018 21:00:09 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Sun, 11 Mar 2018 21:00:10 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 212820 | FreeBSD 10-STABLE from latest HEAD and 11-RELEASE 1 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Mon Mar 12 11:29:21 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 78121F39D75 for ; Mon, 12 Mar 2018 11:29:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 106EF7633C for ; Mon, 12 Mar 2018 11:29:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 4FCDE1446C for ; Mon, 12 Mar 2018 11:29:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2CBTKau070564 for ; Mon, 12 Mar 2018 11:29:20 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2CBTKFf070563 for freebsd-virtualization@FreeBSD.org; Mon, 12 Mar 2018 11:29:20 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 213333] FreeBSD 11-RELEASE fails to boot under KVM/Qemu Date: Mon, 12 Mar 2018 11:29:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Mon, 12 Mar 2018 11:29:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213333 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|New |Closed --- Comment #20 from Andriy Gapon --- *** This bug has been marked as a duplicate of bug 213155 *** --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Mar 13 15:33:37 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 A5E8A36B for ; Tue, 13 Mar 2018 15:33:37 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A3B6836BB; Tue, 13 Mar 2018 15:33:37 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w2DFXale077189 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 13 Mar 2018 11:33:36 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w2DFXYlP061152; Tue, 13 Mar 2018 11:33:34 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Ryzen lockup on bhyve was (Re: new Ryzen lockup issue ?) To: Peter Grehan , Anish , "pholes@sentex.net" , "freebsd-virtualization@freebsd.org" References: <92a60e14-f532-2647-d45d-b500fc59ba88@sentex.net> <425be16f-9fdc-9ed6-72b1-02e28bfd130f@sentex.net> <2f2b6f96-d6ef-8e02-966d-dcbbfb0c92fb@freebsd.org> <48768738-e699-fd06-9154-9b5be1bbabcc@sentex.net> <36c062e4-352b-eebe-5f08-1af250d98eee@sentex.net> <7fa0b7a0-492e-6ded-3b5c-1edeff54d746@sentex.net> <7f599ae6-4de6-4a65-5a03-7e41f5f72530@freebsd.org> <92443071-e9b7-4941-16f3-5d5c423f4d0a@sentex.net> <1b0bb7de-5e12-8b7c-3d5a-93570852d0f2@sentex.net> <87431121-b7fb-1a5c-7081-d76347c27e53@freebsd.org> From: Mike Tancsa Organization: Sentex Communications Message-ID: <493a7783-dac5-5fb0-4ab8-b1a576fb9379@sentex.net> Date: Tue, 13 Mar 2018 11:33:35 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <87431121-b7fb-1a5c-7081-d76347c27e53@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 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: Tue, 13 Mar 2018 15:33:37 -0000 On 3/6/2018 2:42 PM, Peter Grehan wrote: >>     Would virtualbox do this too (send a lot of IPIs)? I first noticed >> the >> lockups using it and not bhyve.  I have been using bhyve now as its >> easier to script the lockups etc. > >  Yes it would. Hmmm, this makes it even more mysterious. > >  I'll go and have a look a the FreeBSD interface code for VBox to see if > anything stands out in the way it uses IPIs. > >  It doesn't use the optimized i/f that bhyve uses, so this points to it > being a more general problem. Hi Peter, I have been stress testing the box without any hypervisor software loaded and all seems pretty stable. I left parallel buildworlds running along with a few background jobs of dd if=/dev/urandom count=10000 | sha256 randomly running in the background for 24hrs. I am now running the buildworlds along with maxing out the network card with bidirectional traffic. Its been up for 6days without issue. Any other thoughts / tests I can do to try and help narrow down this issue ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-virtualization@freebsd.org Tue Mar 13 22:46: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 9BB6AF573FA; Tue, 13 Mar 2018 22:46:05 +0000 (UTC) (envelope-from dexuan.bsd@gmail.com) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (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 DEC177A4DB; Tue, 13 Mar 2018 22:46:04 +0000 (UTC) (envelope-from dexuan.bsd@gmail.com) Received: by mail-lf0-x231.google.com with SMTP id l191-v6so1897794lfe.1; Tue, 13 Mar 2018 15:46:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=FQFMc5Ss1ANsk9ngvYYLiCreKBElog3p0Yf4XycdV7I=; b=DY7uojdWxVV4Y+dnCt+T4Jqtrgl6FsnaBx3ipULu6dX0Yt//W0kYon43ngkJJ2aIqP lEEYN5pdWeWwtQOtqaOElybP3Uyp2I4wkdA5ZvvfMS1A2gzSPGVGk+pmWPMi/TDMVbUM 4tfEILF0YAKihK64LKruxqc9XWuopUjpsDoTGvNofTixi0aCyn1u+JHr18cHeGuSlArx qOuQXT8akms0dL2F6gksMsChnjsdxn36TBZo2uwxRNYs+lqGdzJFkXtRIFsMCY93UnDq KHA+PP3+Qtp27uBwoguNmhSuP8/KMJtVVs2U4u8ENDxUKHuc6W7K1V7K0WKduD6qL7OU UvKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=FQFMc5Ss1ANsk9ngvYYLiCreKBElog3p0Yf4XycdV7I=; b=PVhQHt+gxSHRnUl1PNtmCMxa+ytYkRrcTPh/NvpHyAfuTgOt2lTXDU3xP0ZA55FqWQ FxJM1M+2o+N34SPY8+hSXTXhZlEGrD0cOftT3XIw26CO05J9G4MYxQyHQSkFHcuhlflu MIUYaqhvDKD/1DnpNaHK6eDVgwD3VOWUp1beZRIvO3o7ppjtnaoxV9oc6rvQuOwT6HI3 5MLKfzSWAmuiwViJg7TASsUdq9RgYpc+Irq4ZDpEFFjBAl6hglLPs3PTUtPFaVwW8aGr GyvjRwZjzLo9QMshUBPUSmDtiXy964rk88f5RlgVbBDpuPBUBxjS9lRZreW/TwZ4ypZf VKFA== X-Gm-Message-State: AElRT7GgqmT2zxuKMzNP80c8pkX0bzcod73vcqgGN175d/HKAxaTPbe2 uyqbl8LS3l0xqXTASYe5KaVu5+jvBQ/PFdf6LSUtMQ== X-Google-Smtp-Source: AG47ELtgvsAvspnG/BezU+DuJLqv+by3wQbjDW+ak4iHs1u/48kv+8rxfbtk1iDPFWkCc+tjFbCYAKbqQIhebAoFzSA= X-Received: by 2002:a19:e9cc:: with SMTP id j73-v6mr1509483lfk.99.1520981163279; Tue, 13 Mar 2018 15:46:03 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:d8e8:0:0:0:0:0 with HTTP; Tue, 13 Mar 2018 15:46:02 -0700 (PDT) In-Reply-To: References: From: Dexuan-BSD Cui Date: Tue, 13 Mar 2018 15:46:02 -0700 Message-ID: Subject: Re: A strange SCSI-disk-detached issue for FreeBSD VM on Hyper-V/Azure To: freebsd-scsi@freebsd.org, freebsd-virtualization@freebsd.org, Scott Long , scottl@freebsd.org, Warner Losh , jhibbits@freebsd.org, avg@freebsd.org, asomers@freebsd.org, cem@freebsd.org, mav@freebsd.org Cc: Dexuan Cui Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 14 Mar 2018 01:04:07 +0000 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: Tue, 13 Mar 2018 22:46:05 -0000 I reported a bug for this issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226583 I'm working on a fix. -- Dexuan On Mon, Jan 29, 2018 at 7:44 PM, Dexuan-BSD Cui wrot= e: > With the the recent Azure host upgrade, some FreeBSD VMs can't > properly detect HDD-backed disks. > The issue happens to the latest 12-CURRENT too. > > da0 (0:0:0:0=EF=BC=89is also backed by HDD, but somehow is not affected. > da1 (1:0:1:0) it not affected either, only the extra disks, e,g. da2 > (3:0:0:0=EF=BC=89, are affected. > > These are the logs of my VM, which has da0, da1 and da2. These 3 disks > are on 3 different disk controllers. > > > [root@decui-d4-repro ~]# dmesg -c > /dev/null > [root@decui-d4-repro ~]# camcontrol rescan all > Re-scan of bus 0 was successful > Re-scan of bus 1 was successful > Re-scan of bus 2 was successful > Re-scan of bus 3 was successful > Re-scan of bus 4 was successful > Re-scan of bus 5 was successful > > [root@decui-d4-repro ~]# dmesg > (aprobe0:ata0:0:0:0): Disable ATA disks on simulated ATA controller (0x71= 118086) > (aprobe0:ata0:0:1:0): Disable ATA disks on simulated ATA controller (0x71= 118086) > (probe1:(probe0:blkvsc0:0:1:0): Down reving Protocol Version from 4 to 2? > blkvsc0:0:0:0): storvsc inquiry (36) [0 0 4 2 1f ... ] > (probe1:blkvsc0:0:1:0): storvsc inquiry (36) [7f 0 5 2 1f ... ] > (probe0:blkvsc0:0:0:0): storvsc scsi_status =3D 2, srb_status =3D 6 > (probe0:(probe1:blkvsc0:0:0:0): storvsc inquiry (5) [0 0 0 5 0 ... ] > (probe0:blkvsc0:0:1:1): Down reving Protocol Version from 4 to 2? > blkvsc0:0:0:0): storvsc inquiry (6) [0 83 0 1c 1 ... ] > (probe1:blkvsc0:0:1:1): invalid LUN 1 for op: INQUIRY > (probe0:blkvsc0:0:0:1): invalid LUN 1 for op: INQUIRY > (probe0:blkvsc1:0:0:0): Down reving Protocol Version from 4 to 2? > (probe0:blkvsc1:0:0:0): storvsc inquiry (36) [7f 0 5 2 1f ... ] > (probe1:(probe0:blkvsc1:0:1:0): storvsc inquiry (36) [0 0 5 2 1f ... ] > (probe1:blkvsc1:0:0:1): Down reving Protocol Version from 4 to 2? > blkvsc1:0:1:0): storvsc scsi_status =3D 2, srb_status =3D 6 > (probe1:blkvsc1:0:1:0): storvsc inquiry (5) [0 0 0 8 0 ... ] > (probe0:blkvsc1:0:0:1): invalid LUN 1 for op: INQUIRY > (probe1:blkvsc1:0:1:0): storvsc inquiry (6) [0 83 0 30 1 ... ] > (probe0:storvsc2:0:0:0): Down reving Protocol Version from 4 to 2? > (probe1:(probe0:storvsc2:0:1:0): Down reving Protocol Version from 4 to 2= ? > storvsc2:0:0:0): storvsc inquiry (36) [7f 0 5 2 1f ... ] > (probe1:(probe0:storvsc2:0:1:0): storvsc inquiry (36) [7f 0 5 2 1f ... ] > (probe1:storvsc2:0:0:1): Down reving Protocol Version from 4 to 2? > (probe0:storvsc2:0:1:1): Down reving Protocol Version from 4 to 2? > (probe1:storvsc2:0:0:1): invalid LUN 1 for op: INQUIRY > storvsc2:0:1:1): invalid LUN 1 for op: INQUIRY > (probe0:storvsc3:0:0:0): Down reving Protocol Version from 4 to 2? > (probe1:(probe0:storvsc3:0:1:0): Down reving Protocol Version from 4 to 2= ? > storvsc3:0:0:0): storvsc inquiry (36) [0 0 4 2 1f ... ] > (probe1:(probe0:storvsc3:0:1:0): storvsc inquiry (36) [7f 0 5 2 1f ... ] > storvsc3:0:0:0): storvsc scsi_status =3D 2, srb_status =3D 6 > (probe0:(probe1:storvsc3:0:0:0): storvsc inquiry (5) [0 0 0 5 0 ... ] > (probe0:storvsc3:0:1:1): Down reving Protocol Version from 4 to 2? > storvsc3:0:0:0): storvsc inquiry (6) [0 83 0 1c 1 ... ] > (probe1:storvsc3:0:1:1): invalid LUN 1 for op: INQUIRY > GEOM: new disk da2 > (probe0:pass3 at storvsc3 bus 0 scbus5 target 0 lun 0 > storvsc3:0:0:1): invalid LUN 1 for op: INQUIRY > pass3: Fixed Direct Access SPC-2 SCSI device > pass3: 300.000MB/s transfers > pass3: Command Queueing enabled > pass3 at storvsc3 bus 0 scbus5 target 0 lun 0 > pass3: detached > (da2:storvsc3:0:0:0): fatal error, could not acquire reference count > (pass3:(da2:storvsc3:0:storvsc3:0:0:0): storvsc inquiry (5) [0 b1 0 3c 0 = ... ] > 0:0): Periph destroyed > da2: Delete methods: > Opened disk da2 -> 6 > g_access(918): provider da2 has error > g_access(918): provider da2 has error > g_access(918): provider da2 has error > g_access(918): provider da2 has error > > > According to the log, first it looks da2 is indeed detected, but then > it's detached immediately: > > pass3: detached > > The above line comes from xpt_denounce_periph_sbuf(), which is called by: > > cam_periph_invalidate() at cam_periph_invalidate+0xe7/frame 0xfffffe00004= eb7f0 > xpt_async_process_dev() at xpt_async_process_dev+0x162/frame 0xfffffe0000= 4eb840 > xptdevicetraverse() at xptdevicetraverse+0xa3/frame 0xfffffe00004eb890 > xpttargettraverse() at xpttargettraverse+0x6a/frame 0xfffffe00004eb8d0 > xpt_async_process() at xpt_async_process+0x114/frame 0xfffffe00004eb9e0 > xpt_done_process() at xpt_done_process+0x38a/frame 0xfffffe00004eba20 > xpt_done_td() at xpt_done_td+0x136/frame 0xfffffe00004eba70 > fork_exit() at fork_exit+0x84/frame 0xfffffe00004ebab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00004ebab > > > I'm trying to figure out why CAM detaches da2 -- it looks something is wr= ong? > > Currently, with the below hack, da2 can be recognized and > reading/writing da2 works fine: > > --- a/sys/cam/cam_periph.c > +++ b/sys/cam/cam_periph.c > @@ -1942,8 +1942,10 @@ cam_periph_error(union ccb *ccb, cam_flags camflag= s, > * Let peripheral drivers know that this > * device has gone away. > */ > +#if 0 > xpt_async(AC_LOST_DEVICE, newpath, NULL); > xpt_free_path(newpath); > +#endif > } > } > > And I'm further debugging. I appreciate any suggestion. > > Thanks! > > -- Dexuan From owner-freebsd-virtualization@freebsd.org Wed Mar 14 01:22:43 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 4F338F374F9 for ; Wed, 14 Mar 2018 01:22:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D4CAF80BB8 for ; Wed, 14 Mar 2018 01:22:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 23F2B27F0C for ; Wed, 14 Mar 2018 01:22:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2E1Mgrk007538 for ; Wed, 14 Mar 2018 01:22:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2E1MfvD007537 for freebsd-virtualization@FreeBSD.org; Wed, 14 Mar 2018 01:22:41 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225588] VirtualBox 5.2.6 guests freeze after a while, sometimes with I/O errors Date: Wed, 14 Mar 2018 01:22:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jwb@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 14 Mar 2018 01:22:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225588 --- Comment #4 from Jason W. Bacon --- I'm not seeing this issue with CentOS in 5.2.8. A Debian install that fail= ed under 5.2.6 also worked under 5.2.8. My Windows 10 guest still doesn't work, but that may be due to permanent da= mage caused by the previous failures, which happened during Windows Update. I plan to try a fresh install when I get a chance, but that may be a while.= .. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Mar 14 03:51:00 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 4481FF4CC1C for ; Wed, 14 Mar 2018 03:51:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7A4787C74 for ; Wed, 14 Mar 2018 03:50:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id ECD7E292B8 for ; Wed, 14 Mar 2018 03:50:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2E3ow3T043702 for ; Wed, 14 Mar 2018 03:50:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2E3owx4043700 for freebsd-virtualization@FreeBSD.org; Wed, 14 Mar 2018 03:50:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 226583] FreeBSD VM on Hyper-V/Azure can't properly detected SCSI disk da2 Date: Wed, 14 Mar 2018 03:50:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 14 Mar 2018 03:51:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226583 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org Keywords| |patch --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Mar 14 05:32:12 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 66EEEF56D0F for ; Wed, 14 Mar 2018 05:32:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E293E6D3C2 for ; Wed, 14 Mar 2018 05:32:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 409482A1E0 for ; Wed, 14 Mar 2018 05:32:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2E5WBpX036933 for ; Wed, 14 Mar 2018 05:32:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2E5WBNB036931 for freebsd-virtualization@FreeBSD.org; Wed, 14 Mar 2018 05:32:11 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225588] VirtualBox 5.2.6 guests freeze after a while, sometimes with I/O errors Date: Wed, 14 Mar 2018 05:32:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: w.schwarzenfeld@utanet.at X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 14 Mar 2018 05:32:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225588 w.schwarzenfeld@utanet.at changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |w.schwarzenfeld@utanet.at --- Comment #5 from w.schwarzenfeld@utanet.at --- bug #215526 seems a similar problem. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Mar 14 05:49:00 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 0E8F7F57A97 for ; Wed, 14 Mar 2018 05:49:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A123C6DDCC for ; Wed, 14 Mar 2018 05:48:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id CC4F82A356 for ; Wed, 14 Mar 2018 05:48:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2E5mwpb077331 for ; Wed, 14 Mar 2018 05:48:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2E5mwjF077330 for freebsd-virtualization@FreeBSD.org; Wed, 14 Mar 2018 05:48:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 218731] FREEBSD 11 SCSI drive issue with all 11.xxxx versions running under HYPER-V as a VM Date: Wed, 14 Mar 2018 05:48:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: decui@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 14 Mar 2018 05:49:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218731 --- Comment #17 from Dexuan Cui --- (In reply to ds from comment #16) I highly suspect this bug can be fixed by the attached patch in comment #2 = of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226583, but I don't hav= e a physical disk on the host to pass through to the VM. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Mar 14 07:10:19 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 7207AF5AC87 for ; Wed, 14 Mar 2018 07:10:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0205570FE5 for ; Wed, 14 Mar 2018 07:10:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2D2BA2AE89 for ; Wed, 14 Mar 2018 07:10:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2E7AHZx088798 for ; Wed, 14 Mar 2018 07:10:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2E7AHpo088796 for freebsd-virtualization@FreeBSD.org; Wed, 14 Mar 2018 07:10:17 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 226583] FreeBSD VM on Hyper-V/Azure can't properly detected SCSI disk da2 Date: Wed, 14 Mar 2018 07:10:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: decui@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 14 Mar 2018 07:10:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226583 --- Comment #3 from Dexuan Cui --- Posted a patch for review: https://reviews.freebsd.org/D14690 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Mar 14 07:21:44 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 1E4C9F5B629 for ; Wed, 14 Mar 2018 07:21:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A813A7192A for ; Wed, 14 Mar 2018 07:21:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id EE0B62B015 for ; Wed, 14 Mar 2018 07:21:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2E7LgZP024174 for ; Wed, 14 Mar 2018 07:21:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2E7Lgcc024172 for freebsd-virtualization@FreeBSD.org; Wed, 14 Mar 2018 07:21:42 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 226583] FreeBSD VM on Hyper-V/Azure can't properly detected SCSI disk da2 Date: Wed, 14 Mar 2018 07:21:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: decui@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 14 Mar 2018 07:21:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226583 --- Comment #4 from Dexuan Cui --- (In reply to Dexuan Cui from comment #3) I manually tested the patch with releng/{10.3, 10.4, 11.0, 11.1}, stable/{1= 0, 11), and master on local Windows Server 2012 R2, 2016 and Azure, and I don't hit any regression. For Azure testing, I created multiple VMs (Standard D4= v2 (8 vcpus, 28 GB memory) ) in West Central US region and ran a lot of "hot add/remove disks" tests, e.g. a) hot add and remove a disk on LUN0 b) hot add and remove a disk on LUN1 c) hot add and remove a disk on LUN9 d) hot add and remove a disk on LUN0, and LUN9 e) hot add and remove a disk on LUN1, and LUN9 f) hot add and remove a disk on LUN0~7 g) hot add and remove a disk on LUN0~6, LUN8 h) hot add and remove a disk on LUN1, 9, 10, 11, 12, 13, 14, 15 i) hot add and remove a disk on LUN0, 9, 10, 11, 12, 15, 18, 63 I didn't find any issue. Hongxiong also helped to test it on 2012 R2 and 2016. No issue. Hongxiong is going to run more test cases on Azure. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Mar 14 15:35:26 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 3CB84F595D8 for ; Wed, 14 Mar 2018 15:35:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CFF08867CA for ; Wed, 14 Mar 2018 15:35:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2718A2F4A2 for ; Wed, 14 Mar 2018 15:35:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2EFZPYW070371 for ; Wed, 14 Mar 2018 15:35:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2EFZPE1070370 for freebsd-virtualization@FreeBSD.org; Wed, 14 Mar 2018 15:35:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 226583] FreeBSD VM on Hyper-V/Azure can't properly detected SCSI disk da2 Date: Wed, 14 Mar 2018 15:35:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: preetpal.sohal@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 14 Mar 2018 15:35:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226583 Preetpal Sohal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |preetpal.sohal@gmail.com --- Comment #5 from Preetpal Sohal --- I encountered this bug using an A1 sized VM in Azure (you can probably chan= ge the importance level in the bug tracker). This bug seems to be affecting ot= her users on Azure as well (see https://forums.freebsd.org/threads/disk-gets-detached-then-periph-destroyed= -according-to-var-run-dmesg-boot-azure-data-disks.61266/#post-381342). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Mar 14 18:43:42 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 EA47BF34426 for ; Wed, 14 Mar 2018 18:43:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85BFD70B32 for ; Wed, 14 Mar 2018 18:43:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B8B43F35 for ; Wed, 14 Mar 2018 18:43:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2EIhepj035048 for ; Wed, 14 Mar 2018 18:43:40 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2EIhe86035047 for freebsd-virtualization@FreeBSD.org; Wed, 14 Mar 2018 18:43:40 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225588] VirtualBox 5.2.6 guests freeze after a while, sometimes with I/O errors Date: Wed, 14 Mar 2018 18:43:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jwb@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 14 Mar 2018 18:43:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225588 --- Comment #6 from Jason W. Bacon --- Interesting... I spoke too soon about 5.2.8 solving the problem. The latest round of Cent= OS Yum updates triggered it again. I restored the .vdi file using an OVA snapshot and reran updates + zeroing = free blocks (in prep for compressing the disk image). Did this procedure twice, once with IDE and no host cache, and again with S= ATA and host cache. No problems in either case. So it looks like we may have a workaround. It's still a mystery why this problem popped up in 5.2.6, though. I've been running CentOS VMs for years and never had to care about controller setting= s. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Mar 14 19:01:49 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 59D06F3592E for ; Wed, 14 Mar 2018 19:01:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA8FF7135B for ; Wed, 14 Mar 2018 19:01:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 47B4710CA for ; Wed, 14 Mar 2018 19:01:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2EJ1moP088689 for ; Wed, 14 Mar 2018 19:01:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2EJ1mi5088688 for freebsd-virtualization@FreeBSD.org; Wed, 14 Mar 2018 19:01:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 226583] FreeBSD VM on Hyper-V/Azure can't properly detected SCSI disk da2 Date: Wed, 14 Mar 2018 19:01:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: decui@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_severity Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 14 Mar 2018 19:01:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226583 Dexuan Cui changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Only Me |Affects Some People --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Mar 14 21:55:49 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 B0CCFF4C871 for ; Wed, 14 Mar 2018 21:55:49 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 559EE78E39 for ; Wed, 14 Mar 2018 21:55:49 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: by mail-qk0-x233.google.com with SMTP id g184so5204207qkd.10 for ; Wed, 14 Mar 2018 14:55:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=IRkL8df6Gn0xkaPXlh9XQHnMiZiq2fuZaZ2jhpmNrso=; b=icLcZXxXbg/tfgLUcHUoN4OoZUK23OmxwAwwhp4LJxfDpaAPdfjbJzm3ahOFTLstRS +m527pMYAxPQfYYYTxdm7/hh81KUWnS0L4yNAuDB88GmMdjo4z7jEDNKrkDg+KGhl+5G 8yo+HnoOUeldpudbErHj8MLUHv4u+sbscDFce1gQZ9OhouKkQhojZZvkujLOzrpDT+qn mIstayLOWPexC0CxZSL92Aw1a90wzgrIJTAppxoB3wdG81tQTMWP54qXbnRHrTEmx/tP VNiWscdxLDSsGkIXzRLBhsaGPrJyxpNkBwFUQHMsLtf2m90JprMbj8j4/6KDT2+oCKgR mgyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=IRkL8df6Gn0xkaPXlh9XQHnMiZiq2fuZaZ2jhpmNrso=; b=XebkVcFFYXMKILBAo+V64d3k9h62qllzbkBPKcfyvOBosVQ5VoglxioKI4zqPL1TUf fnfZkdSNeK3tEUPgflXZ1U51uYmGB7oJ5r0dEoknGbw/QP7Tp0lNEGr3vAUXFOF9uIqt xxoW0/W3nTTQ0XmObVm+aRA+fWx98J6bdEhrf3guQ0yOfwJBngRyZRLEh+y5Mrf9zTe1 cxeBPDdPNpZ2wAYl75Aczu3TLAbxCkSUvVBlxvDear9zs+9AcbmmIWrx8mU8/y7eaA5R AsJThHDino2Q5VJ3WJOrttuqFFEvWMGrs08wqmY3sF90c4Kfq2EzTYuAw8bqh3YXw8dB TxCQ== X-Gm-Message-State: AElRT7EqKQiNaoeZTQCgFg928n3i2E+OXpx5UU/Jn8b2Tx52Km/8rrfj bLemXiDT9a//v0nz1002wdiBDtfroiTJHbxVeAxAhXXS X-Google-Smtp-Source: AG47ELveAlyAqf/XgFrVYul+NKuKR+FmwKa0diDEfwbZ/icDFVBAKro05Gj9ILXvV1oiX9OJ+mN22PF81bTlcUcw+JA= X-Received: by 10.55.143.1 with SMTP id r1mr9443743qkd.240.1521064548583; Wed, 14 Mar 2018 14:55:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.63.119 with HTTP; Wed, 14 Mar 2018 14:55:48 -0700 (PDT) From: Joe Maloney Date: Wed, 14 Mar 2018 17:55:48 -0400 Message-ID: Subject: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 14 Mar 2018 21:55:50 -0000 Hello everyone, Today after we attempted to merge the latest 11-STABLE into FreeNAS we found an issue with EFI boot during the testing process. To narrow done the issue I have tested the following images: https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180307-r330606-disc1.iso https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180307-r330605-disc1.iso To summarize I setup a bhyve VM with EFI, and graphics. Install with UFS, and ZFS work. After install during the boot the following message appears if ZFS is used: Failed to start image provided by ZFS (14) If UFS is used during the install here is what the message looks like on first boot: Failed to start image provided by UFS (14) Here is a screenshot showing the issue for ZFS: https://imgur.com/a/rQRck If bhyveload is used there is no issue booting. From what I can tell it is only if the EFI firmware is used even with graphics mode off. This has affected both CURRENT, and the latest 11-STABLE snapshot which are linked above. I will be out of office at the end of the week for several weeks, and may be unable to respond to further replies right away. Either way I wanted to make the project aware while others at iX look into this Thanks. Joe Maloney QA Manager / iXsystems Enterprise Storage & Servers Driven By Open Source From owner-freebsd-virtualization@freebsd.org Thu Mar 15 21:06:33 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 08AC3F538F4 for ; Thu, 15 Mar 2018 21:06:33 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 A0E5C78911 for ; Thu, 15 Mar 2018 21:06:32 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: by mail-qk0-x22b.google.com with SMTP id s188so8921099qkb.2 for ; Thu, 15 Mar 2018 14:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=W8nKHsgw8E0VZNKkzNO0EzsWKIeICiCzu/u09OILMR8=; b=hbf7Vv4QVAAUIOeL3m6X5727CBW6CcsHfAet0Hw2rwmv9w5uC/d5z7312B0BqFn1Ho onLEjVj9r9x0VPLLtNMvgMxoVlHYw+duMVLWI7TuKZ0u9xj3hJ7OA1u1IdV+FaQLdQB+ 8jdzppBmyYzqEhHmY5oK4lq6YLFvqKAPSCN71vNavCpyxW5pD2cjJWIrk9QhzpVJ6TKl NzXYjpPiVm2pne16n8pAaonKbocixPnoh8RHWzUVudxz2/XxxkQ5KwYM0Z5TbhqU7gio 3gqfAqCpj8A9FeD/jHlLQ5G5F26ePBULcogYKW8EzPN5sKZcLF9XrlNZ8krCR3NcNHG5 VJ6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=W8nKHsgw8E0VZNKkzNO0EzsWKIeICiCzu/u09OILMR8=; b=uQDML0Cjm94S0SRnoYP2mLlOPd88rcaKO7d/j+K0gh2jlVoTeP5vSUy3mpsmdvdBtS /1jjUtqLRc/gEe2rgkmlIzoU+B3Yg17ysU8EVFTnUWdPu8Iv3XZ6KY9ROEQp75n6qgcx HbqCIi9IBJqtA1pD8fA6LHi4NUBmPaCFpd5P4CTqu9CCP46emYkFS3JpxkbPgLLYAzgX 6ug52XOS4C46RLxLRiikSdHO4kinD72XqnohYP6DdTryYZ6a3hmgGot3CJ1sU8ghnnu+ UA39Phc6uqFKnvvzqEbPanrIkcBA5CecJdnfu53sWeP+h65+4cIKji9duNfyYGJcBlSK gJeg== X-Gm-Message-State: AElRT7HWt2oVXnEiLw24xwlMVhaLYCateySiW/zuHmHxHi5UR11GIk34 C5xcEbMJhPFPkPE4v+fqpqskxKtLkcDsD4eC6i14vb3K X-Google-Smtp-Source: AG47ELtnmJzeygb67hed2hcPxaKTV6bfteg7BOviBX6wpE2muJ8dBlS+hHWq2ortjsiK9DUxg5A/Kz4P32bn22a3Pf0= X-Received: by 10.55.5.8 with SMTP id 8mr15012826qkf.84.1521147991678; Thu, 15 Mar 2018 14:06:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.63.119 with HTTP; Thu, 15 Mar 2018 14:06:31 -0700 (PDT) In-Reply-To: References: From: Joe Maloney Date: Thu, 15 Mar 2018 17:06:31 -0400 Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: freebsd-virtualization@freebsd.org Cc: kevans@freebsd.org, emaste@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Thu, 15 Mar 2018 21:06:33 -0000 I believe the problem may have been introduced with this commit: https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 I can build an 11-STABLE image prior to that commit, and I do not exhibit the booting issues with bhyve using EFI. That r329114 commit does not build at all so I suspect it, or something after it involving loader work based on feedback from other iX engineers. What led me to start looking at this time period was this bug which references a large merge that address the same issue for RPI3: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216940 Unfortunately now something causes that exact same "Failed to start image provided by UFS (14)" error for BHYVE with UEFI. Joe Maloney QA Manager / iXsystems Enterprise Storage & Servers Driven By Open Source On Wed, Mar 14, 2018 at 5:55 PM, Joe Maloney wrote: > Hello everyone, > Today after we attempted to merge the latest 11-STABLE into FreeNAS we > found an issue with EFI boot during the testing process. > > To narrow done the issue I have tested the following images: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180307-r330606-disc1.iso > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180307-r330605-disc1.iso > > To summarize I setup a bhyve VM with EFI, and graphics. Install with > UFS, and ZFS work. > > After install during the boot the following message appears if ZFS is used: > Failed to start image provided by ZFS (14) > > If UFS is used during the install here is what the message looks like > on first boot: > Failed to start image provided by UFS (14) > > Here is a screenshot showing the issue for ZFS: > https://imgur.com/a/rQRck > > If bhyveload is used there is no issue booting. From what I can tell > it is only if the EFI firmware is used even with graphics mode off. > This has affected both CURRENT, and the latest 11-STABLE snapshot > which are linked above. > > I will be out of office at the end of the week for several weeks, and > may be unable to respond to further replies right away. Either way I wanted to > make the project aware while others at iX look into this Thanks. > > Joe Maloney > QA Manager / iXsystems > Enterprise Storage & Servers Driven By Open Source From owner-freebsd-virtualization@freebsd.org Thu Mar 15 21:09:30 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 01643F53D3D for ; Thu, 15 Mar 2018 21:09:29 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from vito.onthenet.com.au (vito.onthenet.com.au [203.22.124.72]) by mx1.freebsd.org (Postfix) with ESMTP id 6473678B8C for ; Thu, 15 Mar 2018 21:09:29 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto2.onthenet.com.au [203.13.68.14]) by vito.onthenet.com.au (Postfix) with ESMTP id 1EAE3209C00A for ; Fri, 16 Mar 2018 07:09:26 +1000 (AEST) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 059B020B4B91 for ; Fri, 16 Mar 2018 07:09:26 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id F3E202820A2 for ; Fri, 16 Mar 2018 07:09:25 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id twI6iyt68Q4f for ; Fri, 16 Mar 2018 07:09:25 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (96-82-80-65-static.hfc.comcastbusiness.net [96.82.80.65]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 99A9E2808C8; Fri, 16 Mar 2018 07:09:23 +1000 (AEST) Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: Joe Maloney Cc: freebsd-virtualization@freebsd.org, kevans@freebsd.org References: From: Peter Grehan Message-ID: Date: Thu, 15 Mar 2018 14:09:20 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=dNCIZtRb c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=IkcTkHD0fZMA:10 a=v2DPQv5-lfwA:10 a=6I5d2MoRAAAA:8 a=nxvoylDK4sPvG11N-PAA:9 a=QEXdDO2ut3YA:10 a=IjZwj45LgO3ly-622nXo:22 wl=host:3 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=Mvd8FVSe c=1 sm=1 tr=0 a=eF5wA05EhuPcU0j7PNT2Vg==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=IkcTkHD0fZMA:10 a=v2DPQv5-lfwA:10 a=6I5d2MoRAAAA:8 a=nxvoylDK4sPvG11N-PAA:9 a=QEXdDO2ut3YA:10 a=IjZwj45LgO3ly-622nXo:22 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: Thu, 15 Mar 2018 21:09:30 -0000 > I believe the problem may have been introduced with this commit: > > https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 Any chance of being able to work out where in that list of commits in CURRENT the loader stopped working ? later, Peter. From owner-freebsd-virtualization@freebsd.org Thu Mar 15 21:11:35 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 72F34F53F2B for ; Thu, 15 Mar 2018 21:11:35 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) (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 DC51C78CDA; Thu, 15 Mar 2018 21:11:34 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f43.google.com with SMTP id g13-v6so1324323lfe.10; Thu, 15 Mar 2018 14:11:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UGhDUlqR7PD7JDnP0Qb3gnnNLHF0HQNFhwFFysWdNXE=; b=cV7lZXCErvqhgio8gZSEISwvUGScM9yUX0RTyNvidPXiMWkRNX8B8VO5RrietYObOC Dt7brCN22kPPqfgDzVQ4X9bWPSaP1vx9FZWOqg6MXayRSnHmx7qvNM7ohaBQrRQZyoZg BKsEbcZ9dzGgIPD+E5Z8l9XfpS2RnlgOiyT/3g3mwBdiArtwu2ucg9hoXrnCg/9LG9jT xh/zUIsM/95U86i84/mzo5wZQ0HDoOG1nQfe36K6qvgU07jn85pPcx97zpG7qRSbi0ib lTAFYXt8WHnwQVssZbascCRtYWF30gNnrjSUnBJXej3U02HzP5w+DdEsJiDJ/VnmUPt3 jgZA== X-Gm-Message-State: AElRT7G41NknqU1Qj7EYgv/RL4Lwq9auZPvseFjjcExi9B9qYthCu5BR J5zGEVZd7VcQsjXGY4/QqD5fDbKtxYE= X-Google-Smtp-Source: AG47ELtv3UcQaHHv4CE3vjJU4HA26m6FXV9bSRjjdV6EZI1Q5EPN7rfqXsRsSuSVSKKe3R4VNpd9wg== X-Received: by 10.46.7.80 with SMTP id i16mr7110952ljd.78.1521148286692; Thu, 15 Mar 2018 14:11:26 -0700 (PDT) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com. [209.85.215.53]) by smtp.gmail.com with ESMTPSA id 63-v6sm1381829lfr.61.2018.03.15.14.11.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Mar 2018 14:11:26 -0700 (PDT) Received: by mail-lf0-f53.google.com with SMTP id e5-v6so8269681lfb.7; Thu, 15 Mar 2018 14:11:26 -0700 (PDT) X-Received: by 2002:a19:9e95:: with SMTP id h143-v6mr7812178lfe.129.1521148286171; Thu, 15 Mar 2018 14:11:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.54.1 with HTTP; Thu, 15 Mar 2018 14:11:05 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Thu, 15 Mar 2018 16:11:05 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: Joe Maloney Cc: freebsd-virtualization@freebsd.org, Ed Maste , tsoome@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Thu, 15 Mar 2018 21:11:35 -0000 On Thu, Mar 15, 2018 at 4:06 PM, Joe Maloney wrote: > On Wed, Mar 14, 2018 at 5:55 PM, Joe Maloney wrote: >> Hello everyone, >> Today after we attempted to merge the latest 11-STABLE into FreeNAS we >> found an issue with EFI boot during the testing process. >> >> To narrow done the issue I have tested the following images: >> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180307-r330606-disc1.iso >> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180307-r330605-disc1.iso >> >> To summarize I setup a bhyve VM with EFI, and graphics. Install with >> UFS, and ZFS work. >> >> After install during the boot the following message appears if ZFS is used: >> Failed to start image provided by ZFS (14) >> >> If UFS is used during the install here is what the message looks like >> on first boot: >> Failed to start image provided by UFS (14) >> >> Here is a screenshot showing the issue for ZFS: >> https://imgur.com/a/rQRck >> >> If bhyveload is used there is no issue booting. From what I can tell >> it is only if the EFI firmware is used even with graphics mode off. >> This has affected both CURRENT, and the latest 11-STABLE snapshot >> which are linked above. >> >> I will be out of office at the end of the week for several weeks, and >> may be unable to respond to further replies right away. Either way I wanted to >> make the project aware while others at iX look into this Thanks. >> >> Joe Maloney >> QA Manager / iXsystems >> Enterprise Storage & Servers Driven By Open Source > > I believe the problem may have been introduced with this commit: > > https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 > > I can build an 11-STABLE image prior to that commit, and I do not > exhibit the booting issues with bhyve using EFI. That r329114 commit > does not build at all so I suspect it, or something after it involving > loader work based on feedback from other iX engineers. > > What led me to start looking at this time period was this bug which > references a large merge that address the same issue for RPI3: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216940 Given how that PR went, CC'ing tsoome@ who diagnosed the RPi3 problem -- he's good at these kind of things. =) > > Unfortunately now something causes that exact same "Failed to start > image provided by UFS (14)" error for BHYVE with UEFI. > From owner-freebsd-virtualization@freebsd.org Thu Mar 15 22:01:44 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 23CDAF57A0F for ; Thu, 15 Mar 2018 22:01:44 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com [209.85.215.42]) (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 84BFC7B846; Thu, 15 Mar 2018 22:01:43 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f42.google.com with SMTP id g13-v6so1484903lfe.10; Thu, 15 Mar 2018 15:01:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Ys+oTlJ70TPLuxIM6my7Ok0CLRSXx6htVk8sCTqZtP8=; b=PKDASUE8a+pC6e3S2GalYbqlt1ZWn0TLxJaHhLwi8R31OmWrHJ6Q1Nw6jZK8Qs4cMU ncsgv+2g7MQuhWnO9Nlkzm/Q3U7QVcR7M37qhfBZTC1yqLU6eUDKx+T2li44/oSGjPKZ yhEJa4i/4A5bkWvCDrzFeu3fEwApcbZENb4drjhyCnyHls+lpgwCvfacNg+fc6Bgtv3f dVw02dNjKU2Vd1Iw80h3wHdFBG1H9PvzEysOkTGA2JEIdNNySCa8pnWkW2BmMP4VBj1W qx3WpYXFZ5Za8v18482VJn7Nu3a10jlCc2s9wPTJf+Yi0zVtOA0IpbuWJXYkhLeuqJgw VMAQ== X-Gm-Message-State: AElRT7HY/Rwgq9Q3cYN5jbYisDxLi+te0XEPqj7QyOZqHcdzpmmPQ/6w AMOOUq2BDP2wEjoib77UA5Z6jjnwpFw= X-Google-Smtp-Source: AG47ELt3oFm+jRIyvsGxQaTDK/moM4vFzH9ynonRfnyW0DE5AuajjSe9Vd1v5SqR4UXifVNEIbkXNw== X-Received: by 2002:a19:8f91:: with SMTP id s17-v6mr7832097lfk.56.1521151294621; Thu, 15 Mar 2018 15:01:34 -0700 (PDT) Received: from mail-lf0-f44.google.com (mail-lf0-f44.google.com. [209.85.215.44]) by smtp.gmail.com with ESMTPSA id j73sm1289350ljb.57.2018.03.15.15.01.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Mar 2018 15:01:34 -0700 (PDT) Received: by mail-lf0-f44.google.com with SMTP id h127-v6so12429045lfg.12; Thu, 15 Mar 2018 15:01:34 -0700 (PDT) X-Received: by 2002:a19:e9cc:: with SMTP id j73-v6mr6687380lfk.99.1521151294378; Thu, 15 Mar 2018 15:01:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.54.1 with HTTP; Thu, 15 Mar 2018 15:01:13 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Thu, 15 Mar 2018 17:01:13 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: Peter Grehan Cc: Joe Maloney , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Thu, 15 Mar 2018 22:01:44 -0000 On Thu, Mar 15, 2018 at 4:09 PM, Peter Grehan wrote: >> I believe the problem may have been introduced with this commit: > > >> https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 > > Any chance of being able to work out where in that list of commits in > CURRENT the loader stopped working ? > Indeed- if you could work out the exact commit in that range from head that caused it, I wouldn't think it to be a tough fix. After tonight I'm out until Sunday, but should have time Sunday or Monday to try and diagnose it further. From owner-freebsd-virtualization@freebsd.org Thu Mar 15 23:07:50 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 71861F5C67F for ; Thu, 15 Mar 2018 23:07:50 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com [209.85.215.45]) (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 43A2C7E9E7 for ; Thu, 15 Mar 2018 23:07:48 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f45.google.com with SMTP id x205-v6so12672003lfa.0 for ; Thu, 15 Mar 2018 16:07:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:cc; bh=d31TjShogQlYS0xZT19bdMVpCqKrz5dfdf9Zpn2tM0A=; b=FP01UIcf4xx5pCQ+gJOxO2wmKmbAQ1wvazaNBb+dNY1fUkU9NlYcGINMX/3Fy/IGeg Hli3W7SUxhv/HB6Iz5LvHXAA0YZih7UkxPPeFNfuKjGu9SmqnqrABHZeifcAc2J7/l7w F3FQf/6C+M4UX387XnNsqaG31G+9zjlNEN8FgriTOgUmCYRhscM4Z313fTCQyS5uVAWj dHjvT9Vu/qlwhKVlIqykMBSdCiTkx+RD9idd3vnN64pecx1RWCKP8i25q8iGbvHusoMk NWqnOrR8C+9Fzz7xKt4Da36ERR82lVGs3h3JmlAw/1EFc3mIN8PNZb/MAHMINEcfNPQe LzZA== X-Gm-Message-State: AElRT7GvDZJp8zoR3k+m49HtIFY1q6mcZIzBvOhA+sLvypgFYHYo1BiV 8bK9sL7MzmGTKmSnyNK69dIVX2XoTXI= X-Google-Smtp-Source: AG47ELsr0obSu1ereymxte86KyRyB3lc5oQjqNabYFU35DspdMnuI6+KAtT/QFL5iBMWz4uKmB5nRQ== X-Received: by 2002:a19:1cc4:: with SMTP id c187-v6mr7282391lfc.44.1521155267188; Thu, 15 Mar 2018 16:07:47 -0700 (PDT) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com. [209.85.215.45]) by smtp.gmail.com with ESMTPSA id r20sm143863ljc.8.2018.03.15.16.07.47 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Mar 2018 16:07:47 -0700 (PDT) Received: by mail-lf0-f45.google.com with SMTP id f75-v6so12638436lfg.6 for ; Thu, 15 Mar 2018 16:07:47 -0700 (PDT) X-Received: by 10.46.128.214 with SMTP id r22mt6648917ljg.51.1521155266841; Thu, 15 Mar 2018 16:07:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.54.1 with HTTP; Thu, 15 Mar 2018 16:07:26 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Thu, 15 Mar 2018 18:07:26 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI Cc: Peter Grehan , Joe Maloney , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Thu, 15 Mar 2018 23:07:50 -0000 On Thu, Mar 15, 2018 at 5:01 PM, Kyle Evans wrote: > On Thu, Mar 15, 2018 at 4:09 PM, Peter Grehan wrote: >>> I believe the problem may have been introduced with this commit: > > >>> https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 >> >> Any chance of being able to work out where in that list of commits in >> CURRENT the loader stopped working ? >> > > Indeed- if you could work out the exact commit in that range from head > that caused it, I wouldn't think it to be a tough fix. After tonight > I'm out until Sunday, but should have time Sunday or Monday to try and > diagnose it further. Can one of you try this with boot1.efi+loader.efi built from today's head stand/? I'm not sure what I'm expecting here since these are among my first times trying bhyve, but this is what I'm seeing now (vs. from the mentioned head snapshot where I noted similar behavior as originally mentioned): 1.) Get to loader.efi, menu is good 2.) Break into loader prompt 3.) `lsdev`- pager is restricted to the line the prompt is on, so the output is useless 4.) `boot` 5.) "Unhandled ps2 mouse command 0xe1" At this point, the boot looks screwed until I VNC into it- it booted fine here, but the console stopped working after the kernel handoff. Thanks, Kyle Evans From owner-freebsd-virtualization@freebsd.org Fri Mar 16 01:46:13 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 2A96BF37756 for ; Fri, 16 Mar 2018 01:46:13 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 7525B846B4; Fri, 16 Mar 2018 01:46:12 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id v9-v6so13026951lfa.11; Thu, 15 Mar 2018 18:46:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=OvLNFoiaaWccb0xyCw+N1mnrU8e58B49lYRb8pMXDds=; b=hxqUgAtOavwEy5BmA//uGD+yL3/nX4LRMHqdWycVqAPBznFdLklAG4QPsFKmYyG1hv 8/XQmqMXMpKjl/6RACeDSkGs07XjsgvOrAactHvrRVTqsfmig9jKTHW9OhNfvYIdM5Az V0jxj9/N4Zwm6OAuVHFmEUaQhCbImjTnSyevmztUVUhxuXJhD110GuxCyFH74GMMNz9X 37HCuyyLlnT6LDHddN03PN9HcMpChujp/IYmYomQUnE36nDZDFNKxA7uJHoxC459ZLYv Dl66neRWawBX9EUNf1rR58Slax2jNORaNxM395M05zyCP2TSuwdpc+dAScijMIzcBCOr Q7Ag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=OvLNFoiaaWccb0xyCw+N1mnrU8e58B49lYRb8pMXDds=; b=AKk3q8bD45cMwWSZypugF2NH/K36avCzB/Uj1ZAt0uPvm8dDHLFueCDl4SjJUlEqjb c8BROJ+G6WKDqFQXfHnSKCp/CIuyAnIQoQcGQjA3KwMf+kHItWPW/wYlXTQKiLL3drIz 8jeLY7cETs/3fherMIYVxi9XI8ZAM3b++RmLdN9QrSLOEbD6hPOLmC+ai+v+NxQR1kDv Jv85/KF22J8Zsin6OOSgCLJ7pVEhn92JFTRVzmi+wjNh9o+37D6f0ZpQoxyM1s2oPWxW 77oWO67Jwi86Fhf8gkoIyhZ736SiA2t6JDnpir3BBn7ep0hZCydvH7elTgizGmaqbffV 3hyw== X-Gm-Message-State: AElRT7EvGxyHUQdPH4vw+xsQZZYZGz0Y44WKq3cxVebjtnNEjQNjAE1M /GrLzh/wdwuHRP6wnrRvVrqr9bdw0Rbj5L0w2UY= X-Google-Smtp-Source: AG47ELvnNj+tftl7wntDPNXYJJEHo+4fq5Ral3zxgaCQCJYUkTteFRfB0hFgEhQSKuVwcpQ+hYvY17ihWWfg6MLxAkY= X-Received: by 10.46.129.88 with SMTP id t24mr24109ljg.60.1521164770794; Thu, 15 Mar 2018 18:46:10 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:a74f:0:0:0:0:0 with HTTP; Thu, 15 Mar 2018 18:46:10 -0700 (PDT) Reply-To: araujo@freebsd.org In-Reply-To: References: From: Marcelo Araujo Date: Fri, 16 Mar 2018 09:46:10 +0800 Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: Kyle Evans Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 16 Mar 2018 01:46:13 -0000 2018-03-16 7:07 GMT+08:00 Kyle Evans : > On Thu, Mar 15, 2018 at 5:01 PM, Kyle Evans wrote: > > On Thu, Mar 15, 2018 at 4:09 PM, Peter Grehan > wrote: > >>> I believe the problem may have been introduced with this commit: > > > >>> https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 > >> > >> Any chance of being able to work out where in that list of commits in > >> CURRENT the loader stopped working ? > >> > > > > Indeed- if you could work out the exact commit in that range from head > > that caused it, I wouldn't think it to be a tough fix. After tonight > > I'm out until Sunday, but should have time Sunday or Monday to try and > > diagnose it further. > > Can one of you try this with boot1.efi+loader.efi built from today's > head stand/? I'm not sure what I'm expecting here since these are > among my first times trying bhyve, but this is what I'm seeing now > (vs. from the mentioned head snapshot where I noted similar behavior > as originally mentioned): > > 1.) Get to loader.efi, menu is good > 2.) Break into loader prompt > 3.) `lsdev`- pager is restricted to the line the prompt is on, so the > output is useless > 4.) `boot` > 5.) "Unhandled ps2 mouse command 0xe1" > > At this point, the boot looks screwed until I VNC into it- it booted > fine here, but the console stopped working after the kernel handoff. > > Thanks, > > Kyle Evans > _______________________________________________ > 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" > Hi Kyle, I will do that today and report back as soon as I have something. Best, -- -- Marcelo Araujo (__)araujo@FreeBSD.org \\\'',)http://www.FreeBSD.org \/ \ ^ Power To Server. .\. /_) From owner-freebsd-virtualization@freebsd.org Fri Mar 16 01:56:06 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 63FEEF3D540 for ; Fri, 16 Mar 2018 01:56:06 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com [209.85.215.41]) (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 C103384CAC; Fri, 16 Mar 2018 01:56:05 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f41.google.com with SMTP id m69-v6so13033703lfe.8; Thu, 15 Mar 2018 18:56:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6UbOjKgc4xrF91WmwI4tOmVxCp4NpjrW9BdHl7nw3hw=; b=Bd/F0Tw+hokgks6856gT2WFfApiO/vwqNzj+41Fc82xho3ww/W1DvuRUcL60njn6Tp nDM5uy/OdvZ3T0MHNstcoPxbV+IdrMO5qfBICuFIGvR65fM00TsRniSkyUnLzWu03FeS txlYsESnRg9W+PfCAFQKeFwzKZixVowU6f8gH85qAvnfepmMqjW9oC9UVb+GagD1jSUJ OrJNbLzi7Myu8ksgTU0ziDoSPR5Egm1JR9q5b08G+NRES+1XDeOoMLPCbKvjcYgq8pVU dU2/eIso1EiDrunvZo0QK6TR3rNBZLL8G35oGoBsCCAYQOpnfqQoVRyaLuz5vyR9dkNB iJXg== X-Gm-Message-State: AElRT7Hx/tmfbNy+wJkY7zUcC2kyVQt9JvOYZbwMumC2KvE4iSjc1k1p JCiXV+gn23Th9Po3VU5NEyUMKFKdZvs= X-Google-Smtp-Source: AG47ELtoB6ePyKYfeCfzwGqi/eWTLTGnuGKqLf7dEdhZY/sIIudgWa63gzZnVXAH3aRj231MHSU2/g== X-Received: by 2002:a19:1d12:: with SMTP id d18-v6mr33750lfd.128.1521165363623; Thu, 15 Mar 2018 18:56:03 -0700 (PDT) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com. [209.85.215.49]) by smtp.gmail.com with ESMTPSA id d204-v6sm1459337lfe.8.2018.03.15.18.56.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Mar 2018 18:56:03 -0700 (PDT) Received: by mail-lf0-f49.google.com with SMTP id g13-v6so2085713lfe.10; Thu, 15 Mar 2018 18:56:03 -0700 (PDT) X-Received: by 2002:a19:c987:: with SMTP id z129-v6mr40152lff.74.1521165363312; Thu, 15 Mar 2018 18:56:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.54.1 with HTTP; Thu, 15 Mar 2018 18:55:42 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Thu, 15 Mar 2018 20:55:42 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: araujo@freebsd.org Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Fri, 16 Mar 2018 01:56:06 -0000 On Thu, Mar 15, 2018 at 8:46 PM, Marcelo Araujo wrote: > > > 2018-03-16 7:07 GMT+08:00 Kyle Evans : >> >> On Thu, Mar 15, 2018 at 5:01 PM, Kyle Evans wrote: >> > On Thu, Mar 15, 2018 at 4:09 PM, Peter Grehan >> > wrote: >> >>> I believe the problem may have been introduced with this commit: > > >> >>> https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 >> >> >> >> Any chance of being able to work out where in that list of commits in >> >> CURRENT the loader stopped working ? >> >> >> > >> > Indeed- if you could work out the exact commit in that range from head >> > that caused it, I wouldn't think it to be a tough fix. After tonight >> > I'm out until Sunday, but should have time Sunday or Monday to try and >> > diagnose it further. >> >> Can one of you try this with boot1.efi+loader.efi built from today's >> head stand/? I'm not sure what I'm expecting here since these are >> among my first times trying bhyve, but this is what I'm seeing now >> (vs. from the mentioned head snapshot where I noted similar behavior >> as originally mentioned): >> >> 1.) Get to loader.efi, menu is good >> 2.) Break into loader prompt >> 3.) `lsdev`- pager is restricted to the line the prompt is on, so the >> output is useless >> 4.) `boot` >> 5.) "Unhandled ps2 mouse command 0xe1" >> >> At this point, the boot looks screwed until I VNC into it- it booted >> fine here, but the console stopped working after the kernel handoff. >> >> Thanks, >> >> Kyle Evans >> _______________________________________________ >> 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" > > > Hi Kyle, > > I will do that today and report back as soon as I have something. > Thanks! If it's still failing, I think capturing the output of "lsdev" and "show currdev" prior to a failed boot might be most helpful just to make sure there's not something obviously sketchy happening. From owner-freebsd-virtualization@freebsd.org Fri Mar 16 04:22:33 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 B9DFEF4DD5F for ; Fri, 16 Mar 2018 04:22:33 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 1A3E66A3C4; Fri, 16 Mar 2018 04:22:33 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: by mail-lf0-x22b.google.com with SMTP id z143-v6so7154953lff.3; Thu, 15 Mar 2018 21:22:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=BJpN2NH/qONlNGNispW/zlKsp2xV2Ks9Q/PK7wiFoO8=; b=OkCmbLq7ANMsNBP/HkvTNYNtyDtJQppeE+mDnW3pWlbkVfpv3cPHjAECVYN8+LaP6X H6oIORchVWX7ADhIMergZ/1CSOzBR38IHxcChxR3wSreDVkmBDAuqfz1l1syqK99Louj kSLnre/VXOiHQtfjSnpjJmDw2mAkxWe/OOWBrIA2MVrQxneHmgblxSu5mwaXMLbwbEV2 hdN5Xp62Dq1pEioxU/V4smeovg/zAZFwRGQu4B8/RkrYLxgYUsMaFccaNuZqHXLSaLxj 2kl8GSMI9EIRISlRVhUTduBqsUC6BX+1ZBeaJUPGpHX26FE+mWMInWBILs4Iqm/k0Ki2 6qVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=BJpN2NH/qONlNGNispW/zlKsp2xV2Ks9Q/PK7wiFoO8=; b=jIq1ZcL0Lj7102f3e+1US9HL5GveEfO9oeWzHbffmtoUZDsEy+rds93jD0oYmjjb9X iODRKxgJl9FpyyNDKSVTW6o9yjl4qBc3qu9J+/c2Okjlppw3hE+N5WGJ3FUOnbywsOah /Rjst75522/5ALCDKWOmoF604KTgF49XfRoCQqv73sdMmdoXbfTE34lvbKKSTmUVec9c mqeDPatzdE4SfPMEQjkO88hHR71QdCYlDdsTzOg4JL5sNRc3F4KwuIYRiSxvECKwfApQ Ll0GZajMOn5dkp3vvGI4JcwwF8pcDAhGoFH2o6GTBs/USYrY/JjJ33pL9rbW56fbKIp2 743A== X-Gm-Message-State: AElRT7Fv66+ZS0lVt51h7mzsN9l9MilGVx6J6xqdU60qk8JB6BOvw2Ol 9xl4o6E/uffbVo86s6ZuMR2VCZOmg0647NBTM81t1g== X-Google-Smtp-Source: AG47ELvMMmoCkCS5Ywg/QfYblP/6e06wQNAxB+kB54LLCFhDSxbjq9YLMRoaQU8E1UEvITXo8tyG4uW9d/1Jw2UQ/5I= X-Received: by 10.46.25.134 with SMTP id 6mr255977ljz.14.1521174151087; Thu, 15 Mar 2018 21:22:31 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:a74f:0:0:0:0:0 with HTTP; Thu, 15 Mar 2018 21:22:30 -0700 (PDT) Reply-To: araujo@freebsd.org In-Reply-To: References: From: Marcelo Araujo Date: Fri, 16 Mar 2018 12:22:30 +0800 Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: Kyle Evans Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 16 Mar 2018 04:22:34 -0000 2018-03-16 9:55 GMT+08:00 Kyle Evans : > On Thu, Mar 15, 2018 at 8:46 PM, Marcelo Araujo > wrote: > > > > > > 2018-03-16 7:07 GMT+08:00 Kyle Evans : > >> > >> On Thu, Mar 15, 2018 at 5:01 PM, Kyle Evans wrote: > >> > On Thu, Mar 15, 2018 at 4:09 PM, Peter Grehan > >> > wrote: > >> >>> I believe the problem may have been introduced with this commit: > > > >> >>> https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 > >> >> > >> >> Any chance of being able to work out where in that list of commits > in > >> >> CURRENT the loader stopped working ? > >> >> > >> > > >> > Indeed- if you could work out the exact commit in that range from head > >> > that caused it, I wouldn't think it to be a tough fix. After tonight > >> > I'm out until Sunday, but should have time Sunday or Monday to try and > >> > diagnose it further. > >> > >> Can one of you try this with boot1.efi+loader.efi built from today's > >> head stand/? I'm not sure what I'm expecting here since these are > >> among my first times trying bhyve, but this is what I'm seeing now > >> (vs. from the mentioned head snapshot where I noted similar behavior > >> as originally mentioned): > >> > >> 1.) Get to loader.efi, menu is good > >> 2.) Break into loader prompt > >> 3.) `lsdev`- pager is restricted to the line the prompt is on, so the > >> output is useless > >> 4.) `boot` > >> 5.) "Unhandled ps2 mouse command 0xe1" > >> > >> At this point, the boot looks screwed until I VNC into it- it booted > >> fine here, but the console stopped working after the kernel handoff. > >> > >> Thanks, > >> > >> Kyle Evans > >> _______________________________________________ > >> 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" > > > > > > Hi Kyle, > > > > I will do that today and report back as soon as I have something. > > > > Thanks! If it's still failing, I think capturing the output of "lsdev" > and "show currdev" prior to a failed boot might be most helpful just > to make sure there's not something obviously sketchy happening. > Hi, I think we had two bad snapshots! I just finished the tests with HEAD and 11-STABLE latest snapshots: 1) HEAD: FreeBSD-12.0-CURRENT-amd64-20180315-r331001-disc1.iso 2) Stable: FreeBSD-11.1-STABLE-amd64-20180315-r330998-bootonly.iso I have installed it using ZFS and tested using AHCI and virtio-blk. So everything worked fine. Seems those broken snapshots have missed some commits related with EFI. Thank you all. -- -- Marcelo Araujo (__)araujo@FreeBSD.org \\\'',)http://www.FreeBSD.org \/ \ ^ Power To Server. .\. /_)