All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: unstable network trouble
Date: Thu, 27 Oct 2005 15:57:50 +0200	[thread overview]
Message-ID: <4360DCDE.6000207@suse.de> (raw)

   Hi,

With current unstable (hg7500) I have the problem that networking for 
domU's doesn't work reliable.  Seems to be more or less random, havn't 
seen any pattern yet, sometimes it works normally and sometimes it doesn't.

In case it does _not_ work it looks like this (domain 1 runs fine, 
domain 3 is broken):

The xen-backend device is present in sysfs:

   master-xen root ~# ls /sys/devices/xen-backend
   .  ..  vbd-1-768  vbd-1-832  vbd-3-51712  vif-1-0  vif-3-0

The vif network interface is missing:

   master-xen root ~# ip link ls | grep vif
   3: vif0.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
   6: vif1.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue

/etc/xen/scripts/vif-bridge is not called according to /var/log/messages:

   master-xen root /var/log# grep vif-bridge /var/log/messages
   Oct 27 15:22:50 master-xen logger: /etc/xen/scripts/vif-bridge: up 
XENBUS_PATH=backend/vif/1/0

The backend entries in xenstore look just fine:

master-xen root ~# xenstore-dump backend/vif
1/
     0/
         bridge           xenbr0
         mac              aa:00:57:4f:25:a7
         handle           0
         script           /etc/xen/scripts/vif-bridge
         frontend-id      1
         domain           debian
         frontend         /local/domain/1/device/vif/0
3/
     0/
         bridge           xenbr0
         mac              aa:00:ca:d7:83:e1
         handle           0
         script           /etc/xen/scripts/vif-bridge
         frontend-id      3
         domain           gentoo
         frontend         /local/domain/3/device/vif/0

ideas anyone?

cheers,

   Gerd

             reply	other threads:[~2005-10-27 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 13:57 Gerd Knorr [this message]
2005-10-27 15:12 ` unstable network trouble Ewan Mellor
2005-10-27 15:43   ` Gerd Knorr
2005-10-27 15:57     ` Ewan Mellor
2005-10-28  9:06       ` Gerd Knorr
2005-10-28  9:59         ` Gerd Knorr
2005-10-28 11:11           ` Ewan Mellor
2005-10-28 10:03         ` Gerd Knorr
2005-10-31 10:58     ` Gerd Knorr

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=4360DCDE.6000207@suse.de \
    --to=kraxel@suse.de \
    --cc=xen-devel@lists.xensource.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 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.