On Sat, Mar 27, 2010 at 12:06:03PM +0000, Keir Fraser wrote:
> On 27/03/2010 11:47, "Pasi Kärkkäinen" <pasik@xxxxxx> wrote:
> >> If the domain actually boot sokay then I suppose pygrub is unlikely to be
> >> the problem. Not sure it's impossible though, and I would at some point try
> >> booting a kernel in dom0 filespace, just to discount pygrub.
> > Ok, I copied the kernel+initramfs to dom0, changed the configuration file,
> > and now "xm create -c" works!
> > So it looks like a pygrub problem..
> Yes, or xend's bootloader plumbing. I doubt any devs test pygrub as a matter
> of course so this could have been broken for a good while.
Yeah.. I just tried reverting pygrub and GrubConf.py to revision 20098 (Aug 20
before many pygrub changes, but it didn't help. Same problem with the console.
So I guess xend then..
Xen-devel mailing list