Hi Lindsay,
in case you didn't think about this already. ;-)
Are there any container config differences between the ubuntu and the debian
containers?
The default timeout and retry for dhclient is 60sec, how long do you wait til
you connect to the prompt?
How does your bridge setup (network in general) look like?
auto vmbr0
iface vmbr0 inet manual
bridge_ports eth3
bridge_stp off
# 30sec forward delay is default if fd isn't set to 0
bridge_fd 0
bridge_vlan_aware yes
Did you try to set a static IP for the first boot, remove the IP inside the
container and run the dhclient manually?
Maybe tcpdump can give you more insight.
== my CT config ==
arch: amd64
cpulimit: 1
cpuunits: 1024
hostname: fs-server.lab.domain.tld
memory: 2048
nameserver: 192.168.2.252 192.168.2.254 192.168.2.14
net0: bridge=vmbr0,hwaddr=62:35:64:65:39:37,ip=dhcp,name=eth0,tag=208,type=veth
onboot: 1
ostype: debian
rootfs: rbd:vm-223250-disk-1,size=8G
searchdomain: lab.domain.tld
swap: 512
Cheers,
Alwin
On 05/27/2016 09:03 AM, Lindsay Mathieson wrote:
> On 27 May 2016 at 00:56, Alwin Antreich <[email protected]> wrote:
>> may you please post your CT config, as I use the debian8 proxmox templates
>> without these issues?
>
>
> arch: amd64
> cpulimit: 1
> cpuunits: 1024
> hostname: ctest0
> memory: 512
> net0: name=eth0,bridge=vmbr0,hwaddr=66:38:30:64:31:64,ip=dhcp,type=veth
> ostype: debian
> rootfs: volume=gtest:subvol-920-disk-1,size=8G
> swap: 512
>
>
> debian 8.4 has come up once, after a few minutes delay. It had no ip
> on the network, which I think also indicates dhcp issues. Haven't been
> able to get it up again since though.
>
> thanks,
>
_______________________________________________
pve-user mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
