All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: unstable network trouble
Date: Thu, 27 Oct 2005 17:43:38 +0200	[thread overview]
Message-ID: <4360F5AA.20207@suse.de> (raw)
In-Reply-To: <20051027151234.GX13783@leeni.uk.xensource.com>

> There does seem to be a problem with the hotplug scripts either not running at
> all or bailing out early.

Hmm, no, seems to be a missing hotplug event.

I've added a debug line to xen-backend.rules:

SUBSYSTEM=="xen-backend", RUN+="/bin/logger -p daemon.debug -- 
xen-backend: $env{ACTION} %k"

A successfull start looks like this:

   Oct 27 17:34:50 master-xen logger: xen-backend: add vbd-19-768
   Oct 27 17:34:50 master-xen logger: xen-backend: add vbd-19-832
   Oct 27 17:34:50 master-xen logger: xen-backend: add vif-19-0
   Oct 27 17:34:50 master-xen logger: xen-backend: online vif-19-0

With broken network the "online" event is missing:

   Oct 27 17:35:31 master-xen logger: xen-backend: add vbd-20-832
   Oct 27 17:35:31 master-xen logger: xen-backend: add vbd-20-768
   Oct 27 17:35:31 master-xen logger: xen-backend: add vif-20-0

Oh, and btw, reboot doesn't work all the time either.  Sometimes the 
domain comes up again as it should, and sometimes it doesn't.

cheers,

   Gerd

  reply	other threads:[~2005-10-27 15:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 13:57 unstable network trouble Gerd Knorr
2005-10-27 15:12 ` Ewan Mellor
2005-10-27 15:43   ` Gerd Knorr [this message]
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=4360F5AA.20207@suse.de \
    --to=kraxel@suse.de \
    --cc=ewan@xensource.com \
    --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.