Recent content by keeka

  1. K

    NFS server side copy stopped working

    @lubosr Many thanks for the analysis. Good in the sense it is not an LXC specific issue!
  2. K

    NFS server side copy stopped working

    @lubosr Thanks. I'm currently running kernel 7.0.14-20-pve. I will stick with NFS4.1 and I also disabled NFS4.2 on the lxc based server for the time being. Re your bug report. I wondered if this issue only surfaces with that kernel and LXC or if it manifests with same/similar kernel running...
  3. K

    NFS server side copy stopped working

    I have successfully been using a privileged lxc to export NFS shares for quite a while. Each share exports a separate ZFS dastaset. Mounting those shares on a Debian 13 desktop system, all file operations worked apparently flawlessly. My client fstab specified NFS vers=4 but I believe v4.2 was...
  4. K

    Backup of live pfSense VM to NAS fails

    An uneducated guess, and one that assumes the 'vma_writer_close: close failed - Host is down' is not what's implied! But, could your live guest backup be failing because you do not have qemu agent installed (VMs) or enabled (PVE guest config)? Since they successfully backup when off/shutdown...
  5. K

    Machine type subject to deletion...

    I haven't come across this kvm warning with PVE as yet (upgrade path PVE7->8->9). But I have encountered it after upgrading a regular Debian 12 desktop to Debian 13. The machine was unsupported and qemu would not even start. The kvm guests affected by the deprecated machine types were ancient...
  6. K

    set vm ram in GB instead of MB in gui

    I have many CTs, Some running with less than 128MB RAM. Host has only 32GB RAM total. So quite like to specify guest memory in MB!
  7. K

    PVE 9 apparmor errors

    I switched to chrony at some point but I cannot remember if I was using systemd-timesyncd or full ntpd. Either way AIUI `apt install chrony` will warn about removal of a conflicting package. My preference would be for switching time daemon rather than editing apparmor's package files. You could...
  8. K

    PVE 9 apparmor errors

    IIRC older PVE installs may have had the full debian ntp package. Newer installations and guides recommend chrony.
  9. K

    is it possible to reject or quarantine spam based on conditions I set ?

    If you want the ability to reject mail based on spam score, I believe you must enable 'before queue filtering'. As far as custom rules, there are quite a few examples on here. You define those in /etc/mail/spamassassin/custom.cf. You can also define matches on headers directly in the web GUI and...
  10. K

    Migrating from read-only file system

    Mount tmpfs on /var/log/pve/tasks? You may also need to specify an alternate, writetable `--tmpdir`.
  11. K

    ifupdown2 fun after upgrade

    I have been burnt by this in the past when purging configuration from uninstalled packages (with ifupdown and grub-pc). I assumed common files were factored out in to some shared dependency but IIRC some configuration came from postinst scripts.
  12. K

    Is it possible to keep one VM running while updating Proxmox VE from 8 to 9?

    I am in a similar situation. I have a spare router but I've not needed it. Having no PVE storage on the system disk makes for a simple image of the entire system disk (<5GB) for peace of mind. Then apt update && apt dist-upgrade Modify apt sources apt update && apt dist-upgrade --download-only...
  13. K

    203.30.8.0/21 is listed on the Policy Block List (PBL)

    In these instances, where some MTA declines to relay a sender's message because the recipient domain fails some PBL/RBL query, I wonder if that MTA: sends an SMTP reject/fail response during the initial transaction. sends a failed delivery notification to the sender some point after accepting...
  14. K

    203.30.8.0/21 is listed on the Policy Block List (PBL)

    How many do that I wonder? To refuse to deliver an email because the receiving domain's MX is on a PBL (or other BL for that matter) doesn't seem inline with intended use of blocklists.
  15. K

    Mountpoints for LXC containers broken after update

    It's not clear to me from reading this thread or the linked bugzilla page if this is a bug or an anticipated consequence of recent kernel/security code. Assuming it is the latter, and is here to stay, will unprivileged containers no longer support RO mountpoints?