Are you running CentOS 5.2
repo Xen or some self-compiled Xen? If it’s the former, I wouldn’t jump
straight to blaming Xen, as I suspect the only reason CentOS 5.2 would support
vifname is because they patched it in, so it may not fully support it (similar
to how F8 doesn’t). If it is a self-compiled Xen, then yeah, it looks like it’s
Xen related, but I haven’t tried to resolve the issue, because I assumed it was
specific to my Fedora release from the repo (and I haven’t reported it to
bugzilla, which would be fruitless at this point with F8 soon losing support).
Dustin
From: Rudi Ahlers
[mailto:rudiahlers@xxxxxxxxx]
Sent: Thursday, September 18, 2008 12:05
To: Dustin.Henning@xxxxxxxxxxx
Subject: Re: [Xen-users] domU network interface not reporting bandwidth
usage
On Thu, Sep 18, 2008 at 4:55 PM, Dustin Henning <Dustin.Henning@xxxxxxxxxxx>
wrote:
Does this work on your other
domains? That may be implied, but I
wanted to confirm, because I have noticed in F8 with Xen from repo, the xm
top command doesn't show network traffic if using vifname, but does when the
default vifX.Y is used. I should think that would be related to xm top
checking for vifX.Y and not vifname (F8 uses a version of Xen where
vifname
would have to have been patched in), but if that weren't the case, and it
were somehow related to using vifname, that would be interesting.
Dustin
Yes, you're right - the domains with a default vif does show
network stats, but the ones where I specify the name doesn't
This is on CentOS 5.2 thought, so is it something todo with
XEN then?
--
Kind Regards
Rudi Ahlers
|
