Building SLES 15 using SuSE Manager 3.2/AutoYaST for BOTH PowerPC & x86_64
Environment:
I'm attempting to create a build infrastructure for both PPC LPARs and x86 VMs using a single SUMA.
By following the SuSE Documentation for Deploying SLES on Power, I am able to build SLES 15 on Power9/PowerVM LPARs.
My problem now is getting the same infrastructure to also build SLES 15 on x86_64/vSphere VMs.
I am able to build SLES 15 on the VMs using the ISOs - so there is nothing intrinsically wrong with the VMware environment. I also was able to produce an AutoYaST profile from an install.
The DHCP server on SUMA correctly identifies the VMs and assigns an IP address from the proper range, and also properly directs the VM to load the grub.efi file. Watching via WireShark, I see the VM successfully transfer the file using TFTP.
And then nothing happens.....
If I boot the VM into the boot selection screen and manually initiate the PXE boot via a network interface, it gets the file and cycles back to the boot selection screen. Lather, rinse, repeat. I never get a GRUB menu, the installer never starts, nothing.
Looking at the docs I linked above, there is some custom GRUB configuration and a special Cobbler Trigger. I'm beginning to wonder if what I want to do is technically feasible, or am I asking too much of Cobbler.
Has anyone else ever attempted to set up such a build infrastructure? If so, were you successful and how did you do it?
Does anyone have any insight into doing what I'm attempting using SUMA 3.2?
- IBM Power9/PowerVM LPARs
- Intel x86_64/vSphere 6.7 VMs (using EFI)
- SuSE Manager (SUMA) 3.2
- SLES 15
I'm attempting to create a build infrastructure for both PPC LPARs and x86 VMs using a single SUMA.
By following the SuSE Documentation for Deploying SLES on Power, I am able to build SLES 15 on Power9/PowerVM LPARs.
My problem now is getting the same infrastructure to also build SLES 15 on x86_64/vSphere VMs.
I am able to build SLES 15 on the VMs using the ISOs - so there is nothing intrinsically wrong with the VMware environment. I also was able to produce an AutoYaST profile from an install.
The DHCP server on SUMA correctly identifies the VMs and assigns an IP address from the proper range, and also properly directs the VM to load the grub.efi file. Watching via WireShark, I see the VM successfully transfer the file using TFTP.
And then nothing happens.....
If I boot the VM into the boot selection screen and manually initiate the PXE boot via a network interface, it gets the file and cycles back to the boot selection screen. Lather, rinse, repeat. I never get a GRUB menu, the installer never starts, nothing.
Looking at the docs I linked above, there is some custom GRUB configuration and a special Cobbler Trigger. I'm beginning to wonder if what I want to do is technically feasible, or am I asking too much of Cobbler.
Has anyone else ever attempted to set up such a build infrastructure? If so, were you successful and how did you do it?
Does anyone have any insight into doing what I'm attempting using SUMA 3.2?
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
ASKER