news: Xen: announce removal of hard-code scheduler weight

Also describe a possible side-affect due to changes in the default
(unspecified) value from 1000 to 256.

Signed-off-by: Jim Fehlig <jfehlig@suse.com>
Reviewed-by: John Ferlan <jferlan@redhat.com>

diff --git a/docs/news.xml b/docs/news.xml
index 75a05430843dc53f0a3ff220c61ec0a8ec9f313f..93ab59cf421c74e4d790a6b342950f207daa7ed3 100644 (file)
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -66,6 +66,22 @@
           If someone customizing IP address inside VM, it will be helpful.
         </description>
       </change>
+      <change>
+        <summary>
+          Xen: Remove hard-coded scheduler weight
+        </summary>
+        <description>
+          The libxl driver was accidentally hard-coding the per-domain
+          scheduler weight to 1000, silently ignoring any user-provided
+          <code>&lt;shares&gt;</code> in <code>&lt;cputune&gt;</code>. The
+          driver now honors <code>&lt;shares&gt;</code>, and defers setting
+          a default value to Xen. Note that the Xen default is 256, so any
+          domains started after this improvement will have one fourth the
+          shares of previously started domains. If all domains must have
+          equal CPU shares, administrators must manually set the weight of
+          previously started domains to 256, or restart them.
+        </description>
+      </change>
     </section>
     <section title="Bug fixes">
     </section>