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-changelog] This patch explains network-* options in xm.1, including

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] This patch explains network-* options in xm.1, including the bits that are
From: Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Thu, 17 Nov 2005 16:02:09 +0000
Delivery-date: Thu, 17 Nov 2005 16:02:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User emellor@xxxxxxxxxxxxxxxxxxxxxx
# Node ID 88c2d4bbe7c99ed64d42695f694fa092bceb6d13
# Parent  c2f0ed9158ad7fe84b803a7da449dae8492e58d2
This patch explains network-* options in xm.1, including the bits that are
currently not really working.

Signed off by: Sean Dague <sean@xxxxxxxxx>

diff -r c2f0ed9158ad -r 88c2d4bbe7c9 docs/man/xm.pod.1
--- a/docs/man/xm.pod.1 Thu Nov 17 10:58:36 2005
+++ b/docs/man/xm.pod.1 Thu Nov 17 11:01:13 2005
@@ -550,10 +550,10 @@
 =item B<sched-sedf> I<period> I<slice> I<latency-hint> I<extratime> I<weight>
-Set Simple EDF scheduler parameters.  This scheduler provides weighted
-CPU sharing in an intuitive way and uses realtime-algorithms to ensure
-time guarantees.  For more information see
-docs/misc/sedf_scheduler_mini-HOWTO.txt in the Xen distribution.
+Set Simple EDF (Earliest Deadline First) scheduler parameters.  This
+scheduler provides weighted CPU sharing in an intuitive way and uses
+realtime-algorithms to ensure time guarantees.  For more information
+see docs/misc/sedf_scheduler_mini-HOWTO.txt in the Xen distribution.
@@ -640,10 +640,53 @@
-=item B<network-attach> I<domain-id> I<[script=script]> I<[ip=ipaddr]>
+=item B<network-attach> I<domain-id> I<[script=scriptname]> I<[ip=ipaddr]>
 I<[mac=macaddr]> I<[bridge=bridge-name]> I<[backend=bedomain-id]>
+Creates a new network device in the domain specified by domain-id.  It
+takes the following optional options:
+=over 4
+=item I<script=scriptname>
+Use the specified script name to bring up the network.  Defaults to
+the default setting in xend-config.sxp for I<vif-script>.
+=item I<ip=ipaddr>
+Passes the specified IP Address to the adapter on creation.  
+FIXME: this currently appears to be B<broken>.  I'm not sure under what
+circumstances this should actually work.
+=item I<mac=macaddr>
+The MAC address that the domain will see on its ethernet device.  If
+the device is not specified it will be randomly generated with the
+00:16:3e vendor id prefix.
+=item I<bridge=bridge-name>
+The name of the bridge to attach the vif to, in case you have more
+than one.  This defaults to 
+=item I<backend=bedomain-id>
+The backend domain id.  By default this is domain 0.
 =item B<network-detach> I<domain-id> I<devid>
+Removes the network device from the domain specified by I<domain-id>.
+I<devid> is the virtual interface device number within the domain
+(i.e. the 3 in vif22.3).
+FIXME: this is currently B<broken>.  Network devices aren't completely
+removed from domain 0.
 =item B<network-list> I<domain-id>

Xen-changelog mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] This patch explains network-* options in xm.1, including the bits that are, Xen patchbot -unstable <=