From: Erwan Velu <erwan.velu@free.fr>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] Making pxe working in the "NAT" mode
Date: Fri, 16 Feb 2007 11:12:08 +0100 [thread overview]
Message-ID: <45D58378.9040509@free.fr> (raw)
In-Reply-To: <45D529B9.5020001@codemonkey.ws>
Anthony Liguori wrote:
> Hi Erwan,
>
> I really like the idea of your patch. Of course, the hard coding is
> not really reasonable :-) Also, PXE is an x86-ism. What you've
> really done is added a mechanism to publish a BOOTP name. We do need
> to add a new option too as one may want to use -boot n without
> publishing a BOOTP filename.
>
> Using your patch as a basis, I've written three patches. The first
> one is the tsize negotiation fix for the TFTP server. The second adds
> a -bootp option for specifying the location of the BOOTP image. The
> third changes the -tftp option to take root directory. The end
> result, is that now you can say:
>
> qemu -hda /tmp/a.img -boot n -tftp ~/tftpboot -bootp /pxelinux.0
>
> And you get the same results without the hard coding. What do you think?
I just love it, you exactly did the stuff I didn't knew how to do. It
just push a turn a simple Proof-of-concept into a "ready-to-use" feature.
Thanks a lot for you excellent work, I hope now this patch could be
integrated upstream for allowing people to use PXE in qemu without the
need of knowing how to configure the dhcp/tftp and bridging stuff.
One more time, thanks anthony for this patches.
prev parent reply other threads:[~2007-02-16 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 22:16 [Qemu-devel] [PATCH 1/1] Making pxe working in the "NAT" mode Erwan Velu
2007-02-16 3:49 ` Anthony Liguori
2007-02-16 10:12 ` Erwan Velu [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=45D58378.9040509@free.fr \
--to=erwan.velu@free.fr \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.