kvm upgrade issue 1.2 to 1.3

[ERS]

Windows kvm machine fails to boot after 1.2 to 1.3 upgrade. Says there was a HW change (there was a reference to this on the wiki). Asks for the install CD, but when I insert it and try to boot from it, it just ignores it and fails anyway. Any idea on what the problem may be and how to fix it?

Thanks

 

[tom]

Windows kvm machine fails to boot after 1.2 to 1.3 upgrade. Says there was a HW change (there was a reference to this on the wiki). Asks for the install CD, but when I insert it and try to boot from it, it just ignores it and fails anyway. Any idea on what the problem may be and how to fix it?

Thanks

what windows version?

 

[ERS]

Windows server 2008 64-bit. Sorry, forgot that info.

Also, I made an error while evaluating the problem. The CD rom boots, but it doesn't run, with the same error. A 32 bit win 2008 server CD boots fine (we have both versions, depending on the memory requirements, we may use one or the other atop kvm), the 64bit one and the normal boot present the following error:

Windows failed to start. A recent hardware or softw
cause. To fix the problem:

1. Insert your windows instalation disk and rest
2. Choose your languahe settings, and then click
3. Click repair your computer

I can only read this because the java vnc viewer does not resize the screen anymore (I haven't use the nc trick to redirect vnc, probably works that way). The resize doesn't work with the CD install screen (32bit) either... so I guess that's another prob with this upgrade

 

[ERS]

Does anyone know anything that may help me?

 

[dietmar]

see http://www.proxmox.com/forum/showthread.php?t=1559

 

[ERS]

Thank you very much I actually read that thread before posting but, at the time, thought it didn't apply to me. Then I noticed the whole 64-bit issue (although, in my case, nothing showed up on the logs), but didn't make the correlation between the issues. Sorry for that and thanks once again. Now I have some random crashes (simmilar to what happened with 1.2 with the i5000 mem controller), but without a lead on the damn logs. Will look into it and post any helpful info I may find.