From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, eblake@redhat.com, berrange@redhat.com,
quintela@redhat.com, amit.shah@redhat.com
Cc: david@gibson.dropbear.id.au
Subject: [Qemu-devel] More structured migration URIs?
Date: Mon, 5 Jan 2015 12:14:25 +0000 [thread overview]
Message-ID: <20150105121424.GF5244@work-vm> (raw)
Hi,
I keep thinking of things where it might make sense to add
options onto the migration URIs and wondered if it makes
sense to restructure the migration URIs; my proposal would be:
a) Restructure tcp:hhhh:pppp into protocol=tcp,host=hhhh,port=pppp
b) Have a requirement that protocol= is the first entry in the list
c) If it doesn't start protocol= then it's the old format.
d) This would also change in the 'migrate' command to keep it symmetric
Eric/Daniel does this make sense for libvirt?
My current set of things I might want to add are:
1) A flag saying if a return channel is needed
For sockets qemu can open this afterwards when needed, but Dave Gibson's
review of my postcopy world pointed out that it might not be that
easy for all protocols to open the reverse later.
2) Flags for opening multiple sockets/FDs - e.g. to pass the pages down
a separate fd.
Thoughts?
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next reply other threads:[~2015-01-05 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 12:14 Dr. David Alan Gilbert [this message]
2015-01-05 12:29 ` [Qemu-devel] More structured migration URIs? Daniel P. Berrange
2015-01-05 12:37 ` Dr. David Alan Gilbert
2015-01-05 12:45 ` Daniel P. Berrange
2015-01-05 14:21 ` Dr. David Alan Gilbert
2015-01-05 17:02 ` Eric Blake
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=20150105121424.GF5244@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=eblake@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 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).