Xen devel - Oct 2006 - Re: W2K3 Server Installation fails with ACPI=1 on

Hi Stefan,

The problem is cause by the VBD/VNIF PCI device in DM checked in
changeset 11160: PCI Device ID: 5853(Xen),class:ff80 (unknown)
ACPI Window does not understand this device and can not find device
driver associate with it.

To verify this just revert the patches of changset 11161/11160
We are working on the fix now, revert patch is not the solution
anyway...

Thanks,

Winston

-----Original Message-----

Date: Tue, 10 Oct 2006 16:32:29 -0400
From: Stefan Berger <stefanb@us.ibm.com>
Subject: Re: [Xen-devel] W2K3 Server Installation fails with ACPI=1 on
	xen-3.0.3-rc3 changeset 11732
To: Ralf Schenk <rs@databay.de>
Cc: xen-devel@lists.xensource.com
Message-ID:
	
<OF4683B6BE.3EB6CE9B-ON85257203.0070CFC5-85257203.0070D435@us.ibm.com>
Content-Type: text/plain; charset="us-ascii"

xen-devel-bounces@lists.xensource.com wrote on 10/10/2006 10:48:27 AM:
> Hello !
> 
> I installed Windows 2003 Server (RC2) sucessfully on xen 3.0.3-rc3
> changeset 11732. XEN and DOM0 is 64-bit X86_64 based.
> 
> The hardware I use is a Athlon 64 X2 3800+ (EE, Energy Efficient
> Version) on a simple ASUS M2N-MX Mainboard.
> 
> However I wasn''t able to run the installation with ACPI enabled in
the
> config file for the domain (acpi=1). The setup procedure simply
freezes
> after loading all the drivers.
> 
If you comment the ''acpi=1'' line it should work. ACPI is
enabled anyway.

-- Stefan
****************

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> The problem is cause by the VBD/VNIF PCI device in DM checked in
> changeset 11160: PCI Device ID: 5853(Xen),class:ff80 (unknown)
> ACPI Window does not understand this device and can not find device
> driver associate with it.
> 
> To verify this just revert the patches of changset 11161/11160
> We are working on the fix now, revert patch is not the solution
> anyway...
I just tried this, and as far as I can see cset 11161 doesn''t make any
difference to the behaviour, while 11160 is fairly obviously
irrelevant to this kind of thing.

With or without 11161, I see guests crashing with

(XEN) sh error: sh_page_fault__shadow_3_guest_2(): disabled-APIC access: not
supported
(XEN) .domain_crash called from multi.c:3197
(XEN) Domain 3 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    0008:[<000000008081d1ac>]
(XEN) RFLAGS: 0000000000010086   CONTEXT: hvm
(XEN) rax: 00000000ffd01000   rbx: 0000000000000000   rcx: 00000000ffdff120
(XEN) rdx: 00000000fec00000   rsi: 00000000ffd03034   rdi: 0000000000000000
(XEN) rbp: 0000000000060aa4   rsp: 0000000000060a84   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 0000000080050033   cr4: 0000000000000651
(XEN) cr3: 0000000000fd97a0   cr2: 0000000000000000
(XEN) ds: 0023   es: 0023   fs: 0030   gs: 0000   ss: 0010   cs: 0008
qemu-dm[5399]: segfault at 00002aaba96ec000 rip 00002ab993166fe0 rsp
00007fffff912188 error 6

(This is using a 64 bit host, but I see a similar crash with 32 and
32p hosts).

Just to confirm, 11161 in xen-unstable.hg is

# HG changeset patch
# User chris@kneesaa.uk.xensource.com
# Date 1155812483 -3600
# Node ID 5c1021595e3ce923ff11e338172d4639da2aecb5
# Parent  5e3166de7120f474903d58bd74b7e2d12c3d8ea7
[qemu] Add the xen platform device to the qemu PCI bus.
Useful functionality will come later.

Signed-off-by: Steven Smith <ssmith@xensource.com>
Signed-off-by: Christian Limpach <Christian.Limpach@xensource.com>


and 11160 is


# HG changeset patch
# User ssmith@weybridge.uk.xensource.com
# Date 1155815205 -3600
# Node ID 5e3166de7120f474903d58bd74b7e2d12c3d8ea7
# Parent  24827cb8a94596987284c4b934365165468949a2
[NET] Fix ``rx->offset: 10, size: 4294967295'''' bug.

Signed-off-by: Steven Smith <sos22@cam.ac.uk>


These are the csets you''re talking about, yes?

Steven.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel