From owner-freebsd-bugs@freebsd.org Thu Oct 13 09:16:16 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 806B9C10C71 for ; Thu, 13 Oct 2016 09:16:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56654154 for ; Thu, 13 Oct 2016 09:16:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9D9GG62030734 for ; Thu, 13 Oct 2016 09:16:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 213439] ifOutOctets are always zero for Xen xn interfaces Date: Thu, 13 Oct 2016 09:16:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: Trond.Endrestol@ximalas.info X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2016 09:16:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213439 Bug ID: 213439 Summary: ifOutOctets are always zero for Xen xn interfaces Product: Base System Version: 11.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: Trond.Endrestol@ximalas.info CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Virtualization platform is XenServer 7.0.0. The XenServer guest is: root@[WITHHELD]:~ # uname -a FreeBSD [WITHHELD].fig.ol.no 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #1 r306639: Mon Oct 3 17:36:35 CEST 2016=20=20=20=20 root@[WITHHELD]:/usr/obj/usr/src/sys/XENGUEST amd64 The kernel configuration file is available at http://ximalas.info/~trond/create-zfs/canmount/XENGUEST-amd64-stable-11 Just for comparison, here's lo0: root@[WITHHELD]:~ # snmpget -v 2c -c public localhost 1.3.6.1.2.1.2.2.1.2.1 IF-MIB::ifDescr.1 =3D STRING: lo0 root@[WITHHELD]:~ # snmpget -v 2c -c public localhost 1.3.6.1.2.1.2.2.1.10.1 IF-MIB::ifInOctets.1 =3D Counter32: 190342 root@[WITHHELD]:~ # snmpget -v 2c -c public localhost 1.3.6.1.2.1.2.2.1.16.1 IF-MIB::ifOutOctets.1 =3D Counter32: 190491 This is for xn0: root@[WITHHELD]:~ # snmpget -v 2c -c public localhost 1.3.6.1.2.1.2.2.1.2.2 IF-MIB::ifDescr.2 =3D STRING: xn0 root@[WITHHELD]:~ # snmpget -v 2c -c public localhost 1.3.6.1.2.1.2.2.1.10.2 IF-MIB::ifInOctets.2 =3D Counter32: 1799356094 root@[WITHHELD]:~ # snmpget -v 2c -c public localhost 1.3.6.1.2.1.2.2.1.16.2 IF-MIB::ifOutOctets.2 =3D Counter32: 0 This is for xn1: root@[WITHHELD]:~ # snmpget -v 2c -c public localhost 1.3.6.1.2.1.2.2.1.2.3 IF-MIB::ifDescr.3 =3D STRING: xn1 root@[WITHHELD]:~ # snmpget -v 2c -c public localhost 1.3.6.1.2.1.2.2.1.10.3 IF-MIB::ifInOctets.3 =3D Counter32: 2647317261 root@[WITHHELD]:~ # snmpget -v 2c -c public localhost 1.3.6.1.2.1.2.2.1.16.3 IF-MIB::ifOutOctets.3 =3D Counter32: 0 In the latter two cases ifOutOctets are always zero, but not for the lo0 ca= se. Is this a bug in the xn driver? --=20 You are receiving this mail because: You are the assignee for the bug.=