On 05/17/2018 03:28 PM, Jiri Denemark wrote:
> On Wed, May 09, 2018 at 13:36:55 +0200, Halil Pasic wrote:
>>
>>
>> On 05/09/2018 12:41 PM, Jiri Denemark wrote:
>>> On Tue, May 08, 2018 at 10:44:22 -0400, Collin Walling wrote:
Hi
I have noticed something that may be misconstrued
On Wed, May 09, 2018 at 13:36:55 +0200, Halil Pasic wrote:
>
>
> On 05/09/2018 12:41 PM, Jiri Denemark wrote:
> > On Tue, May 08, 2018 at 10:44:22 -0400, Collin Walling wrote:
> >> Hi
> >>
> >> I have noticed something that may be misconstrued regarding the libvirt
> >> domain xml format
> >>
On 05/09/2018 01:35 PM, Kashyap Chamarthy wrote:
On Tue, May 08, 2018 at 10:44:22AM -0400, Collin Walling wrote:
Hi
I have noticed something that may be misconstrued regarding the libvirt domain
xml format
for defining a cpu model. There seems to be a misalignment where the libvirt
On 05/09/2018 12:41 PM, Jiri Denemark wrote:
On Tue, May 08, 2018 at 10:44:22 -0400, Collin Walling wrote:
Hi
I have noticed something that may be misconstrued regarding the libvirt domain
xml format
for defining a cpu model. There seems to be a misalignment where the libvirt
documentation
On Tue, May 08, 2018 at 10:44:22AM -0400, Collin Walling wrote:
> Hi
>
> I have noticed something that may be misconstrued regarding the libvirt
> domain xml format
> for defining a cpu model. There seems to be a misalignment where the libvirt
> documentation
> states something that is not
On Tue, May 08, 2018 at 10:44:22 -0400, Collin Walling wrote:
> Hi
>
> I have noticed something that may be misconstrued regarding the libvirt
> domain xml format
> for defining a cpu model. There seems to be a misalignment where the libvirt
> documentation
> states something that is not
Hi
I have noticed something that may be misconstrued regarding the libvirt domain
xml format
for defining a cpu model. There seems to be a misalignment where the libvirt
documentation
states something that is not supported, but libvirt itself gives no clear
indication of
such. This is
