From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2a00:1450:400c:c09::231; helo=mail-wm0-x231.google.com; envelope-from=zaolin.daisuki@gmail.com; receiver=edk2-devel@lists.01.org Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 8516A210D43B0 for ; Mon, 18 Jun 2018 05:14:37 -0700 (PDT) Received: by mail-wm0-x231.google.com with SMTP id r125-v6so15130955wmg.2 for ; Mon, 18 Jun 2018 05:14:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=LUsesMgu4qTr779BZ7tFymUetjXnTDhBbbJrw0s3wws=; b=imPu+UcH9ecPGWzTWLI3Mg0BhCfJs66EAinuOVLpkMlXu4Zvym/9M5vhaQ88YceQcc ZpAG3ClhH/XsxzJ2cBjVENBU8Bv5UgW3zWKGOYdKgKlhrSKvcgVIrNvdllE0QRCAap5a yT6SyFSTKeFMaDud5Sz/9TDs3kIpkmM3QveJi60lkf8M5QvvHy6G5UdaoxJcBrbvMBkd oQlApqQPojR6lIqU4ViPXjx6SRIKo5QMP1Uszthatz2JKKepfMTlh/+JG1Xhm6nuR+PN fhMNeOnBYq+Vg8UHa85TpnRTtkG4RlN6MGbLH++2t7CyLAuslOtDYOQN92qV4L8OjklQ 3sLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=LUsesMgu4qTr779BZ7tFymUetjXnTDhBbbJrw0s3wws=; b=hB1L9vgXGScjdk2tUtVDWHKHTPBxJ/Ybv9lzlD3YShtKPfKnuqzQORwmqL+ePzIhL1 BnG10AeO8L456cELoUzI6C3gGSbuy4DfzzHJa+VAQTVVZ6I9IdSCXXdk7MXP8petVdDu J3VHHOYjeNIjLTT9UZERSMoKzlRzXJRVws3IkArHi0X4SMSdMw0PvsCFICZ+3/b4O1LS XOipq3IdsWc8g1VBbEuAejrvcjTAGMHkbvlGm1/s8coEWEfuPqw+z616cv+ObOK2DLFJ NLCSMP9jjvufGstF79K5CtlCgh0k41lICiNeYzKoaEzviQ3cR2WdBr6fAIkexEA2Dlvn d/JA== X-Gm-Message-State: APt69E3PBESmkDeupnwQgU13kbxBAS3p/NlHZz8lJ1o6Jc//i8OiMhFb FyjW+9Rw1GQdhfwcxIjyi2YrNbZB X-Google-Smtp-Source: ADUXVKL/CBhnPJwTLMxdiCiB0orvWk0zgorDgXJukAw5OlnfGp4BT8ksAV3njrqsMaMIDcHnXj21mw== X-Received: by 2002:a1c:af95:: with SMTP id y143-v6mr8543066wme.28.1529324075492; Mon, 18 Jun 2018 05:14:35 -0700 (PDT) Received: from [172.25.20.172] (b2b-78-94-0-50.unitymedia.biz. [78.94.0.50]) by smtp.gmail.com with ESMTPSA id n7-v6sm17293792wrr.39.2018.06.18.05.14.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jun 2018 05:14:34 -0700 (PDT) To: Laszlo Ersek 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> <8e848f93-54b0-74b7-0580-f5d313399265@redhat.com> <3c921d7e-32de-7fc4-38ef-87de340688f6@gmail.com> From: Philipp Deppenwiese Message-ID: <5061cc63-73f7-95c3-be94-6a774bebf5cf@gmail.com> Date: Mon, 18 Jun 2018 14:14:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: 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: Mon, 18 Jun 2018 12:14:37 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Hey Laszlo, We guess that's an issue on our side because of some NVRAM issues with VirtualBox. We located it through Windows 10 debugging. Thanks a lot for your support and testing! Maybe you are interested to join the www.osfc.io and talk about some OVMF details. :) Best Regards, Philipp On 14.06.2018 19:29, Laszlo Ersek wrote: > On 06/13/18 23:25, Philipp Deppenwiese wrote: >> We are getting the error after the Windows 10 installation. >> >> Windows boots up for few seconds and then crashes. > I've installed a brand new libvirt domain from the installer ISO > discussed below, reusing the virtual hardware config from my previous > Windows 10 domain -- after enabling SB with EnrollDefaultKeys.efi as > very first step. > > I've installed a bunch of virtio drivers in the guest. As I mentioned > earlier, Windows would permit the installation of those drivers from the > Fedora virtio-win ISO, but it would also block those drivers from being > launched: > > "Windows cannot verify the digital signature for the drivers required > for this device. A recent hardware or software change might have > installed a file that is signed incorrectly or damaged, or that might be > malicious software from an unknown source. (Code 52)" > > Using the WHQL'd RHEL variants, the virtio drivers work fine. I also > installed Firefox in the guest, Cygwin (for having an openssh server), > and the QEMU guest agent. > > I haven't experienced any issues with the guest, beyond the usual > "Windows Update hogs resources beyond recognition" (once I installed the > virtio-net driver). > > Thanks, > Laszlo > >> On 13.06.2018 23:18, Laszlo Ersek wrote: >>> 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 >> _______________________________________________ >> edk2-devel mailing list >> edk2-devel@lists.01.org >> https://lists.01.org/mailman/listinfo/edk2-devel >>