From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"avi@redhat.com" <avi@redhat.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>
Subject: Re: KVM: injection failed, MSI lost (Operation not permitted)
Date: Thu, 27 Sep 2012 14:46:46 +0200 [thread overview]
Message-ID: <50644AB6.6080008@siemens.com> (raw)
In-Reply-To: <20120927121256.GA26749@redhat.com>
On 2012-09-27 14:12, Michael S. Tsirkin wrote:
> On Tue, Sep 25, 2012 at 05:32:47PM +0200, Jan Kiszka wrote:
>> On 2012-09-25 16:19, Michael S. Tsirkin wrote:
>>> Each time I kill qemu-kvm I get this error:
>>> KVM: injection failed, MSI lost (Operation not permitted)
>>>
>>> Jan, any idea?
>>
>> Race in shutting down resources?
>>
>> What do you do precisely? I never saw this.
>>
>> Jan
>
> I boot guest like this:
>
> /home/mst/qemu-test/bin/qemu-system-x86_64 -enable-kvm -cpu kvm64 -m
> 1G -drive file=/home/mst/rhel6-try.qcow2 -net
> nic,model=virtio,netdev=foo -netdev id=bar -device e1000,netdev=bar
> -redir tcp:8022::22 -netdev
> tap,id=foo,ifname=msttap0,script=/home/mst/ifup,downscript=no,vhost=off
> -vnc :1 -smp 16 -snapshot
>
> At some later point I kill it from another shell:
>
> kill `pgrep qemu`
Hmm, cannot reproduce, even under flood-ping load on the virtio device,
ie. the one that is using MSI. I'm afraid you will have to trace the
event flow.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2012-09-27 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 14:19 KVM: injection failed, MSI lost (Operation not permitted) Michael S. Tsirkin
2012-09-25 15:32 ` Jan Kiszka
2012-09-27 12:12 ` Michael S. Tsirkin
2012-09-27 12:46 ` Jan Kiszka [this message]
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=50644AB6.6080008@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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 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.