From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Gary R Hook <grhookatwork@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Tunneled Migration with Non-Shared Storage
Date: Wed, 19 Nov 2014 10:55:41 +0000 [thread overview]
Message-ID: <20141119105540.GC31875@redhat.com> (raw)
In-Reply-To: <20141119093516.GA2355@work-vm>
On Wed, Nov 19, 2014 at 09:35:16AM +0000, Dr. David Alan Gilbert wrote:
> * Paolo Bonzini (pbonzini@redhat.com) wrote:
> >
> >
> > On 18/11/2014 21:28, Dr. David Alan Gilbert wrote:
> > > This seems odd, since as far as I know the tunneling code is quite separate
> > > to the migration code; I thought the only thing that the migration
> > > code sees different is the file descriptors it gets past.
> > > (Having said that, again I don't know storage stuff, so if this
> > > is a storage special there may be something there...)
> >
> > Tunnelled migration uses the old block-migration.c code. Non-tunnelled
> > migration uses the NBD server and block/mirror.c.
>
> OK, that explains that. Is that because the tunneling code can't
> deal with tunneling the NBD server connection?
Yep, pretty much. The tunnelling code was built around the idea of a
single connection to be tunnelled.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2014-11-19 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <546B781B.3070309@gmail.com>
2014-11-18 16:51 ` [Qemu-devel] Tunneled Migration with Non-Shared Storage Gary R Hook
2014-11-18 20:28 ` Dr. David Alan Gilbert
2014-11-18 21:38 ` Paolo Bonzini
2014-11-19 9:35 ` Dr. David Alan Gilbert
2014-11-19 10:19 ` Paolo Bonzini
2014-11-19 10:55 ` Daniel P. Berrange [this message]
2014-11-19 20:00 ` Gary R Hook
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=20141119105540.GC31875@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=grhookatwork@gmail.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.