From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: cs 23453:4f4970d2848d beaks Win 7 Date: Thu, 1 Sep 2011 10:32:29 +0100 Message-ID: <1314869549.28989.86.camel@zakaz.uk.xensource.com> References: <4E5F43F2.6010601@amd.com> <1314867058.28989.84.camel@zakaz.uk.xensource.com> <4E5F4B7E.8090601@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E5F4B7E.8090601@amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christoph Egger Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Thu, 2011-09-01 at 10:08 +0100, Christoph Egger wrote: > On 09/01/11 10:50, Ian Campbell wrote: > > On Thu, 2011-09-01 at 09:36 +0100, Christoph Egger wrote: > >> cs 23453:4f4970d2848d breaks Win 7. It fails to initialize the CPUs > >> as shown in the device manager and this causes a BSOD on shutdown. > > > > Are you 100% sure it's that cset? > > Yes, I am. I found that c/s by bisecting. I used the latest xen-kernel > and toolchain, just replaced the hvmloader binary and booted a > Win7 guest (both 32bit and 64bit) with one vcpu. > > An hvmloader binary built from c/s 23452 works. > BTW: I use the rombios. > > > It moves a few things around but it doesn't actually remove anything. > > From a first glance, bios_info_setup() is called earlier with this c/s. I guess something could be clobbering that datastructure but there isn't much of interest in it now anyway. This stuff has subsequently been reorganised even more and moved around etc. I presume it is broken even for xen-unstable.hg 23809:85b29185c911? I'll see if I can repro. Can you post your guest cfg file please? Ian.