Search results

Hi Tom, Ok, then i know.

Server : DELL blade M610 CPU : Intel Xeon E5540

Nvm, it was just my hosts file that can't recognized my hosts even if the nodes are talking just over ip.

Hi, After latest update one of my servers are not connected to the cluster. I can use the console but the server seems to be (RED) see picture : it has problem to detect the hostname of the servers and there is not usable to start. I have try to restart the server again and without success.

Confirmed, works great!

Anyone ? :confused:

I can confirmed that is work also for me. Here comes my results: root@w01-c-h:~# grep -r . /sys/module/kvm*/parameters /sys/module/kvm_intel/parameters/ept:Y /sys/module/kvm_intel/parameters/pml:N /sys/module/kvm_intel/parameters/vpid:Y /sys/module/kvm_intel/parameters/enable_shadow_vmcs:N...

Hi, One of my main nodes that handle my KVM vms stop working after i reboot the server and use the latest kernel version : 4.2.0-1-pve I facing this error after i have rebooted and trying to start my KVM servers : https://gyazo.com/dcbcae37625f46aed2a7120642f22dcf Then if i reboot the server...

I do some more research about this, i try to force the lxc to start with debug log. root@host4:~# lxc-start -lDEBUG -o mylogfile.log -F -n 102 lxc-start: commands.c: lxc_cmd_rsp_send: 237 failed to send command response -1 Broken pipe systemd 215 running in system mode. (+PAM +AUDIT +SELINUX...

Hi, I use proxmox v4, but i do have problem with bring up the network to my lxc container. Scenario if i want the network start again, i start with stop the container via CLI and then i type lxc-monitor -n ID. then i start again and after 10 retries the networks became online. This is how it...

Thank you!

The solution : By adding bridge_vlan_aware yes to /etc/network/interfaces under each bridge network interface you can use vlan tag as usual again. an example : http://gyazo.com/345590f19fe49f087d5bc33795a8ea53

By adding bridge_vlan_aware yes to /etc/network/interfaces under each bridge network interface you can use vlan tag as usual again. an example : http://gyazo.com/345590f19fe49f087d5bc33795a8ea53

Sorry it will not be an option, i want the vlan to be tagged directly to the virtual machine and i use a lot of vlans so that will be difficult to using ovs.

I have the same problem as you have. The problem is related to the newest update then the vlan support does not exist anymore. The network between the servers housed by the same host have no problem to communicate between VPS to VPS but the vlan from the primary host to others is not working...

Hi proxmox, Since the latest update are all my vlan that are tagged to the virtual servers (both lxc and kvm) dead. are there any progress on this? or are there any option to revert the previous update? /Egner