New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is photon-os-installer bits injection into a broken (Ph4 rev1) installation possible? #11
Comments
Hi @dcasota, Thanks for reporting this. You need not make your own binary for consuming 2.0 installer bits as the changes are merged in the photon 4.0 branch. In order to consume 2.0 bits, you need to follow these steps.
docs to build photon from source - https://vmware.github.io/photon/assets/files/html/3.0/photon_installation/build-photon.html In order to make your own custom installer binary, you can install the
build-options-file - https://github.com/vmware/photon/blob/4.0/common/data/build_install_options_all.json If you are building any other image than iso. You can follow the steps mentioned in the readme under the heading Building Photon Cloud images using Photon OS Installer. I will update the readme to add the required packages to install before building the binary. Let me know if you find any more issues. Thanks, |
fyi After 14 hours in progress and somewhere in step 3, I've changed my virtual hardware specs from 2vcpu to 4vcpu + 32gb ram, and restarted the process with |
It's already present. Try this- |
Hi @gpiyush-dev, the make image failed during kafka.spec. Here's the protocol snippet. Kind regards, Daniel |
It's a known issue that is intermittent in nature, seen from Gradle side. If you retrigger it again you might not see it. |
Thanks, the iso has been successfully created!
Eg. configure Photon to allow ssh access and download the iso. Hope this helps for your readme, too. Thanks for the journey so far! I'll share the findings about photon-os-installer 2.0 as soon as possible. The build process with multiple runs [hardware-limited first run, process limitation aware next run(s)] is somewhat slow, and the more branches the slower. Using more performant hardware and fully run the build virtual machine in memory may be an approach for optimization. Not sure if there is a different, affordable build process approach. Simply building all ~2'000 packages and the iso of a branch in an hour would be nice though. |
Yep, booting from photon.media=cdrom by default takes /dev/sr0 as the media to mount -
|
Indeed. First, the recipe on how to consume the photon-os-installer bits is much more better than the copy-based injection attempt. That said, many thanks for the support. -> close "issue". photon-os-installer is promising. On goal might be to allow choice for boot devices (usb, internal hd, cdrom), uefi/bios boot, for filesystems (fat32, exfat,) and driver support (usb 2.0), and for mount/unmount virtual media from same or different device. Photon OS should easily run on legacy hardware.
|
Hi @gpiyush-dev
For the use case that iso is not attached to cdrom, but Photon OS has started with default kernel cmdline photon.media=cdrom, here a suggestion. Instead of aligning it fixed to /dev/cdrom , doing a pre-detection of bootable, syslinux-marked partitions helps to install Photon OS on much more baremetal (legacy) hardware. The bash code snippet below lists detected, bootable, syslinux-marked medias. As output you get eg. /dev/sdb1.
In case of one or more detected medias with supported filesystems, ask the user to select his Photon OS boot and repo media. Hope this helps. Daniel |
Thanks, @dcasota for the suggestion. I will try to implement this. |
|
Hi,
I'm struggling with utilizing the 2.0 bits. On photon-4.0-ca7c9e933.iso the setup before the installer ui phase breaks on a tiny, physical x86_64 workstation with mbr boot. Nothing new (vmware/photon#1042), and the workaround of modifying the kernel commandline with photon.media=UUID= works flawlessly.
The photon-os-installer 2.0 approach seems somewhat interesting (the wording 'secondary ks device' nails it perfectly!), hence, I've build the photon-os-installer 2.0 bits accordingly to the recipe (btw. I had to install python3-devel, too) and copied ./dist/photon-os-installer into the /bin directory of the broken installation. I thought that simply a copy would be enough. Starting the executable, now it throws 'No module named curses'. I thought it makes sense to share with you this finding. A simple copy of photon-os-installer wasn't mentioned as eligible method though.
ps.1
On photon-4.0-ca7c9e933-aarch64.iso with UEFI boot the setup enters the installer ui phase without the described photon-os-installer 1.x issue.
ps.2
Running make image on photon-4.0-ca7c9e933 (Azure virtual machine)
throws out
Please, clarify the step "Building Photon Cloud images using Photon OS Installer".
The text was updated successfully, but these errors were encountered: