All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike <mike-kcIQ9yavhvsV/sYkb9DZNQ@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: VM networking stops working
Date: Wed, 21 Nov 2007 21:52:35 +0100	[thread overview]
Message-ID: <47449A93.5090007@eliteserver.biz> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2815 bytes --]

Hello,
I have a problem with my virtual machines. I am using kvm53
on an AMD Athlon(tm) 64 X2 Dual Core Processor 5000+.
As distribution I use Ubuntu server 7.10.
As kernel I use Linux 2.6.22-14-server #1 SMP Sun Oct 14 22:09:15 GMT 
2007 x86_64 GNU/Linux.

I have 3 different vms running. At the beginning they all work without a 
problem.
Then, after one moment to another one or more stop working.
I did a ping test to all the machines, the vm with the failure stops 
pinging.
The result from external ping: Destination host unreachable.
The same result from a ping onto the main server.

Here are my configuration files:
cat /etc/qemu-ifup
#!/bin/sh
/sbin/ifconfig $1 0.0.0.0 promisc up
/usr/sbin/brctl addif br0 $1
sleep 2
------------------------------------------------------------------------
cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto br0
iface br0 inet static
address 195.24.77.169
netmask 255.255.255.0
gateway 195.24.77.1
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
------------------------------------------------------------------------
I use scripts for starting the vms:
kvm -hda apache.img -hdb apache_storage.img -m 512 -boot c -net 
nic,vlan=0,macaddr=00:16:3e:00:00:01 -net tap -nographic -daemonize
kvm -hda postfix.img -m 512 -boot c -net 
nic,vlan=0,macaddr=00:16:3e:00:00:12 -net tap -nographic -daemonize
kvm -hda openvpn.img -m 256 -boot c -net 
nic,vlan=0,macaddr=00:16:3e:00:00:03 -net tap -nographic -daemonize
------------------------------------------------------------------------
The tapN devices are being created at the startup of the vms.

When I run dmesg I have this:
[  112.390943] br0: port 2(tap1) entering learning state
[  112.391919] br0: port 3(tap0) entering learning state
[  112.397605] br0: port 4(tap2) entering learning state
[  122.674313] tap0: no IPv6 routers present
[  122.729185] tap1: no IPv6 routers present
[  122.843901] tap2: no IPv6 routers present
[  123.336081] kvm: emulating exchange as write
[  127.367940] br0: topology change detected, propagating
[  127.367949] br0: port 4(tap2) entering forwarding state
[  127.362971] br0: topology change detected, propagating
[  127.362977] br0: port 2(tap1) entering forwarding state
[  127.362978] br0: topology change detected, propagating
[  127.362980] br0: port 3(tap0) entering forwarding state

No indication of a problem, nowhere in the log files.

I don't know if the vms are freezing, or the network forwarding stops 
working.
I also activated "net.ipv4.conf.default.forwarding=1"

I googled days for that problem, but without a result.
I hope that maybe you have a solution for this problem. That would be 
great, because I prefer using kvm instead of other virtualization systems.

Thank you very much in advance,
Greetings from Luxembourg.

Have a nice day,
Mike


[-- Attachment #1.2: Type: text/html, Size: 3151 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

             reply	other threads:[~2007-11-21 20:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 20:52 Mike [this message]
     [not found] ` <47449A93.5090007-kcIQ9yavhvsV/sYkb9DZNQ@public.gmane.org>
2007-11-21 21:22   ` VM networking stops working Izik Eidus
     [not found]     ` <4744A18D.2050705-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-21 21:40       ` Mike
     [not found]         ` <4744A5E5.9060902-kcIQ9yavhvsV/sYkb9DZNQ@public.gmane.org>
2007-11-21 21:40           ` Izik Eidus
     [not found]             ` <4744A5CA.8050604-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-21 21:53               ` Mike
     [not found]                 ` <4744A8CA.5070702-kcIQ9yavhvsV/sYkb9DZNQ@public.gmane.org>
2007-11-21 21:52                   ` Izik Eidus
     [not found]                     ` <4744A881.1060201-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-21 22:06                       ` Mike
     [not found]                         ` <4744ABD8.8020409-kcIQ9yavhvsV/sYkb9DZNQ@public.gmane.org>
2007-11-21 22:05                           ` Izik Eidus
     [not found]                             ` <4744ABBC.30708-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-21 22:15                               ` Mike
2007-11-21 22:32                               ` Mike
2007-11-21 22:09   ` Lynn Kerby
     [not found]     ` <E729CB4A-EA27-46BD-A54D-47D87117DE90-br2HoPxSX4msTnJN9+BGXg@public.gmane.org>
2007-11-22 10:51       ` Mike

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=47449A93.5090007@eliteserver.biz \
    --to=mike-kciq9yavhvsv/sykb9dznq@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 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.