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 could not be connected.

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Error: Device 2049 could not be connected.
From: Paradox <paradox@xxxxxxxxxxx>
Date: Fri, 21 Sep 2007 21:57:43 +0200
Delivery-date: Fri, 21 Sep 2007 12:57:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <8206ae960709211112h1b7923c6h5f4b3162f6f5fe6f@xxxxxxxxxxxxxx>
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>
References: <E1IYkGm-0007s4-4c@host-192-168-0-1-bcn-london> <46F3F18A.3080807@xxxxxxxxxxx> <8206ae960709211112h1b7923c6h5f4b3162f6f5fe6f@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060427 Debian/1.7.13-0ubuntu04.10

I think I have some configuration problem...modifying xen configuration the hotplug error disappears, but now I have (I hope...) a "last" problem.

I use this command: xm create -c myvmconf vmid=1

Dom start and I receive this message: http://doxspace.altervista.org/xen-error.txt

hummm......I think this is configuration problem (swap error for example...first line...)....I have some doubt about "disk" option...

My configuration is here: http://doxspace.altervista.org/myvmconf

Grub configuration: http://doxspace.altervista.org/menu.lst

You have some ideas?


Best Regards

xSAPPYx wrote:

Check your xen-hotplug log, it should give you some ideas where your failure is.

I ran into this error a few days ago on a gentoo box. a weird version
of 'stat' was installed, so the hotplug scripts were failing their
sanity checks.

Anyway, poke at your logs and find the errors


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>