grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: <grub-devel@gnu.org>
Subject: Re: [PATCH 0/3] fix ipv6 support
Date: Thu, 6 Aug 2015 10:23:52 -0400	[thread overview]
Message-ID: <55C36DF8.1040008@fb.com> (raw)
In-Reply-To: <20150806040632.GA12717@linux-dsax.tai.apac.novell.com>

On 08/06/2015 12:06 AM, Michael Chang wrote:
> On Wed, Aug 05, 2015 at 10:50:37AM -0700, Josef Bacik wrote:
>> These patches are on top of Michael Chang's bootp6 code (which we also really
>> need so it would be great if those could go in as well).  At Facebook we have
>> ipv6 only clusters that we need to be able to provision over the network.  The
>> current grub2 support for ipv6 is broken in a few ways.  The routing stuff
>> needed to be reworked to handle talking to an ipv6 router properly.  I tried to
>> not change the code too much in order to make sure I didn't regress the ipv4
>> support.
>
> Thanks for your feedback, that's very encouraging to me. :-)
>
> The patch is still in review and need to solve some issues addressed by
> Andrei. I was distracted by some other stuff later and my own server
> hosted virtual machine to develope and test ipv6 was accidently broken
> by system update of virtualization package. The major changes that cause
> the failure seems to be qemu changes to enable ipxe UEFI option rom
> which somehow did not provide ipv6 support in it's UNDI driver, along
> with some other issues in edk2/ovmf itself.
>
> Anyway boop6 patches seems to be innocent to the new problem I have and
> can continue the work by not loading iPXE UEFI option rom from qemu. To
> whom who may be interested here is libvirt guest config I use to disable
> option rom and use edk2's network stack.
>
>      <interface type='network'>
>        <rom bar='off'/>
>      </interface>
>
> I will continue on working on the patches and follow through review for
> the patch set with upstream.
>

That would be great, anything you post I'll pull in immediately and test 
on real hardware in one of our ipv6 only clusters to make sure it's 
still working.  From my perspective none of your code has given me any 
problems, it pulls the dhcp information that uefi has already properly, 
and manually doing the bootp thing also works properly.  Thanks,

Josef



      reply	other threads:[~2015-08-06 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 17:50 [PATCH 0/3] fix ipv6 support Josef Bacik
2015-08-05 17:50 ` [PATCH 1/3] efinet: handle get_status() properly Josef Bacik
2015-08-05 17:50 ` [PATCH 2/3] net: add local route when creating link local ipv6 interface Josef Bacik
2015-08-05 17:50 ` [PATCH 3/3] net: fix ipv6 routing Josef Bacik
2015-08-06  4:06 ` [PATCH 0/3] fix ipv6 support Michael Chang
2015-08-06 14:23   ` Josef Bacik [this message]

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-all 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=55C36DF8.1040008@fb.com \
    --to=jbacik@fb.com \
    --cc=grub-devel@gnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).