Yesterday after agreeing to download some updates, I could not find the Virtual Machine Manager for the 3 XEN VMs (vm1-oes[novell oes]; vm2-gw[groupwise]; vm3-gms[groupwise mobility service]) that I have on my server. (In fact, I was no longer sure if I was looking at the host, or if I was looking at one of the VMs. I tried to do a reboot of the server, and at reboot I had the option to select XEN (then the default), but the boot failed to complete (progress bar at about 95%). I left it at that yesterday. Today I have done an automatic repair but the XEN boot option has disappeared, though I believe the various VM folders and files are still present.

The automatic repair option seemed to work (including repair of Ext3 file system); the next stage said that Initrd modules (jbd; mbcache; ext3) were missing from /etc/sysconfig/kernel so I selected repair to add the missing modules to the initial RAM disk. "Calling mkinitrd failed', and I took a photo of the resulting log file, which is a bit much to type out here.
Then the repair process said 'Boot loader error detected' and again I chose the automatic repair option.

In an earlier post with a similar issue, I see that the poster was asked to run some zypper commands, which I have done and am able to copy here:

Directory: /root/Desktop
Sun Apr 8 14:13:23 ACST 2018
noddy:~/Desktop # zypper pd
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...
S | Repository | Internal Name | Name | Version | Arch | Is Base
--+------------+---------------+-------------------------------------+------------+--------+--------
i | @System | SUSE_SLES | SUSE Linux Enterprise Server 11 SP4 | 11.4-1.109 | x86_64 | Yes
noddy:~/Desktop # zypper lr -d
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
--+--------------------------------------------------+--------------------------------------------------+---------+---------+----------+----------+------------------------------------------------------------------------------------------------------+--------------
1 | PK_TMP_DIR | PK_TMP_DIR | Yes | Yes | 99 | plaindir | dir:///var/tmp/TmpDir.AA9maF |
2 | SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109 | SUSE-Linux-Enterprise-Server-11-SP4 11.4.4-1.109 | Yes | No | 99 | yast2 | cd:///?devices=/dev/sr0 |
3 | nu_novell_com:SLE11-Public-Cloud-Module | SLE11-Public-Cloud-Module | No | Yes | 99 | NONE | https://nu.novell.com/repo/$RCE/SLE11-Public-Cloud-Module/sle-11-x86_64?credentials=NCCcredentials | nu_novell_com
4 | nu_novell_com:SLE11-SP4-Debuginfo-Pool | SLE11-SP4-Debuginfo-Pool | No | Yes | 99 | NONE | https://nu.novell.com/repo/$RCE/SLE11-SP4-Debuginfo-Pool/sle-11-x86_64?credentials=NCCcredentials | nu_novell_com
5 | nu_novell_com:SLE11-SP4-Debuginfo-Updates | SLE11-SP4-Debuginfo-Updates | No | Yes | 99 | NONE | https://nu.novell.com/repo/$RCE/SLE11-SP4-Debuginfo-Updates/sle-11-x86_64?credentials=NCCcredentials | nu_novell_com
6 | nu_novell_com:SLE11-Security-Module | SLE11-Security-Module | No | Yes | 99 | NONE | https://nu.novell.com/repo/$RCE/SLE11-Security-Module/sle-11-x86_64?credentials=NCCcredentials | nu_novell_com
7 | nu_novell_com:SLES11-Extras | SLES11-Extras | No | Yes | 99 | NONE | https://nu.novell.com/repo/$RCE/SLES11-Extras/sle-11-x86_64?credentials=NCCcredentials | nu_novell_com
8 | nu_novell_com:SLES11-SP4-Pool | SLES11-SP4-Pool | Yes | Yes | 99 | rpm-md | https://nu.novell.com/repo/$RCE/SLES11-SP4-Pool/sle-11-x86_64?credentials=NCCcredentials | nu_novell_com
9 | nu_novell_com:SLES11-SP4-Updates | SLES11-SP4-Updates | Yes | Yes | 99 | rpm-md | https://nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64?credentials=NCCcredentials | nu_novell_com
n

So, can I resuscitate this server by simply adding the XEN boot option back into the bootloader file? Would love some guidance, please.

Jerome