qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Brennan <xaero@xaerolimit.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Network Issues
Date: Sun, 02 Mar 2008 16:31:02 -0500	[thread overview]
Message-ID: <47CB1C96.80306@xaerolimit.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

For some time now, I have been attempting to get the user-mode
networking stack to work when booting any flavor of FreeBSD's bootonly
ISO for a NetInstall.

I can get qemu to boot just fine. The problem is, I can't get it to
actually connect to the outside world and start the install.

I select the device ed0 and no to ipv6, yes to dhcp and it gets an ip of
10.0.2.15 which is fine, I give it a hostname (fbsd for the sake of ease
in this case) and select 'OK', it does what it needs to to format the
partitions and then it fails saying it can't connect to the ftp mirror.
at first, I thought this may have been a dns issue, so I choose to
select my own mirror and pluged in the IP of the mirror. Still failed.

So I had some light discussion in freenode/#qemu and it was suggested
that there is a patch to fix this known issue. But I am unsure of which
patch is needed and how I would use that when using Portage to install
qemu (if need be, I can make a custom ebuild in an overlay that would
patch the srcs.)

So my point is this, can someone help me by pointing me in the right
direction?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHyxyW8hUIAnGfls4RArS8AJ0SHC7DKMfbV9upn/AjU44OiZ7CzQCginwA
Zqf6mW5pSF/I9wafc95/vXQ=
=uHxe
-----END PGP SIGNATURE-----

                 reply	other threads:[~2008-03-02 21:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47CB1C96.80306@xaerolimit.net \
    --to=xaero@xaerolimit.net \
    --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 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).