public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
To: "Alexey Eremenko"
	<alexey.eremenko-atKUWr5tajBWk0Htik3J/w@public.gmane.org>,
	kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Akio Takebe <takebe_akio-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
Subject: Re: [Patch] adding some scripts at installing
Date: Tue, 30 Oct 2007 19:31:58 +0900	[thread overview]
Message-ID: <CCC81AE019AC3Ctakebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E032160C95C584-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>

Hi, Alexey

>Yes, that would be better.
>
>However, I found that when using multiple virtual bridges (via brctl),
>you need to have several script files.
>
Thank you for your comment.
Are there any other necessary files not including in my patch?
I may forgot some files because my machine is installed Xen.
If you found some of them, can you tell me them?

>In the future, I hope that bridging functionality could be integrated into 
>Qemu/KVM, so that we won't need that script at all.
>
It's nice. 

Best Regards,

Akio Takebe


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-10-30 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30  9:29 [Patch] adding some scripts at installing Akio Takebe
2007-10-30  9:36 ` Alexey Eremenko
     [not found]   ` <64F9B87B6B770947A9F8391472E032160C95C584-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-10-30 10:31     ` Akio Takebe [this message]
     [not found] ` <CAC81AD75E5BE2takebe_akio-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-10-30 11:25   ` Avi Kivity

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=CCC81AE019AC3Ctakebe_akio@jp.fujitsu.com \
    --to=takebe_akio-+cum20s59erqfuhtdcdx3a@public.gmane.org \
    --cc=alexey.eremenko-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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