qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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:38:48 -0500	[thread overview]
Message-ID: <4A3AA5D8.8050303@codemonkey.ws> (raw)
In-Reply-To: <20090618201227.GI3517@poweredge.glommer>

Glauber Costa wrote:
> Sure.
>
> Question is, whether or not there is any value in doing this now.
>   

Doing what you proposed would be difficult to support long term.  I 
don't think it qualifies as an interim solution.  You would have to pass 
host configuration information in the migration protocol and that's a 
fundamental change to the way migration works in QEMU today.

If you assume the management application knows about the devices added, 
then it also knows about what the new arguments should be for QEMU.  
Maybe we should think about ways to delay the launching of QEMU (or at 
least the argument parsing) until after migration has completed.

Then, we have the ability to transfer the command line arguments 
(through a separate channel) similar to how ssh migration used to work.

We're really close to a machine config for pc though, I'm not sure that 
that's not a quicker solution.

Regards,

Anthony Liguori

  reply	other threads:[~2009-06-18 20:39 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
2009-06-18 20:12   ` Glauber Costa
2009-06-18 20:38     ` Anthony Liguori [this message]
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=4A3AA5D8.8050303@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).