On Sat, Mar 27, 2010 at 11:29:25AM +0000, Keir Fraser wrote:
> On 27/03/2010 11:24, "Pasi Kärkkäinen" <pasik@xxxxxx> wrote:
> >> Assuming worked somewhat recently, I'd bisect. If it hasn't worked recently
> >> I'd wonder what's different/special about those RPMs or test setup. I
> >> wonder
> >> if it has something to do with using pygrub? Lots of grub2-support patches
> >> went into that recently.
> > I just tried 4.0.0-rc4, and it doesn't work there either:
> > [root@dom0 ~]# xm create -f /etc/xen/f12test-nonmanaged -c
> > Using config file "/etc/xen/f12test-nonmanaged".
> > xenconsole: Could not read tty from store: No such file or directory
> > [root@dom0 ~]# Started domain f12test (id=1)
> > About pygrub.. Michael reported pvgrub doesn't work either, it crashes..
> > it might be different issue though.
> 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..
[root@dom0 ]# cat /etc/xen/f12test-nonmanaged
name = "f12test"
uuid = "dbe06b39-a570-2b98-a2fe-8f17738fd1d5"
maxmem = 512
memory = 512
vcpus = 2
#bootloader = "/usr/bin/pygrub"
kernel = "/root/testfoo/vmlinuz-220.127.116.11-174.2.22.fc12.x86_64"
ramdisk = "/root/testfoo/initramfs-18.104.22.168-174.2.22.fc12.x86_64.img"
root = "/dev/mapper/vg_f12test-lv_root"
extra = "ro LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc
KEYTABLE=fi console=hvc0 earlyprintk=xen"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
disk = [ "phy:/dev/vg_f12test/f12test,xvda,w" ]
vif = [ "mac=00:16:36:36:25:bf,bridge=virbr0,script=vif-bridge" ]
Xen-devel mailing list