blnsvr.exe keeps closing on server 2012

[si458]

Hi,

ive updated my proxmox machine to latest 2.3 and the balloon is a life saver! saves so much memory
however one of our KVM Machines isnt playing ball???

i enable the balloon, install drivers, copy software, etc...
all works for about 3 mins then the service stops, and the exe closes? and i have to manually start the service again?

im getting an error appear in my event log saying 'The BalloonService service has reported an invalid current state 0.'

the KVM Machine is WinServer2012 with 5G ram max and 1G min and most of the time is only uses about 4.2G

but whats weird is I have 2 other WinServer2012 KVM Machines and they are perfectly fine, its just this one

Any ideas people?

Regards

Simon

 

[tom]

First, do not use the term "container" for a KVM guest - Containers or VPS is used for OpenVZ.
http://pve.proxmox.com/wiki/Container_and_Full_Virtualization

If the blnsrv service is unstable on your box, tell windows to restart the service automatically.

here is a screenshot of a win2008r2, but there should be the same for 2012.

 

[si458]

Hi,
sorry my bad about my term, ive edited my original post

also ive already tried that and it still makes no difference

here is some info that might b helpful

root@proxmox:~# pveversion --verbose
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-48
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
root@proxmox:~#

root@proxmox:~# qm config 152
args: -vnc 0.0.0.0:102,password
balloon: 1024
boot: dc
bootdisk: ide0
cores: 2
ide0: local:152/vm-152-disk-1.qcow2,size=60G
ide2: isoimages:iso/virtio-win-0.1-52.iso,media=cdrom,size=57126K
memory: 5120
name: Win2012EX
net0: virtio=3E:22:18:8D:02:55,bridge=vmbr99
ostype: win8
sockets: 1
root@proxmox:~#

 

[phildefer]

Hi,

i have the same problème with all my Windows machine because of, i think, the SMS inventory

I make a bug report at Red Hat : https://bugzilla.redhat.com/show_bug.cgi?id=927619

 

[si458]

Hi People,

im just wondering if the is any update to this issue? as im still having the problem

ive told the service to restart after failure but it never restarts

regards

simon

 

[tom]

did you try latest version (see http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/)?

 

[si458]

im just about to try using 65 as im still using 59

which folder should i use? i normally use the WIN8 folder as im running Server2012 ???

 

[si458]

hi tom,

it didnt work, it crashed after 1 minute again! so its still exactually the same!

can you just confirm which folder i should be using for Server2012?

regards

simon

 

[ebiss]

wiki Windows_2012_guest_best_practices
http://pve.proxmox.com/wiki/Windows_2012_guest_best_practices

 

[si458]

wiki Windows_2012_guest_best_practices
http://pve.proxmox.com/wiki/Windows_2012_guest_best_practices

thanks for link but ive already tried that and it just doesnt work

it only seems to happen if I install Exchange server on the server?

 

[macday]

thanks for link but ive already tried that and it just doesnt work

it only seems to happen if I install Exchange server on the server?

Hi, I had the same problem on an old Win 2003 and Exchange 2003. I migrated all Mail-Data to our new Kerio-Connect Server and disabled the Exchange-Services. After than the blnsrv.exe worked as it should.

 

[Crunk_Bass]

I also had problems with the service after installing service pack 1 on Windows 7.

A simple reinstall of the service (blnsvr.exe -u, restart the vm, blnsvr.exe -i) fixed the problem.