Re: [Xen-devel] Bug: Windows 2003 fails to install on xen-unstable tip

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 23.04.13 at 13:52, George Dunlap <george.dunlap@xxxxxxxxxxxxx> wrote:
> On 23/04/13 12:33, Jan Beulich wrote:
>>>>> On 23.04.13 at 12:38, George Dunlap <george.dunlap@xxxxxxxxxxxxx> wrote:
>>> Do you not have boot images of Windows 2003 that you can test yourself?
>> In fact I don't have any non-machine-bound Windows images at
>> all. Let me go see whether my American colleagues could help out
>> here...
> 
> So I manually broke the patch down into 5 component parts (attached).  
> The installer works just fine for the first 3 -- the ones actually 
> mentioned in the patch changeset.

The first four then apparently. And the fifth is actually part of
what the third bullet point says. And I don't think it's really valid
to split the changes apart like this (e.g. pieces 1 and 3 necessarily
belong together).

>  It breaks when the handler is moved 
> into the generic IRQ timer code rather than having its own callback (I 
> think that's what's happening there, anyway).

That was the reason I always said if we need to revert, then
only this part (plus anything related to it - see above regarding
the splitting of the original patch). Yet I still don't see what's
wrong here, hence I'm hesitant to revert. In particular with the
latest debugging patch having shown that we do inject the
interrupt regularly. And with what you narrowed it down to it
must be the periodic interrupt code that the problem is in, yet
we by now also know it's not the injection of the interrupt alone
(or the interrupt asserted there doesn't really end up getting
injected into the guest).

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel