For information, if I manually edit the Mirage-generated "main.ml" to say:
let block1 () = Block.connect "xvda1" (instead of Block.connect "/path/to/disk.img") Then it works fine! However this is not what I want, as main.ml should really work out of the box. :) It seems to me that there is some naming glue between the code generator, Block.connect and Xen that I don't understand. Can anyone shed some light on this? Op 20 jan 2015, om 15:18 heeft Raphael 'kena' Poss het volgende geschreven: > Hi all, > > I'm having trouble with all the "block" examples in mirage-skeleton, using > Xen 4.4. > It all boils down to Block.connect not finding the disk image I describe in > the .xl description file. > > For example: in block/block_test.xl > disk = [ > 'format=raw,vdev=xvda,access=rw,target=/home/kena/src/mirage-skeleton/block/disk.img' > ] > > Gives: > > Block.connect /home/kena/src/mirage-skeleton/block/disk.img: unable to match > '/home/kena/src/mirage-skeleton/block/disk.img' to any available devices [ > 51712 ] > Block.connect /home/kena/src/mirage-skeleton/block/disk.img: could not find > device > > This happened first with a fresh install of Mirage 2.0, then also with Mirage > 2.1/2.2 from the opam dev repository. > For what it's worth it seems my Mirage install works OK, as the 'console' and > 'static_website' demo appear to work perfectly fine. > > Any hints as to where and how to investigate this? > > -- > Raphael 'kena' Poss · [email protected] > http://science.raphael.poss.name/ > > > -- Raphael 'kena' Poss · [email protected] http://science.raphael.poss.name/ _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
