Search results

Perfect. If your issue is resolved, please mark your thread as "solved". You can do this by editing your first post and setting the flag. :)

If manual mount points for storages exist, is_mountpoint prevents data from being written accidentally. Here is an example: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_configuration_12

Sorry, i meant only "/boot".

Tell me... could it be that there is a duplicate IP in your network? That would also have such effects. Which networks do you use? Are they all in the correct RFC? Because if, for example, public subnets are used internally, this can also have very strange effects.

Thats a configuration inside your container OS, so it is not directly related to Proxmox. What OS is installed in your container?

Have you ever cleaned up Root? Cleanup apt cache: apt clean Cleanup packages no longer used: apt autoreove --purge After please post your content of /boot/grub And please also the output of pvs vgs lvs

Ja, in Proxmox Mailgateway. Aber das ist ein komplettes differentes Produkt als Mailcow. Daher bitte im Mailcow Forum auf Hilfe warten, oder direkt beim Support nachfragen. Kann ich nur empfehlen, die sind sehr gut!

Jetzt bin ich auch überfordert :p ... wenn du uns jetzt noch den Zusammenhang mit Proxmox VE erklären könntest...?

Thank you for clarify. Have you ever replaced the network cable for test?

This should basically work... do you have an ISO for me where I can test this?

o_O :eek: sorry, haven't seen the category... Yes, of course that is possible. You have to to copy you export to your new server in the directory: /var/lib/pmg/backup/. After this your backup is available in the webinterface for import.

Seems to be something very RedHat specific... Ubuntu runs normally with it. Which Kernel version does your RHEL use?

Does this also happen from other machines in the network? Even if you ping other targets on the Internet? What happens if you ping another internal machine?

Yes, but only on KVM's.

There is no export/import. However, there is an upgrade guide: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8#New_installation It also describes the important paths and files that can be copied to a new host.

Have you enabled the needed flag?

Perfect . Please mark your thread as "solved". You can do this by editing your first post and setting the flag.

Have you switched to the old cgroup too? https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pct_cgroup_compat nano /etc/default/grub - GRUB_CMDLINE_LINUX_DEFAULT="quiet" +GRUB_CMDLINE_LINUX_DEFAULT="quiet systemd.unified_cgroup_hierarchy=0" Save and Update Grub. Then reboot your whole host.

Regardless of your topic, there is a ready-made project for this: https://github.com/bashclub/zamba-lxc-toolbox

Please have also a look at the docs for this: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_cloud_init_on_windows