Re: Running Windows 2k3 guest in ACPI multi-processor HAL mode (acpi=1)

Re: Running Windows 2k3 guest in ACPI multi-processor HAL mode (acpi=1)

[Julian Pawlowski]

Hey George,

thnx for answering :-)


Am 13.03.2007 14:08 Uhr schrieb "George Dunlap" unter <dunlapg@umich.edu>:

> I believe that 3.0.3 had some problems with ACPI/SMP... If you can,
> try 3.0.4, and let us know if you still have problems.

Actually I'm just about to do so but having problems installing Xen 3.0.4
from source on openSUSE 10.1.

I'll let you know the results.


Cheers,
Julian

Re: Running Windows 2k3 guest in ACPI multi-processor HAL mode (acpi=1)

[Julian Pawlowski]

Hello again,

>> I believe that 3.0.3 had some problems with ACPI/SMP... If you can,
>> try 3.0.4, and let us know if you still have problems.
> 
> Actually I'm just about to do so but having problems installing Xen 3.0.4
> from source on openSUSE 10.1.

I'm now running Novells Xen preview for SLES10 (based on Xen 3.0.4) on SuSE
Linux 10.1 successfully with acpi=1 and Windows 2003 Server as guest system.

Thank you guys :-)


Regards
Julian

Running Windows 2k3 guest in ACPI multi-processor HAL mode (acpi=1)

[Julian Pawlowski]

Hey guys,

I'm using standard openSUSE 10.2 Xen installation and would like to start a
Windows 2003 Server as guest with SMP support. So Windows would have to be
in ACPI-Multi-Processor HAL mode to support SMP correctly.

Unfortunately the virtual machine crashes every time I try to start the
installation of Windows with acpi=1 in the hvm configuration file. The blue
installation screen appears and a few seconds later the machine dies, I
guess it is the time when Windows Setup loads the ACPI supporting driver.

Installation with acpi=0 just works fine but of course the later machine has
no SMP enabled and therefore is not able to use the 4 assigned processor
cores. I just tried to replace the hal.sll in c:\windows\system32 with the
correct one with ACPI-SMP support and changed acpi=0 to acpi=1 in the vm
configuration file. Still no luck, the machine dies right after the windows
bootscreen appears :-(

So, how can I solve this?
Would it be better with Xen 3.0.4 as the openSUSE 10.2 standard is still
3.0.3 (with some modifications from Novell I think)?

Thanks a lot for your support!


Regards,

Julian Pawlowski