From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu 0.9.0 win32 PXE boot can't work
Date: Fri, 20 Jul 2007 12:55:49 +0100 [thread overview]
Message-ID: <200707201255.49615.paul@codesourcery.com> (raw)
In-Reply-To: <a0ea16650707191725k74b3fdb6h1f74db6daa1af869@mail.gmail.com>
On Friday 20 July 2007, 姚春林 wrote:
> > Can you try using the other nic types? I'm most interested in the
> > results with the rtl8139 model.
>
> I have used rtl8139 the first time.Does not work.
>
> I think the etherboot is OK. because I can use it to boot from vmware.
> and the ethereal captured the DHCP offer packet on tap nic.
> How the tap-win32 and qemu deal with this packet?
qemu doesn't do anything with the network traffic. It just passes it on to
your host OS. This is almost certainly a bug in your host networking
configuration. i.e. you don't have a dhcp server listening on that interface.
Configure it exactly the same as you would on a real network/machine.
Paul
prev parent reply other threads:[~2007-07-20 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 13:57 [Qemu-devel] qemu 0.9.0 win32 PXE boot can't work 姚春林
2007-07-19 15:45 ` Anthony Liguori
2007-07-20 0:25 ` 姚春林
2007-07-20 0:38 ` Anthony Liguori
2007-07-20 11:55 ` Paul Brook [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=200707201255.49615.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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.