This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: Communicating with the domU from dom0 without Network

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: Communicating with the domU from dom0 without Network
From: Ligesh <xen@xxxxxxxxxx>
Date: Tue, 8 Aug 2006 23:45:36 +0530
Cc: muli@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Michael LeMay <mdlemay@xxxxxxxxxxxxxx>
Delivery-date: Tue, 08 Aug 2006 11:10:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C0FE64C8.A3E%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060808144545.GA6025@xxxxxxxxxx> <C0FE64C8.A3E%Keir.Fraser@xxxxxxxxxxxx>
Reply-to: Ligesh <xen@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Tue, Aug 08, 2006 at 03:56:56PM +0100, Keir Fraser wrote:
> That's not how TCP/IP works and a statement like 'serial ports do not allow
> multiple simultaneous streams' is not true since a serial port is part of a
> physical link layer so you can implement whatever protocol you like over the
> top (just as you can with e.g. an Ethernet port).

 You have to build a network stack over serial port where every packet has a 
header with the destination port.  You can simulate the entire tcp/ip stack 
over the serial port, but this is again a non-trivial effort. What I meant was 
out-of-box, as in, you just do an open("/dev/ttyS0", "r"), and read and write, 
you won't get multiple connections; you will have to ensure the co-operation of 
the kernel, where it will have to create virtual network ports that will allow 
simultaneous connections to exist.

 Anyway, ultimately my proposal is that multi-stream message passing system 
that is not depended on the ip address would be highly desirable. You can 
actually implement it over the serial port or even the virtual network card 
itself--by using the mac addresses to identify the machines. This would make 
writing system management softwares much easier. Since the future seems to 
point at virtualization getting ubiquitous, this almost becomes a necessary 

:: Ligesh :: http://ligesh.com 

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>