From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=66.187.233.73; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id E5976211944D4 for ; Wed, 13 Jun 2018 14:18:16 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 147F4406DE3D; Wed, 13 Jun 2018 21:18:16 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-122-190.rdu2.redhat.com [10.10.122.190]) by smtp.corp.redhat.com (Postfix) with ESMTP id 927552166BB6; Wed, 13 Jun 2018 21:18:15 +0000 (UTC) To: Philipp Deppenwiese Cc: edk2-devel@lists.01.org References: <2660d487-aa83-e92c-c816-dd205470fea3@redhat.com> <6583409f-e15f-bc73-d16e-bb59be8f2a2c@gmail.com> <4146cdc8-0812-4ee0-bb20-51883fbddbee@redhat.com> <6a91f5ec-99c6-a067-a737-6f6833eb407b@redhat.com> <9c8625a2-1eaa-074a-0f76-600ab14c5379@gmail.com> From: Laszlo Ersek Message-ID: <8e848f93-54b0-74b7-0580-f5d313399265@redhat.com> Date: Wed, 13 Jun 2018 23:18:14 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <9c8625a2-1eaa-074a-0f76-600ab14c5379@gmail.com> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.7]); Wed, 13 Jun 2018 21:18:16 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.7]); Wed, 13 Jun 2018 21:18:16 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'lersek@redhat.com' RCPT:'' Subject: Re: [OvmfPkg] Secure Boot issues X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 21:18:17 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 06/13/18 21:41, Philipp Deppenwiese wrote: > Hey Laszlo, > > It's free for trial and available under: > > https://www.microsoft.com/de-de/evalcenter/evaluate-windows-10-enterprise I tried the following ISO: af9a46ddd2a88ea01e9d3a52f56cf48e6e9d989e5a35f6e88d68be48dccfcb8d 14393.0.160715-1616.rs1_release_cliententerprise_s_eval_x64fre_en-us.iso I simply took my Windows 10 libvirt domain that I used yesterday for testing, and booted it off of the above ISO, rather than the virtual hard disk. I didn't go through with the entire installation, just until it asked for the virtio-win driver CD (so that it could continue reading the virtio-scsi Windows installer ISO, post-EFI), at which point I forced off the VM. Nonetheless, until that point, everything seemed to work fine. Did you encounter the crash after that point, or before it? Thanks Laszlo > On 13.06.2018 21:21, Laszlo Ersek wrote: >> On 06/13/18 15:45, Philipp Deppenwiese wrote: >>> Hey Laszlo, >>> >>> We are using VirtualBox as virtualization solution and >>> don't load guest drivers. But we had the same issue with >>> the current Qemu version as well. >>> >>> Can you try to test your setup with the latest Windows 10 LTSB ? >>> That would help us to understand if that's a general EDK2 >>> issue or just our problem. >> My testing yesterday was supposed to cover the "latest in Windows 10 >> LTSB" -- I had indeed installed the OS earlier from a Windows 10 >> Enterprise N 2015 LTSB ISO, but yesterday that long-term guest of mine >> pulled down all pending updates. >> >> Is that not what you mean? Can you give me an ISO filename and a SHA1 >> checksum then? I could try looking it up in MSDN. (It's not guaranteed >> that my subscription will allow me access to it though.) >> >> Thanks >> Laszlo >