This is a real head scratcher.
Have others experienced an application inside a guest VM having problems with a version of PVE even though the actual guest OS seems to be running fine? Seems counter intuitive to my understanding of virtualisation, I figure if the guest OS is fine, all applications should be ok.
I have a win7 pro guest OS running a copy of XPUnlimited which is a 3rd party terminal services app.
On pve1.8 with virtio (hdd/net) it works without issues, however when migrated to a new server running pve 2.2 it will not allow more than 1x RDP connection. This is despite all other network functionality working (pings/web/single RDP). Secondary RDP connections begin the login process, but go to a blue screen, hang for a minute and then logs out and closes the RDP window.
Normally I would go to the company for support except that it works (and has worked for over a year) with no problems on pve 1.8.
I've tried:
Have others experienced an application inside a guest VM having problems with a version of PVE even though the actual guest OS seems to be running fine? Seems counter intuitive to my understanding of virtualisation, I figure if the guest OS is fine, all applications should be ok.
I have a win7 pro guest OS running a copy of XPUnlimited which is a 3rd party terminal services app.
On pve1.8 with virtio (hdd/net) it works without issues, however when migrated to a new server running pve 2.2 it will not allow more than 1x RDP connection. This is despite all other network functionality working (pings/web/single RDP). Secondary RDP connections begin the login process, but go to a blue screen, hang for a minute and then logs out and closes the RDP window.
Normally I would go to the company for support except that it works (and has worked for over a year) with no problems on pve 1.8.
I've tried:
- removing the virtio drivers and using e1000 (no change)
- using -cpu host in case there were flags not seen on the qemu64
- restored the vm onto both new and old server from the same backup - works in 1.8 not in 2.2
Code:
NEW Server
------------------
# pveversion -v
pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-16-pve: 2.6.32-82
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-1
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-34
qemu-server: 2.0-71
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1
Code:
OLD Server
-----------------
# pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.24-11-pve: 2.6.24-23
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6