public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Haydn Solomon <haydn.solomon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Vista 32 Premium 32 bit gets blue screen on boot
Date: Thu, 23 Aug 2007 10:42:27 +0300	[thread overview]
Message-ID: <46CD3A63.5040701@qumranet.com> (raw)
In-Reply-To: <b75785ba0708220952q24827d43k8b59d4a92eacb3a3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.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/

  parent reply	other threads:[~2007-08-23  7:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 16:52 Vista 32 Premium 32 bit gets blue screen on boot Haydn Solomon
     [not found] ` <b75785ba0708220952q24827d43k8b59d4a92eacb3a3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-22 17:29   ` Huang2, Wei
2007-08-23  7:42   ` Avi Kivity [this message]
     [not found]     ` <46CD3A63.5040701-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-23 17:55       ` Haydn Solomon
     [not found]         ` <b75785ba0708231055u7fbb13aendcaf7e7f05a95725-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-23 18:13           ` Avi Kivity
     [not found]             ` <46CDCE4F.9010208-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-26  0:50               ` Haydn Solomon
     [not found]                 ` <b75785ba0708251750m648ec0b8n94182cf38afc72ed-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-27 12:14                   ` Avi Kivity
     [not found]                     ` <46D2C010.7000104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-27 12:40                       ` Alexey Eremenko
2007-08-27 17:24                       ` Haydn Solomon

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=46CD3A63.5040701@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=haydn.solomon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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