Re: vista install oddities

Re: vista install oddities

[Shahar Frank]

Milas,

What host are you using, and what Vista version is it? Is it an OEM
version or other non standard version?

Vista is known to use some new ACPI features, and in fact some licensing
options require ACPI 2.0 (not supported).

Shahar   

-------------------------------------------------------------------------
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/

Re: vista install oddities

[Wayde Milas]

Shahar Frank wrote:
> Milas,
>
> What host are you using, and what Vista version is it? Is it an OEM
> version or other non standard version?
>
> Vista is known to use some new ACPI features, and in fact some licensing
> options require ACPI 2.0 (not supported).
>
> Shahar   
>
>   
Using linux 2.6.21 (gentoo) as the host. Gentoo compiled with gcc 4.x 
but kvm compiled with gcc 3.x (kvm actually compiled fine with gcc 4.x 
but I saw all the warnings on configure so i  thought i might as well 
stick to 3).

Vista is the retail upgrade version of Ultimate. Comes in the black 
shiny largish case. Comes with 2 DVD's 32 and 64 bit vista. I am trying 
to install the 32 bit version. Trying to upgrade over the top of windows 
xp home 32 bit version, full retail. The full retail version of windows 
xp home 32 installs no problem.

Outside of kvm this upgrade path worked no problem.

Any other info I can supply please ask :)

-------------------------------------------------------------------------
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/

vista install oddities

[Wayde Milas]

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.

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.

I am able to attach screenshots or help debug this if given some idea how :)

Wayde

-------------------------------------------------------------------------
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/

Re: vista install oddities

[Avi Kivity]

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/

Re: vista install oddities

[Wayde Milas]

Avi Kivity wrote:
> 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.
>   
>   
>
Maybe... but define "different one". The ultimate upgrade comes with its 
own unique key and the only restriction that applies is that it must be 
installed upon a working windows install.

Something else I just tried. When not in kvm on an install I can hit 
next and NOT put a key. I get a popup warning me that I'll have to put 
in a key withing 30 days or the os will cease to function and I hit ok 
to proceed.

Inside kvm if I do the same thing I get the same popup, hit proceed, and 
I'm taken right back to the key activation screen and am not able to 
proceed.

Is it possible vista detects that its running virtulized and prevents 
any install because of it?


-------------------------------------------------------------------------
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/

Re: vista install oddities

[Avi Kivity]

Wayde Milas wrote:
>
>>
>> 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.
>>    
> Maybe... but define "different one". The ultimate upgrade comes with
> its own unique key and the only restriction that applies is that it
> must be installed upon a working windows install.

I don't know anything about this really.

>
> Something else I just tried. When not in kvm on an install I can hit
> next and NOT put a key. I get a popup warning me that I'll have to put
> in a key withing 30 days or the os will cease to function and I hit ok
> to proceed.
>
> Inside kvm if I do the same thing I get the same popup, hit proceed,
> and I'm taken right back to the key activation screen and am not able
> to proceed.
>
> Is it possible vista detects that its running virtulized and prevents
> any install because of it?
>

Maybe.  Non-upgrade installs do work.

-- 
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/