Search results

Hi Dietmar, Actually I'm changing RAM, CPU and a few others things. Here it is a vardump from a Array that gives me TimeOut: PUT /api2/json/nodes/{node}/qemu/{vmid}/config Array ( [name] => vps167 [description] => VM test [vcpus] => 1 [cpulimit] => 1 [net0] =>...

Hi, I'm running into trouble when working with PVE API. When I pass a "large" array to "PUT /api2/json/nodes/{node}/qemu/{vmid}/config", Proxmox makes part of the changes and then throw Time Out Error. If I pass a smaller array, with a few config params, it doesn't Time Out. How can I...

Hi, I'd like to hear from you guys, if running a cluster with 11 or more Nodes in Unicast (UDPU) can lead me to any instability in Proxmox ? I'm not using High Avaibility or distributed file system, i'm just using ZFS and NFS Share. Thanks in advance.

In my case everything runs good for 2 - 3 weeks, and then it happens. I'm investigating if it could be caused by using Unicast instead of Multicast. Are you using Unicast too ?

same here, every week

Hello, When I used "ifconfig -a", I realized that the MAC Address for "TapXXX" interface is different from the MAC Address configured in Proxmox GUI: Shouldn't it be the same ?

Same problem here, I've just posted another thread about this. I think this is caused by the last updates.

I started to face some problems with my cluster since the last week. Sometimes my cluster shows nodes with interrogation icon: That's really strange. I have to restart all nodes so they get back working again (online state). I already tried "service pve-cluster restart", but doesn't...

Hi, is there any way to check real disk usage on KVM guests ? EDIT: found it: https://balau82.wordpress.com/2011/05/08/qemu-raw-images-real-size/

Hello there, I'm facing a problem with Windows guest clock. The problem is that Windows Guest VM is synching with the Host Clock, overwriting the previous time. I know that when VM starts, it synch by default, and then after startup, VM synchs with a NTP server. But after hours of execution...

Hi, When a VM starts, an Interface is added, as we can see in ifconfig: tap100i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether 4a:69:1b:65:cf:41 txqueuelen 1000 (Ethernet) RX packets 23583 bytes 31600364 (30.1 MiB) RX errors 0 dropped 0...

https://pve.proxmox.com/wiki/Dynamic_Memory_Management#KSM

KSM daemon is responsible to take RAM back to the host when a VM releases RAM.

I could figure it out. KSM-Daemon wasn't installed. Thank you.

The case is that there's a bug, when ballooning release memory on VM, this memory is not being released on host. It was working until I upgrade to Proxmox 5

Hello guys, I found a bug on Proxmox 5, after upgrading. Proxmox 5 is not releasing balloning memory. As we can see below, ballooning drivers are still working: But that free memory is not being released to the host, that VM above just increased 12 GB on Host System total ram usage:

EDIT: I found a Proxmox 5 bug: https://forum.proxmox.com/threads/proxmox-5-ballooning-not-working-after-upgrade.36496/

I'd like to know too if ballooning is still causing high cpu usage. Maybe updated drivers has fixed this issue ?

Thank you for supporting me guys. I figured it out using command "pvecm e 1" on the 4th node, and than I could successfully add to the cluster. Many thanks.

I have a cluster with 3 nodes working smoothly, I'm using UDPU instead of Multicast. When I try to add the 4th node, it hangs on Waiting for Quorum. Here's is my Corosync: logging { debug: off to_syslog: yes } nodelist { node { name: ns524364 nodeid: 1 quorum_votes: 1...