public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Qemu Developers <qemu-devel@nongnu.org>
Cc: kvm@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Windows 10 guest hang during 'info mem'
Date: Fri, 24 Nov 2017 13:57:29 +0100	[thread overview]
Message-ID: <20171124135729.60ceff1e@redhat.com> (raw)

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.

             reply	other threads:[~2017-11-24 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 12:57 Igor Mammedov [this message]
2017-11-24 14:05 ` Windows 10 guest hang during 'info mem' Paolo Bonzini
2017-11-24 14:50   ` [Qemu-devel] " Igor Mammedov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171124135729.60ceff1e@redhat.com \
    --to=imammedo@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox