Hi,
I've got a new physical server from my provider and installed Proxmox. They have scripted the install and I then got the latest version of Proxmox VE (i.e. 3.4.8). I tired to create a container (through vzctl create and a homebrew template) and couldn't get it start at all. I then went to the web console, downloaded a standard package (i.e. debian-7.0-standard_7.0-2_i386.tar.gz), created a container with the web interface, switch to ssh, entered vzctl start 301 and got :
The dmseg gives me :
The technical support told me it maybe was my network configuration. I then tried to create the container in Bridged mode only to notice I couldn't start it either. This time it gave me :
The dmseg gives me :
And for instance, here is my network configuration:
Except that, all is juste plain fresh Proxmox install. I have tried precisely the same process on my other machine (currently running Proxmox 3.4.6) and all went fine. I really not understand what's happening. Is there a bug in the new release or have I totally missed something ?
Further details on my machines :
The one causing problem :
The one working fine :
Regards,
Pierre.
I've got a new physical server from my provider and installed Proxmox. They have scripted the install and I then got the latest version of Proxmox VE (i.e. 3.4.8). I tired to create a container (through vzctl create and a homebrew template) and couldn't get it start at all. I then went to the web console, downloaded a standard package (i.e. debian-7.0-standard_7.0-2_i386.tar.gz), created a container with the web interface, switch to ssh, entered vzctl start 301 and got :
Code:
root@host:~# vzctl start 301
Starting container ...
Container is mounted
Adding IP address(es): 10.10.30.251
Unable to add IP 10.10.30.251: Inappropriate ioctl for device
Unable to del IP 10.10.30.251: Inappropriate ioctl for device
Container start failed (try to check kernel messages, e.g. "dmesg | tail")
Killing container ...
Container was stopped
Container is unmountedThe dmseg gives me :
Code:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: failed command: FLUSH CACHE EXT
ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 6
res 11/04:00:2f:57:0d/00:00:00:00:00/a6 Emask 0x3 (HSM violation)
ata1.00: status: { ERR }
ata1.00: error: { ABRT }
ata1.00: hard resetting linkata1.01: hard resetting linkata1.01: failed to resume link (SControl 0)
ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.01: SATA link down (SStatus 0 SControl 0)
ata1.00: configured for UDMA/100
ata1: EH complete
CT: 301: started
CT: 301: stoppedThe technical support told me it maybe was my network configuration. I then tried to create the container in Bridged mode only to notice I couldn't start it either. This time it gave me :
Code:
root@host:~# vzctl start 302Starting container ...
Container is mounted
Setting CPU units: 1000
Setting CPUs: 1
Configure veth devices: veth302.0
Error: veth feature is not supported by kernel
Please check that vzethdev kernel module is loaded
Container start failed (try to check kernel messages, e.g. "dmesg | tail")
Killing container ...
Container was stopped
Container is unmountedThe dmseg gives me :
Code:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA EXT
ata1.00: cmd 25/00:00:80:e2:f6/00:01:66:00:00/e0 tag 27 dma 131072 in
res 11/04:00:88:76:93/04:01:6d:00:00/ed Emask 0x3 (HSM violation)
ata1.00: status: { ERR }
ata1.00: error: { ABRT }
ata1.00: hard resetting link
ata1.01: hard resetting link
ata1.01: failed to resume link (SControl 0)
ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.01: SATA link down (SStatus 0 SControl 0)
ata1.00: configured for UDMA/100
ata1: EH complete
md: md1: resync done.
RAID1 conf printout:
--- wd:2 rd:2
disk 0, wo:0, o:1, dev:sda2
disk 1, wo:0, o:1, dev:sdb2
CT: 302: started
CT: 302: stoppedAnd for instance, here is my network configuration:
Code:
root@host:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
iface eth0 inet manual
iface eth1 inet manual
auto vmbr0
iface vmbr0 inet static
address 62.210.X.X
netmask 255.255.255.0
gateway 62.210.X.X
bridge_ports eth0
bridge_stp off
bridge_fd 0
auto vmbr1
iface vmbr1 inet static
address 10.10.30.254
netmask 255.255.255.0
bridge_ports none
bridge_stp off
bridge_fd 0
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -t nat -A POSTROUTING -s '10.10.30.0/24' -o vmbr0 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s '10.10.30.0/24' -o vmbr0 -j MASQUERADEExcept that, all is juste plain fresh Proxmox install. I have tried precisely the same process on my other machine (currently running Proxmox 3.4.6) and all went fine. I really not understand what's happening. Is there a bug in the new release or have I totally missed something ?
Further details on my machines :
The one causing problem :
Code:
root@newhost:~/create-template# pveversion
pve-manager/3.4-8/5f8f4e78 (running kernel: 2.6.32-40-pve)The one working fine :
Code:
root@oldhost:~# pveversion
pve-manager/3.4-6/102d4547 (running kernel: 2.6.32-39-pve)Regards,
Pierre.
