From: Paolo Bonzini <pbonzini@redhat.com>
To: Jason Baron <jbaron@redhat.com>
Cc: kwolf@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org,
quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/3] qtest: add migrate-test
Date: Fri, 14 Dec 2012 12:25:55 -0500 (EST) [thread overview]
Message-ID: <1530082961.24589944.1355505955172.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20121214161404.GC1776@redhat.com>
> > Do you think this function could be turned into a libqtest call?
>
> Seems like a good idea.
>
> > It would take mach_a as an argument, add -incoming
> > tcp:localhost:4444
> > to the command line of mach_a, use that to spawn mach_b, and
>
> why add to mach_a? I thought -incoming is just for the destination.
Yep. Tack it at the end of mach_a's command line (actually at the end
of the parameter of qtest_start) and use the result to start mach_b. The
command-lines for the two machines must match (apart from -incoming of
course), it's not necessary to pass it twice.
> > return mach_b as the return value (or perhaps change mach_a to
> > refer to the new machine).
>
> I think it makes sense for the caller to create and pass the machines
> and then just call a library function to do the migrate. That way the
> caller 'owns' the machines. But maybe I'm missing something.
Yeah, owning the machines makes sense. In this case migration would
just be a constructor for QTestState.
The alternative is to kill mach_a during migration and only proceed
with mach_b, since mach_a is effectively not going to be used.
Paolo
next prev parent reply other threads:[~2012-12-14 17:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 22:02 [Qemu-devel] [PATCH 0/3] qtest: add migration testing Jason Baron
2012-12-13 22:02 ` [Qemu-devel] [PATCH 1/3] qtest: Enable creation of multiple qemu instances Jason Baron
2012-12-14 20:30 ` Blue Swirl
2012-12-15 9:14 ` Paolo Bonzini
2012-12-15 9:20 ` Blue Swirl
2012-12-17 17:13 ` Jason Baron
2012-12-19 19:42 ` Blue Swirl
2012-12-13 22:02 ` [Qemu-devel] [PATCH 3/3] qtest: add migrate-test Jason Baron
2012-12-14 8:08 ` Paolo Bonzini
2012-12-14 16:14 ` Jason Baron
2012-12-14 17:25 ` Paolo Bonzini [this message]
2012-12-13 22:02 ` [Qemu-devel] [PATCH 2/3] qtest: extend qtest_qmp() to fill in the reply Jason Baron
2012-12-14 0:07 ` Andreas Färber
2012-12-14 16:10 ` Jason Baron
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=1530082961.24589944.1355505955172.JavaMail.root@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jbaron@redhat.com \
--cc=kwolf@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.