All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mattia Gentilini <mgentili@CS.UniBO.IT>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vdq and qemu
Date: Sat, 02 Jun 2007 14:16:26 +0200	[thread overview]
Message-ID: <46615F9A.1000805@CS.UniBO.IT> (raw)
In-Reply-To: <46613B3C.1040801@basicsedv.de>

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

Adrian Lambeck ha scritto:
> Thanks for the reply! I am using vdeq to connect the qemu instance to 
> the vde_switch and therefor I can not use dpipe. I will have to look 
> into the sources of vdeq to see if I can change this somehow.
> 
> Adrian Lambeck
> 
why not? dpipe connects vde_switch(es) together, it doesn't interfere 
with vdeq.

To better understand how to interconnect vde_switch, vdeq and dpipe I 
attach this schema, inspired by those made by Renzo Davoli, main 
developer of VDE. In particular, connection number 3 is made when you 
launch vdeq specifying the switch to connect QEMU to. Then, you launch 
dpipe with the tho vde_plug(s) to connect two vde_switch(es). the plugs 
implement the little gray connections you see in the left part of the 
schema, while dpipe creates the connection number 4 (green). The 
connection number 2 (dark red) could be created either by slirpvde or a 
tun/tap interface.

-- 
|\/|55: Mattia Gentilini e 55 oggetti non identificati
|/_| MSc in Computer Science      | www.getfirefox.com
|\/| University of Bologna, Italy | www.getthunderbird.com
* Using Windows Vista Business powered by Galvatron (Athlon 64 X2) *

[-- Attachment #2: VDE-example.png --]
[-- Type: image/png, Size: 55662 bytes --]

  reply	other threads:[~2007-06-02 12:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02  9:41 [Qemu-devel] vdq and qemu Adrian Lambeck
2007-06-02 12:16 ` Mattia Gentilini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-10 13:04 adrian.lambeck
2007-05-14 12:13 ` Mattia Gentilini

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=46615F9A.1000805@CS.UniBO.IT \
    --to=mgentili@cs.unibo.it \
    --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.