From: Umair Azam <uazam@i2cinc.com>
To: "xs-devel@lists.xenserver.org" <xs-devel@lists.xenserver.org>,
xen-devel@lists.xen.org
Subject: problem with my xenserver host NIC
Date: Thu, 13 Feb 2014 06:40:28 +0500 [thread overview]
Message-ID: <52FC228C.9040207@i2cinc.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3628 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 4323 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
reply other threads:[~2014-02-13 1:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52FC228C.9040207@i2cinc.com \
--to=uazam@i2cinc.com \
--cc=xen-devel@lists.xen.org \
--cc=xs-devel@lists.xenserver.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 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.