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


Re: [Xen-users] losetup /dev/loop0 /xen/centos.img failed

lee hartley wrote:
yep, sorry...

kernel = "/boot/vmlinuz-2.6.18-53.el5xen"
ramdisk = "/boot/initrd-2.6.18-53.el5xen.img"
memory = 512
name = "centos.5-1"
vif = [ '' ]
dhcp = "dhcp"
disk = ['file:/home/xen/centos51/centos.5-1.img,sda1,w',

Change this to

disk = ['tap:aio:/home/xen/centos51/centos.5-1.img,xvda1,w', 'tap:aio:/home/xen/centos51/centos.swap,xvda2,w']

root = "/dev/sda1 ro"

Change to root = "/dev/xvda1 ro"

Then recreate your initrd image using --preload=xenblk and --with-xennet.

I thought I read somewhere to try doing it as ide (not sure it applies
here)....i assume to try that i would have to change the config file
to hdax and add an option somewhere...i looked in the xend conf, but
did not look like the right place...

thanks a lot for taking the time to have a look!


On Dec 14, 2007 2:19 AM, Sadique Puthen <sputhenp@xxxxxxxxxx> wrote:
Your guest configuration file, please.


lee hartley wrote:
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

Xen-users mailing list

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