From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: yogi <anantyog@linux.vnet.ibm.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org,
Yogananth Subramanian <anantyog@in.ibm.com>
Subject: Re: [KVM-AUTOTEST PATCH] kvm test: Adding remote migration support
Date: Thu, 18 Jun 2009 11:01:52 -0300 [thread overview]
Message-ID: <1245333712.15882.23.camel@freedom> (raw)
In-Reply-To: <1245282473.5874.13.camel@yogi-laptop>
On Thu, 2009-06-18 at 05:17 +0530, yogi wrote:
> Hello Everyone
>
>
> > I went trough the discussion about this patch and I also agree we should
> > be implementing this test as a server side test. However I thought it
> > would be good having this patch rebased to the new kvm test code just in
> > case we need it in the future. This is part of the patch queue work.
> >
>
> I have rebased the patch to the new kvm test code.
>
> The same set of parameters should be added to kvm_tests.cfg file,as the
> previous patch
>
> hostip = 192.168.1.2 #ur host machine ip
> remoteip = 192.168.1.2 #can use same ip for local migration
> remuser = root #remote machine user
> rempassword = 123456 #passwd for remote user
> remote_dst = yes #could be enabled for local migration too
> qemu_path_dst = /tmp/kvm_autotest_root1/qemu
> image_dir_dst = /tmp/kvm_autotest_root1/images
>
>
> Thanks and Regards
> Yogi
Thank you very much Yogi! As I have said, your patch was stored for
future reference.
--
Lucas Meneghel Rodrigues
Software Engineer (QE)
Red Hat - Emerging Technologies
prev parent reply other threads:[~2009-06-18 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 0:46 [KVM-AUTOTEST PATCH] kvm test: Adding remote migration support Lucas Meneghel Rodrigues
2009-06-17 0:53 ` Lucas Meneghel Rodrigues
2009-06-17 23:47 ` yogi
2009-06-18 14:01 ` Lucas Meneghel Rodrigues [this message]
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=1245333712.15882.23.camel@freedom \
--to=lmr@redhat.com \
--cc=anantyog@in.ibm.com \
--cc=anantyog@linux.vnet.ibm.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.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