Search results

I tried, but uptime difference between the real VPS and ProxMox is still.. For example, VPS uptime is 6seconds, ProxMox shows ~3minutes. You think this kernel may solve "unregister_netdevice: waiting for lo=ffff81031ea93800 to become free. Usage count = 4 ve=182" problems or all my problems...

anyone?

You should edit /boot/grub/menu.lst file and reboot your machine, then your server will run up with your selected kernel :)

What the differences between: pve-kernel-2.6.18-2-pve: 2.6.18-5 and pve-kernel-2.6.18-1-pve: 2.6.18-4?

**** NEW ERROR **** 2.6.18-1-pve when i try to stop VM via Proxmox, status changed to mounted and: unregister_netdevice: waiting for lo=ffff81031ea93800 to become free. Usage count = 4 ve=182 delta:~# Message from syslogd@delta at Feb 5 15:22:04 ... kernel:unregister_netdevice: waiting for...

It seems like ProxMox have bug, because inside VPS all is fine. :)

<removed>

omega:~# pveversion -v pve-manager: 1.5-5 (pve-manager/1.5/4627) running kernel: 2.6.18-1-pve proxmox-ve-2.6.18: 1.5-5 pve-kernel-2.6.24-7-pve: 2.6.24-11 pve-kernel-2.6.18-2-pve: 2.6.18-5 pve-kernel-2.6.24-9-pve: 2.6.24-18 pve-kernel-2.6.18-1-pve: 2.6.18-4 qemu-server: 1.1-11 pve-firmware: 1.0-3...

URGENT Hello, i have upgraden from 1,4 to 1,5 ProxMox, and i have strange problem with uptime. Proxmox shows that VPSes are alive more than 1 Hour, but Hardnode is alive only 15 minutes, only KVM shows true time. In Administration -> Cluster - TIME OK In VM Manager -> Virtual Machines - TIME...

Actually, i did it for my self: iptables -A INPUT -p tcp -s MY_IP/32 --dport 80 -j ACCEPT iptables -A INPUT -p tcp -s MY_IP/32 --dport 443 -j ACCEPT iptables -A INPUT -p tcp --dport 80 -j DROP iptables -A INPUT -p tcp --dport 443 -j DROP Only you, could connect to PVE Web Management, it didnt...

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) So bugs are fixed and i can install it without any problems? :) Actually I need to do: apt-get update apt-get dist-upgrade apt-get upgrade apt-get --reinstall proxmox-ve-2.6.18 because, i had installed old one kernel yes?

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) I ask, or to correct any errors in that time was, for example, it was not possible to restart the VPS;or kernel sysmsgd errors;or when I try to migrate LIVE from 2.6.18 to 2.6.18, I received errors on the lo venet0 interfaces and they waited...

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) Hey, does 2.6.18 kernel debugged? With VMs rebooting inside fix?

Hey, i have problem with my VE's. I had installed 18 and i had disabled that kernel because it didint work properly, so i returned to 2.6.24-9-pve.. So the problem is: my VE after reboot command didint boot back, it show mounted. I need to umount and start by myself. beta:~# pveversion -v...

BTW the live migrate on 18 kernel crashes machine and shows a lot of lo and venet0 errors like my others posts. I will test soon as possible, because i have installed 24 kernel :)

Hey, i do not use ipv6. 18 kernel works strange, when i start/stop/destroy VE's server freezes PVE site shows perl timeout error, i get syslogd messages about venet0 ant lo interfaces..

i know.. but i can't fix it.. Message from syslogd@delta at Jan 4 17:59:27 ... kernel:unregister_netdevice: waiting for lo=ffff81003052a000 to become free. Usage count = 3 ve=190 Message from syslogd@delta at Jan 4 17:59:37 ... kernel:unregister_netdevice: waiting for lo=ffff81003052a000...

huh? i need to fix it ... :[

How to fix VPS rebooting and messages? Because sometimes VPS reboots fine, somtimes not.

2.6.18