Search results for query: "hook script"

Hi Everyone, Strange issue, not sure what's up exactly but hopefully someone can help. I rebooted after adding a new drive to my HBA (PCI passthrough), but got a red error when booting 6.8.12-10 in initird and got dumped to bios. May not be related to that because I've had some other strange...

I am following Proxmox documentation https://pve.proxmox.com/wiki/PCI_Passthrough https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_pci_passthrough and trying to passthrough onboard SATA controller to an OMV VM. IOMMU is enabled in the BIOS/UEFI, SATA controller is the only device in...

Has been tested some different approaches, but its hasn’t lead not any good. Added "options vfio-pci ids=10b5:9733" in vfio.conf, still got error when starting VM. Added "blacklist vfio-pci ids=5f:04.0" in blacklist.conf, then it disappears from the list. Added it manually "qm set 100 -hostpci0...

I don't know why I encountered same issue, but different case root@pve-home:~# apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not...

Hey all - I am preparing to upgrade my main server from 7.4 to 8 and I had prepared a systemd.link file like outlined in the admin guide here. It says that link files are added to initramfs and a refresh should be run using the command:update-initramfs -u -k all When doing that I got the...

iirc securetmp does what it does in making a bind mount which is what triggers this behaviour, at least if you are not using LVM for your storage. IMO trading a security feature for working backups is not a great choice to make, but it's certainly "easier" than compiling your own qemu-ga. Users...

Thanks, that works now. I had to change the mount point and rename of the subvol. This was a problem initially because I had to create the volume manually to create an encrypted fs and I am not familiar with all the conventions of Proxmox container storage management. It differs from...

Have a new pct created with the gui: arch: amd64 cores: 1 hostname: testct memory: 2048 nameserver: 192.168.1.1 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:C6:DA:75,link_down=1,type=veth ostype: debian rootfs: zfs16Tr10:subvol-112-disk-0,replicate=0,size=12G searchdomain...

This is an area that is very lacking in PVE, unfortunately. If not using HA, simply setting startup delay and some ordering will suit your use case. I mean, it's just 7 VMs, its doable. But once HA quicks in, currently there is no way to easily such order. Not even mention cluster wide...

Danke. Hab ich so gemacht: proxmox-boot-tool kernel pin 6.8.12-2-pve Setting '6.8.12-2-pve' as grub default entry and running update-grub. Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.8.12-9-pve Found initrd image: /boot/initrd.img-6.8.12-9-pve Found linux image...

Here is the log when apt upgrade failed on a fresh 8.3 install ``` Proxmox update upgrade error leaves proxmox in a state where the VM can't boot. ``` ``` root@msi:~# sudo apt update 107 packages can be upgraded. Run 'apt list --upgradable' to see them. root@msi:~# sudo apt upgrade -y...

Yes, but the proxmox-boot-tool doesn't exist on all installations (like mine).

Don't you need to run ```proxmox-boot-tool refresh```? From: https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_kernel_pin and run the command $ proxmox-boot-tool kernel pin 6.8.12-8-pve --next-boot Set kernel '6.8.12-8-pve' in /etc/kernel/next-boot-pin. Refresh the actual boot ESPs now...

Hi, I have a simple hookscript to make sure that required mount points for containers are mounted in the host at startup. Mounting is working as expected, but umounting in the post-stop phase does not work. The post-stop trigger is executed (I tested by creating a tmp file in the post-stop...

After some back and forth, I have manage to solve it. It is not really a Proxmox issue, but rather Linux specific. Just make sure that the LVM is discovered after the multipath, adjust the multipath setup, have the multipath package installed, loaded the multipath modules, and fix the race...

I was running updates this morning. Noticed the warning on the first host I was upgrading... I didn't follow APT's recommendation, however, I did do a update-grub before a reboot. System came back up without issue. As long as my system boots, I won't be running anything additional until this...

Hi all, I'm getting mad. please help me. # cat /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5...

Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync. Removable bootloader found at '/boot/efi/EFI/BOOT/BOOTX64.efi', but GRUB packages not set up to update it...

Reconfiguring the kernel will always end in: apt reinstall proxmox-kernel-6.8.12-9-pve proxmox-kernel-6.8.12-9-pve is not currently installed, so it will not be reinstalled proxmox-kernel-6.8.12-9-pve is not currently installed, so it will not be reinstalled The following partially installed...

Hi all, I'm not talking about pass-through on LXC or VM. I'm talking about the host. I have a little pc with n150 cpu and a Intel Alder Lake-N card. If I boot it as a ubuntu live distro, everything seems fine, but if I install a proxmox the card is not recognized as it should :-( I install...