Search results

yes, update-initramfs -u resolved my problem.

A quick question, in general, for win7 and win2012r2, should i keep virtio drivers version 1.141-stable or go to 1.149-lastest ?

Hello dcsapak, you're certainly right ! hibernate have been activated after 30 minutes. i had correct this, it's certainly that. Thank you :)

Hello, One VM change state in "pause" for an unknown reason. I started it and after somes minutes or hours, been in pause. I must resume it on open console. It's a Windows 7 64 bits. I have other Linux or Windows 2012 VM. No "pause" problem. If i open console and a windows session, i can use...

Hello, i using proxmox since version 3.0 like this : nodes 1 and 2 : volume 0 : OS volume 1 to 3 : drbd storage, in version 8.4, with drbdr0, drbdr1 and drbdr2. node 3 : for HA and backup. Since pve 5, i encounter problems to use drbd. cat /proc/drbd : diskless lvscan : "Device mismatch...

For my part, I could not help you there, I do not know vmware and putting proxmox on top is complicating life. You will lose less time using an old computer than testing with vmware.

I do not know what you're trying to do, but you get complicated to put proxmox on vmware. Installs proxmox in bare metal and nothing else, even for tests.

hello quangnhut, with last version pfsense and proxmox, you can do can install pfsense with virtio network card. install it like a real hardware. configure pppoe if needed, all network cards. in my case, i must do this : menu system, advanced, networking. Hardware Checksum Offloading : enable...

Hello, For me, I will have tested with pleasure but I do not have the possibility at this time.

yeeaahhh, very good news for me too !

ok, thank you Fabian.

For me, only update kernel is enough. Not need to change something else.

It must not be for nothing that they return back ;) For me, no problem with the kernel test 4.4.35-2-pve and the 4.4.21-71 since more than one day. So it was that.

For me, "more simple". No hardware upgrade. Problems occurs after updating proxmox, with new kernel. So, i think about maybie a kernel "bug" and see this topic. The main one is to have found the solution. OOM serial killer did not reoffend at this moment. Pratically one day. Keep our fingers...

Hi Jorge, to install this kernel, do : dpkg -i pve-kernel-4.4.35-2-pve_4.4.35-78~test1_amd64.deb Reboot and login. uname -a must return 4.4.35-2-pve

Since yesterday evening : 1st server : Fabian test kernel with a VM test, a backup / restore of the VM victim. No killed at this moment. 8 GB ram used of 32 GB. Only this VM is running. The VM was killed even if if running alone, with 4.4.35-77 kernel. 2nd server : kernel 4.4.21-71, 5 VMs, 17...

My VM victim was killed by OOM serial killer this afternoon, on 2nd proxmox host. Kernel 4.4.35-77 and min_free_kbytes had 262144 value. 32 GB RAM (same 1st hardware). I can now run kernel 4.4.21-71 on one server to get all stable. I will run the same VM from a backup, as test, with your test...

My host had running kernel 4.4.21-71 before upgrade and encounter OOM kill problem. Other agency (no problem), supermicro motherboard too (no same models) : 1st : 64 GB, kernel 4.4.35-76 2nd : 128 GB, kernel 4.4.35-77 I had increasing the min_free_kbytes value this morning. The serial killer...

Hi Udo, 60 : root@mtp-prox02:~# cat /proc/sys/vm/swappiness 60 I had done this on several proxmox host. All 60.

Hello Fabian. For me : Motherboard : Supermicro X9DR3-F. Storage : DRBD v8.4 (compiled with the link said above) for VM. NFS on a synology RS2212 for backup. Memory & Swap size : 32 Go & 31 Go. Memtest OK. Here some files in attachment. Only the VM killed on the node concerned was running.