public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: jason wang <jasowang@redhat.com>
To: sudhir kumar <smalikphy@gmail.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
	KVM mailing list <kvm@vger.kernel.org>,
	Autotest mailing list <autotest@test.kernel.org>,
	Michael Goldish <mgoldish@redhat.com>
Subject: Re: Latest kvm autotest patch queue
Date: Thu, 25 Jun 2009 21:02:02 +0800	[thread overview]
Message-ID: <4A43754A.9060201@redhat.com> (raw)
In-Reply-To: <a50cf5ab0906222112g2519ffe5y7ec1d8bb5c13ef1@mail.gmail.com>

sudhir kumar 写道:
> On Mon, Jun 22, 2009 at 6:54 PM, Lucas Meneghel Rodrigues<lmr@redhat.com> wrote:
>   
>> KVM Autotest patch queue
>>
>> --------------------------------------------------------------------------------
>> Michael Goldish (mgoldish@redhat.com)
>>
>> 1) KVM test: optionally convert PPM files to PNG format after test - Reviewed
>>
>> 2) Step file tests: introducing a new feature and some small changes - Reviewed
>>
>> 3) Introducing kvm_subprocess - Reviewed
>>
>> --------------------------------------------------------------------------------
>> Jason Wang (jasowang@redhat.com)
>>
>> 1) TAP network support in kvm-autotest
>>
>> Michael Goldish has a similar patch to this one, so we need to decide which one
>>     
> I remember Michael's patch using nmap to get the ip of the guest. I
> tested the patch and found nmap taking too long to do a lookup and get
> the guest ip. I will suggets two things here.
> 1. Modify nmap options to make nmap lookup really faster.
> 2. Provide an option to use a dictionary based(mac address to ip
> mapping) lookup in config file and return mapped ip for a mac address.
>
> I can send a patch for option 2 on top of Michael's patch. In the
> simplest form it will generate a dictionary from a macaddress vs IP
> address list(provided by the dhcp server in your lab/environment. you
> can put this list in a file and use it). You need to specify macaddr
> parameter in config file from this list. Looking the mac address the
> parser will return the corresponding ip address from the dictionary
> generated.
>
> Please let me know if 2 sounds good. Also I think I missed to look at
> Jason's patch?
>   
My patch could be seen at http://patchwork.kernel.org/patch/23524/. I 
think the mac:ip dictionary is not flexible enough especially in a 
network with public dhcp server. The scanning method could be used in 
either public or private bridge. But my patch still have some problems 
to solve and need advices:
1 Mac address generation: I could rework the patch and make it could 
accept user specified address range, but the user should guarantee its 
validity.
2 IP scanner: Is there any option of nmap could make the scanning faster 
than -sP? I also agree that nmap is not a elegant method, but it seems 
the sole choice ( or write a simple scanner through python?) . Another 
method is to snoop the dhcp session through tcpdump during the 
vm.create() but this method does not feed for all dhcp server.
3 I want the make network method to be an exclusive options and want to 
know if it is useful to have both user mode nics and bridge nics 
simultaneously.
4 Based on advices of Michael Goldish I would add an index to 
get_address() and get_port() to adapt the environments with multiple nics.

I would rework the patches based on the comments, and like to see the 
patch of michael.
Thanks.
**

      reply	other threads:[~2009-06-25 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 13:24 Latest kvm autotest patch queue Lucas Meneghel Rodrigues
2009-06-23  4:12 ` sudhir kumar
2009-06-25 13:02   ` jason wang [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=4A43754A.9060201@redhat.com \
    --to=jasowang@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@redhat.com \
    --cc=mgoldish@redhat.com \
    --cc=smalikphy@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox