Proxmox VE 4.0 beta2 LXC problem with network to start

[Egner]

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 looks then i try to start the server and the network fails :

root@host4:~# lxc-info -n 102
Name: 102
State: RUNNING
PID: 1618
CPU use: 0.53 seconds
Memory use: 6.79 MiB
KMem use: 0 bytes
Link: veth102i0
TX bytes: 0 bytes
RX bytes: 0 bytes
Total bytes: 0 bytes
Link: veth102i1
TX bytes: 0 bytes
RX bytes: 0 bytes
Total bytes: 0 bytes


Does anyone of you have any clue have to resolve this issue ?

Thanks Egner.

 

[Egner]

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 +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
Detected virtualization 'lxc'.
Detected architecture 'x86'.


Welcome to Debian GNU/Linux 8 (jessie)!


Set hostname to <tc01-vm-c>.
Failed to install release agent, ignoring: No such file or directory
Failed to create root cgroup hierarchy: No such file or directory
Failed to allocate manager object: No such file or directory


Here is the log output : http://pastebin.com/j0DkNzVJ

Thanks.

 

[Egner]

Anyone ?

 

[Jason Murray]

Anyone ?

Did you have any response or find a solution? I recently upgraded to Proxmox 4 in production, and while our upgrades of openvz containers worked in our lab environment, our two Jessie containers won't run correctly after conversion, giving the same error messages when running lxc-start -n [vmid] -f. I can use pct start [vmid] and the command succeeds, but the network does not come up. Using pct enter [vmid] works, but I cannot get networking to start.

 

[Egner]

Yes it has, Please use proxmox new LXC templates and start migrate the files from OpenVZ container to the new LXC container and the problem will be solved for you.