Search results

hi, at the moment quota are only available when using the legacy cgroupv1 option. https://pve.proxmox.com/pve-docs/chapter-pct.html#pct_cgroup https://pve.proxmox.com/pve-docs/chapter-pct.html#_using_quotas_inside_containers

https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_qdevice_technical_overview

check /etc/hostname file as well. is this PVE part of a cluster or standalone node?

at hetzner you'll most likely have to add a hwaddress to your bridges in the /etc/network/interfaces file, their switches block packets from "unknown" mac addresses (only your physical machine's mac address will work). something like: auto vmbr0...

hi, you marked the thread as [SOLVED] but didn't elaborate about the problem solution. could you please share?

hi, in the manpage it's detailed under --mp[n]: Use volume as container mount point. Use the special syntax STORAGE_ID:SIZE_IN_GiB to allocate a new volume. this works the same way for rootfs. the UI does not always generate a command, since the parameters go to the API (in fact pct etc...

hi, you can make a feature request on our bugtracker [0] just for your info, one way to wipe would be running sgdisk --zap-all /dev/foo (where /dev/foo is your disk) in the installer's debugging mode [1] (CTRL-D will drop you in a shell) [0]: https://bugzilla.proxmox.com [1]...

i would suggest taking a look at this link here [0] though it seems like when i select Turkey it still gives the nonworking address. debian website has another mirror listed in Turkey [1] otherwise you can just try selecting a different country (geographically close to your location to avoid...

hi, try changing the debian mirrors, it seems like http://ftp.tr.debian.org does not currently work.

hi, try to ssh from e.g. proxmox1 to proxmox3 and vice versa. this should work without any user interaction (and no errors) for migration to work correctly. if it doesn't work then take a look at the ssh keys in .ssh/known_hosts folder

hi, that's the problem. your NAS was not accessible at the time of the backup (as you guessed in your later edit) you could check the logs on your NAS and also on your PVE to further narrow down why that was the case

hi, please show the error message you receive. probably ;) depending on your exact network setup, you can do port forwarding (from your router), or you could set up an nginx reverse proxy [0] hope this helps! [0]: https://pve.proxmox.com/wiki/Web_Interface_Via_Nginx_Proxy

the VNC service runs on the PVE server (because it's started by QEMU, running outside of the VM). glad to be of help, please mark the thread as [SOLVED] :)

you're welcome, please mark the thread as [SOLVED] :)

it seems like it worked (you just forgot a space after grep ;) ), and the pveproxy service is running according to the ss output... (see the bottom of your screenshot, with *:8006 the journalctl you've attached doesn't tell much, but i guess since the service is working it should be fine. so...

you have to connect to your PVE host for the VNC session, the port number will determine the VM that you're connecting to.

hi, check if the port is open: ss -antlp | grep 8006 if it shows you any output like "pveproxy" that means the service is running. if not, then you can check journalctl to see if there are any errors when starting the GUI service (pveproxy)

* 10.24.35.141 is this IP address of your PVE server? * are you on the same network segment as the PVE server?

do you have any scheduled backups around those times? could you also check the journals around the time where it suspends the VM?

hi, this is likely not related to your issue. which version are you on? please post the output from pveversion -v did you check the power settings inside windows?