From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: kvm.git next: KVM internal error. Suberror: 1
Date: Mon, 08 Feb 2010 13:45:01 +0100 [thread overview]
Message-ID: <4B70074D.1010508@siemens.com> (raw)
In-Reply-To: <4B6FFF86.4040309@redhat.com>
Avi Kivity wrote:
> On 02/08/2010 02:04 PM, Jan Kiszka wrote:
>> Avi,
>>
>> with 2c8232f over kvm-kmod and "qemu-system-x86_64 -m 256 vm-image.qcow2 -snapshot -serial stdio -s -smp 2" I just got this:
>>
>>
>
> What is vm-image.qcow2?
>
>> KVM internal error. Suberror: 1
>> rax 0000000000000000 rbx 0000000000006f08 rcx 0000000000000000 rdx 0000000000000052
>> rsi 0000000000000000 rdi 00000000000f4fd4 rsp 0000000000006ed8 rbp 00000000000f7280
>> r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000
>> r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
>> rip 00000000f000ff53 rflags 00010016
>>
>
> ffffff53 is an 'iret'. But f000ff53 doesn't make sense.
>
>> cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0)
>> ds 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>> es 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>> ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>> fs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>> gs 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
>> tr 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
>> ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
>> gdt f7a20/37
>> idt f8aa0/0
>> cr0 11 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
>> emulation failure
>>
>> Before that run, I started the very same VM and shut it down via
>> system_powerdown. This is reproducible!
>>
>
> Not sure I understand. This is with -snapshot, so how can a previous
> run have any effect?
>
>> Maybe it's the same issue that causes the #UD regression with
>> -no-kvm-irqchip.
>
> I wasn't able to reproduce.
>
Looks like tried to outsource my own bugs: I was on queues/vcpu-state,
ie. my state writeback rework, and I'm unable to reproduce over qemu-kvm
master. Will do my homework.
Still, the issue around -no-kvm-irqchip exists with master.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-02-08 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 12:04 kvm.git next: KVM internal error. Suberror: 1 Jan Kiszka
2010-02-08 12:11 ` Avi Kivity
2010-02-08 12:45 ` Jan Kiszka [this message]
2010-02-08 12:55 ` Gleb Natapov
2010-02-08 12:59 ` Jan Kiszka
2010-02-08 13:48 ` Avi Kivity
2010-02-08 14:12 ` Avi Kivity
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=4B70074D.1010508@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox