Sage Problem on Windows 2008 Server -

[maxprox]

Hello,
I am in urgent need of an information referring the following software:
“sage classic line 2010” (bookkeeping software). The software doesn’t work on the virtualized windows 2008 server.
Sage run without major problems for approx. 1 year.
So I suppose there occurred a mistake with the virtualization related to windows 2008.
When starting “sage – workstation software” I get 50% CPU load factor and no window comes up.
With the installation of a java-update the same problems occurred. (50% CPU without a window coming up).
I tried some vz dumps from the last year (at this time sage was working well under Proxmox 2.0 beta) without success and the same 50% CPU load!
Even the deinstallation doesn’t work.
Thanks for your help and assistance. I don’t know what to do?

The VMID.conf:

root@proxmox01:/var/lib/vz/sicherung# cat /etc/pve/nodes/proxmox01/qemu-server/119.conf 
bootdisk: ide0
cores: 1
ide0: local:119/vm-119-disk-1.qcow2
ide1: local:119/vm-119-disk-2.qcow2
ide2: cdrom,media=cdrom
keyboard: de
memory: 4096
name: W2K8n2
net0: e1000=52:54:00:2C:8F:EF,bridge=vmbr0
onboot: 0
ostype: w2k8
sockets: 2
startup: order=3,up=29

My Version:

pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

regards
maxprox

 

[ngm]

Re: Sage Problem on Windows 2008 Server

Hello,

We are having a similar problem on a fresh install of Proxmox 2.1 running a fresh install of Windows 2008 R2 SP1. Both Proxmox and Windows have the latest updates.
The software (Voipbox) ran without any problems for a long time on a physical machine and inside an ESX environment. We first migrated one virtual machine from ESX to Proxmox and after we had the problems, we did a fresh Windows install.

When run, the software uses 100% CPU (just one core) and nothing happens, even after a few hours.
We tried to change the CPU type: host, qemu64. We also tried to reduce the number of cores to one.
If it matters, the software is 32bit.

The server is a Del PowerEdge 2950 with 2 quad-core Intel Xeon X5450 CPUs and 16GB of RAM.
On the same machine, we are running without any problems 4 OpenVZ CentOS 6 virtual machines. Also, besides this software, anything seems to be running fine in Windows.

Thank you!

root@proxmox1:~# pveversion -v
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

root@proxmox1:~# cat /etc/pve/local/qemu-server/202.conf 
boot: cd
bootdisk: virtio0
cores: 2
cpu: host
ide1: none,media=cdrom
memory: 4096
name: webserver
net0: virtio=3E:E4:47:76:4F:09,bridge=vmbr32
net1: virtio=7E:04:06:4C:9F:58,bridge=vmbr10
onboot: 1
ostype: win7
sockets: 2
virtio0: local-lvm:vm-202-disk-1

 

[maxprox]

Hello,
It looks like that the cause of the problem comes not from Proxmox.
Today I've tried different vzdumps in Proxmox 1.9 and get the same error.
Apparent it's up to Windows. I can not find the error

maxprox

 

[ngm]

The company which offers paid support for that software (Voipbox) tried to install different versions of the software and make different settings (they just had remote desktop access inside Windows). After several hours, they said that they could not find any solution and that this problem never appeared on any of their clients.

 

[maxprox]

The company which offers paid support for that software (Voipbox) tried to install different versions of the software and make different settings (they just had remote desktop access inside Windows). After several hours, they said that they could not find any solution and that this problem never appeared on any of their clients.

Hello ngm,

yes it's analogical with the sage support, but the sage support is not so competent.
At present I'm trying different vzdump backups on two different proxmox versions (2.1 and 1.9).
What I still do not understand, is that it does not works under any combination ...
The time I perform the backup it works.
And I get no error message, only a process with 50% CPU load
(Supermicro system, 2x Xeon quad core, 16 GB RAM, with two Linux VMs which work well)

maxprox