Search results

I'm still scared doing this since I don't want to screw up my networking :( Maybe I move physically to the machine over the weekend. I think that this should be handled somehow by the Proxmox VE (i.e. it shouldn't create longer network if names than acceptable by Linux/Debian). Can I file a bug...

Thanks @spirit, the most straightforward answer so far! 1) Regarding renaming of the network interface, I don't have any file in /etc/systemd/network, should I create one and put this into its contents? [Match] MACAddress=01:23:45:67:89:ab # my mac address [Link] Name=lan0 # any short...

Hi, I'm having exactly the same issue, after assigning VLAN ID=112 to one of the VMs the VM refuses to start: Error: argument "enx4865ee1606c9.112" is wrong: "name" not a valid ifname can't add vlan tag 112 to interface enx4865ee1606c9 kvm: network script /var/lib/qemu-server/pve-bridge failed...

Ok, makes sense! Thanks Danilo for the explanation!

Okay, I heard that somewhere, that Linux kernel tends to preoccupy almost all available memory for performance reasons. I don't think I have any sleeping processes because the server is literally empty. Nothing running on it, definitely not 4GBs. But I can imagine that the memory is prepared...

I was also wondering about the same, this is how it looks like on my machine: 1) Debian guest VM - The VM says memory usage 3.72 GiB 2) However there is almost nothing running on the machine and the guest VM reports much less memory usage: root@proxmox-docker:~# free total...

Nice, I'm very glad to hear that, thank you!

I thought it would be cool to have an option to hibernate VMs (instead of shutdown) on PVE host reboot. It's especially handy when VMs require manual intervention for startup. Any thoughts on this?