From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] about DHCP server in qemu
Date: Thu, 29 Sep 2005 18:14:06 -0400 [thread overview]
Message-ID: <20050929221406.GA6019@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <433C61B7.6070804@wasp.net.au>
On Fri, Sep 30, 2005 at 01:50:47AM +0400, Brad Campbell wrote:
> >No. In fact, the server is set up to always return the same IP in response
> >to
> >a request.
> err.. it works for me...
Yes, it seems that Fabrice has slipped in a few changes since I last looked at
the slirp code. :) The internal DHCP server can now support 16 dhcp clients.
That's for multiple clients within a single qemu guest though (think multiple
NICs here). I don't see any way for qemu guests to be able to ping each other
(for example) if they are both using user-net.
> Even if it worked like a full fledged DHCP server, there's no
> >way to
> >connect multiple guests together. The best you can do is slirpvde.
> >
> This gives me 9 qemu sessions that all get different 10.x.x.x ip addresses
> via dhcp
>
> #!/bin/sh
> rm /tmp/qemu-irc-*
> for i in 1 2 3 4 5 6 7 8 9 ; do
> qemu-img create -b /tracks/lin.img -f qcow /tmp/qemu-irc-$i
> qemu -fda /tracks/floppy.img -hda /tmp/qemu-irc-$i -boot a -user-net
> -macaddr C0:0F:FE:01:01:9$i -m32 &
> done
>
> Regards,
> Brad
I find it suprising that this works. From the code in slirp/bootp.c it looks
like qemu's dhcp server will give out 10.0.2.15 first, then 10.0.2.16, and so
on (so it goes in sequential order). But thats within a single qemu session.
Theres no way for multiple user-net qemu guests to communicate (at least on
the ethernet level) so the guests should have the same ip address. Very strange.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-09-29 22:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 15:00 [Qemu-devel] about DHCP server in qemu octane indice
2005-09-29 20:34 ` Jim C. Brown
2005-09-29 21:50 ` Brad Campbell
2005-09-29 22:14 ` Jim C. Brown [this message]
2005-09-30 8:17 ` octane indice
2005-09-30 12:21 ` Oliver Gerlich
2005-09-30 13:10 ` Jim C. Brown
2005-09-30 14:51 ` octane indice
2005-10-01 21:17 ` Jim C. Brown
2005-10-02 2:39 ` Henrik Nordstrom
2005-10-02 19:23 ` Jim C. Brown
2005-10-03 11:34 ` octane indice
2005-09-30 18:28 ` John R. Hogerhuis
2005-09-30 21:37 ` Henrik Nordstrom
2005-09-30 21:59 ` Jim C. Brown
2005-10-03 15:55 ` octane indice
2005-10-03 18:12 ` Henrik Nordstrom
2005-10-03 19:20 ` Christian MICHON
2005-10-03 20:37 ` Henrik Nordstrom
2005-10-04 7:47 ` Christian MICHON
2005-10-04 11:43 ` Jim C. Brown
2005-10-05 9:38 ` Henrik Nordstrom
2005-10-03 21:31 ` Jim C. Brown
2005-10-04 4:19 ` octane indice
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=20050929221406.GA6019@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--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.