Last weekend I decided to upgrade my proxmox server.
I did an upgrade and rebooted with the pve-kernel-2.6.35-1-pve kernel.
I am running ipv6 connectivity through a tunnel over ipv4 for my network.
The tunnel runs on a virtual vyatta box on my proxmox server.
I normally use ipv6 to connect to my servers and after everything rebooted,
i noticed hickups on all ssh connections (over ipv6) to my servers.
I finally decided to reboot to the 2.6.32 kernel and the hickups were gone.
Current config
I tend to use debian guests with virtio disk/network.
[Q1] Anyone else seen this kind of problems with up to 20 seconds hickups of guests/network traffic ?
I wanted to add another vps, defined it and tried to open it.
But no VNC to be seen.
So I looked at the log files and this is what I see:
[Q2] Anyone any idea why VNC won't work ?
I see a lot warnings like this
# grep "Jun 13" /var/log/daemon.log| grep meminfo | wc -l
346
[Q3] I know they are just warnings, but is it harmful ?
I did an upgrade and rebooted with the pve-kernel-2.6.35-1-pve kernel.
I am running ipv6 connectivity through a tunnel over ipv4 for my network.
The tunnel runs on a virtual vyatta box on my proxmox server.
I normally use ipv6 to connect to my servers and after everything rebooted,
i noticed hickups on all ssh connections (over ipv6) to my servers.
I finally decided to reboot to the 2.6.32 kernel and the hickups were gone.
Current config
Code:
# pveversion -v
pve-manager: 1.8-17 (pve-manager/1.8/5948)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.24: 1.6-26
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.35-1-pve: 2.6.35-11
pve-kernel-2.6.24-12-pve: 2.6.24-25
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.27-1pve1
vzdump: 1.2-13
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1I tend to use debian guests with virtio disk/network.
[Q1] Anyone else seen this kind of problems with up to 20 seconds hickups of guests/network traffic ?
I wanted to add another vps, defined it and tried to open it.
But no VNC to be seen.
So I looked at the log files and this is what I see:
Code:
Jun 13 23:31:02 vhost10 proxwww[966]: update ticket
Jun 13 23:31:02 vhost10 pvedaemon[2632]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Jun 13 23:31:02 vhost10 pvedaemon[1115]: creating new VM 123 on node 0 (localhost)
Jun 13 23:31:02 vhost10 qm[1116]: VM 123 creating new virtual machine
Jun 13 23:31:02 vhost10 qm[1116]: VM 123 creating new disk - size is 20 GB
Jun 13 23:31:02 vhost10 pvedaemon[1115]: VM 123 created
Jun 13 23:31:06 vhost10 pvedaemon[2632]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Jun 13 23:31:12 vhost10 pvedaemon[2632]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Jun 13 23:31:16 vhost10 pvedaemon[1151]: starting VM 123 on node 0 (localhost)
Jun 13 23:31:16 vhost10 qm[1152]: VM 123 start
Jun 13 23:31:16 vhost10 pvedaemon[1151]: VM 123 started
Jun 13 23:31:18 vhost10 pvedaemon[2631]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Jun 13 23:31:20 vhost10 pvedaemon[1174]: starting vnc proxy UPID:1174-14196717:1308000680:vncproxy:0:123:root:5900:/t7oL1ir649mn9Zi2QkXXgcvVw
Jun 13 23:31:20 vhost10 pvedaemon[1174]: CMD: /bin/nc -l -p 5900 -w 30 -c /usr/sbin/qm vncproxy 123 /t7oL1ir649mn9Zi2QkXXgcvVw 2>/dev/null
Jun 13 23:31:50 vhost10 pvedaemon[1174]: VM 123 vnc proxy failed - 256[Q2] Anyone any idea why VNC won't work ?
I see a lot warnings like this
Code:
Jun 13 23:49:59 vhost10 pvedaemon[2631]: WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead346
[Q3] I know they are just warnings, but is it harmful ?