From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EMgyt-0008UG-5X for qemu-devel@nongnu.org; Tue, 04 Oct 2005 03:12:55 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EMgyp-0008Sv-KK for qemu-devel@nongnu.org; Tue, 04 Oct 2005 03:12:53 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EMgym-0008Om-Sa for qemu-devel@nongnu.org; Tue, 04 Oct 2005 03:12:50 -0400 Received: from [64.233.182.206] (helo=nproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EMgvD-000313-If for qemu-devel@nongnu.org; Tue, 04 Oct 2005 03:09:07 -0400 Received: by nproxy.gmail.com with SMTP id n15so193826nfc for ; Tue, 04 Oct 2005 00:09:06 -0700 (PDT) Message-ID: <46d6db660510040009i1173586esa7daf446e2a3e883@mail.gmail.com> Date: Tue, 4 Oct 2005 09:09:06 +0200 From: Christian MICHON Subject: Re: [Qemu-devel] tun/tap networking: patch for existing tun In-Reply-To: <434194AF.9060504@eclis.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050930221321.C7BED31C14@ravel.n2.net> <433F92CB.1060600@eclis.ch> <43402ABC.3040805@us.ibm.com> <20051002193912.GB13825@jbrown.mylinuxbox.org> <20051003151425.GC27327@jbrown.mylinuxbox.org> <43417879.5020106@bellard.org> <46d6db660510031222y70cb7257u7f32f823474c8917@mail.gmail.com> <434194AF.9060504@eclis.ch> Reply-To: Christian MICHON , 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 no vde for windows hosts :( On 10/3/05, Jean-Christian de Rivaz wrote: > Christian MICHON a =E9crit : > > to do so, does that mean we would need to launch a 1st qemu > > instance which would contain the dhcp server, and next qemu > > instances would connect to it ? > > > > if so, 'qemu -server' and 'qemu -client -connect_to server' could > > be useful... > > As I understand and with what I know, you can do that now using a > virtual network (VDE for example). What matter is that fact that two > qemu instances are connected on the same network. DHCP protocol (like > any others netowrk protocol) is over that network and is not visible to > qemu. > > To do what you wants, you have to use to different operating system > image, one that contains a DHCP server, and the second that contain a > DHCP client. > > 1) create a virtual switch: "vde_switch -s /tmp/my_switch.ctl" > > 2) start a virtual server: "vdeq -s /tmp/my_switch.ctl qemu-softmmu -hda > dhcp-server.bin [...]" > > 3) start a virtual client: "vdeq -s /tmp/my_switch.ctl qemu-softmmu -hda > dhcp-client.bin [...]" > > -- > Jean-Christian de Rivaz > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > -- Christian