Re: [Xen-users] vm create test ="losetup /dev/loop0 /data/xen/domains/test/disk.img failed"

[Christian Nitschmann <christian.nitschmann@xxxxxxxxxx>]

Thank you for the fast answer.
It seems that SELinux was the culprit. After disabling it, there were no 
problems with starting a xen-domu with disk-images in my own directories.
Greetings from Germany

Chris


Mark Williamson schrieb:
> I'll second the suggestion of SELinux; you either need to:
>
> a) switch it off (not ideal since you'll lose the security benefits)
> b) make sure the image is in the right place to satisfy it
> c) educate SELinux about your preferred domain image path.
>
> I'd also note that using tap:aio: instead of file: has been the preferred 
> means of serving a block device from a file for a while now and might be 
> worth trying.
> Cheers,
> Mark
>
>   
> > On Wednesday June 18 2008 03:40:18 am Christian Nitschmann wrote:
> >     
> > > When i try to start the new debian-etch-machine with "*xm create
> > > /etc/xen/test -c*" i always get the following error message:
> > > -------------------------------
> > > Using config file "./test".
> > > Error: Device 2049 (vbd) could not be connected. losetup /dev/loop0
> > > /data/xen/domains/test/disk.img failed
> > >       
> > Maybe selinux? If it is set to enforcing, your images have to be
> > in /var/lib/xen/images.
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >     
>
>   
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users