From: Cole Robinson <crobinso@redhat.com>
To: samuel.thibault@ens-lyon.org
Cc: ondrejj@salstar.sk, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] slirp + ipxe + ipv6 dns issue
Date: Fri, 24 Mar 2017 21:17:43 -0400 [thread overview]
Message-ID: <db8ccb55-0570-4b6f-1635-7df2ff0b9ec3@redhat.com> (raw)
Hi Samuel,
A Fedora user reported a regression for his ipxe setup (Jan, CCd). He has a
public PXE server and config. You can see details about his config here:
http://boot.salstar.sk/ipxe/
Reproducer:
wget http://boot.salstar.sk/ipxe/ipxe.lkrn
qemu-system-x86_64 -kernel ipxe.lkrn
Non-working output looks like:
Configuring (net0 52:54:00:12:34:56)..... ok
Could not get time and date: Connection timed out (http://ipxe.org/4c116035)
https://boot.salstar.sk/by_mac/52%3A54%3A00%3A12%3A34%3A56..................
Connection timed out (http://ipxe.org/4c116035)
https://boot.salstar.sk/by_ip/10.0.2.15.................. Connection timed out
(http://ipxe.org/4c116035)
https://boot.salstar.sk/menu.ipxe.................. Connection timed out
(http://ipxe.org/4c116035)
Press any key to enter failsafe menu ...
Working output will quickly drop into a text UI boot menu.
I bisected to this commit:
commit f7725df38750c1eaebc6665159bb58ec23864c92
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Sun Mar 20 16:02:52 2016 +0100
slirp: Add RDNSS advertisement
And infact just reverting it on top of qemu.git makes things work again.
I'm not really sure if this is a bug or if it's just exposing a config issue
on the ipxe server... I tried enabling some ipxe debug commands like
ping/nslookup but didn't really get anywhere. Any thoughts/ideas?
Thanks,
Cole
next reply other threads:[~2017-03-25 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 1:17 Cole Robinson [this message]
2017-03-26 18:39 ` [Qemu-devel] slirp + ipxe + ipv6 dns issue Samuel Thibault
2017-03-27 11:15 ` Ján ONDREJ (SAL)
2017-03-27 20:34 ` Cole Robinson
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=db8ccb55-0570-4b6f-1635-7df2ff0b9ec3@redhat.com \
--to=crobinso@redhat.com \
--cc=ondrejj@salstar.sk \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).