From: Luiz Capitulino <lcapitulino@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v3 0/5] Add QMP migration events
Date: Thu, 17 Jun 2010 11:23:07 -0300 [thread overview]
Message-ID: <20100617112307.53482385@redhat.com> (raw)
In-Reply-To: <m3eig6ssj7.fsf@trasno.mitica>
On Wed, 16 Jun 2010 21:10:04 +0200
Juan Quintela <quintela@redhat.com> wrote:
> Luiz Capitulino <lcapitulino@redhat.com> wrote:
> > On Tue, 15 Jun 2010 17:24:59 +0200
> > Juan Quintela <quintela@redhat.com> wrote:
>
> >> >
> >> > I still don't see the need for MIGRATION_STARTED, it could be useful in
> >> > the target but I'd like to understand the use case in more detail.
> >>
> >> At this point, if you are doing migration with tcp, and you are putting
> >> the wrong port on source (no path or any other error), you get no info
> >> at all of what is happening.
> >
> > Shouldn't the migrate command just the return the expected error?
>
> No. Think you are "having troubles". You try to find what happens.
> launch things by hand. And there is no way to know if anybody has
> conected to the destination machine. Some notification that migration
> has started is _very_ useful. expecially when there are
> networks/firewalls/... in the middle.
[...]
> That is it. But you continue telling that going to the old house and
> doing a info migrate is a good interface.
I'm sorry? When did I ever claimed such a thing?
First point: all you describe is MIGRATION_CONNECTED, at the end of the day
it would do exactly what you want for MIGRATION_STARTED.
The second, and most important point, is that we're trying not to make
things worse. Adding a number of events to circumvent a bad designed
command and having the wrong expectations (ie. help developer debugging)
is a clear recipe for disaster.
Anyway, I think it doesn't matter anymore, as QMP is not going to be declared
stable for 0.13. In this case we'll have enough time to design the proper
interface.
> To add insult to injury, the problem is that libvirt people are not
> collaborative, and expect things that can't be done, are uncooperative,
Again, I've never claimed that and I think you're taking this thread to
the wrong direction.
> ....
>
> Libvirt folks "also" do lots of things wrong, they are not perfect. But
> it in this case, who is being completely unreasonable is qemu land.
>
> Later, Juan.
>
next prev parent reply other threads:[~2010-06-17 14:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 12:10 [Qemu-devel] [PATCH v3 0/5] Add QMP migration events Juan Quintela
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 1/5] Exit if incoming migration fails Juan Quintela
2010-06-23 1:47 ` Anthony Liguori
2010-06-24 20:41 ` [Qemu-devel] [PATCH] win32: Add define for missing EPROTONOSUPPORT Stefan Weil
2010-06-27 20:25 ` Blue Swirl
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 2/5] Factorize common migration incoming code Juan Quintela
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 3/5] QMP: Introduce MIGRATION events Juan Quintela
2010-06-09 20:54 ` Luiz Capitulino
2010-06-10 10:33 ` [Qemu-devel] " Juan Quintela
2010-06-11 13:12 ` Luiz Capitulino
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 4/5] QMP: Emit migration events on incoming migration Juan Quintela
2010-06-09 12:10 ` [Qemu-devel] [PATCH v3 5/5] QMP: Emit migration events on outgoing migration Juan Quintela
2010-06-09 14:47 ` [Qemu-devel] [PATCH v3 0/5] Add QMP migration events Yoshiaki Tamura
2010-06-09 15:59 ` [Qemu-devel] " Juan Quintela
2010-06-09 22:07 ` Yoshiaki Tamura
2010-06-09 20:52 ` [Qemu-devel] " Luiz Capitulino
2010-06-09 21:19 ` Yoshiaki Tamura
2010-06-10 10:44 ` [Qemu-devel] " Juan Quintela
2010-06-11 14:30 ` Luiz Capitulino
2010-06-11 14:38 ` Anthony Liguori
2010-06-11 16:42 ` Luiz Capitulino
2010-06-12 11:20 ` Juan Quintela
2010-06-14 14:36 ` Luiz Capitulino
2010-06-14 15:45 ` Juan Quintela
2010-06-12 11:14 ` Juan Quintela
2010-06-14 13:58 ` Anthony Liguori
2010-06-14 14:24 ` Luiz Capitulino
2010-06-14 14:35 ` Anthony Liguori
2010-06-14 14:42 ` Luiz Capitulino
2010-06-12 11:05 ` Juan Quintela
2010-06-14 14:03 ` Anthony Liguori
2010-06-14 16:02 ` Juan Quintela
2010-06-14 16:10 ` Anthony Liguori
2010-06-14 18:35 ` Juan Quintela
2010-06-14 19:07 ` Anthony Liguori
2010-06-14 19:54 ` Juan Quintela
2010-06-14 20:01 ` Anthony Liguori
2010-06-15 10:30 ` Juan Quintela
2010-06-15 13:40 ` Luiz Capitulino
2010-06-15 15:24 ` Juan Quintela
2010-06-16 18:01 ` Luiz Capitulino
2010-06-16 19:10 ` Juan Quintela
2010-06-17 14:23 ` Luiz Capitulino [this message]
2010-06-17 16:34 ` Juan Quintela
2010-06-17 16:45 ` Luiz Capitulino
2010-06-17 17:53 ` Anthony Liguori
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=20100617112307.53482385@redhat.com \
--to=lcapitulino@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 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.