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-users] Error: Device 2049 (vbd) could not be connected. - again aft

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Error: Device 2049 (vbd) could not be connected. - again after reboot
From: Frank <josephbeuys@xxxxxx>
Date: Sat, 01 Sep 2007 12:09:49 +0200
Delivery-date: Sat, 01 Sep 2007 03:06:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Macintosh/20070728)
It's very strange. I thought I had solved the problem with xen and the not starting domU yesterday but now I see the same error as yesterday again only after a reboot an I've changed nothing, only iptables.
I don't have an answer for that behaivior.

server1:/etc/xen# xm create -c xen-etch.cfg
Using config file "xen-etch.cfg".
Error: Device 2049 (vbd) could not be connected. Backend device not found.
h966380:/etc/xen# ifconfig

Xen-users mailing list