On 22.05.2017 20:44, Michael S. Tsirkin wrote:
On Mon, May 22, 2017 at 02:58:56PM +0200, Igor Mammedov wrote:
On Mon, 22 May 2017 14:01:15 +0300
Evgeny Yakovlev wrote:
On 22.05.2017 13:35, Igor Mammedov wrote:
On Mon, 22 May 2017 12:50:30 +0300
Evgeny Yakovlev wrote:
When running wind
On Mon, May 22, 2017 at 02:58:56PM +0200, Igor Mammedov wrote:
> On Mon, 22 May 2017 14:01:15 +0300
> Evgeny Yakovlev wrote:
>
> > On 22.05.2017 13:35, Igor Mammedov wrote:
> > > On Mon, 22 May 2017 12:50:30 +0300
> > > Evgeny Yakovlev wrote:
> > >
> > >> When running windows 2016 server guest
On Mon, 22 May 2017 14:01:15 +0300
Evgeny Yakovlev wrote:
> On 22.05.2017 13:35, Igor Mammedov wrote:
> > On Mon, 22 May 2017 12:50:30 +0300
> > Evgeny Yakovlev wrote:
> >
> >> When running windows 2016 server guests we have encountered a problem
> >> with ACPI representation of CPU devices. T
On 22.05.2017 13:35, Igor Mammedov wrote:
On Mon, 22 May 2017 12:50:30 +0300
Evgeny Yakovlev wrote:
When running windows 2016 server guests we have encountered a problem
with ACPI representation of CPU devices. This windows version contains a
hidinterrupt.sys driver which looks for ACPI devi
On Mon, 22 May 2017 12:50:30 +0300
Evgeny Yakovlev wrote:
> When running windows 2016 server guests we have encountered a problem
> with ACPI representation of CPU devices. This windows version contains a
> hidinterrupt.sys driver which looks for ACPI device node with _HID set
> to "ACPI0010" and
When running windows 2016 server guests we have encountered a problem
with ACPI representation of CPU devices. This windows version contains a
hidinterrupt.sys driver which looks for ACPI device node with _HID set
to "ACPI0010" and "ACPI0011". ACPI0010 is also a valid id for CPU
container device wh
