From mboxrd@z Thu Jan  1 00:00:00 1970
From: Umair Azam <uazam@i2cinc.com>
Subject: problem with my xenserver host NIC
Date: Thu, 13 Feb 2014 06:40:28 +0500
Message-ID: <52FC228C.9040207@i2cinc.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4138881865152443097=="
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "xs-devel@lists.xenserver.org" <xs-devel@lists.xenserver.org>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

This is a multi-part message in MIME format.
--===============4138881865152443097==
Content-Type: multipart/alternative;
 boundary="------------060709020604090003000508"

This is a multi-part message in MIME format.
--------------060709020604090003000508
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi guys,

Can u help to make me understand whats the problem with my xenserver 
host NIC

Feb 13 04:37:41 xenserver-Host1 kernel: [84621.965144] 
/local/domain/3/device/vif/0: Initialising
Feb 13 04:37:41 xenserver-Host1 kernel: [84621.965194] 
/local/domain/3/device/vif/0: Initialising
Feb 13 04:37:42 xenserver-Host1 kernel: [84622.459354] *device vif3.0 
entered promiscuous mode*
Feb 13 04:37:42 xenserver-Host1 kernel: [84622.609173] 
/local/domain/3/device/vif/1: Initialising
Feb 13 04:37:42 xenserver-Host1 kernel: [84622.609256] 
/local/domain/3/device/vif/1: Initialising
Feb 13 04:37:43 xenserver-Host1 kernel: [84623.098415] device vif3.1 
entered promiscuous mode
Feb 13 04:37:43 xenserver-Host1 kernel: [84623.238585] 
*/local/domain/3/device/vif/2: Initialising*
Feb 13 04:37:43 xenserver-Host1 kernel: [84623.238657] 
/local/domain/3/device/vif/2: Initialising
Feb 13 04:37:43 xenserver-Host1 kernel: [84623.737693] device vif3.2 
entered promiscuous mode
Feb 13 04:37:43 xenserver-Host1 kernel: [84623.876452] 
/local/domain/3/device/vif/3: Initialising
Feb 13 04:37:43 xenserver-Host1 kernel: [84623.876541] 
/local/domain/3/device/vif/3: Initialising
Feb 13 04:37:44 xenserver-Host1 kernel: [84624.367713] device vif3.3 
entered promiscuous mode
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.888799] blkback: 
event-channel 8
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.891066] blkback: ring-ref 8
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.891180] blkback: protocol 
1 (x86_32-abi)
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.897358] blkback: 
event-channel 9
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.897573] blkback: ring-ref 9
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.897650] blkback: protocol 
1 (x86_32-abi)
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.900317] 
/local/domain/3/device/vif/0: Connected
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.902502] 
/local/domain/3/device/vif/1: Connected
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.904564] 
/local/domain/3/device/vif/2: Connected
Feb 13 04:38:08 xenserver-Host1 kernel: [84648.909578] 
/local/domain/3/device/vif/3: Connected
Feb 13 04:38:26 xenserver-Host1 kernel: [84666.557634] *e1000e: eth0 NIC 
Link is Down*
Feb 13 04:38:39 xenserver-Host1 kernel: [84679.967459] nfs: server 
10.11.17.31 not responding, timed out
Feb 13 04:38:39 xenserver-Host1 kernel: [84679.967472] nfs: server 
10.11.17.31 not responding, timed out
Feb 13 04:39:12 xenserver-Host1 kernel: [84712.977493] nfs: server 
10.11.17.31 not responding, timed out
Feb 13 04:39:24 xenserver-Host1 kernel: [84724.987474] nfs: server 
10.11.17.31 not responding, timed out
Feb 13 04:39:36 xenserver-Host1 kernel: [84736.427442] *vif3.3: draining 
TX queue*
Feb 13 04:39:36 xenserver-Host1 kernel: [84736.987447] nfs: server 
10.11.17.31 not responding, timed out
Feb 13 04:40:00 xenserver-Host1 kernel: [84760.987443] nfs: server 
10.11.17.31 not responding, timed out
Feb 13 04:40:48 xenserver-Host1 kernel: [84808.987488] nfs: server 
10.11.17.31 not responding, timed out
Feb 13 04:41:48 xenserver-Host1 kernel: [84868.987466] nfs: server 
10.11.17.31 not responding, timed out
Feb 13 04:42:24 xenserver-Host1 kernel: [84904.987446] nfs: server 
10.11.17.31 not responding, timed out
Feb 13 04:43:19 xenserver-Host1 kernel: [84959.538298] *e1000e: eth0 NIC 
Link is Up 100 Mbps Full Duplex, Flow Control: None*
Feb 13 04:43:19 xenserver-Host1 kernel: [84959.538406] e1000e 
0000:00:19.0: eth0: 10/100 speed: disabling TSO
Feb 13 04:43:24 xenserver-Host1 kernel: [84964.987445] nfs: server 
10.11.17.31 not responding, timed out


