WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [PATCH] [Xen-users] Problems with pygrub: ValueError:unabletoopen fi

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

At the time of my first reply, I didn't see that you replied to your own post. So here is a more appropriate answer.

Your first issue is that you are not able to load a domU kernel that is located in dom0, right? In that case make sure that the file is really there (ls -l /boot/vmlinuz-2.6.16-1.2080_FC5xenU) and is accessible by xend. SELinux might block access to /boot from Xen. You should try to disable SELinux to check if that is true. If you do not want to disable SELinux, you might also cp vmlinuz and the corresponding initrd (.img) to a place that is accessible for xend (e.g. on FC5 this should be /var/lib/xen for instance).

The second issue is that pygrub does not work. Since FC5 has recent e2fsprogs, your issue should be different than the one my patch addressed. The message "ValueError: unable to open file" could have several reasons:

- kernel and initrd were not properly installed in the *guest* filesystem
- no valid grub configuration /boot/grub/grub.conf exists in the guest filesystem - the filesystem image file was no created properly and pygrub fails to open the filesystem (with my patch applied, this would read "unable to open filesystem")

I hope that helps.

Best Regards,
Michael Paesold


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>