The dom0 kernel should work fine as a domU as well, so the guest being blocked indicates that it may be because of a device attach being blocked. In particular, I wonder if you're using the qemu block backend, which requires a process in dom0 that may not have been spawned for some reason.
You can debug this by using 'xenstore-ls' to show the filesystem tree for /local/domain/<domid> and see what state the various devices are in. Did you try the script in /root to create a linux guest image btw? Magnus may have snuck some magic in there to deal with this :) -anil > On 1 Jun 2015, at 09:03, Ahmed Ismail <[email protected]> wrote: > > Hey, > > Thank you for your e-mail Luke. > No, see that's the weird thing, when I use logical volumes I can create domU > guests without any issue, even with memory set at 512MB. > The issue is specifically with using .img files instead of logical volumes. > I've upgraded Xen to 4.5 on the CT and tried few more other modifications to > the configurations, but no cookie. > I'm sure it's something really simple that I'm missing.. > > In any case, the LVs will have to do for now. > I'm still trying a number of other things on the side, and if I do manage to > find a way around this, I'll try and send out an RCA & solution in the hope > that others may benefit. > > Have a wonderful day! > > Cheers, > -- > Ahmed > _______________________________________________ > MirageOS-devel mailing list > [email protected] > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
