Proxmox 1.5 and AMD Athlon X2 BE-2400 with Windows 2003 R2 / Exchange 2003

V

vandiekie

New Member
Mar 9, 2010
6
0
1
Hi all,

First of all, I want to say that i'm a happy user of Proxmox 1.4 environment with an Exchange 2003 server (W2K3 32bits, R2) for over a year.

But sad enough, after upgrading Proxmox from 1.4 to 1.5 I can't get my W2K3 machine working properly.

It is now starting up (windows server), but it fails to give me any networking, and it wants to install a new CPU driver (15!! times):

driver installat&#1.png

After clicking Continue Anyway it gives me multiple Unknown device under the Processor section:

unknown device..png

The NIC driver is installed (Intel PRO/1000MT), but it won't show up with the networking devices under the control panel, network connections applet.

So frankly, i've got 2 problems (no network, and the CPU isn't installed correctly). Maybe there's some correlation between these 2 problems, but I can't seem to solve is.....

I've already tried to uninstall both the Unknown devices and the NIC, but the NIC installs fine (but still no networking!) and the Unknown devices (probably the CPU driver), won't install because it gives me an access denied when installing:

access denied..png

Can anybody give me some advice on this problem??

Thanks!
 
Hi,
you can try to define another cpu-type in the config:
Code: 
args: -cpu qemu64,-nx

Switch off the vm and on again - perhaps your cpu-problem are gone?
I have running a win2003-server without trouble on a AMD Phenom(tm) II X4 965 Processor.

Udo
 
Hi Udo,

Thanks for your quick reply; sorry for my question (i'm still a bit of a proxmox noob :) ), but where do you specify those arguments?



udo said:
Hi,
you can try to define another cpu-type in the config:
Code: 
args: -cpu qemu64,-nx

Switch off the vm and on again - perhaps your cpu-problem are gone?
I have running a win2003-server without trouble on a AMD Phenom(tm) II X4 965 Processor.

Udo
Click to expand...
 
which kernel do you run? post your 'pveversion -v'

I suggest you go for the 2.6.18.
 
Hi Tom,

pveversion -v gives me:

vm:~# pveversion -v
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5

I'm already on 2.6.18 (if i'm correct)...

tom said:
which kernel do you run? post your 'pveversion -v'

I suggest you go for the 2.6.18.
Click to expand...
 
Hi Udo,

Found the config:

name: W2K3EXCH2K3
ide2: local:iso/intelpro1000mt.iso,media=cdrom
bootdisk: ide0
ostype: w2k3
memory: 2048
sockets: 1
onboot: 1
cores: 2
ide0: local:101/W2K3EXCH2K3.qcow2
description: Windows 2003 R2 + Exchange 2003 SP2 mailserver
vlan0: e1000=DA:E1:4C:3F:51:B0

Where do I place the args?

-cpu qemu64,-nx ?



udo said:
Hi,
in the VMID.conf like
Code: 
/etc/qemu-server/123.conf

BTW, the win2003 run with the 2.6.32-kernel but it runs also under 2.6.18+24 (for a short test of the smp-performance).

Udo
Click to expand...
 
I've added:

args: -cpu qemu64,-nx

at the end of the config:

name: W2K3EXCH2K3
ide2: local:iso/intelpro1000mt.iso,media=cdrom
bootdisk: ide0
ostype: w2k3
memory: 2048
sockets: 1
onboot: 1
cores: 2
ide0: local:101/W2K3EXCH2K3.qcow2
description: Windows 2003 R2 + Exchange 2003 SP2 mailserver
vlan0: e1000=DA:E1:4C:3F:51:B0
args: -cpu qemu64,-nx

I'll keep my fingers crossed (restarting the VM now).

EDIT: Still no improvements .... the Unknown devices are still there and when I try to uninstall and scan for new hardware changes, it gives me the same errors as in my first thread post :(


udo said:
Hi,
pick a line as you please ;-)

At the end or so.. it's don't matter.

Udo
Click to expand...
 
Last edited:
restart does not activate the setting. stop and start.
 
Hi Tom,

Isn't that the same as stopping the Windows environment and after that starting the environment from the Proxmox webinterface?

I'm currently trying your suggestion, but I was just asking myself if it makes any difference?

EDIT: Stopping and starting the VM gives the same behaviour on the Unknown device (CPU) ....

Do you have any other suggestions?

tom said:
restart does not activate the setting. stop and start.
Click to expand...
 
Last edited:
You must log in or register to reply here.
Top Bottom