Search results for query: "hook script"

# proxmox-boot-tool kernel unpin Removed /etc/kernel/next-boot-pin. Removed /etc/kernel/proxmox-boot-pin. # proxmox-boot-tool refresh Running hook script 'proxmox-auto-removal'.. Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount...

I did an in-place upgrade from PVE8 to PVE9 but after the update the kernel and zfs are still showing old versions even though they both seem to have updated: # pveversion pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.8.12-18-pve) # uname -a Linux ghar80 6.8.12-18-pve #1 SMP...

It seems this script does exactly what I want to achieve. Thank you very much.

You could also use this ready-made hook script, or use it as a template. This logic is already integrated there. https://forum.proxmox.com/threads/proxmox-backup-server-pbs-automatisch-via-wol-starten-und-stoppen.127266/#post-620586

I installed an RTX 5060 in one of my Proxmox nodes and I am trying to install the driver on the host so that LXCs can use the GPU. It keeps failing due to a kernel error. I see that there are issues with the 6.17 kernel, since I am running VE 9.1 I reinstalled the latest 6.14 kernel, 6.14.11-5...

@Glowsome, thanks for the 'ansible-fix', we're using saltstack (slightly different architecture - client connects to server, not vice versa) that's why we currently workaround using the hook script. btw. i reported the bug and it seems to be fixed (at least code wise) - but i don't know when it...

ja die scripte liegen auf dem pve, ich lass den verify über das hook script laufen damit der erst danach runterfährt wenn er fertig ist bzw nutze ich das für meinen zweiten pbs der einmal die Woche die Backups vom Haupt PBS synct der ist dann immer aus sonst.

Und bei mir sind PBS und PVE getrennte Rechner, das Hook Script liegt auf dem PVE, korrekt?

nimm doch einfach ein hook-script da kannst Du sagen das er wenn das Backup zu Ende ist er den Rechner runterfahren soll #!/bin/bash #set -e; #set -x; # fstrim vor backup if [ "$1" == 'pre-start' ]; then /usr/sbin/qm guest exec "$3" -- fstrim -v /boot ; /usr/sbin/qm guest exec "$3" --...

On my end i have deployed my workaround via Ansible: - name: Place override for NetworkManager and resolv.conf ansible.builtin.copy: content: | [main] dns=none dest: /etc/NetworkManager/conf.d/00-dns.conf when: - ansible_virtualization_type == "lxc" -...

Hi, we face the same issue. and i can confirm the above mentioned workaround is working. (we currently apply it via a hook-script - i wonder if this just works by accident?) to me - the actual issue - looks like to be related to having multiple DNS servers configured. we see the following in...

hi all, i have same issue, i have installed package "grub-efi-amd64" than i make reboot after command: echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v -u comes update-initramfs -u -k all what is the problem here, why this error comes, package...

I kept cracking at it, I think I have a working solution As far as I can tell, everything works, but I did not test extensively /boot is now a small thick LVM volume pve-root is now a thin volume in the data (local-lvm) thin pool that uses about 3.8G The data thin pool has been grown to use...

Continuing attempt to make root mostly a thin volume root@proxmox:/# lvcreate -L 512M -n boot pve Logical volume "boot" created. WARNING: This metadata update is NOT backed up. root@proxmox:/# mkfs.ext4 /dev/pve/boot mke2fs 1.47.2 (1-Jan-2025) Discarding device blocks: done Creating...

ok log below: just for the protocol: I have 4 of these R730. All with the same hardware in it, all latest BIOS, latest Lifecycle/Drac, latest H330 Firmware, all in HBA Mode. 3 for Proxmox, 2 of them with this 600GB SAS 15k Dell drives. One with Proxmox Backup Server and 6 Seagate Barracuda...

I encountered a similar issue. I desired to execute a hook script that would reinitialize the AMD GPU after a virtual machine (VM) shutdown. The script functioned correctly when the VM was shut down via the web interface. However, if I initiated a VM shutdown from within the VM, the hook script...

I’m using https://github.com/gnif/vendor-reset/ to achieve perfect resets on my Vega64 and APU in my Ryzen 7 9700x. However, I’m hoping to create a hook script that will return a GPU to amdgpu after the VM is stopped, so I’ll give a similar script a shot.

if the node is supposed to (logically) stay in the original cluster, please be aware of the requirements regarding network stability and latency! other than that, yes, a hook script is the way to go for this at the moment. you might consider taking a look at Proxmox Datacenter Manager and SDN...

Deshalb mache ich mit dem PBS VM Backups aller VMs, aber z.B. SQL und Exchange sichere ich zusätzlich per Veeam Agent. Damit kann man dann zu den VM Restores über den PBS auch Application Restores ausgewählter Datenbanken machen. Die kleine 5 Instanzen Lizenz, kann man sich ja leisten.

Habe ich gemacht, WebUI bleibt nicht verfügbar. Fehler vom Anfang ist auch noch vorhanden root@prxmxserv:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following package was automatically installed...