From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Sharma Subject: Re: Timeout connecting to device Date: Tue, 23 Aug 2005 18:36:20 -0700 Message-ID: <430BCF14.2040409@intel.com> References: <430A387C.2030108@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <430A387C.2030108@intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org 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. > >