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 562] New: [Xen-HVM] Backend device not found: Error mess

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 562] New: [Xen-HVM] Backend device not found: Error message during xm-test
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 08 Mar 2006 07:17:50 +0000
Delivery-date: Wed, 08 Mar 2006 07:18:47 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: [Xen-HVM] Backend device not found: Error message during
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux-2.6
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ricardoz@xxxxxxxxxx

Hardware Platform:
xSeries x460

SLES9 SP2 32bit and 64bit.

Test Tool:


- During a xm-test run, 11_create_concurrent_pos.py exposes a problem where a
domain is not created due to the backend device not being found. Here is the
xm-test output:

Started domain 11_create_7
[dom0] Waiting 20 seconds for domU boot...
Console executing: ['/usr/sbin/xm', 'xm', 'console', '11_create_7']
[11_create_7] Sending `foo'
[11_create_7] Sending `ls'
[11_create_7] Sending `echo $?'
[7] Started 11_create_7
[dom0] Running `xm create /tmp/xm-test.conf'
Using config file "/tmp/xm-test.conf".
Error: Device 768 (vbd) could not be connected. Backend device not found.
Failed to create domain
REASON: [8] Failed to create domain

- Dan Stekloff and I looked at my qemu-dm log file for the particular pid and
found the following:

domid: 127
qemu: the number of cpus is 1
shared page at pfn:1c00, mfn: 2c289
char device redirected to /dev/pts/19
False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, count:
0, size: 0

- From Stekloff: Qemu-dm goes to read the req from the shared page and... looks
like nothing is there:

//get the ioreq packets from share mem
static ioreq_t* __cpu_get_ioreq(int vcpu)
    ioreq_t *req;

    req = &(shared_page->vcpu_iodata[vcpu].vp_ioreq);

    if ( req->state == STATE_IOREQ_READY )
        return req;

    fprintf(logfile, "False I/O request ... in-service already: "
                     "%x, pvalid: %x, port: %"PRIx64", "
                     "data: %"PRIx64", count: %"PRIx64", size: %"PRIx64"\n",
                     req->state, req->pdata_valid, req->addr,
                     req->u.data, req->count, req->size);
    return NULL;

- I'll provide more info later.

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 562] New: [Xen-HVM] Backend device not found: Error message during xm-test, bugzilla-daemon <=