xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Konieczny <jajcus@jajcus.net>
To: xen-devel@lists.xen.org
Subject: Re: [BUG] libxenstat and xentop confused by renamed VIF interfaces
Date: Wed, 21 May 2014 10:15:02 +0200	[thread overview]
Message-ID: <537C6086.3090807@jajcus.net> (raw)
In-Reply-To: <537C5B32.7050109@jajcus.net>

On 05/21/14 09:52, Jacek Konieczny wrote:
> The 'vifname' option is very useful to have predictable interface names
> for firewall configuration or network monitoring. The problem is
> libxenstore under Linux parses /proc/net/dev to extract 'vif.${domid}.*'

I mean _libxenstat_, of course.

Xen 4.4.0.

Greets,
	Jacek

  reply	other threads:[~2014-05-21  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21  7:52 [BUG] libxenstore and xentop confused by renamed VIF interfaces Jacek Konieczny
2014-05-21  8:15 ` Jacek Konieczny [this message]
2014-05-21 10:29 ` Ian Campbell
2014-05-21 10:48   ` [BUG] libxenstat " Jacek Konieczny
2014-05-21 10:53     ` Ian Campbell
2014-05-21 11:35   ` Jacek Konieczny
2014-05-21 11:52     ` Ian Campbell
2014-05-21 14:01       ` Jan Beulich

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=537C6086.3090807@jajcus.net \
    --to=jajcus@jajcus.net \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).