Windows Xp mouse pointer

[vitor costa]

I have some Proxmox on diferent locations (cutomers). All works ok with mouse + VNC Console in almost all then. But In the first customer a install proxmox (i guess version 1.1 or 1.2 with kernel 2.6.24, now this host have PVE 1.7 with 2.6.18) on Windows XP Vms the virtual mouse pointer is not in sync with VNC Console.

I transfer one of this VMs to another Host where VMs with XP pointer is OK and the transfered VM have the pointer ok too.
So i think this problem is in Proxmox instalation... maybe the many updates (from 1.1 to 1.7 version).

Maybe reseting VNC configurations..... but i dont know where i can config this...

Thanks in advance

 

[dietmar]

So i think this problem is in Proxmox instalation... maybe the many updates (from 1.1 to 1.7 version).

Please compare the output of:

# pveversion -v

 

[vitor costa]

Output bad server:

pve-manager: 1.7-10 (pve-manager/1.7/5323)
running kernel: 2.6.18-4-pve
proxmox-ve-2.6.18: 1.7-10
pve-kernel-2.6.32-4-pve: 2.6.32-28
pve-kernel-2.6.18-4-pve: 2.6.18-10
qemu-server: 1.1-25
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-9
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-10

Normal server:

pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.18-4-pve
proxmox-ve-2.6.18: 1.7-10
pve-kernel-2.6.18-4-pve: 2.6.18-10
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-10

 

[tom]

post the config file of the problematic XP VM (see /etc/qemu-server/VMID.conf)

 

[vitor costa]

All vms xp in problematic host have the seme problem. Transfering the VM (image + vmid.conf) to another host = perfect. So i dont think problem is ralated to vmid.conf... I think is host problem...

Anyway here some the vmid.conf:

name: windowsxp-dp
ide2: local:iso/winxpsp3.iso,media=cdrom
bootdisk: ide0
ostype: other
ide0: drbd:vm-109-disk-1
memory: 1024
sockets: 2
vlan1: rtl8139=22:20:B8:8E:96:B7
onboot: 0
cores: 1

Another one:

name: xp-av
ide2: none,media=cdrom
sockets: 2
vlan1: rtl8139=D2:E0:C7:8B:2E:75
bootdisk: ide0
ide0: drbd:vm-106-disk-1
ostype: wxp
memory: 512
onboot: 0
cores: 1

 

[tom]

All vms xp in problematic host have the seme problem. Transfering the VM (image + vmid.conf) to another host = perfect. So i dont think problem is ralated to vmid.conf... I think is host problem...

Anyway here some the vmid.conf:

name: windowsxp-dp
ide2: local:iso/winxpsp3.iso,media=cdrom
bootdisk: ide0
ostype: other
ide0: drbd:vm-109-disk-1
memory: 1024
sockets: 2
vlan1: rtl8139=22:20:B8:8E:96:B7
onboot: 0
cores: 1

'ostype: other' looks like a good hint. go for winxp and try again. (power off and start the guest, a reboot is not enough after this change).

 

[vitor costa]

How you can see one vmid.conf have "OS: other" , but the other one have os: winxp" , both have the same problem.. So change OS type will not help...
Again: transfering this vm (image + conf) to another Proxmox Host fix the pointer sync problem... so the problem is not in guest configuration or image...

 

[udo]

Output bad server:

pve-manager: 1.7-10 (pve-manager/1.7/5323)
...

Normal server:

pve-manager: 1.7-11 (pve-manager/1.7/5470)
...

Hi,
what's about "apt-get update; apt-get upgrade" ? To have the same version?

Udo

 

[vitor costa]

I can try update, but i not think this will help... i have many servers with many versions pve (1.7, 1.5, 1.3) only this one have this problem.
I think this is in QEMU configuration or VNC server config or X11 (used vnc). Where i can clean the configs to vnc console ? If i backup all vms, and reinstall proxmox in same server i are sure will work... but i trying avoid that...