From: Anthony Liguori <anthony@codemonkey.ws>
To: Glauber Costa <glommer@redhat.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] sending pci information over the wire
Date: Thu, 18 Jun 2009 15:03:21 -0500 [thread overview]
Message-ID: <4A3A9D89.5000305@codemonkey.ws> (raw)
In-Reply-To: <20090618193946.GH3517@poweredge.glommer>
Glauber Costa wrote:
> Hi folks,
>
> I have some trial code here for a proposal, which I'd like to hear your
> opinions about (Well, I _had_, because I'm totally stupid and git reset'd --hard
> the wrong location, that happened to contain part of the code for it)
>
> Let me start by explaining what I'm trying to accomplish, and say that I myself
> am not sure this is the best approach, it is just a crazy idea that poped up.
>
> Right now, migration of pci devices work by a bit of luck. This is because the
> other side of the wire can enumerate the devices in a different order, causing
> them to end up at different addresses. Markus approach of pci_addr= patches
> do help that fact.
>
> However, theoretically, there can be a case in which we:
> * start receiving guest, with parameters determined by pci_addr=
> * start live migration
> * add a device.
>
Once we have a machine config (and please, let's avoid the 2017 jokes
please), I imagine that the machine config will be transferred as a
non-live section.
That will solve this problem quite nicely.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-06-18 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 19:39 [Qemu-devel] sending pci information over the wire Glauber Costa
2009-06-18 20:03 ` Anthony Liguori [this message]
2009-06-18 20:12 ` Glauber Costa
2009-06-18 20:38 ` Anthony Liguori
2009-06-19 8:55 ` Gerd Hoffmann
2009-06-19 13:10 ` Anthony Liguori
2009-06-19 14:33 ` Gerd Hoffmann
2009-06-19 14:47 ` Paul Brook
2009-06-19 15:16 ` Anthony Liguori
2009-06-19 15:38 ` Gerd Hoffmann
2009-06-19 15:56 ` Anthony Liguori
2009-06-20 18:58 ` 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=4A3A9D89.5000305@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=glommer@redhat.com \
--cc=kraxel@redhat.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).