From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JVvmW-0001MK-Qt for qemu-devel@nongnu.org; Sun, 02 Mar 2008 16:31:40 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JVvmT-0001Kw-Un for qemu-devel@nongnu.org; Sun, 02 Mar 2008 16:31:40 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JVvmT-0001Kp-MX for qemu-devel@nongnu.org; Sun, 02 Mar 2008 16:31:37 -0500 Received: from gv-out-0910.google.com ([216.239.58.191]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JVvmT-0004ME-HR for qemu-devel@nongnu.org; Sun, 02 Mar 2008 16:31:37 -0500 Received: by gv-out-0910.google.com with SMTP id n40so2184486gve.36 for ; Sun, 02 Mar 2008 13:31:34 -0800 (PST) Message-ID: <47CB1C96.80306@xaerolimit.net> Date: Sun, 02 Mar 2008 16:31:02 -0500 From: Chris Brennan MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Network Issues Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org -----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-----