From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org,
Antonios Motakis <a.motakis@virtualopensystems.com>
Subject: [Qemu-devel] vhost-user: migration?
Date: Wed, 18 Jun 2014 12:33:34 +0300 [thread overview]
Message-ID: <20140618093334.GA12677@redhat.com> (raw)
Just a query whether migration works for you
guys with vhost-user and snabbswitch.
vhost user code seems to have enough hooks in
place to make it work, but was it tested
in practice?
--
MST
next reply other threads:[~2014-06-18 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 9:33 Michael S. Tsirkin [this message]
2014-06-18 11:24 ` [Qemu-devel] vhost-user: migration? Nikolay Nikolaev
2014-06-18 11:29 ` Michael S. Tsirkin
2014-06-18 11:41 ` Nikolay Nikolaev
2014-06-18 12:35 ` Michael S. Tsirkin
2014-06-18 13:37 ` Nikolay Nikolaev
2014-06-18 14:13 ` Michael S. Tsirkin
2015-01-09 3:24 ` Zhang Haoyu
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=20140618093334.GA12677@redhat.com \
--to=mst@redhat.com \
--cc=a.motakis@virtualopensystems.com \
--cc=imammedo@redhat.com \
--cc=n.nikolaev@virtualopensystems.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).