Re: [libvirt] [PATCH] docs: formatdomain: Note the caveats for CPU policy option "force"

2018-06-22 Thread Kashyap Chamarthy
On Fri, Jun 22, 2018 at 02:19:52PM +0200, Jiri Denemark wrote: > On Tue, Jun 12, 2018 at 10:58:46 +0200, Kashyap Chamarthy wrote: [...] > > diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in > > index 6912762f28..4d6c3892ee 100644 > > --- a/docs/formatdomain.html.in > > +++

Re: [libvirt] [PATCH] docs: formatdomain: Note the caveats for CPU policy option "force"

2018-06-22 Thread Jiri Denemark
On Tue, Jun 12, 2018 at 10:58:46 +0200, Kashyap Chamarthy wrote: > Eduardo Habkost has pointed out that the current documentation of > libvirt's CPU feature policy "require" vs. "force" does not match > QEMU's behaviour. > > Update the documentation by spelling out the QEMU version dependency and

Re: [libvirt] [PATCH] docs: formatdomain: Note the caveats for CPU policy option "force"

2018-06-12 Thread Eduardo Habkost
On Tue, Jun 12, 2018 at 10:58:46AM +0200, Kashyap Chamarthy wrote: > Eduardo Habkost has pointed out that the current documentation of > libvirt's CPU feature policy "require" vs. "force" does not match > QEMU's behaviour. > > Update the documentation by spelling out the QEMU version dependency

[libvirt] [PATCH] docs: formatdomain: Note the caveats for CPU policy option "force"

2018-06-12 Thread Kashyap Chamarthy
Eduardo Habkost has pointed out that the current documentation of libvirt's CPU feature policy "require" vs. "force" does not match QEMU's behaviour. Update the documentation by spelling out the QEMU version dependency and explain in which scenarios the usage of "policy = 'force'" is applicable