OK, so I upgrdaed to Proxmox 4.0 yesterday, upgrade went smooth on the host.
Converting openvz guest , not so good.
Followed the guide - https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC
Everything looked good up to the networking part.
The web interface did not configure for NAT (guest was using 10.10.10.10 as an openvz guest, no network access using a bridge and a LXC container and an ip of 10.10.10.10).
configured my Proxmox 4.0 LXC guest from the web interface to use a spare public IP address via a bridge ...
Host ip 64.251.17.23
LXC guest ip 64.251.17.25
crashed the host, can not ping host or guest, can not access the web interface, can not ssh into guest.
The guest is (was) a working openvz guest converted to LXC.
Seems to be a bit of a bug.
The host is co-loco so I do not have physical access, have to have it shipped back for maintenance.
I was sort of hoping you had LXC figured out a you had with openvz, but, it seems LXC is not ready for prime time =(
Converting openvz guest , not so good.
Followed the guide - https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC
Everything looked good up to the networking part.
The web interface did not configure for NAT (guest was using 10.10.10.10 as an openvz guest, no network access using a bridge and a LXC container and an ip of 10.10.10.10).
configured my Proxmox 4.0 LXC guest from the web interface to use a spare public IP address via a bridge ...
Host ip 64.251.17.23
LXC guest ip 64.251.17.25
crashed the host, can not ping host or guest, can not access the web interface, can not ssh into guest.
The guest is (was) a working openvz guest converted to LXC.
Code:
ping banshee -c2 PING banshee (64.251.17.23) 56(84) bytes of data.
--- banshee ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999msSeems to be a bit of a bug.
The host is co-loco so I do not have physical access, have to have it shipped back for maintenance.
I was sort of hoping you had LXC figured out a you had with openvz, but, it seems LXC is not ready for prime time =(