public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Armando Montiel <armando.montiel@gmail.com>
To: kvm@vger.kernel.org
Subject: KVM in remote server with bridge in a single ethernet interface
Date: Fri, 25 Jun 2010 12:35:12 -0500	[thread overview]
Message-ID: <i02pch$9js$1@dough.gmane.org> (raw)

Hi,

I have only one ethernet port in a remote server. (eth0)

I have a public address with x.x.x.164 netmask 255.255.255.240 gw x.x.x.161

and want to use in my guest OS the next available ip address (x.x.x.165
netmask 255.255.255.240 gw x.x.x.161)

Is this posible with brctl to achieve this?

I did a file called ifcfg-br0 with:


DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
BROADCAST=x.x.x.175
HWADDR=xx:xx:xx:xx:xx:xx
IPADDR=x.x.x.164
NETMASK=255.255.255.240
NETWORK=x.x.x.160
ONBOOT=yes
GATEWAY=x.x.x.161

then replace ifcfg-eth0 with:
DEVICE=eth0
BRIDGE=br0
#BOOTPROTO=none
ONBOOT=yes

then reboot, after that i use:



I was connected to my remote server but problems begin when I assigned
the x.x.x.165 ip addres to the guest OS with

virt-manager to begin installation. I lost the remote connection. Maybe
I miss something to avoid loosing the connection ?

i'm still receiving ping from x.x.x.165 but x.x.x.164 is not responding.


Here is my config:

Distro: Centos 5.5 x64

Linux v2.noc.com.mx 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 EDT
2010 x86_64 x86_64 x86_64 GNU/Linux

kvm-83-164.el5_5.9
kvm-qemu-img-83-164.el5_5.9
kmod-kvm-83-164.el5_5.9
etherboot-zroms-kvm-5.4.4-13.el5.centos

eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
          inet addr:x.x.x.164  Bcast:x.x.x.175  Mask:255.255.255.240
          inet6 addr: fe80::225:90ff:fe04:7874/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7140395 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2491842 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9632227753 (8.9 GiB)  TX bytes:226154906 (215.6 MiB)
          Memory:fb5e0000-fb600000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:109391 errors:0 dropped:0 overruns:0 frame:0
          TX packets:109391 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:46719292 (44.5 MiB)  TX bytes:46719292 (44.5 MiB)

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:357 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:110402 (107.8 KiB)



             reply	other threads:[~2010-06-25 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 17:35 Armando Montiel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-06-25 16:40 KVM in remote server with bridge in a single ethernet interface Armando Montiel

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='i02pch$9js$1@dough.gmane.org' \
    --to=armando.montiel@gmail.com \
    --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