Proxmox 4.0 problem

[kde45]

Hi,


OVH Server

Installed Proxmox 4.0 Beta

When i create ct can i see VM 100 but i can not see Directory /var/lib/vz/private/100

When i network change vm100 via Console and restart network its ok
but when i reboot server is network setting away.

Who is the problem.

Thx

 

[spirit]

>>When i create ct can i see VM 100 but i can not see Directory /var/lib/vz/private/100
lxc CT are raw files by default and located in:

/var/lib/vz/images/CTID/

>>When i network change vm100 via Console and restart network its ok
>>but when i reboot server is network setting away.

currently, the network config in the ct is rewriten at when ct start from the proxmox ct ip configuration.

 

[kde45]

yes but we can i change network from VM100 via SSH

Online.net have don't this problem but OVH

 

[spirit]

you don't have GUI web access to your proxmox host ?

 

[kde45]

I have Gui web access

VM100 add mac address and via console or SSH added Ip from Failover IP
but im change it IP from Failover IP restart network its ok VM100 its online.

But when i reboot VM100 have old config network.

 

[spirit]

can't you setup ip configuration in proxmox gui, in CT options ?

(If I understand, you configure network inside the container right ? in this case proxmox rewrite ip configuration at next ct start)

 

[kde45]

I have Vm Proxmox GUI

ID : net0
Name : eth0
Mac address : OVH Failover Macaddress
Bridge : vmbr0

and via Console write this in VM

auto lo eth0
iface lo inet loopback
iface eth0 inet static
address IP.FAIL.OVER
netmask 255.255.255.255
broadcast IP.FAIL.OVER
post-up route add GATEWAY_VM dev eth0
post-up route add default gw GATEWAY_VM
pre-down route del GATEWAY_VM dev eth0
pre-down route del default gw GATEWAY_VM

Yes rewrite my configuration next start from VM

 

[mir]

The problem is that the gui does not respect user configured network settings outside of the gui so you are stock with the features available for network settings provided by the gui.

 

[kde45]

what should I do ?

 

[mir]

You can't really do anything other than wait for a bug fix.

 

[kde45]

The problem is also that nothing is saved. Not only the network conf

/var/lib/vz/private and root is not stored
/var/lib/vz/image see raw file

And this problem have with 4.0 and 3.4

 

[kde45]

a no idea?

 

[spirit]

The problem is also that nothing is saved. Not only the network conf

/var/lib/vz/private and root is not stored
/var/lib/vz/image see raw file

And this problem have with 4.0 and 3.4

with proxmox 4, lxc by default create a raw file inside /var/lib/vz/image/CTID/....raw
Filesystem of the lxc container is in this file.

with proxmox 4, if you don't define size for the container disk, it will create the filesystem in the host filesystem in /var/lib/vz/private/CTID/... , like with openvz with proxmox 3.4.


About the network config rewrite, you need to wait that proxmox team fix the code, to allow to not overwrite ip configuration.

 

[kde45]

this problem is actual all proxmox user just or only with me