Search results

Hey, Though it seemed related to the update timers the system was found 'hung' this morning, it failed at 3:10 which is more or less the same time as before. The machine simply stops responding to anything. Keyboard numlock led responds, no console shows anymore, network traffic stops, does...

Running the latest PBS as a stand-alone I've ran into an issue then machine becomes unavailable. Both console and network no longer respond. Sometimes console seems sluggish to respond, then stops. My observation and impression is this is after proxmox-backup-daily-update ran. To that end I...

in case this is still relevant if all you're going to do is run an OPNSENSE FW on that proxmox node the N100 could do for that kind of traffic, if you think minimal IDS/IPS consider OPNSense can run suricata which has considerable performance available, you can tune the ruleset for this CPU...

no need for such an elaborate apology, I'm in year 32 of IT, I've seen way to many forums, communities and newsgroups. I expect/hope stuff would finally just work most of the time. And I'm known to be grumpy. a helpful attitude is obviously admirable also consider the promox webui is just a...

that command was actually a recommended approach by a Proxmox team support member. Due to me growing old and being quite tired I had also rebooted the server instead of restarting it. Multi-tasking only works well when you're young I guess. Time to not do that again. If anything, it shows your...

same as before, don't understand what happened using CLI is my preferred way of working since mosten often this tells me exactly what happened this time however, Proxmox just 'flipped' as I did something incredibly stupid after 'rm -Rf /etc/pve + reboot (not restart)' I'm not sure what made...

If you want to run application containers, for example, Docker images, it is recommended that you run them inside a Proxmox QEMU VM. This will give you all the advantages of application containerization, while also providing the benefits that VMs offer, such as strong isolation from the host and...

running a very simple set-up with Proxmox on ZFS I'm looking to have snapshot of everything in /etc and other select directories. Essentially / without rpool and subsequent volumes. Since df -h shows mountpoint to be /root/RPOOL/pve-1 / i tried: zfs snapshot -r rpool/ROOT/pve-1@may2024...

I don't understand what you're asking # pveupdate # pveupgrade

After a mere pveupdate+pveupgrade the standalone Proxmox VE is now broken (again) Things that broke are : a kernel module .conf file (fix= `rm /etc/modprobe.d/e1000e.conf`) the GPU udev rules suddenly contained GROUP== instead of GROUP= (fix: remove = from ==) not 100% sure but the monitor...

thanks, did work for some time but the issue is back and resurfaces after multiple repeats of this sequence

unless you did something not documented here and something I've not tried yet, the issue will resurface my system is a single-node Proxmox set-up, which I think is part of the issue resurfacing

no solutions presented in this thread work and keep working this seems to be an issue which is not addressed as it only seems to happen on non-cluster proxmox ?

@mfgamma not sure what you mean with that. In terms of attack surface OPNsense inside or outside of Proxmox is not so much different. To make the picture more complete. Know it is possible yet of low likelihood a vulnerability will exist in both Linux and BSD. Of the top of my head I only...

i wasted a lot of time on pci-passthrough with AMD GPU eventually I ... started using a reset script for the PCI which is required with some GPU This is more or less what is required, in case you want to attempt 2 GPU in your machine erased all configuration added to the boot loader (mostly...

Depends entirely in how far you'd trust pfsense/opnsense. This week I finally had time to dive into the OPNSense Suricate service crashing issue. This issue is poorly documented or I missed out on where it is documented. Now I do have a bit more trust in OPNSense. Obviously chances an freemium...

there are actually limitations to virtio queue size (max = 1024), you can actually find that with a few minutes on a search engine https://doc.dpdk.org/guides-23.03/nics/virtio.html

you seem to conflate network interfaces which are virtual and network interfaces which are virtual -device 'virtio-net-pci,mac=XXX,netdev=net0,bus=pci.0,addr=0x12,id=net0,vectors=10,mq=on,packed=on,rx_queue_size=1024,tx_queue_size=256' setting this manually in 105.conf is probably mandatory

silly checklist * does the Protectli VP4650 have virtualisation enabled and/or hyperthreading ? * is the Qemu-guest-agent installed in opnsense ? * are you bonding network interfaces ? * how many cores did you assign to the opnsense vm ? * how much memory did you assign to the opnsense vm ?

wild guess, this depends on the VM network interface not being the physical network interface for proxmox ?