From: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel@lists.01.org
Subject: Re: [OvmfPkg] Secure Boot issues
Date: Wed, 13 Jun 2018 21:41:26 +0200 [thread overview]
Message-ID: <9c8625a2-1eaa-074a-0f76-600ab14c5379@gmail.com> (raw)
In-Reply-To: <6a91f5ec-99c6-a067-a737-6f6833eb407b@redhat.com>
Hey Laszlo,
It's free for trial and available under:
https://www.microsoft.com/de-de/evalcenter/evaluate-windows-10-enterprise
Best Regards, Philipp
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
next prev parent reply other threads:[~2018-06-13 19:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 13:12 [OvmfPkg] Secure Boot issues Philipp Deppenwiese
2018-06-12 13:59 ` Laszlo Ersek
2018-06-12 14:51 ` Philipp Deppenwiese
2018-06-12 18:14 ` Laszlo Ersek
2018-06-13 13:45 ` Philipp Deppenwiese
2018-06-13 19:21 ` Laszlo Ersek
2018-06-13 19:41 ` Philipp Deppenwiese [this message]
2018-06-13 21:18 ` Laszlo Ersek
2018-06-13 21:25 ` Philipp Deppenwiese
2018-06-14 17:29 ` Laszlo Ersek
2018-06-18 12:14 ` Philipp Deppenwiese
2018-06-18 12:30 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c8625a2-1eaa-074a-0f76-600ab14c5379@gmail.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox