From: Chris Friesen <chris.friesen@windriver.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] call flow to hit get_pci_config_device() during live migration
Date: Fri, 9 Jun 2017 14:00:41 -0600 [thread overview]
Message-ID: <593AFE69.7090206@windriver.com> (raw)
In-Reply-To: <593AC202.5000404@windriver.com>
On 06/09/2017 09:42 AM, Chris Friesen wrote:
> Hi,
>
> I'm investigating an issue seen over a live migration from a modified
> qemu-kvm-ev-2.3.0-31.el7_2.7.1 to a modified qemu-kvm-ev-2.6.0-28.el7_3.9.1. We
> hit an issue down in get_pci_config_device() that caused the migration to fail.
>
> The qemu logs on the destination are included below.
>
> I'm looking for some guidance on the call flow that leads to this function, and
> the likely causes of the bad config data. And if anyone can help me decode the
> config data information in the log (cmask/wmask/wlcmask) and the logic of the
> "bad config data" check I'd appreciate it.
I think what I end up with is that byte 0x20 (ie 32) of the PCI config for the
virtio-blk device is 0 in the data coming over the wire, and 0xC in the local
copy. Since cmask is 0xff we need to check all the bits in the byte, and both
wmask and w1cmask are 0 so the version on the wire and the local version should
be the same.
Does that seem right?
Chris
next prev parent reply other threads:[~2017-06-09 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 15:42 [Qemu-devel] call flow to hit get_pci_config_device() during live migration Chris Friesen
2017-06-09 20:00 ` Chris Friesen [this message]
2017-06-09 23:18 ` Chris Friesen
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=593AFE69.7090206@windriver.com \
--to=chris.friesen@windriver.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).