Search results

Yes, sorry, patch is for guest CloudLinux kernel. Yes, I do monitor ram (about 90Gb out of 190 used) and io delay is on 16% level during vm going down. as far as I remember the VM was stable on: Nov 23, 2016 not sure what kernel was latest at that time. Here's the vm bootup log, during those...

No, my last post was with a new test kernel built according to my CloudLinux support case. They made kernel updates based on our crashdumps VM crashed again today on 4.4.35-2-pve This was not happening on 4.3

So CL guys proposed new kernel: We have released a kernel that include needed patch, please consider updating and rebooting to start using it: yum install kernel-2.6.32-673.26.1.lve1.4.21.el6 kmod-lve-1.4-21.el6 --enablerepo=cloudlinux-updates-testing But it didn't help. I blame this for now...

So #CloudLinux guys say it's probably this issue https://patchwork.kernel.org/patch/7086701/ and they say this patch will be included in next kernel version. Patch on my system should be applied faster, so I'll report back about the result asap

yeah, thx for that, I don't use brtfs ) But saw the messages about scsi regression stuff, will try to move vm to at least sata emulation. But freebsd vm living on sata crashes with drives failing too

I tried switching balooning off, but got crash again this night. I also opened support ticket to Cloudlinux support team but I'm pretty sure it's proxmox+kvm issue...

Thank you for your reply. This is a brand new dell server. And no, my VM's do not user swap thus it is enabled RAID-6 + zfs with a caching ssd # pveperf /VM-DATA CPU BOGOMIPS: 153621.60 REGEX/SECOND: 1841587 HD SIZE: 2794.25 GB (VM-DATA) FSYNCS/SECOND: 2079.90 which is...

Hi guys, Sorry I have no text logs yet, only screenshots. my problem is, sometimes once in 2-3 days, VM's crash with messages shown on pictures attached: First: we got messages about e1000 errors, so I've changed nic's to RTL ones and errors disappeared. Second: From what I can see at...

That's funny: # corosync-cmapctl| grep mcast runtime.config.totem.rrp_problem_count_mcast_threshold (u32) = 100 runtime.totem.pg.mrp.srp.mcast_retx (u64) = 0 runtime.totem.pg.mrp.srp.mcast_rx (u64) = 0 runtime.totem.pg.mrp.srp.mcast_tx (u64) = 12473 totem.interface.0.mcastaddr (str) =...

Hi guys, have a problem: Master server: Slave server config: I'm trying to execute on slave # pvecm add 172.16.0.3 -ring0_addr 172.16.0.2 -f I have subscription for slave server too but at this stage it shouldn't care, right? I have tested completely the same configuration on 2 pm...

Probably you have routing problems. Can you ping your proxmox interface from internet?

Hi guys, a quick story: I was searching for the way of running vmdk images (esxi5.1) without any conversion, so after a bit of googling: 1. I took the PBX.vmdk (small text file, see quote) and PBX-flat.vmdk (8 Gb) partition data, placed in the correct dir; 2. renamed PBX.vmdk to...

Have you tried chmod +x /sbin/ifup-local reboot or cd /etc/sysconfig/network-scripts && ./ifup-post ifcfg-eth0 like I proposed?

you forgot something obvious: chmod +x /sbin/ifup-local reboot or cd /etc/sysconfig/network-scripts && ./ifup-post ifcfg-eth0 also check all other interfaced added from proxmox are removed

For Centos I use this: vim /sbin/ifup-local #!/bin/sh if [[ "$1" == "eth0" ]] then ip a add xxx.xxx.xxx.128/24 dev eth0:128 ip a add xxx.xxx.xxx.131/24 dev eth0:131 ip a add xxx.xxx.xxx.132/24 dev eth0:132 ip a add xxx.xxx.xxx.133/24 dev eth0:133 ip a add xxx.xxx.xxx.134/24 dev eth0:134 #else...

Please read this topic: https://forum.proxmox.com/threads/lxc-multiple-nics-accessibility-issue.28194/#post-143353

Yes, there is a solution, do not add another network interfaces - add aliases. So you have 2 nic's present in the container(example): one for internal network 2. external ip1 (eth1) ext ip2 (eth1:1) etc and it will work and cpanel or plesk will see it

that's the network part net0: name=eth0,bridge=vmbr0,gw=2xx.xxx.xxx.xx3,hwaddr=F2:CE:FB:53:D8:E4,ip=2xx.xxx.xxx.130/24,type=veth net5: name=eth5,bridge=vmbr0,hwaddr=fe:f4:93:42:2e:8a,ip=192.168.xxx.130/24,type=veth onboot: 1 ostype: centos I have centos, I think you have ubuntu so you have to...

An answer: net0,1,2,3,4 are all in the same subnet, from the networks point of view (all connected with vmbr0) as well as from the address definition view (all have an IP address in xxx.xxx.xxx.xxx/24). There is no need to define 4 virtual NICs for that, define only net0 and assign the...

Interfaces are active. IP's are available only from /24 network. All connections outside /24 network are unavailable, like bridge is broken