From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Vista 32 Premium 32 bit gets blue screen on boot Date: Thu, 23 Aug 2007 10:42:27 +0300 Message-ID: <46CD3A63.5040701@qumranet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Haydn Solomon Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Haydn Solomon wrote: > I've installed vista premium home 32 bit on previous versions of kvm, > namely 24-1 which is packaged with fedora 7. Since then I've removed > these packages and building kvm from releases from sourceforge > provided qumranet website. When I try to install vista premium home 32 > bit using kvm release 36 I'm getting blue screen. I'm running on a > dell 1720 core 2 duo, 2 GB ram. I'm running fedora 7 64-bit. The > previously installed windows xp ( installed using kvm release 35 ) is > running fine under release 36. I'm starting kvm with the following: > > /usr/local/kvm/bin/qemu-system-x86_64 \ > -hda vistahome.img \ > -m 400 \ > -no-rtc \ > -localtime \ > -boot d \ > -cdrom /home/hsolomon/isos/VISTA_32_PREMIUM.iso & > > The message from the blue screen is: > > ***STOP: 0X000000A5 ( 0X0001000B, 0X50434146, 0XFFD0502C, 0X00000000 ) > > Any feedback would be appreciated. Thanks and great piece of work here > guys. > Can you check which version of kvm causes the regression? If kvm-35 works and kvm-36 doesn't, try copying kvm-35's bios.bin (from qemu/pc-bios) to the install location (/use/local/share/qemu/bios.bin by default) -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/