Kiefer Chang

@hernad Do you still need the feature and could you submit a PR? As Sheng mentioned, [switching to another TTY](https://docs.harvesterhci.io/v1.1/troubleshooting/installation#logging-into-the-harvester-installer-a-live-os) does the trick too. > Additional commit to fix yaml:...

Close the issue since we publish the image: https://hub.docker.com/r/rancher/harvester-cluster-repo/tags

@Oats87 We'll try to create one and get back to you. Thanks!

We can confirm the issue doesn't happen recently after bumping to Rancher 2.7.5-rc releases; thanks!

@w13915984028 can you check which issues we want to fix in 1.4.0?

The display area might be too small. Does the console resolution look normal? These steps might help: - Add `nomodeset` kernel parameter: https://docs.harvesterhci.io/v1.0/install/usb-install/#graphics-issue - Manually specify the VGA mode in...

@db-at-work Please see if https://github.com/harvester/harvester/issues/2708#issuecomment-1244965316 help. The serial console default dimension is too slow.

For the PXE path, how about just letting the installer fail with a reason but allowing the use of a flag to bypass the check? For the interactive path, I'd...

Add `require/release-note` label. We need to mention this might stop automatic installation in some low-spec hardware and the user needs to specify the `harvester.install.skipchecks=true` parameter.

@tserong we also ~~need a section in https://docs.harvesterhci.io/v1.3/install/harvester-configuration to explain the new field~~ and update the examples in https://docs.harvesterhci.io/v1.3/install/pxe-boot-install **update** section in the document is not needed since it's only...