Search results

See: https://github.com/Aterfax/pbs-client-docker?tab=readme-ov-file#error-function-not-implemented-os-error-38

I would not advise having the service wait for network.target rather thanpve-cluster.service. You need to wait for the cluster file system to start for the sync file to be present. Using network.target won't necessarily achieve this. If you're planning on updating the hosts file often and need...

I'd still personally go with Puppet-however... Just make a systemd service one-shot that copies /etc/pve/priv/hosts after the cluster filesystem starts? If you wanted you can then also set a systemd timer to call it every now and then. The following is completely untested and I have not...

I would typically approach this using Puppet to do the config management on the hosts. e.g. https://forge.puppet.com/modules/puppetlabs/host_core/readme I appreciate most may not be running a Puppet / foreman solution though.

Having a look at this now with makedeb since I am after the client binary for an aarch64 host. Getting issues with it failing to find OpenSSL development headers :/ pkgbuildand libssl-dev already available. --- stderr thread 'main' panicked at...

For those after an automated docker (Cronjob'd) I chucked something together here which should be relatively straightforward to use. https://github.com/Aterfax/pbs-client-docker

Had a quick read of that earlier today, sounds like they silenced the repeated warnings rather than fixing a bug per se. Seems unclear if this is a red herring error warning or indicative of any real issues (probably worth you doing some iperf3 tests to see if you have any poor performance.)...

Had that happen sometimes and it be cleared by a reseat / wipe down of the PCIe pins with isopropyl alcohol. Give that a try and see if it clears up.

Have been using Linux 6.2.11-1-pve-relaxablermrr without issue since 8.0 came out. https://github.com/Aterfax/relax-intel-rmrr/releases Looking at testing and releasing the most recent autobuild today.

Have a look at: https://github.com/Aterfax/relax-intel-rmrr/discussions/38 There's no need to stop or pause the VMs while installing the debs (changes can only take effect after a reboot into the new kernel) and the installation of the debs should automatically run update-initramfs. I've never...

You could use the most recent signed and tested version which would indeed be a downgrade from your current version but should function fine (although you may need to pin the kernel version to be booted (https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_kernel_pin). Alternatively you can use...

Also had this issue on Proxmox 7.2 . The mentioned earlier first mentioned script also fixes up getting the SMART data for a P420i on DL380p Gen 8.

This issue still appears to be present (I just 'enjoyed' fixing this.) root@proxmox:~# pveversion pve-manager/7.2-7/d0dd0e85 (running kernel: 5.15.39-3-pve) root@proxmox:~# grub-install --version grub-install.real (GRUB) 2.04-20

Unfortunately, not a scooby doo.

I've now finished tooling about with the README files to match the current setup.

I resolved the weirdness with the Docker build process, I forgot to copy the patches into the docker image! :rolleyes: As to broken builds: One possibility if people are not cloning the repo itself byte for byte and are copying and pasting certain files, they will almost certainly break the...

The build "system" is done so any releases will be appearing here in future: https://github.com/Aterfax/relax-intel-rmrr/releases I still need to untease what is breaking the patching in the Docker method but the current release was built on my Proxmox node and is working fine...

Ah well, I've kicked off a recompile which will take a bit but as I said I am running 5.15.35-1-pve-relaxablermrr and pass through is definitely working as I am passing a quadro card through to a VM! Let me know if you want me to upload the finished debs!

Hmm, that is odd since if you forked my repo it should have built the most recent kernel (the pve-kernel master branch) if you used build7.1-12.sh. I'd give it ago using that version first if you haven't. (Did you use build7.sh?) I should probably rename build7.1-12.sh to build_latest.sh...

Hmm, I did write this at 4 or 5 in the morning so there is a distinct chance I have made a mistake somewhere, but I did uninstall recompile and re-install as part of my testing and my current booted kernel is doing passthrough ok. Have a look and see if you've got the right kernel booted by...