[SOLVED] Kernel disables tap every hour!

Sakis

Active Member
Aug 14, 2013
121
6
38
I have a strange problem lately. The kernel disables one specific tap every hour. Its a HA windows kvm with e1000 nic. I tried to disable ΗΑ and restart it but i get same problem every hour.

Code:
Jan  9 03:27:23 xxxx rgmanager[343083]: [pvevm] VM 100 is running
Jan  9 03:27:23 xxxx rgmanager[343100]: [pvevm] VM 103 is running
Jan  9 03:27:33 xxxx rgmanager[343133]: [pvevm] VM 100 is running
Jan  9 03:27:56 xxxx kernel: vmbr0: port 4(tap103i1) entering disabled state
Jan  9 03:27:56 xxxx kernel: vmbr0: port 4(tap103i1) entering disabled state
Jan  9 03:28:01 xxxx /USR/SBIN/CRON[343237]: (root) CMD (/usr/local/rtm/bin/rtm 31 > /dev/null 2> /dev/null)
Jan  9 03:28:03 xxxx rgmanager[343284]: [pvevm] VM 100 is running
Jan  9 03:28:04 xxxx rgmanager[343304]: [pvevm] VM 103 is not running
Jan  9 03:28:04 xxxx rgmanager[3732]: status on pvevm "103" returned 7 (unspecified)
Jan  9 03:28:05 xxxx rgmanager[3732]: Stopping service pvevm:103
Jan  9 03:28:06 xxxx rgmanager[343325]: [pvevm] VM 103 is already stopped
Jan  9 03:28:06 xxxx rgmanager[3732]: Service pvevm:103 is recovering
Jan  9 03:28:07 xxxx rgmanager[3732]: Recovering failed service pvevm:103
Jan  9 03:28:07 xxxx pvevm: <root@pam> starting task UPID:xxxx:00053D33:1242F0A6:52CE0937:qmstart:103:root@pam:
Jan   9 03:28:07 xxxx task  UPID:xxxx:00053D33:1242F0A6:52CE0937:qmstart:103:root@pam:: start VM  103: UPID:xxxx:00053D33:1242F0A6:52CE0937:qmstart:103:root@pam:
Jan  9 03:28:08 xxxx kernel: device tap103i1 entered promiscuous mode
Jan  9 03:28:08 xxxx kernel: vmbr0: port 4(tap103i1) entering forwarding state
Jan  9 03:28:09 xxxx rgmanager[343368]: [pvevm] Task still active, waiting
Jan  9 03:28:09 xxxx pvevm: <root@pam> end task UPID:xxxx:00053D33:1242F0A6:52CE0937:qmstart:103:root@pam: OK
Jan  9 03:28:09 xxxx rgmanager[3732]: Service pvevm:103 started
Jan  9 03:28:18 xxxx kernel: tap103i1: no IPv6 routers present
Jan  9 03:28:24 xxxx rgmanager[343415]: [pvevm] VM 100 is running
Jan  9 03:28:27 xxxx kernel: IPv6 addrconf: prefix with wrong length 56
Jan  9 03:28:37 xxxx /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing
Jan  9 03:28:43 xxxx rgmanager[343525]: [pvevm] VM 100 is running
Jan  9 03:28:44 xxxx rgmanager[343542]: [pvevm] VM 103 is running

Code:
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!