From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: RE: [PATCH] remove _PS0 from the DSDTo Date: Mon, 28 Feb 2011 15:52:38 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini , "Kay, Allen M" Cc: Ian Campbell , "xen-devel@lists.xensource.com" , Jean Guyader List-Id: xen-devel@lists.xenproject.org On 28/02/2011 15:33, "Stefano Stabellini" wrote: > On Sat, 26 Feb 2011, Kay, Allen M wrote: >> Hi Stefano, >> >> I just tried this patch booting Win7-64bit in following two configurations: >> >> 1) Passthrough two NIC devices - onboard + PCIe E1000 >> 2) Passthrough SNB IGD + USB + audio + NIC >> >> In both cases, Windows failed to boot complaining about BIOS is not ACPI >> compliant. >> >> If I don't passthrough any devices, Windows can boot successfully. >> > > In that case we have a problem because I don't see any other way we > could fix the issue in a way that is acceptable for xen 4.1. > We could emulate PM capabilities in qemu even for devices that don't > support it or make the presence of _PS0 conditional on the presence of > PM capabilities on the devices. In both cases the fix will miss 4.1. Stefano: Your patch should have deleted the _PS3 method along with _PS0. It is an ACPI requirement that if you define an object to turn a device off (i.e., _PS3 in this case) then you must also supply a symmetric object to turn on the device (i.e., _PS0). So you must remove both, and there's no reason not to since they both only contain debug stuff. I suggest try again and see if _PS3 removal solves Allen's Windows boot issue. -- Keir > However there is a simple workaround for it: just disable acpi in the > config file of the VM. > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel