From: Arun Sharma <arun.sharma@intel.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Timeout connecting to device
Date: Tue, 23 Aug 2005 18:36:20 -0700 [thread overview]
Message-ID: <430BCF14.2040409@intel.com> (raw)
In-Reply-To: <430A387C.2030108@intel.com>
I didn't see any responses to this query. I also see:
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=176
which is essentially the same issue. Do VBDs work for anyone on the list?
It sounds like
> XENBUS xs_read_watch: 0
is an indication of the fact that after the right entries were made in
xenstore (I can see them on /var/lib/xenstored/store/domain), but xenbus
is not able to read events?
# find . -name *end
./a9b503a7-2494-409f-9e06-2bd1f9283953/device/vbd/768/backend
./45194ebb-4029-4131-9013-d17cd3dbc828/device/vbd/768/backend
./53ffa08b-5f90-45a4-9671-8d6fff7f8509/backend
./53ffa08b-5f90-45a4-9671-8d6fff7f8509/backend/vbd/a9b503a7-2494-409f-9e06-2bd1f9283953/768/frontend
./53ffa08b-5f90-45a4-9671-8d6fff7f8509/backend/vbd/45194ebb-4029-4131-9013-d17cd3dbc828/768/frontend
Couple of questions:
- is there a way to debug xenstored? It doesn't seem to be logging much.
- Could we add some debug flags elsewhere as well (xenbus with debug=1?)
to make debugging problems of this nature easier?
A golden "working" log file would also be useful so we can compare our
logs against it..
-Arun
Arun Sharma wrote:
>
> Is there any userspace configuration I'm missing?
>
> -Arun
>
> xen_blk: Initialising virtual block device driver
> XENBUS xs_read_watch: 0
> xen_blk: Timeout connecting to device!
> Netdev frontend (TX) is using grant tables.
> Netdev frontend (RX) is using grant tables.
> xen_net: Initialising virtual ethernet driver.
> CBNET: Registered protocol family 2
> IP: routing cache hash table of 256 buckets, 4Kbytes
> TCP established hash table entries: 4096 (order: 4, 65536 bytes)
> TCP bind hash table entries: 4096 (order: 3, 49152 bytes)
> TCP: Hash tables configured (established 4096 bind 4096)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Root-NFS: No NFS server available, giving up.
>
>
next prev parent reply other threads:[~2005-08-24 1:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 20:41 Timeout connecting to device Arun Sharma
2005-08-22 20:42 ` Arun Sharma
2005-08-24 1:36 ` Arun Sharma [this message]
2005-08-24 4:43 ` Rusty Russell
2005-08-24 8:25 ` Christian Limpach
2005-08-25 3:18 ` Rusty Russell
2005-08-25 11:01 ` Christian Limpach
2005-08-26 0:27 ` Rusty Russell
2005-08-26 10:37 ` Christian Limpach
2005-08-29 0:17 ` Rusty Russell
2005-08-29 0:23 ` Christian Limpach
2005-08-25 0:31 ` Arun Sharma
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=430BCF14.2040409@intel.com \
--to=arun.sharma@intel.com \
--cc=xen-devel@lists.xensource.com \
/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.