Siva,

I would try to bring it up with MSFT to see what might have caused that.

Bret, Sean,

Any ideas who could be the contact point from MSFT regarding iSCSI boot 
(and potential issues)?
Siva is observing some blue screens (see first email).

Thanks,
Maciej

On 02-Feb-21 12:55, Sivaraman Nainar wrote:
>
> Hello Maciej:
>
> The issue can be seen in *edk2-stable201911* onwards. Haven’t  tested 
> the earlier versions.
>
> -Siva
>
> *From:* Rabeda, Maciej [mailto:maciej.rabeda@linux.intel.com]
> *Sent:* Tuesday, February 2, 2021 4:57 PM
> *To:* devel@edk2.groups.io; Sivaraman Nainar
> *Cc:* Santhosh Kumar V
> *Subject:* Re: [edk2-devel] reg: IPv6 ISCSI Boot with Windows 2019
>
> Hi Nainar,
>
> Could you try to bisect the issue using older EDKII releases to see 
> whether it reproduces there?
>
> Thanks,
> Maciej
>
> On 01-Feb-21 12:57, Sivaraman Nainar wrote:
>
>     Hello Maciej:
>
>     Do we have any update on this Inquiry. IS this need to be checked
>     in Network Pkg or we need to reach Microsoft.
>
>     The issue happening only with Windows OS especially 2019.
>
>     Thanks
>
>     Siva
>
>     *From:* devel@edk2.groups.io <mailto:devel@edk2.groups.io>
>     [mailto:devel@edk2.groups.io <mailto:devel@edk2.groups.io>] *On
>     Behalf Of *Sivaraman Nainar
>     *Sent:* Monday, January 4, 2021 9:03 AM
>     *To:* devel@edk2.groups.io <mailto:devel@edk2.groups.io>
>     *Cc:* Rabeda, Maciej; Santhosh Kumar V
>     *Subject:* [edk2-devel] reg: IPv6 ISCSI Boot with Windows 2019
>
>     Hello all:
>
>     When IPv6 based ISCSI boot performed with Windows 2019 as OS we
>     are seeing the below error during Windows boots.  Out of 10  times
>     1 time it boots properly. Failure rate is 9/10.
>
>     Does anyone met this issue, Wth IPv4 based boot it always boots to OS.
>
>     -Siva
>
>     This e-mail is intended for the use of the addressee only and may
>     contain privileged, confidential, or proprietary information that
>     is exempt from disclosure under law. If you have received this
>     message in error, please inform us promptly by reply e-mail, then
>     delete the e-mail and destroy any printed copy. Thank you.
>
>     
>