public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Tony Smolar <tony.smolar-H+0wwilmMs3R7s880joybQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: problem upgrading to kvm-33
Date: Sun, 19 Aug 2007 11:53:23 +0300	[thread overview]
Message-ID: <46C80503.8060004@qumranet.com> (raw)
In-Reply-To: <46C10D0C.9080509-H+0wwilmMs3R7s880joybQ@public.gmane.org>

Tony Smolar wrote:
>> So you must use the standard HAL?
>>
>> First can you please provide the cpu type, we had some problems on AMD.
>> Second, what's the host's OS? Is it 32/64 bit? kernel version.
>> Third, does -no-kvm works?
>>
>> Some sanities just for making sure:
>> - Try running qemu with taskset -p 1
>> - Add -L SOURCE_REPOSITROY_PATH_FOR_QEMU_PC-BIOS directory for making
>> sure you use the right bios.bin
>>
>>  
>>
>>     
> Ok, I did some more testing,   The problem does NOT occur with 
> -no-kvm.   It also appeared somewhere between kvm-29 and kvm-31  (29 and 
> 30 didn't build for me).
>
> The good news is that the new version 34 does not seem to have this 
> problem,  I haven't tested it extensively yet.
>   

Good, thanks for checking it out.

> Lastly, what drove me to upgrade in the first place was that I was 
> experiencing minor bugs running "The Sims" under XP.       There would 
> be sound while the game is starting, but once the game starts, sound 
> stops working.   Also the mouse pointer would leave behind "residue" on 
> the screen which would be cleaned up every few seconds (I guess during a 
> refresh).   I also had problems losing sound with iTunes.   I am using 
> the es1370 setting for sound.  Like I said these were minor, and are 
> still present in kvm-34.
>   

Do these issues occur with -no-kvm?  How about with the default sound 
hardware?

-- 
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-19  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-11  3:18 problem upgrading to kvm-33 Tony Smolar
     [not found] ` <46BD2A91.6010106-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2007-08-12 15:52   ` Amit Shah
     [not found]     ` <200708122122.13947.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-12 17:19       ` Tony Smolar
2007-08-12 20:03         ` Izik Eidus
     [not found]         ` <46BF4139.3040100-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2007-08-12 21:13           ` Dor Laor
     [not found]             ` <64F9B87B6B770947A9F8391472E032160D2413DB-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-08-13  0:56               ` Tony Smolar
2007-08-14  2:01               ` Tony Smolar
     [not found]                 ` <46C10D0C.9080509-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2007-08-19  8:53                   ` Avi Kivity [this message]

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=46C80503.8060004@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=tony.smolar-H+0wwilmMs3R7s880joybQ@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