RE: [Xen-users] Getting Windows 2003 to run in multiple cores ???
Have you checked from your device manager that your windows is running
the SMP HAL? It might not be autodetected upon adding the second CPU
if Windows was initially installed with only one vcpu; If you'r system
says 'ACPI Uniprocessor PC' in the device manager (under Computer or
something), try updating the driver (in which case the ACPI
Multiprocessor PC would be found) or removing the device and then
rebooting (and again, the smp hal should get autodetected).
I've noticed that hardware changes do often require shutdown / xm
start (or even xm create) to get applied, too.
Another problem with W2k3 that I came by was running network in bridge
mode (as opposed to NAT) in Xen 3.2-1; if vif was using ioemu, it
would get added as tap0 (and tap1 and so forth) and apparently as
vif[domid].0 etc too, of which the tap was the working iface but the
scripts added only the non-working vif to brctl and the taps would
have to be added manually after startup.
This was addressed by using the GPL PV drivers, thankfully.
Quoting "Madhu Venugopal (vmadhu)" <vmadhu@xxxxxxxxx>:
Thanks for the response.
Unfortunately, "xm start" is not helping me either.
Should I reboot dom0 to get this working ?
I would like to keep it the last option to try as am facing
other issues immediately after the dom0 reboot.
Any other tricks to get multi-core working with Windows ?
BTW, I could not find "xe" command in my XEN installation.
Even after installing the "xe-cli" rpm file, it is failing
Consistently with the error message :
"Error: Connection refused (calling connect )"
From: James Harper [mailto:james.harper@xxxxxxxxxxxxxxxx]
Sent: Monday, August 03, 2009 4:40 PM
To: Madhu Venugopal (vmadhu); xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Getting Windows 2003 to run in multiple cores
> Installed Windows 2003 on XEN successfully (domain name : win1).
> I could not get it running in multiple cores though (tried vcpus=4).
> Windows taskmanager shows only 1 CPU always :-(.
This may not be your problem, but one thing that caught me out early
is that if you make a change to the config file and then do a 'xm
reboot' (or just do shutdown->restart in windows), the change isn't
picked up - it runs with the old config. You need to shut down the
and then 'xm start' it.
Another thing, on the first startup after changing from vcpus=1 to
vcpus=2 (or more), Windows needs to install the SMP HAL so it will say
something like "your hardware has changed and you need to reboot for
change to take effect".
Xen-users mailing list
Xen-users mailing list