From mboxrd@z Thu Jan  1 00:00:00 1970
From: Igor Mammedov <imammedo@redhat.com>
Subject: Windows 10 guest hang during 'info mem'
Date: Fri, 24 Nov 2017 13:57:29 +0100
Message-ID: <20171124135729.60ceff1e@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
        Radim =?UTF-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>
To: Qemu Developers <qemu-devel@nongnu.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:60656 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753227AbdKXM5c (ORCPT <rfc822;kvm@vger.kernel.org>);
        Fri, 24 Nov 2017 07:57:32 -0500
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

I've stumbled on WS2016 hang when trying to list memory map in QEMU.

Steps to reproduce:
  qemu-system-x86_64 -monitor stdio -enable-kvm -m 1G ws2016x64.img
 wait till guest boots and execute in monitor 
  (qemu) info mem

qemu will hang while printing mappings, consuming 100% cpu and not
responding to ^C.

I've also tried with old (2.8) and current qemu master and today's
upstream kernel where it also doesn't work but WS2012R2x64 guest
works just fine.

PS:
CCing KVM list as the issue happens only when KVM is enabled.