2008-09-25 01:20:56 +02:00
|
|
|
Index: xen-3.3.1-testing/docs/man/xmdomain.cfg.pod.5
|
2008-05-24 00:00:43 +02:00
|
|
|
===================================================================
|
2008-09-25 01:20:56 +02:00
|
|
|
--- xen-3.3.1-testing.orig/docs/man/xmdomain.cfg.pod.5
|
|
|
|
|
+++ xen-3.3.1-testing/docs/man/xmdomain.cfg.pod.5
|
2008-05-24 00:00:43 +02:00
|
|
|
@@ -335,16 +335,10 @@ at hda1, which is the root filesystem.
|
|
|
|
|
|
|
|
|
|
=item I<NFS Root>
|
|
|
|
|
|
|
|
|
|
-FIXME: write me
|
|
|
|
|
-
|
|
|
|
|
=item I<LVM Root>
|
|
|
|
|
|
|
|
|
|
-FIXME: write me
|
|
|
|
|
-
|
|
|
|
|
=item I<Two Networks>
|
|
|
|
|
|
|
|
|
|
-FIXME: write me
|
|
|
|
|
-
|
|
|
|
|
=back
|
|
|
|
|
|
|
|
|
|
=head1 SEE ALSO
|
2008-09-25 01:20:56 +02:00
|
|
|
Index: xen-3.3.1-testing/docs/man/xm.pod.1
|
2008-05-24 00:00:43 +02:00
|
|
|
===================================================================
|
2008-09-25 01:20:56 +02:00
|
|
|
--- xen-3.3.1-testing.orig/docs/man/xm.pod.1
|
|
|
|
|
+++ xen-3.3.1-testing/docs/man/xm.pod.1
|
2008-10-11 16:22:01 +02:00
|
|
|
@@ -295,7 +295,8 @@ scheduling by the Xen hypervisor.
|
2008-05-24 00:00:43 +02:00
|
|
|
|
|
|
|
|
=item B<s - shutdown>
|
|
|
|
|
|
|
|
|
|
-FIXME: Why would you ever see this state?
|
|
|
|
|
+The guest has requested to be shutdown, rebooted or suspended, and the
|
|
|
|
|
+domain is in the process of being destroyed in response.
|
|
|
|
|
|
|
|
|
|
=item B<c - crashed>
|
|
|
|
|
|
2008-10-11 16:22:01 +02:00
|
|
|
@@ -308,8 +309,6 @@ restart on crash. See L<xmdomain.cfg> f
|
2008-05-24 00:00:43 +02:00
|
|
|
The domain is in process of dying, but hasn't completely shutdown or
|
|
|
|
|
crashed.
|
|
|
|
|
|
|
|
|
|
-FIXME: Is this right?
|
|
|
|
|
-
|
|
|
|
|
=back
|
|
|
|
|
|
2008-10-11 16:22:01 +02:00
|
|
|
B<NOTES>
|
|
|
|
|
@@ -733,8 +732,6 @@ Xen ships with a number of domain schedu
|
2008-05-24 00:00:43 +02:00
|
|
|
time with the B<sched=> parameter on the Xen command line. By
|
|
|
|
|
default B<credit> is used for scheduling.
|
|
|
|
|
|
|
|
|
|
-FIXME: we really need a scheduler expert to write up this section.
|
|
|
|
|
-
|
|
|
|
|
=over 4
|
|
|
|
|
|
|
|
|
|
=item B<sched-credit> [ B<-d> I<domain-id> [ B<-w>[B<=>I<WEIGHT>] | B<-c>[B<=>I<CAP>] ] ]
|
2008-10-11 16:22:01 +02:00
|
|
|
@@ -784,8 +781,6 @@ The normal EDF scheduling usage in nanos
|
2008-05-24 00:00:43 +02:00
|
|
|
|
|
|
|
|
The normal EDF scheduling usage in nanoseconds
|
|
|
|
|
|
|
|
|
|
-FIXME: these are lame, should explain more.
|
|
|
|
|
-
|
|
|
|
|
=item I<latency-hint>
|
|
|
|
|
|
|
|
|
|
Scaled period if domain is doing heavy I/O.
|
2008-10-11 16:22:01 +02:00
|
|
|
@@ -935,9 +930,6 @@ the default setting in xend-config.sxp f
|
2008-05-24 00:00:43 +02:00
|
|
|
|
|
|
|
|
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 B<mac=>I<macaddr>
|
|
|
|
|
|
|
|
|
|
The MAC address that the domain will see on its Ethernet device. If
|
2008-10-11 16:22:01 +02:00
|
|
|
@@ -963,9 +955,6 @@ Removes the network device from the doma
|
2008-05-24 00:00:43 +02:00
|
|
|
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> [B<-l>|B<--long>]> I<domain-id>
|
|
|
|
|
|
|
|
|
|
List virtual network interfaces for a domain. The returned output is
|
2008-10-11 16:22:01 +02:00
|
|
|
@@ -988,9 +977,6 @@ formatted as a list or as an S-Expressio
|
2008-05-24 00:00:43 +02:00
|
|
|
|
|
|
|
|
The Virtual Network interfaces for Xen.
|
|
|
|
|
|
|
|
|
|
-FIXME: This needs a lot more explanation, or it needs to be ripped
|
|
|
|
|
-out entirely.
|
|
|
|
|
-
|
|
|
|
|
=over 4
|
|
|
|
|
|
|
|
|
|
=item B<vnet-list> [B<-l>|B<--long>]
|
