[Xen-users] Error: Device 2049 (vbd) could not be connected. Backend device not found.

["Adam Keck" <ghostis@xxxxxxxxx>]

Hello All,

 I just ran into this on Debian.  I think the ide setting is a false
lead.  I found that the underlying issue is that the "loop" module
does not get loaded by Debian at boot time.  Adding "loop" to
/etc/modules resolved the issue.  Whatever the distribution, the
solution seems to be to poke Linux in the appropriate manner during
boot to load the "loop" module or to load the loop module at xend
start-up.  Joe's stanza below in /etc/init.d/xend should work work for
the latter.
To me, at least, it looks like converting to ide emulation in one's
image is not needed.

-Adam


On 28 Apr 2006, at 12:55, Joe Warren-Meeks wrote:

Hey guys,


   I read xen-create-image to see why it seemed to work if I used
that. Just by an aside I noticed that there is an option of use-ide

   So, I've set "use-ide = 1" in /etc/xen-tools/xen-tools.conf and
recreated my images and it seems to work now.

   I figure that an IDE server has problems trying to run a SCSI domU


   I'm creating a bunch of domUs now and rebooting to see if they all
start ok. (I also had to up my loopback devices as indicated in
another post)

   Give it a shot and report back.

Just to confirm, changing use-ide = 1 and changing my /etc/init.d/ xend to read:

 start)
       modprobe loop max_loop=64
       cd /dev && /dev/MAKEDEV loop
       xend start
       await_daemons_up
       ;;

fixed my problems. I now have three domU's working happily.

Good luck.

-- joe.

Joe Warren-Meeks                       T: +44 (0) 208 962 0007
Aggregator Limited                     M: +44 (0) 7789 176078
Unit 62/63 Pall Mall Deposit           E: joe.warren-meeks@xxxxxxxxxxxxx
124-128 Barlby Road, London W10 6BL
PGP Fingerprint: 361F 78D0 56F5 8D7F 2639  947D 71E2 8811 F825 64CC

--
-Adam


--
-Adam

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users