-- 
Umair Azam


--------------060709020604090003000508
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi guys,<br>
    <br>
    Can u help to make me understand whats the problem with my xenserver
    host NIC<br>
    <br>
    Feb 13 04:37:41 xenserver-Host1 kernel: [84621.965144]
    /local/domain/3/device/vif/0: Initialising<br>
    Feb 13 04:37:41 xenserver-Host1 kernel: [84621.965194]
    /local/domain/3/device/vif/0: Initialising<br>
    Feb 13 04:37:42 xenserver-Host1 kernel: [84622.459354] <b>device
      vif3.0 entered promiscuous mode</b><br>
    Feb 13 04:37:42 xenserver-Host1 kernel: [84622.609173]
    /local/domain/3/device/vif/1: Initialising<br>
    Feb 13 04:37:42 xenserver-Host1 kernel: [84622.609256]
    /local/domain/3/device/vif/1: Initialising<br>
    Feb 13 04:37:43 xenserver-Host1 kernel: [84623.098415] device vif3.1
    entered promiscuous mode<br>
    Feb 13 04:37:43 xenserver-Host1 kernel: [84623.238585] <b>/local/domain/3/device/vif/2:
      Initialising</b><br>
    Feb 13 04:37:43 xenserver-Host1 kernel: [84623.238657]
    /local/domain/3/device/vif/2: Initialising<br>
    Feb 13 04:37:43 xenserver-Host1 kernel: [84623.737693] device vif3.2
    entered promiscuous mode<br>
    Feb 13 04:37:43 xenserver-Host1 kernel: [84623.876452]
    /local/domain/3/device/vif/3: Initialising<br>
    Feb 13 04:37:43 xenserver-Host1 kernel: [84623.876541]
    /local/domain/3/device/vif/3: Initialising<br>
    Feb 13 04:37:44 xenserver-Host1 kernel: [84624.367713] device vif3.3
    entered promiscuous mode<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.888799] blkback:
    event-channel 8<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.891066] blkback:
    ring-ref 8<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.891180] blkback:
    protocol 1 (x86_32-abi)<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.897358] blkback:
    event-channel 9<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.897573] blkback:
    ring-ref 9<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.897650] blkback:
    protocol 1 (x86_32-abi)<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.900317]
    /local/domain/3/device/vif/0: Connected<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.902502]
    /local/domain/3/device/vif/1: Connected<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.904564]
    /local/domain/3/device/vif/2: Connected<br>
    Feb 13 04:38:08 xenserver-Host1 kernel: [84648.909578]
    /local/domain/3/device/vif/3: Connected<br>
    Feb 13 04:38:26 xenserver-Host1 kernel: [84666.557634] <b>e1000e:
      eth0 NIC Link is Down</b><br>
    Feb 13 04:38:39 xenserver-Host1 kernel: [84679.967459] nfs: server
    10.11.17.31 not responding, timed out<br>
    Feb 13 04:38:39 xenserver-Host1 kernel: [84679.967472] nfs: server
    10.11.17.31 not responding, timed out<br>
    Feb 13 04:39:12 xenserver-Host1 kernel: [84712.977493] nfs: server
    10.11.17.31 not responding, timed out<br>
    Feb 13 04:39:24 xenserver-Host1 kernel: [84724.987474] nfs: server
    10.11.17.31 not responding, timed out<br>
    Feb 13 04:39:36 xenserver-Host1 kernel: [84736.427442] <b>vif3.3:
      draining TX queue</b><br>
    Feb 13 04:39:36 xenserver-Host1 kernel: [84736.987447] nfs: server
    10.11.17.31 not responding, timed out<br>
    Feb 13 04:40:00 xenserver-Host1 kernel: [84760.987443] nfs: server
    10.11.17.31 not responding, timed out<br>
    Feb 13 04:40:48 xenserver-Host1 kernel: [84808.987488] nfs: server
    10.11.17.31 not responding, timed out<br>
    Feb 13 04:41:48 xenserver-Host1 kernel: [84868.987466] nfs: server
    10.11.17.31 not responding, timed out<br>
    Feb 13 04:42:24 xenserver-Host1 kernel: [84904.987446] nfs: server
    10.11.17.31 not responding, timed out<br>
    Feb 13 04:43:19 xenserver-Host1 kernel: [84959.538298] <b>e1000e:
      eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None</b><br>
    Feb 13 04:43:19 xenserver-Host1 kernel: [84959.538406] e1000e
    0000:00:19.0: eth0: 10/100 speed: disabling TSO<br>
    Feb 13 04:43:24 xenserver-Host1 kernel: [84964.987445] nfs: server
    10.11.17.31 not responding, timed out<br>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Umair Azam
</pre>
  </body>
</html>

--------------060709020604090003000508--


--===============4138881865152443097==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============4138881865152443097==--