All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
Cc: kvm@vger.kernel.org
Subject: Re: WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1
Date: Wed, 06 Jan 2010 14:41:55 +0200	[thread overview]
Message-ID: <4B448513.6070505@redhat.com> (raw)
In-Reply-To: <4B44731A.4020405@siriusit.co.uk>

On 01/06/2010 01:25 PM, Mark Cave-Ayland wrote:
> Good news - I downloaded the userspace git repository and managed to 
> identify the offending commit between 0.12.1.1 and 0.12.1.2 using git 
> bisect:
>
>
> 4dad7ff32aa6dcf18cef0c606d8fb43ff0b939a1 is first bad commit
> commit 4dad7ff32aa6dcf18cef0c606d8fb43ff0b939a1
> Author: Avi Kivity <avi@redhat.com>
> Date:   Mon Dec 28 10:48:00 2009 +0200
>
>     Reinstate cpuid vendor override when kvm is enabled
>
>     Due to upstream qemu changes we no longer expose the host cpu 
> vendor id
>     to the guest.  This leads to failures when the syscall/sysenter 
> instructions
>     are used in compatibility mode.
>
>     Change the default to override when kvm is enabled.
>
>     Signed-off-by: Avi Kivity <avi@redhat.com>
>     Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>

Did you install using 0.12.1.1 and then run using 0.12.1.2?  If so, it 
seems Windows XP is not able to move from AMD to Intel.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2010-01-06 12:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 16:09 WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1 Mark Cave-Ayland
2010-01-05 17:15 ` Avi Kivity
2010-01-05 17:25   ` Mark Cave-Ayland
2010-01-06 11:25   ` Mark Cave-Ayland
2010-01-06 12:29     ` Marcelo Tosatti
2010-01-06 12:33       ` Gleb Natapov
2010-01-06 12:39         ` Gleb Natapov
2010-01-06 12:46       ` Mark Cave-Ayland
2010-01-06 12:41     ` Avi Kivity [this message]
2010-01-06 12:50       ` Mark Cave-Ayland
2010-01-06 12:54         ` Gleb Natapov
2010-01-06 13:14           ` Mark Cave-Ayland
2010-01-06 13:47             ` Yaniv Kaul
2010-01-06 12:56         ` Gleb Natapov
2010-01-06 13:02         ` Avi Kivity
2010-01-06 15:45           ` Mark Cave-Ayland
2010-01-06 17:08             ` Mark Cave-Ayland
2010-01-07  8:51               ` Avi Kivity
2010-01-07  9:57                 ` Mark Cave-Ayland
2010-01-07 12:34                   ` Avi Kivity
2010-01-07  8:50             ` Avi Kivity
2010-01-07  9:55               ` Mark Cave-Ayland
2010-01-24  7:40                 ` Avi Kivity
2010-01-25 15:15                   ` Mark Cave-Ayland
2010-01-25 15:27                     ` Avi Kivity
2010-01-25 16:06                       ` Mark Cave-Ayland
2010-01-25 16:09                         ` Avi Kivity
2010-01-25 16:18                           ` Mark Cave-Ayland
2010-01-25 16:22                             ` Avi Kivity
2010-01-25 16:54                               ` Mark Cave-Ayland
2010-01-25 17:37                                 ` Avi Kivity
2010-01-25 22:25                                   ` Mark Cave-Ayland
2010-01-26  6:18                                     ` Avi Kivity
2010-01-26  9:56                                       ` Mark Cave-Ayland

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=4B448513.6070505@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mark.cave-ayland@siriusit.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.