qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nigel Horne <njh@bandsman.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Networking under Hurd quest still not working
Date: Sat, 10 Jul 2010 08:42:04 +0100	[thread overview]
Message-ID: <4C38244C.1070505@bandsman.co.uk> (raw)
In-Reply-To: <20100710060841.GA13806@hall.aurel32.net>

Aurelien,

Thank you for your reply.
>> I've rebuild QEMU and gone back to old images of the Hurd when
>> networking was working (to eliminate that as a cause).  Networking is
>> still not working with the latest Git version of QEMU with Linux host
>> and Hurd guest.
>>      
> Do you have more details about that? I haven't been able to reproduce
> the problem here. Would be nice to have an image and the command line
> you used.
>    

I originally got the image from 
http://www.gnu.org/software/hurd/hurd/running/qemu.html (click on 
"Readily Available Images").  I've made a few changes since then 
(primarily a few apt-get updates and upgrades).

The command line is "qemu -hda debian-hurd-k16-qemu.img -m 512 -boot c 
-net nic,model=rtl8139 -net user --enable-kvm"

The commands I used to get the networking running were:
settrans -afgp /servers/socket/2 /hurd/pfinet -i eth0 -a 10.0.2.15 -g 
10.0.2.2 -m 255.255.255.0
echo "nameserver 10.0.2.3" > /etc/resolv.conf
> The best would be to bisect the issue to find the commit which
> introduced the problem.
>    
-Nigel

-- 
Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter.
NJH Music, ICQ#20252325, twitter: @nigelhorne
njh@bandsman.co.uk http://www.bandsman.co.uk

  reply	other threads:[~2010-07-10  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 16:48 [Qemu-devel] Networking under Hurd quest still not working Nigel Horne
2010-07-10  6:08 ` Aurelien Jarno
2010-07-10  7:42   ` Nigel Horne [this message]
2010-07-10  8:02     ` Aurelien Jarno
2010-07-10  8:16       ` Nigel Horne
2010-07-10  8:37         ` Aurelien Jarno

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=4C38244C.1070505@bandsman.co.uk \
    --to=njh@bandsman.co.uk \
    --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).