Signed-off-by: Roman Bogorodskiy <bogorodskiy@xxxxxxxxx> --- docs/drvbhyve.html.in | 16 ++++++++++++++++ docs/news.xml | 9 +++++++++ 2 files changed, 25 insertions(+) diff --git a/docs/drvbhyve.html.in b/docs/drvbhyve.html.in index 5b5513d3df..78a291c6bb 100644 --- a/docs/drvbhyve.html.in +++ b/docs/drvbhyve.html.in @@ -444,6 +444,22 @@ be wired and cannot be swapped out as follows:</p> </memoryBacking> ... </domain> +</pre> + +<h3><a id="cputopology">CPU topology</a></h3> + +<p><span class="since">Since 4.4.0</span>, it's possible to specify guest CPU topology, if bhyve +supports that. Support for specifying guest CPU topology was added to bhyve in +<a href="http://svnweb.freebsd.org/changeset/base/332298">r332298</a> for <i>-CURRENT</i>. +Example:</p> +<pre> +<domain type="bhyve"> + ... + <cpu> + <topology sockets='1' cores='2' threads='1'/> + </cpu> + ... +</domain> </pre> </body> diff --git a/docs/news.xml b/docs/news.xml index c45850f625..318bca5de1 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -94,6 +94,15 @@ both new APIs consider capabilities of a specific hypervisor. </description> </change> + <change> + <summary> + bhyve: Support specifying guest CPU topology + </summary> + <description> + Bhyve's guest CPU topology could be specified using the + <code><cpu><topology ../></cpu></code> element. + </description> + </change> </section> <section title="Improvements"> <change> -- 2.17.0 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list