Search results

  1. R

    Backup to PBS of running OPNSense VM causes issues

    I think I found something - every Sunday @ 3am (when the backup job starts) I get a series of processes being killed and failure to reclaim memory - bit this is OPNSense running on BSD under the hood - not sure if this is relevant. All i can say is, this backup worked for many months prior -...
  2. R

    OPNsense VM - PBS Backup - issue with "snapshot" mode?

    sorry, my Bad - wasn't sure which was the best - and this thread seemed awfully quiet . . .
  3. R

    Backup to PBS of running OPNSense VM causes issues

    Just checked logs - no errors whatsoever related to IO - just "backup successful"
  4. R

    Backup to PBS of running OPNSense VM causes issues

    Thanks for the tip! ;) What exactly am I looking for in the logs to identify this suspicion ? Why would that affect the continuous operation of the VM when performing a "snapshot" - I thought the VM resumed very quickly and the backup happens independently ?? Up until recently, this wan't a...
  5. R

    OPNsense VM - PBS Backup - issue with "snapshot" mode?

    Yes. Funny enough, If i perform a local backup - it seems better (takes 10 minutes) , but over the network to the PBS - it takes 30 minutes to complete - not sure if that has something to do with it ??
  6. R

    OPNsense VM - PBS Backup - issue with "snapshot" mode?

    I'm running latest OPNsense version in a VM on a standalone host (N305 based) - and perform a backup once a week to a PBS server on another machine - Backup runs at 3 am on Sunday mornings - takes about 30 minutes using snapshot mode (60G disk image) - I get an e-mail report status backup was...
  7. R

    Backup to PBS of running OPNSense VM causes issues

    I'm running latest OPNsense version in a VM on a standalone host (N305 based) - and perform a backup once a week to a PBS server on another machine - Backup runs at 3 am on Sunday mornings - takes about 30 minutes using snapshot mode (60G disk image) - I get an e-mail report status backup was...
  8. R

    Networking Question - eth0: entered promiscuous mode || eth0: left promiscuous mode loop in dmesg

    Looks like I found tthe culprit in another post: https://forum.proxmox.com/threads/e...spammed-by-eth0-left-promiscuous-mode.153412/ Odd behavior indeed ;-)
  9. R

    Network device promiscuous mode

    Looks like I found the culprit in another post: https://forum.proxmox.com/threads/eth0-doesnt-exist-yet-console-is-spammed-by-eth0-left-promiscuous-mode.153412/ Odd behavior indeed ;-)
  10. R

    eth0 doesn't exist, yet console is spammed by "eth0: left promiscuous mode"

    Sorry to hijack this thread - I have a similar issue occurring on latest version 8.4.1 - coincidentally, I also have an LXXC running watchyourlan - so that looks like the culprit: Apr 27 12:18:36 FoxN100 kernel: eth0: entered promiscuous mode Apr 27 12:18:38 FoxN100 kernel: eth0: left...
  11. R

    Networking Question - eth0: entered promiscuous mode || eth0: left promiscuous mode loop in dmesg

    Sorry to hijack this thread - I have a similar issue occurring on latest version 8.4.1: Apr 27 12:18:36 FoxN100 kernel: eth0: entered promiscuous mode Apr 27 12:18:38 FoxN100 kernel: eth0: left promiscuous mode Apr 27 12:18:38 FoxN100 kernel: eth1: entered promiscuous mode Apr 27 12:18:40...
  12. R

    Network device promiscuous mode

    Sorry to hijack this thread - I have a similar issue occurring on latest version 8.4.1: Apr 27 12:18:36 FoxN100 kernel: eth0: entered promiscuous mode Apr 27 12:18:38 FoxN100 kernel: eth0: left promiscuous mode Apr 27 12:18:38 FoxN100 kernel: eth1: entered promiscuous mode Apr 27 12:18:40...
  13. R

    Opt-in Linux 6.14 Kernel for Proxmox VE 8 available on test & no-subscription

    After diving in head first with 6.14 - I somehow borked my cluster. going back to 6.11 got eveything back to "normal" - I have 5 different mini PCs running in the cluster - all over 10GB or LACP'd 2.5GB NW (aka 5GB) - I have no hight traffic and I broke the cardinal sin of having the corosync...
  14. R

    QEMU 9.2 available on pvetest and pve-no-subscription as of now

    Stupid question #354 - running latest PVE 8.3.4 - enabled pvetest and wanted to try qemu 9.2 - after update I see pve-qemu-kvm: 9.2.0-2 in pveversion -v but qemu-server version says: qemu-server: 8.3.8 :oops: Is that right ??
  15. R

    PCI Pass-through: iommu & vfio on 8.2

    Kind of confusing - because there are still many references around (like here: Thomas-Krenn) which leads you to believe it's still relevant. I have several machines in my cluster which have been upgraded over time and still have those entries in /etc/modules - Guess it doesn't hurt . . . :rolleyes:
  16. R

    PCI Pass-through: iommu & vfio on 8.2

    I noticed that iommu is enable by default and no longer requires the "intel_iommu=on" boot parameter - are the vfio modules still required? In the past we always had to add: vfio vfio_iommu_type1 vfio_pci vfio_virqfd to /etc/modules file ??
  17. R

    Vor- und Nachteile: VLAN in proxmox oder in opnsense anlegen?

    Was für ein Prozessor? Ich hab ein R86s gerät mit N5105 CPU (Amazon) - mit 16GB Ram - direkt von die OPNSense VM, Ich kriege 580MB beide Richtungen mit Speedtest-CLI - aber von VLANs und WLAN Ich kriege ungefähr 400MB im schnitt ?!?
  18. R

    Vor- und Nachteile: VLAN in proxmox oder in opnsense anlegen?

    Kurze Frage dazu - welche von die 3 Optionen sind am performanste ?!? Hat jemanden es getestet?? Ich bin zurzeit beim Option2 und kriege nicht die ganze dürchsatz von mein 600MB Glasfaserleitung . . . Danke vorweg!
  19. R

    Best practice - Migrate existing cluster NW to SDN ?

    Thanks Stefan! The documentation is a bit high level - but I've watched a few videos online and have the general understanding. I guess it would have been helpful for those of us who have legacy installations and want to "migrate" or convert to the SDN features - and know what is best...
  20. R

    Best practice - Migrate existing cluster NW to SDN ?

    I thought as much - Appreciate the offer, but my config is a bit convoluted! Maybe you can just give general pointers as best practice reference . . . ?!? Cheers, Robert