Just added the parameter for 1.5.x too. Way easier to do it via the boot menu code than adding it within FOS using sysctl.
Will finally mark this solved! Thanks to everyone.
@Duncan Many thanks to you too!! Great work on the testing you’ve done here, awesome. I think this has given us a great set of recipes we can give people in case they run into that issue. We might even think about sending the kernel parameter
nvme_core.default_ps_max_latency_us=0 as default. @Tom-Elliott @Quazz @george1421 Do you see any issue with that?
nvme_core.default_ps_max_latency_us=0 - not a valid identifier
As George already said, this is not an issue but more a warning. I was hoping to find some time and fix that at some point. Will do so now.
@gusto I am not sure I can follow your questions.
According to this instructions we need to enable it
Options --> Feature --> Nestig - ON
Where did you read about “Nesting”? Can see anything about this in the linked wiki article. Did you follow the instructions mentioned in the wiki about Apparmor?
Do I need also to install NFS on a host (proxmox)?
I have done a LXC installations a couple of years ago but can’t remember this part anymore. If it’s not in the wiki I don’t think it’s needed.
That means I have to change pxelinux.0 to undionly.kpxe?
undionly.kpxe for legacy BIOS machines and
ipxe.efi for UEFI machines. Also see https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence and my post here: https://forums.fogproject.org/post/130612
I have tentatively installed NFS in LXC (centos 7). Then I wanted to destroy the LXC, but I couldn’t destroy the LXC because filesystem in use.
Not sure how to solve this. Not great but rebooting the whole server should definitely fix it.