Search results

Hi, after upgrading one node to 3.1 ( pve-kernel-2.6.32-26-pve 2.6.32-114 in enterprise repository ) the system hangs all the time, the processes are just blocked after booting. I made a lot of tests and with kernel pve-kernel-2.6.32-27-pve (2.6.32-119) from pvetest repository it works...

Of course, thanks to spirit, for his great job analysing this issue and finding the patch, and to e100 for putting this issue in the right direction :-)

It works very well :), bond interface up and working, thank you very much dietmar, great job!

I have same issue, but with Broadcom cards. With this kernel I have to remove bond interface to get it working. At boot time the requested firm is different. With 2.6.32-13: Aug 17 14:01:16 nhprox02 kernel: bnx2 0000:07:00.0: firmware: requesting bnx2/bnx2-mips-06-6.2.1.fw Aug 17 14:01:16...

I've tryed updating initrd image but the issue is not solved, the network card firmware is loaded correctly. I've verified that when passing all traffic through eth0 instead of using bond0 device all works ok, so the issue is related to bond interface. At boot time the bond0 device seems to...

Thanks for your reply, but this is not the case, the interfaces are not renamed. Under both kernels I have eth0,eth1 and bond0 inteface over them. Same behaviour in all of my nodes, with kernel pve-kernel-2.6.32-14-pve I have no network access. Best Regards,

Hello, after booting with the new kernel (pve-kernel-2.6.32-14-pve) the network is unreachable in my server. If I boot again with kernel pve-kernel-2.6.32-13-pve the network works again. pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46) running kernel: 2.6.32-13-pve pve-kernel-2.6.32-13-pve...

cman is not running # /etc/init.d/cman status fenced is stopped # /etc/init.d/cman start Starting cluster: Checking if cluster has been disabled at boot... [ OK ] Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting...

Hello, I am having same problem. From nhprox01 node: nhprox01# cat /etc/pve/.members { "nodename": "nhprox01", "version": 24, "cluster": { "name": "nhprox-cluster", "version": 6, "nodes": 6, "quorate": 0 }, "nodelist": { "nhprox06": { "id": 1, "online": 0, "ip": "172.17.16.43"}...

Any news on this? I had an vpn server with 8 nics running on 1.9 and after upgrading to proxmox 2, I can't boot it. Why it can run on 1.9 and does not work on 2.X? Thanks, best regards, Xabier Elkano

UPDATE: I Know what is going on; I typically perform Proxmox VE installations on a Debian Lenny directly and If I install first the kernel pve-kernel-2.6.32-6-pve_2.6.32-55+ovzfix-1_amd64.deb and try to boot with the kernel, it does not work because in the installation it makes the initrd...

Hi dietmar, I have the same problem here: my network card: 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet (rev 20) 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet (rev 20) pve-manager: 1.9-26...

Thanks for your fast reply! Is possible to see somewhere current bugs on 2.6.32 kernel branch? Best regards.

Hello, I have an issue with vzmigrate in proxmox 1.8 doing an online migration: /bin/sh /usr/sbin/vzmigrate -v --online XX.XX.XX.XX 101 Starting online migration of CT 101 to XX.XX.XX.XX OpenVZ is running... Loading /etc/vz/vz.conf and /etc/vz/conf/101.conf files Check IPs on...