public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Wayde Milas <wmilas-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: vista install oddities
Date: Wed, 06 Jun 2007 09:28:39 +0300	[thread overview]
Message-ID: <46665417.4040107@qumranet.com> (raw)
In-Reply-To: <4665F0F4.4050803-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.org>

Wayde Milas wrote:
> This is a weird one. Using kvm27. I am able to install and run winxp 32 
> bit perfectly. The problem arises when I try and run my Vista Ultimate 
> upgrade. You cannot cold boot the upgrade and install on a blank drive 
> because when you enter the activation code, the software checks to make 
> sure there is a valid version of windows already installed.
>
> Let me outline the way it works:
>
> Base metal:
> * Empty drive, vista installer will gripe that there is no windows 
> installed and that the key entered is for upgrade only.
> * Windows installed installer will upgrade.
>
> kvm/quem
> * Empty drive, vista installer will gripe that it cannot verify the 
> entered key. Note that its not saying that its a bad key.
> * Windows installed installer grips that it cannot verify the entered key.
>
> I'm at a loss on how to debug this one. It obviously has something to do 
> with kvm/quem since the process works when running native.
>   

This is probably some kind of copy protection device, it's making sure
you're upgrading to the same machine and not to a different one.  So
most likely this is by design.
  
> Oh also something else to note.. the upgrader refuses to even get to the 
> key activation screen if the ACPI in XP has been disabled... (Ie the 
> ACPI workaround). It says it needs an ACPI capable machine to install. 
> Switching the driver back to ACPI fixes this.
>   

The acpi workaround is only for Windows XP and Windows 2000.  Windows
Vista won't work without acpi (but on the other hand, seems to suffer
much less from it).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  parent reply	other threads:[~2007-06-06  6:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 23:25 vista install oddities Wayde Milas
     [not found] ` <4665F0F4.4050803-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.org>
2007-06-06  6:28   ` Avi Kivity [this message]
     [not found]     ` <46665417.4040107-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-06 11:46       ` Wayde Milas
     [not found]         ` <46669EA7.801-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.org>
2007-06-06 13:47           ` Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2007-06-07  9:40 Shahar Frank
     [not found] ` <64F9B87B6B770947A9F8391472E032160C26FEE6-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-06-07 12:14   ` Wayde Milas

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=46665417.4040107@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=wmilas-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox