80e28a00ec
- unmodified_drivers: handle IRQF_SAMPLE_RANDOM, it was removed in 3.6-rc1 - bnc#778105 - first XEN-PV VM fails to spawn xend: Increase wait time for disk to appear in host bootloader Modified existing xen-domUloader.diff - Disable the snapshot patches. Snapshot only supported the qcow2 image format which was poorly implemented qemu 0.10.2. Snapshot support may be restored in the future when the newer upstream qemu is used by Xen. - bnc#776995 - attaching scsi control luns with pvscsi - xend/pvscsi: fix passing of SCSI control LUNs xen-bug776995-pvscsi-no-devname.patch - xend/pvscsi: fix usage of persistant device names for SCSI devices xen-bug776995-pvscsi-persistent-names.patch - xend/pvscsi: update sysfs parser for Linux 3.0 xen-bug776995-pvscsi-sysfs-parser.patch - Update to Xen 4.2.0 RC3+ c/s 25779 - Update to Xen 4.2.0 RC2+ c/s 25765 OBS-URL: https://build.opensuse.org/package/show/Virtualization/xen?expand=0&rev=199
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
|
|
@@ -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
|
|
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
|