Search results

This is normal. It puts the current setup in a temp file for editing. But really, on Debian-based systems, the easiest way to run something once per hour/day/week/month is to put a normal bash script into /etc/cron.{hourly, weekly, monthly}. That is how the log rotation and a number of other...

The different file thing is because crontab -e copies the current settings into a temporary file for editing. It is perfectly normal. Have you used Linux before? Did you ask for help? The usual way to run something once per hour on Debian-based systems like PVE is to drop a regular bash script...

I use OpenWRT, which is Linux- rather than BSD-based and it is on a dedicated device in any case. I'm afraid I can't help with OPNSense but they do seem to have some info on their website about running it on KVM-based hypervisors which PVE is. Might be worth taking a look.

Did you install the qemu guest tools in the VM and enable the virtio network driver in the Hardware tab of the VM configuration? Those would be the first things to check. See the manual (linked as "documentation" at the top of the PVE GUI) for details. Whether pass-through of individual ports...

The (easy-to-find) recommended method is to back up and restore the container. You can change the mode during the restore.

It is "obviously" not syncing or the time would be correct. What is the actual output of "chronyc sources"?

If your wg_server is behind a normal ISP router it isn't going to be reachable from the Internet without making some configuration changes there, like enabling a port forward.

According to Intel this chip does theoretically support VT-d but based on this [ 0.056635] DMAR: IOMMU enabled [ 0.417629] pci 0000:00:00.0: DMAR: Disabling IOMMU for graphics on this chipset [ 0.417632] pci 0000:00:00.0: DMAR: Forcing write-buffer flush capability it may not be...

If he removes it he will find out what if anything depends on it. Apt will tell him :)

Interesting. I installed mine via Debian so maybe there is some difference after all. Seems pretty clear that it isn't needed for anything though and it is safe to remove it.

I don't have nmap on my PVE 8.3.3. I don't think it is a dependency of any PVE components. You can use "apt rdepends" to find out what might be depending on it.

The following variation allows you to disable the storage (with pvesm or the GUI) and unmount the drive. Later you can plug it back in and re-enable the storage and it will automatically be mounted. I use a label rather than a UUID so I can rotate my backup drives (they all have the same label)...

It isn't my problem. I was just making a suggestion of a possible reason. So I won't be posting any benchmarks. Thanks.

BTW, PVE does not emulate AMD instructions when running on Intel or vice versa. The CPU flags are really just visibility flags. They can hide features but not create them. The purpose of this is to facilitate live migration between not-identical hardware.

It could be because when you installed Windows on an Intel CPU it decided that certain features were available and said features are not existing or differently implemented on AMD. So it is falling back to a generic version that is slower.

1 TB = 1000 GB. So 2 TB = 2000 GB. Therefore you should write 2000. And maybe learn Si prefixes.

So you plan to put 200 TiB (200,000 * 1 GiB = 200 TiB) on a 5.5 TiB storage? How's that supposed to work?

What kind of storage is "Daten"? Perhaps the limitation comes from there.

Don't shut down active NFS shares. NFS does not play well with unreliable servers.

This is sounding a lot like a duplicate IP somewhere on your network. If that is the case you can get connection reset by peer because you're not connecting to what you think you are.