[Pkg-xen-devel] Bug#377996: Error: Device 2049 (vbd) could not be connected. Backend

Alastair McKinstry mckinstry at debian.org
Wed Jul 12 13:43:34 UTC 2006

Package: xen-utils-3.0
Version: 3.0.2+hg9681-1
Severity: normal

I get this error with xen after some debug cycles, start / stopping nodes.
I found this fix on the net, which fixes the problem:


in /etc/init.d/xen:

        + modprobe loop max_loop=64
        + cd /dev && /dev/MAKEDEV loop
        xend start

This fixes the problem for me, and I request that it (or a variant)
be added to the Debian scripts.

Alastair McKinstry

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-xen-ichec
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)

Versions of packages xen-utils-3.0 depends on:
ii  iproute                   20051007-4     Professional tools to control the 
ii  libc6                     2.3.6-13       GNU C Library: Shared libraries
ii  libncurses5               5.5-2          Shared libraries for terminal hand
ii  python                    2.3.5-10       An interactive high-level object-o
ii  udev                      0.093-1        /dev/ and hotplug management daemo
ii  xen-hypervisor-3.0-amd64  3.0.2+hg9681-1 The Xen Hypervisor for amd64
ii  zlib1g                    1:1.2.3-11     compression library - runtime

Versions of packages xen-utils-3.0 recommends:
ii  bridge-utils                  1.1-1      Utilities for configuring the Linu
pn  libc6-xen                     <none>     (no description available)

-- no debconf information

More information about the Pkg-xen-devel mailing list