I`am struggling now the second day by trying to install incusOS from the iso image on Hardware without TPM and on VM with or without vTPM
I tried nearly all settings on the image download page and tried to follow this documentation:
Hardware issue:
first boot => Secureboot keys are installed
second boot from iso: server hangs without any useful error message:
I tried really all settings during the iso image configuration: Withouth TPM including Secure Boot, without everything, with wipe disk and without wipe disk. RH2288 V3 and RH2488V5 (Both without TPM Module)
Then I switched to VMware to create a VM with TPM Module and without.
Same game but different. VMware doesn`t recognis the iso image as a boot device:
âCD Rom not foundâ
I`am working now over 20 years with several hypervisors and Linux OS but never came to a point where I had to open a topic in a community forum to be able to install an operating system
I really want to use this but when I need to spend days to get it installed, how long would it take to get it stable for a production environment to replace some fully automated VMware clusters?
Answers to possible questions:
yes, I followed the instructions, yes the VM has TPM 2.0 and Secureboot and advanced settings enabled and I uploaded the .der files
both hardware servers have a raid configured but âwipe diskâ was enabled during image creation
no I cannot use the flash tool because we are air gapped and its a pain to build this within an air gapped environment
On the hardware side, you managed to get through the installation fine, but then got stuck there on first boot? If so, that suggests something funky going on with systemd-repart as thatâs whatâs likely to be running at that point of the boot process. Could be something weird going on with the storage maybe? Another option would normally be a TPM issue but since youâre using the software TPM that shouldnât really be possible.
On the VMware side, that error is very weird and isnât something Iâve personally ever run into with the many VMware deployments weâve done lately. Iâd probably start by triple checking that ISO looks correct (should be 3.2GB large and be the ISO not the USB image), obviously need to make sure that the ISO is attached to the VMware drive and that the drive is connected to the VM. Iâm sure you already checked but itâs very easy to miss the âConnect at bootâ checkbox
Anyway, if the ISO looks good, maybe share the VMware config here so I or one of the folks who are doing a lot of IncusOS on VMware deployments (@stephendotcarter, @cylebas) may help.
Hi Stephane,
thanks for your reply. I downloaded nearly 10 different images (always iso for installation purposes). I tried within our company via proxy and also private without any proxy and ssl injection.
I uploaded the iso image to the datastores and also tried to mount them via client devices (vmware console). This behavior is really strange and blieve me, when I say, I work with VMware daily since Version 3.5 I will check tomorrow further.
Probably also triple check that the VM is configured to use UEFI and not regular BIOS as youâd be getting that error on regular BIOS I think (ISO is GPT formatted).
I have seen this behavior âCD-ROM not foundâ when the Secure Boot keys were either not placed in the VMâs folder alongside the .vmx file or not properly defined (exact name) in the Advanced Parameters before the VM was powered on for the first time.
Moving or modifying the Secure Boot keys in the VMâs folder, editing the Advanced Parameters, or recreating the virtual disk after the initial power-on will not help.
You may need to create a new VM, do not power it on after creation, and ensure that all required steps like adding the TPM module, placing the Secure Boot keys in the VM folder, configuring the Advanced Parameters, and enabling Secure Boot are completed before the first power-on.
thanks for testing. I put the files to the folder where the vmx file is located but I will try and double check / recreate everything again- just to be sure.
Status HW Installation: unchanged. I have no starting point of debugging and it takes a lot of time to boot the HW several times to mount the remote iso image. I guess its an issue with the internal usb devices of the Huawei hardware for the OS FS but Its hard to know without any logs or debug output.
I have no empty newer hardware with TPM available at the moment but it would be nice to get it running for performance testing and alua settings and all this stuff.
Right, you mentioned the system is completely offline. Installing in that kind of environment is slightly more involved.
IncusOS itself doesnât actually include Incus or any âprimaryâ application out of the box.
That gets downloaded on first boot which is failing in your case as youâre in an offline environment.
In offline environments you need to use a secondary drive that includes the full update from the image server so it can install from there. We actually have some built-in logic in the image customizer but itâs not currently exposed in the web UI. Iâll see if I can easily surface that so you can grab the second ISO and get that machine fully installed (youâll need to attach the second ISO and then reboot to have it picked up).
For your physical server. If at all possible, try to have someone plug a USB stick with the image to eliminate any virtual media weirdness. Weâve generally seen virtual media work very well with IncusOS, even in rather extreme environments (100kB/s and 300ms latency type thing) but all implementations are different and weâve never dealt with Huawei.
