Search results

:D Suddenly it works! At least I get DNS resolution and I can ping the VLAN20 members. A ping to google does not respond yet.

Thanks for the suggestion! I tried it, but it doesn't work. I imagine that vmbr0 points to the trunk and not some particular VLAN. I also tried vmbr0.20, but that did not work either.

Hello! I want to create a private network for my containers (IP range 10.10.200.0/24), and allow these containers to establish outbound connections. pve is used in a local network, and my pve host connects to my network with a VLAN-aware bridge. I use various VLANs, and VLAN20 shall be used for...

@stefanatproxmox I since switched the setting to SLAAC:

Sorry, please disregard. Ther was indeed a running verification task on the backup server that I overlooked.. :rolleyes:

Hello! I run a regular pve -> pbs backup. However, I can no longer backup a certain container, as it always fails with: Error: unable to acquire lock on snapshot directory "/mnt/vm_backups/ct/101/2022-12-20T20:44:42Z" - base snapshot is already locked by another operation No other backup task...

Hello! My setup is a proxmox instance in a local network alongside a DHCPv6 server (a FritzBox! router). In a nutshell, the router's settings are set such that it assigns the DNS server, prefix and addresses by means of DHCPv6. However, this does not seem to work with my Ubuntu LXC...

Hello! I am using Proxmox 6.1-5 with a Windows 10 VM with passed through GPU. Here is the VM configuration: agent: 1 balloon: 0 bios: ovmf boot: c bootdisk: scsi0 cores: 14 cpu: host efidisk0: local-lvm:vm-101-disk-1,size=128K hostpci0: 0a:00,x-vga=1,pcie=1,romfile=GTX1070_spliced.bin...

That makes sense, thanks for clarifying. Since I need GPU passthrough, I will just not use ballooning.

The system behaviour is like this: I reboot the offending VM with memory settings that lead to overprovisioning, everything freezes (VMs, web GUI, SSH becomes unreactive), and the proxmox host reboots. I then extracted the syslog after the forced reboot, which, of course, is very long. You are...

I understand your concern but it is all the syslog I have. During the crash, nothing is added. I got this with "cat /var/log/syslog" after reboot.

Find a crash syslog attached. Here, one VM was rebooted with "unsafe" settings, meaning 1GB min. RAM and 12GB max. RAM, while the other machine has 2GB min. RAM and 6GB max. RAM. The reboot happens here: Jan 9 18:35:52 pc qmeventd[874]: Restarting VM 101 Anyway, I cannot see anything useful...

Yes, I will try and check the resource monitor that should also include system processes that I cannot see in Task manager. Maybe, but I don't know which one it is in the log rotation. I will just let it crash again.

Yes, it is not from the crash, I will record another one when it crashes in the evening. In the list of tasks, there is no process that uses much memory at all. I cannot see the source of memory consumption. Blnsrv.exe also uses very little, in the order of 1 MB. I will also post a screenshot...

When both machines are running with more conservative memory settings (VM1: 1-8 GB RAM, VM2: 1-6 GB RAM, so no overprovisioning), this is what I get from "free -h" after some idling period of 5 minutes and with ballooning enabled: root@pc:~# free -h total used free...

The testing configuration was as follows: VM1/VM2 each have min. 2GB RAM and max. 8GB RAM set with ballooning enabled. Reporting of RAM usage to the Proxmox user interface is working correctly, meaning that Windows and Proxmox RAM usage display is consistent. RAM usage drops slowly from 90%...

Ok, I will soon return with more information. Could you point me to relevant log files apart from syslog?

The machines in idle only take up around 3GB of RAM, so from the guest side, RAM usage was not excessive. Is ballooning not supposed to manage RAM, so I can overprovision it? If ballooning is enabled in the Proxmox web-GUI, there seems to be a memory leak and every 3-4 seconds, RAM usage...

I have the same problem in Windows 10 1909, just freshly installed. I tried the latest (1.173), as well as the stable version (1.171) and I made sure that the ballooning service was running and drivers installed. Still, I get increasing RAM usage when the service is running. Another problem I...