Search results

Sounds good. So..., what is your problem? Please report a) what you wanted to achieve, b) exactly what you did, c) what you expected to happen and d) what happened instead. If possible do everything on the command line and place full quotes (including the full command and the full error...

Your "+1" is probably better placed over there: https://bugzilla.proxmox.com/show_bug.cgi?id=6144, already mentioned in #47. You'll also find a patch already mentioned in the last comment.

That's what backups are for ;-) Snapshots do not count for that. Be it LVM or ZFS or QCOW or xyz... ---- Edit, not mentioned yet: when I do delete a VM I want to be sure that all data is actually gone! If there are rudiments left over then the mechanism is defect!

Ja, genau. Ich nehme einen meiner externen Emailprovider und lasse alle Email dort relayen. Anleitungen dazu gibt es zuhauf, eine konkrete kann ich - ohne selber zu suchen - aber nicht nennen. Postfix ist ein ausgewachsenes Mailsystem...

That's interesting as PVE uses an Ubuntu Kernel ;-) Possible workaround as a last resort: install Debian Trixie first, then install PVE - https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie - you would lose "OS on ZFS" though...

sendmail gehört (per Default) zu Postfix: ~# dpkg -S $(which sendmail) postfix: /usr/sbin/sendmail Wie sendmail mit dem eigentlichen Postfix kommuniziert ist mir gerade unklar - und egal ;-) Wichtig ist, dass diese Konstruktion nur dann korrekt funktioniert, wenn sie vollständig konfiguriert...

You have pools with different names. (( And this prevents replication which is really annoying :-( )) Migration of running VMs allows me to select a specific storage on the target Migration of LXC does not offer this to me At the end... backup/restore should work. There is no easy...

Dein "allinkl" redet mit dem konfigurierten Emailserver, dazu hast du im Einrichtungsdialog deine Zugangsdaten eingegeben. Dieser Mechanismus funktioniert nur innerhalb des Proxmox-Kontextes. "sendmail" ist eine lokal laufendes Programm, welches üblicherweise einen ebenfalls lokal laufenden MTA...

I do not know how many nodes you utilize. If you have only three of them: https://forum.proxmox.com/threads/proxmox-ceph-performance-with-consumer-grade-samsung-ssd.179948/post-834586

That's worst design possible. Beside the too cheap devices... Look at one node: when one OSD fails, the other one on the same node has to take over the data from the dead one. It can not be sent to another node because there are already copies on all other nodes as there is no fourth node. With...

Nice approach :-) Even though you have redundant switches I would recommend to prepare a separate wire (not a virtual LAN, 1 GBit/s is sufficient) for one of your multiple corosync rings. Disclaimer: your approach is multiple levels above my usual stuff :-)

It's not clear if you know the following page: https://pve.proxmox.com/wiki/Windows_2025_guest_best_practices - maybe some of those hints are helpful for you...

There is no routing inside of a single IP network. All traffic is forwarded inside the bridge from VMa to VMb in the very same way it is done in a physical switch. To force a VM/LXC to send all packets to the router you would need to setup a /30 network for each one. That's the clean and...

Why not virtualize that idea? Create some VMs. Choose a "simple" OS without many bells and whistles. Update them and install relevant software - while being connected to the "normal" LAN. Make snapshots/backups. Setup some bridges without a hardware NIC assigned. Connect the NIC (more than one...

My very first PBS used only rotating rust. First it worked great. After putting a few TB of actual data on it I had exactly that experience. The listing of backups failed with timeout. Trying it immediately again would succeed - because most part of the metadata was already read and stored in...

Probably it's a VM under PVE ;-)

Is it? The relevant drivers for that virtual NIC are already baked in by default? This very old page is irrelevant nowadays? https://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows Some minutes later: I've just started a (rarely used) Win11 VM and it shows me "Red Hat VirtIO...

Search for "journalctl"; the journal has replaced the classic syslog in Debian 13 / Trixie. Use journalctl -f to watch it live. To see the latest output of the previous boot: journalctl -b -1 -e = show the end (-e) of the previous (-1) boot. "-2" for the one before the last one and so on...

Well... it is a virtual device. Capabilities reported may be different than the hardware implements. Did you actually try to transfer more than 1 GBit/s? Give it a try - using iperf3 for example.

To make it PVE related: if the NIC runs under Debian it will probably work with Proxmox. Create a corresponding bridge, add that VM, install virtio drivers and... call it a day. Disclaimer: have have zero Mellanox experience...