|
|
|
|
|
|
|
|
|
|
xen-users
Re: [PATCH] [Xen-users] Problems with pygrub: ValueError:unableto open f
Henning Sprang wrote:
Michael Paesold wrote:
Sorry for the last empty mail (hit the wrong button). Attached is a
patch against xen-unstable to improve the error messages in pygrub
when the e2fsprogs do not support the newer ext2fs_open2 function.
This should help beginners to identify the real problem when pygrub
does not work (e.g. on RHEL4).
I also have that problem on fedora core 5. As far as I can see, your
fix is only about the error message. But how can the actual problem be
solved?
I'd really like to use a simple xen config as given in xmexample1, and
use the images from xen-get.org.
My post to fedora-xen can be found at:
https://www.redhat.com/archives/fedora-xen/2006-April/msg00085.html
Henning,
I also haven't managed to boot a domU different from FC5 on my FC5 dom0.
But I have different problems. Maybe there are some points of interest
for you in this anyway...
You report that when trying to boot xend complains about not finding the
kernel image file.
I disabled selinux in domU and dom0 and then that went away...
I also have no trouble at all working the normal way of booting with a
kernel in dom0 and not using pygrub (which you obviously need if you
want to domU to boot a kernel which is placed in domU itself).
My domUs (debian 3.1, fedora 4 - all happily managing to run on
different dom0) boot up to different points. Usually they get stuck
around mounting the ext3 filesystem... So I'm still working on that...
So I'd be happy if we could mutually keep track of our efforts and
hopefully successes!
Bye,
Andrej
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|