From: Avi Kivity <avi@redhat.com>
To: Doug Goldstein <cardoe@gentoo.org>
Cc: Gleb Natapov <gleb@redhat.com>, KVM mailing list <kvm@vger.kernel.org>
Subject: Re: Unknown KVM internal error on 3.2.1
Date: Tue, 27 Mar 2012 12:53:32 +0200 [thread overview]
Message-ID: <4F719C2C.2070708@redhat.com> (raw)
In-Reply-To: <CAFWqQMQbH0WkRWgSXK9XGh7poKqw6A0NnMK+6bOF-nOV4TnOeA@mail.gmail.com>
On 03/26/2012 10:12 PM, Doug Goldstein wrote:
> >
> > When it happens again, please keep the guest alive so we can examine it
> > via qemu monitor commands.
> >
>
> It happened again. Here's the output requested.
>
> Before resuming:
>
> # virsh qemu-monitor-command bb-rhel-5.3-i686 --hmp x/20i 0xf91b4748
> 0x00000000f91b4748: lock popf
> 0x00000000f91b474a: lock popf
> 0x00000000f91b474c: lock popf
> 0x00000000f91b474e: lock popf
> 0x00000000f91b4750: lock popf
> 0x00000000f91b4752: lock popf
> 0x00000000f91b4754: lock popf
> 0x00000000f91b4756: lock popf
> 0x00000000f91b4758: lock popf
> 0x00000000f91b475a: lock popf
> 0x00000000f91b475c: lock popf
> 0x00000000f91b475e: lock popf
> 0x00000000f91b4760: lock popf
> 0x00000000f91b4762: lock popf
> 0x00000000f91b4764: lock popf
> 0x00000000f91b4766: lock popf
> 0x00000000f91b4768: lock popf
> 0x00000000f91b476a: lock popf
> 0x00000000f91b476c: lock popf
> 0x00000000f91b476e: lock popf
>
> After resuming and immediately running the requested command:
Did the guest run properly after resuming?
>
> # virsh qemu-monitor-command bb-rhel-5.3-i686 --hmp x/20i 0xf91b4748
> 0x00000000f91b4748: mov %eax,%cr0
> 0x00000000f91b474b: mov %ebx,(%ecx)
> 0x00000000f91b474d: mov %edx,%cr0
> 0x00000000f91b4750: mov (%esi),%esi
> 0x00000000f91b4752: mov (%esi),%eax
> 0x00000000f91b4754: prefetchnta (%eax)
> 0x00000000f91b4757: nop
> 0x00000000f91b4758: mov 0xf91db9f8,%eax
> 0x00000000f91b475d: add $0x8,%eax
> 0x00000000f91b4760: cmp %eax,%esi
> 0x00000000f91b4762: jne 0xf91b4738
> 0x00000000f91b4764: lock incl 0xf91da3b0
> 0x00000000f91b476b: pop %ebx
> 0x00000000f91b476c: mov $0x5,%edx
> 0x00000000f91b4771: pop %esi
> 0x00000000f91b4772: mov $0xf91da380,%eax
> 0x00000000f91b4777: jmp 0xc0432047
> 0x00000000f91b477c: push %ebp
> 0x00000000f91b477d: push %edi
> 0x00000000f91b477e: push %esi
>
This is perfectly sane and expected code (unlike the previous dump).
Are you running with transparent hugepages and/or ksm enabled? You
might try to disable them.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-03-27 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 15:35 Unknown KVM internal error on 3.2.1 Doug Goldstein
2012-03-07 10:41 ` Avi Kivity
2012-03-07 11:00 ` Gleb Natapov
2012-03-07 14:19 ` Avi Kivity
2012-03-20 20:40 ` Doug Goldstein
2012-03-26 20:12 ` Doug Goldstein
2012-03-27 10:53 ` Avi Kivity [this message]
2012-03-27 20:00 ` Doug Goldstein
2013-01-30 0:21 ` Doug Goldstein
2014-04-10 8:24 ` LEo
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=4F719C2C.2070708@redhat.com \
--to=avi@redhat.com \
--cc=cardoe@gentoo.org \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.