From: Avi Kivity <avi@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jiri Slaby <jirislaby@gmail.com>
Subject: Re: qemu-kvm loops after kernel udpate
Date: Wed, 12 Sep 2012 11:06:49 +0300 [thread overview]
Message-ID: <50504299.2050205@redhat.com> (raw)
In-Reply-To: <504F93F1.2060005@suse.cz>
On 09/11/2012 10:41 PM, Jiri Slaby wrote:
> On 09/11/2012 09:03 PM, Marcelo Tosatti wrote:
>> On Tue, Sep 11, 2012 at 08:11:36PM +0200, Jiri Slaby wrote:
>>> Hi,
>>>
>>> it looks like an update from next-20120824 to next-20120910 makes kvm
>>> defunct. When I try to run qemu, it loops forever without printing
>>> anything on the monitor.
>>>
>>> -no-kvm makes it indeed work.
>>>
>>> Cmdline I use:
>>> qemu-kvm -k en-us -usbdevice tablet -balloon virtio -hda IMAGE -smp 2 -m
>>> 1000M -net user -net nic,model=e1000 -usb -serial pty
>>>
>>> Before I start investigating further, like biscection, is this a known
>>> issue already and fix available somewhere?
>>
>> Its not a known issue. 'info registers' (for both vcpus) and
>> 'x /20i $eip' might help track it down.
>
> I don't think it's in a state with something loaded.
>
> (qemu) cpu 0
> (qemu) info registers
> EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000623
> ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
> EIP=0000fff0 EFL=00010002 [-------] CPL=3 II=0 A20=1 SMM=0 HLT=0
> ES =0000 00000000 0000ffff 00009300
> CS =f000 000f0000 0000ffff 0000f300
This is before the first instruction is executed.
You're on an Intel host, yes? Please provide the output of vmxcap
(http://goo.gl/c5lUO), and a snapshot of kvm_stat while the guest is hung.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-12 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 18:11 qemu-kvm loops after kernel udpate Jiri Slaby
2012-09-11 19:03 ` Marcelo Tosatti
2012-09-11 19:41 ` Jiri Slaby
2012-09-12 8:06 ` Avi Kivity [this message]
2012-09-12 8:13 ` Jiri Slaby
2012-09-12 8:18 ` Avi Kivity
2012-09-12 8:20 ` Jiri Slaby
2012-09-12 18:11 ` Jiri Slaby
2012-09-13 9:59 ` Avi Kivity
2012-09-13 18:32 ` Jiri Slaby
2012-09-18 19:40 ` Jiri Slaby
2012-09-18 19:46 ` Andrew Morton
2012-09-19 0:00 ` Stephen Rothwell
2012-09-19 0:20 ` Andrew Morton
2012-09-19 1:36 ` Stephen Rothwell
2012-09-19 14:18 ` [PATCH] mm: call invalidate_range_end in do_wp_page even for zero pages Haggai Eran
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=50504299.2050205@redhat.com \
--to=avi@redhat.com \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@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;
as well as URLs for NNTP newsgroup(s).