All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Kaczmarek <tedkaz@optonline.net>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Seeing bridge issues, how do I tell what domU is using what	interface?
Date: Thu, 13 Oct 2005 17:49:51 -0400	[thread overview]
Message-ID: <1129240191.12282.100.camel@pluto.linsolutions.com> (raw)

I seeing an issue sporadically where a Dom does not see the network.
In once case it was triggered by running SPF on a Dom, in that scenario
putting the DomU's interface in promiscuous mode fixes it. I have hit
another condition where putting the DomU's interface in promiscuous mode
doesn't fly. With some sporadic failure of domU creation still floating
this can be a real pita. 


Is their a way to get mapping of domU to vif ?
Log files don't provide it.


Opened up an rfe on this a while back as well

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=248


Regards,
Ted

             reply	other threads:[~2005-10-13 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 21:49 Ted Kaczmarek [this message]
2005-10-13 21:59 ` Seeing bridge issues, how do I tell what domU is using what interface? Nicholas Lee
2005-10-13 23:25   ` Ted Kaczmarek
2005-10-13 23:42     ` Ewan Mellor
2005-10-14  0:31       ` Ted Kaczmarek

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=1129240191.12282.100.camel@pluto.linsolutions.com \
    --to=tedkaz@optonline.net \
    --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.