From: "Sivaraman Nainar" <sivaramann@amiindia.co.in>
To: "Rabeda, Maciej" <maciej.rabeda@linux.intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Santhosh Kumar V <santhoshkumarv@amiindia.co.in>
Subject: Re: [edk2-devel] reg: IPv6 ISCSI Boot with Windows 2019
Date: Tue, 2 Feb 2021 11:55:05 +0000 [thread overview]
Message-ID: <B4DE137BDB63634BAC03BD9DE765F19702E3DC8014@VENUS1.in.megatrends.com> (raw)
In-Reply-To: <656b85e5-cbcb-6b83-6905-0c02b618b763@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1691 bytes --]
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] 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.
[cid:image001.png@01D6F988.5718F450]
-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.
[-- Attachment #1.2: Type: text/html, Size: 6776 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 630513 bytes --]
next prev parent reply other threads:[~2021-02-02 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1656E9FAA1FFAC66.9531@groups.io>
2021-02-01 11:57 ` [edk2-devel] reg: IPv6 ISCSI Boot with Windows 2019 Sivaraman Nainar
2021-02-02 11:26 ` Maciej Rabeda
2021-02-02 11:55 ` Sivaraman Nainar [this message]
2021-02-02 13:53 ` Maciej Rabeda
2021-02-02 17:34 ` [EXTERNAL] " Bret Barkelew
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=B4DE137BDB63634BAC03BD9DE765F19702E3DC8014@VENUS1.in.megatrends.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