898ade9d0e
disk in Xen kernel 26133-IOMMU-defer-BM-disable.patch 26324-IOMMU-assign-params.patch 26325-IOMMU-add-remove-params.patch 26326-VT-d-context-map-params.patch 26327-AMD-IOMMU-flush-params.patch 26328-IOMMU-pdev-type.patch 26329-IOMMU-phantom-dev.patch 26330-VT-d-phantom-MSI.patch 26331-IOMMU-phantom-dev-quirk.patch - Upstream patches from Jan 26294-x86-AMD-Fam15-way-access-filter.patch 26320-IOMMU-domctl-assign-seg.patch 26332-x86-compat-show-guest-stack-mfn.patch 26333-x86-get_page_type-assert.patch - bnc#794316 - VUL-0: CVE-2012-5634: xen: VT-d interrupt remapping source validation flaw (XSA-33) CVE-2012-5634-xsa33.patch - Update to Xen 4.2.1 c/s 25952 - Upstream patches from Jan 26195-x86-compat-atp-gmfn-range-cont.patch 26196-ACPI-set-PDC-bits-rc.patch 26200-IOMMU-debug-verbose.patch 26203-x86-HAP-dirty-vram-leak.patch 26229-gnttab-version-switch.patch (Replaces CVE-2012-5510-xsa26.patch) 26230-x86-HVM-limit-batches.patch (Replaces CVE-2012-5511-xsa27.patch) OBS-URL: https://build.opensuse.org/package/show/Virtualization/xen?expand=0&rev=220
83 lines
2.3 KiB
Diff
83 lines
2.3 KiB
Diff
Index: xen-4.2.0-testing/docs/man/xmdomain.cfg.pod.5
|
|
===================================================================
|
|
--- xen-4.2.0-testing.orig/docs/man/xmdomain.cfg.pod.5
|
|
+++ xen-4.2.0-testing/docs/man/xmdomain.cfg.pod.5
|
|
@@ -333,16 +333,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
|
|
Index: xen-4.2.0-testing/docs/man/xm.pod.1
|
|
===================================================================
|
|
--- xen-4.2.0-testing.orig/docs/man/xm.pod.1
|
|
+++ xen-4.2.0-testing/docs/man/xm.pod.1
|
|
@@ -299,7 +299,8 @@ scheduling by the Xen hypervisor.
|
|
|
|
=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>
|
|
|
|
@@ -312,8 +313,6 @@ restart on crash. See L<xmdomain.cfg> f
|
|
The domain is in process of dying, but hasn't completely shutdown or
|
|
crashed.
|
|
|
|
-FIXME: Is this right?
|
|
-
|
|
=back
|
|
|
|
B<NOTES>
|
|
@@ -737,8 +736,6 @@ Xen ships with a number of domain schedu
|
|
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>] ] ]
|
|
@@ -788,8 +785,6 @@ The normal EDF scheduling usage in nanos
|
|
|
|
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.
|
|
@@ -939,9 +934,6 @@ the default setting in xend-config.sxp f
|
|
|
|
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
|
|
@@ -967,9 +959,6 @@ Removes the network device from the doma
|
|
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
|