another workaround: //understand losetup -f and -a $ sudo losetup -f $ sudo losetup -a
//actually do the mount and check that it worked and which device it picked $ sudo losetup `sudo losetup -f` <iso_file> $ sudo losetup -a //then use phy:/dev/loop<num> in your xen config file I wouldn't recommend this for disk partition, use tap:aio: instead. But for cdrom image files, it is a good workaround. Also, remember that file: is deprecated due to the problems with loopback devices which is what this workaround uses, which is why you should only use it for iso (read-only) files. -- xend fails to connect guest to dom0 block device or loopback file https://bugs.launchpad.net/bugs/205450 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
