[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Error: Device 2049 (vbd) could not be connected. - again after reboot

  • To: Frank <josephbeuys@xxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Sat, 01 Sep 2007 13:15:49 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 01 Sep 2007 05:15:56 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=P7q8D7U2pmmTZjQecREACWYyaYHMZLAdAvzMotHWtukIpW03gsXkombCSBUX5OBvHBSUofzD40svyGQVDhWZynFuqpzlPOtQ8qPS8BiyThrCpqtojamB4fu6pi7WePfy8ghl/R5i7At2DUNvRq27oLzzG6YtdQq9emBg2b7vA+A=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Frank wrote:
But why than there are problems with the loop devices with xen if 8 is compiled in. I only unsed 2 img files as loop device and got this error
"Error: Device 2049 (vbd) could not be connected. Backend device not
After I added "loop max_loop=64" the error was gone.
Stopping and restarting domains can leave loop connections dangling in fascinating ways: and if you're using file-based DomU's, *each disk or partition in the devices for the Xen config file* is an additional loopback point.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.