This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 732] New: Misleading errors messages in xend.log

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 732] New: Misleading errors messages in xend.log
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 10 Aug 2006 01:20:33 -0700
Delivery-date: Thu, 10 Aug 2006 01:21:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Misleading errors messages in xend.log
           Product: Xen
           Version: 3.0-testing
          Platform: x86
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P4
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: anthony@xxxxxxxxxxxxxxxxx

Whenever I start a domain for every VBD I get a message in the Dom-0 xend.log:
   exception looking up device number for XXXX: [Errno 2] No such file or
directory: '/dev/XXXX'
Where XXXX is the name of the VBD in the Domain.

The message seems to have no effect as the domain still starts perfectly well,
and my understanding from reading xen-devel archives from August 2005 is that
if I create some /dev/XXXX block devices the messages will go away. (My Dom-0
devices are all sdXX, while my Dom-U devices are all hdXX).

Surely a much better solution would be to prevent the messages being generated
in the first place.

When I first started using Xen, I had a problem with a domain not starting, saw
these messages and wasted a lot of time on the assumption that these messages
related to why the domain wasn't working.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 732] New: Misleading errors messages in xend.log, bugzilla-daemon <=