Search results

Logs (/var/log) or default local pve storage (/var/lib/vz) might also be the culprit. Check directories under /var du -shx /var/*

Configure postfix, on the PVE host, to send mail via your SMTP server. `dpkg-reconfigure postfix`.

Thanks for posting this. I've used your hookscript and seems a simple solution to mirroring traffic with traditional bridges. One typo, I think, in sub RemoveMirror promiscuous mode should be turned off: system("ip", "link", "set", "$target", "promisc", "off");

I have not removed apparmor but I have noticed it is not started in PVE debian containers: Bullesye ~# journalctl -b | grep apparmor Aug 10 22:31:22 ct1 apparmor.systemd[62]: Not starting AppArmor in container Bookworm ~# journalctl -b | grep apparmor Aug 10 23:40:03 ct2 systemd[1]...

After an apt dist-upgrade and host reboot yesterday evening, my CT docker guests' disk graphs have sprung to life and are reporting IO again. The upgraded packages: libpve-common-perl:all 8.2.2 qemu-server:amd64 8.2.4 pve-docs:all 8.2.3 proxmox-kernel-6.8.12-1-pve-signed:amd64 6.8.12-1...

Have you ever, in the past, managed to successfully restore a clonezilla disk image that contained lvm-thin volumes? I've shyed away from it due to seeing similar logs from clonezilla regarding volumes on LVM-thin VGs. Consequently I only use clonezilla to backup the PVE system disk, which in...

Bear in mind /run/ is on tmpfs, and /run/sshd created when sshd initiated on demand via systemd in debian lxc. I once had issues with sshd in the debian container.

Just a follow up. I checked the pfsense guest. camcontrol output is similar to that of the opnsense guest. However, trim is enabled for rootfs. I must have manually enabled it on the pfsense guest post-install too, but before applying a major upgrade. My memory fails me on that one. Next time...

Thanks. Next time I will try the guest 'ssd emulation' option and see if the opn installer recognises it as such. The camcontrol output in post #1 is apparently why trim was not enabled. But I'd have expected it to display something more informative - the above appears to be a failure of some...

OK, it does seem that trim is working in as far as: I create a large file in the guest, I see the lvm-thin volume on the host grow and then shrink back when I delete the file in the guest. However, I don't seem to be able to reclaim the jump in storage needs following the opnsense guest upgrade...

Storage is lvm-thin. The opnsense guest config is similar in most respects to the pfsense guest I mentioned in my reply to @sw-omit. # qm config 101 affinity: 0,4 agent: 1 balloon: 0 boot: order=scsi0 cores: 2 cpu: host hotplug: 0 memory: 2048 name: opn net0...

I was considering something similar but would like to get to the bottom of it because I don't see these issues with a pfsense vm with identical config. That vm has been through several upgrades and the disk use (lvm-thin backed disk and PVE backups) has remained the same size (1.2GB) for several...

I created an opnsense 24.1 guest. Backed up, this vm uses 1.2GB. I upgraded the guest to opnsense 24.7. The backup now occupies 2.84GB. I'd enabled the discard option on the vm. But it seems the opnsense installer, unable to determione the disk type, did not enable trim: ~ # camcontrol identify...

IME messages that exceed the postfix maximum message size are rejected and logged but the events do not appear in the Tracking Center. I think it would be helpful if they did.

Those grub-pc and grub-efi-amd64 preinst, postinst, prerm, postrm scripts look pretty complex. I will put any OCD tidying up to one side on this occassion!

That could be it! Thanks for the help. I mean to look at the grub packages' pre/post install/remove scripts to see what they do in respect of running grub-install and update-grub. I'm old enough to remember LILO and once had a stab at installing linux (unsuccessfully) on an hp ux machine...

Thanks for that. The host was originally installed with PVE6. I don't recall the exact history, but I remember installing grub-efi-amd64 following the upgrade to PVE7. That process removed grub-pc. IIRC if I then purged grub-pc and reran update-grub, I ended up with a non bootable system. I'm...

The PVE host is setup for EFI only booting and I am using grub, not systemd boot. Some time ago, I switched form `grub-pc` to `grub-efi-amd64`. As you can see, grub-pc was installed, then removed and its configuration remains. So I was wondering: Do I still need `grub-pc-bin`? Can I purge...

Since I am booting via EFI, do I still need to retain grub-pc-bin package? # dpkg --list | grep grub ii grub-common 2.06-13+pmx2 amd64 GRand Unified Bootloader (common files) ii grub-efi-amd64 2.06-13+pmx2...

There doesn't seem to be anything amiss there. As you're aiming to 'pass through' to an LXC, any IOMMU config is not needed at this point. I have a much older intel cpu/igpu (vaapi). I can pass the dri device node through to multiple unprivileged lxc and they then successfully use the renderer...