All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank van der Linden <Frank.Vanderlinden@Sun.COM>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: windows7 installer lockup with viridian=1
Date: Mon, 27 Apr 2009 15:52:52 -0600	[thread overview]
Message-ID: <49F62934.2050501@Sun.COM> (raw)
In-Reply-To: <f4527be0904261028u7fef3e1cg5e1165917e774ec2@mail.gmail.com>

Andrew Lyon wrote:
> On Sun, Apr 26, 2009 at 6:02 PM, Andrew Lyon <andrew.lyon@gmail.com> wrote:
>> Hi,
>>
>> I've been testing both 64 and 32 bit flavour of windows 7 on Xen since
>> the first public beta release, a few weeks ago I upgraded to Xen
>> unstable and added viridian=1 to all of my smp windows guests as it
>> prevents bsod bugcheck code 101 when under heavy load, today I tried
>> to upgrade my windows 7 hvm's to build 7077 and found that the
>> installer/bootloader locks up if viridian=1 is set.
>>
>> It is not the installer that locks up as such, its the windows 7
>> equivalent of the boot progress bar that all recent versions of
>> windows display before the graphics drivers are loaded and the display
>> switches to a higher resolution with the mouse active.

I can reproduce this on our Xen bits (which is 3.3.x plus some patches, 
including the viridian code).

When I modify the viridian code to not advertise the APIC-via-MSR 
capability, Windows 7 boots just fine. With it, it hangs at the same 
point you describe.

I don't recall that this happened when I initially tested Windows 7, so 
perhaps something changed in the vlapic code that triggers this issue.

- Frank

  reply	other threads:[~2009-04-27 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 17:02 windows7 installer lockup with viridian=1 Andrew Lyon
2009-04-26 17:28 ` Andrew Lyon
2009-04-27 21:52   ` Frank van der Linden [this message]
2009-04-28  8:04     ` Tim Deegan
2009-04-29  8:08       ` Tim Deegan
2009-05-23 12:59         ` Andrew Lyon
2009-05-23 13:28           ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49F62934.2050501@Sun.COM \
    --to=frank.vanderlinden@sun.com \
    --cc=andrew.lyon@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.