WARNING - OLD ARCHIVES

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/

I am new to xen, and trying to get things up and going...this looks
like it might be an obvious thing for someone who has seen it...
I have installed centos 5.1 w/virtulization
untarred a prebuilt image (I ran the same image on ubuntu without any
startup issues)
I have changed modprobe.conf (options loop max_loop=64) and if i ls
/dev/loop*, i see them all there
when I try to start it up, here is what i see
xm create /home/xen/centos51/centos.5-1.xen3.cfg -c
Using config file "/home/xen/centos51/centos.5-1.xen3.cfg".
Error: Device 2049 (vbd) could not be connected. losetup /dev/loop0
/home/xen/centos51/centos.5-1.img failed
I can run
# losetup /dev/loop0 /home/xen/centos51/centos.5-1.img
with out error
and see it
losetup -a
/dev/loop0: [fd00]:39190531 (/home/xen/centos51/centos.5-1.img)
however, it does not like this
losetup /dev/loop0
loop: can't get info on device /dev/loop0: No such device or address
which might be ok, not sure, but makes me think this is the kind of
response xm is getting to say it failed (maybe checks first and then
does the losetup?)
I would be very grateful for someone to point me in a direction of
things to try or what package or conf I might be lacking....
thanks a lot
lee
--
Everything should be made as simple as possible, but not simpler. --
Albert Einstein
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users