Hi,
If I recall most versions I have installed put a syms file in /boot
I know the deb packages don’t but I rarely use debs for xen, mainly because I can only upgrade when someone writes a new deb which is rare and upgrading from source over debs has always caused more problems than its worth.
If the syms file can be deleted then that’s fine but what is its purpose?
Thanks
Ian
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Viau
Sent: 01 April 2011 21:18
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Grub2 xen priority order
> On Fri, 1 Apr 2011 20:30:32 +0100 <itobin@xxxxxxxxxxxxx> wrote:
>
> The issue is when compiling from source it creates another file in /boot called xen-syms-4.1.0
Are you talking about 4.1.0 or 4.0.x?
>
> When running update-grub its puts the xen-syms-4.0.1 higher in the list but its not correct, it should be /xen.gz or similar. When the server boots it fails therefore you have to manually select the correct boot entry, obviously not practical.
>
> You can either manually edit /boot/grub/grub.cfg which isn't the right way or edit the file that that the previous person mentioned, and this worked.
>
> Hope that makes sense.
>
> Ian
>
Hi there,
I am just tuning into this thread now, and I do recall that the Xen Hypervisor symbols file was being picked up as a Xen Hypervisor and added as a grub boot loader item. Has anyone tried to write a patch to fix this? If someone was so inclined to submit such a patch to the Debian BTS, that would be awesome :)
I know the Debian Xen packages (at least the 4.0.1 stuff) do not put this xen-syms file and if you delete it, from my experience everything still works. If you are not as daring to delete it, you may also place this file in another folder such as /boot/xen/ and the non-working grub entry is no longer created as well.
-M
