From: Peter Xu <peterx@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
mst@redhat.com, Juan Quintela <quintela@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] VT-d migration support
Date: Mon, 9 Jan 2017 16:45:12 +0800 [thread overview]
Message-ID: <20170109084512.GH4135@pxdev.xzpeter.org> (raw)
In-Reply-To: <20170109021845.GE4135@pxdev.xzpeter.org>
On Mon, Jan 09, 2017 at 10:18:45AM +0800, Peter Xu wrote:
> On Fri, Jan 06, 2017 at 01:27:38PM +0000, Dr. David Alan Gilbert wrote:
>
> [...]
>
> > > (P.S. I found that split irqchip cannot work well with migration. Is
> > > this an known issue?)
> >
> > How did it fail?
>
> The keyboard hangs after migration.
>
> Command line for reference:
>
> $qemu -M q35,kernel-irqchip=split -enable-kvm \
> -netdev user,id=net0 \
> -device e1000,netdev=net0 \
> -m 512M -monitor stdio \
> $incoming /var/lib/libvirt/images/vm1.qcow2
>
> Here $incoming is "" for init vm, and "-incoming tcp:0:6666" for the
> dest side. Not sure whether this is reproducable issue. Looks like
> some EOI ack is missing.
>
> Host: 4.10.0-rc1+ (I should also tried 4.6.4-301.fc24)
> Qemu: latest master
>
> Looking into it.
The problem is that we didn't setup the first 24 gsi routing entries
(which is used by the userspace ioapic) in kernel after the migration.
Will post a fix for it later.
-- peterx
prev parent reply other threads:[~2017-01-09 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 4:06 [Qemu-devel] [PATCH v3 0/2] VT-d migration support Peter Xu
2017-01-06 4:06 ` [Qemu-devel] [PATCH v3 1/2] migration: allow to prioritize save state entries Peter Xu
2017-01-06 13:19 ` Dr. David Alan Gilbert
2017-01-06 4:06 ` [Qemu-devel] [PATCH v3 2/2] intel_iommu: allow migration Peter Xu
2017-01-06 7:05 ` Jason Wang
2017-01-06 7:13 ` Peter Xu
2017-01-06 13:27 ` [Qemu-devel] [PATCH v3 0/2] VT-d migration support Dr. David Alan Gilbert
2017-01-09 2:18 ` Peter Xu
2017-01-09 8:45 ` Peter Xu [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=20170109084512.GH4135@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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.