public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: kvm@vger.kernel.org, Avi Kivity <avi@qumranet.com>,
	Rik van Riel <riel@surriel.com>, Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [Regression] kvm-userspace: VM freezes after booting FreeDOS
Date: Thu, 10 Jul 2008 15:02:40 -0500	[thread overview]
Message-ID: <48766AE0.2050400@codemonkey.ws> (raw)
In-Reply-To: <52d4a3890807101252h13c24b0ej35b4af71ac6b5b58@mail.gmail.com>

Mohammed Gamal wrote:
> On Thu, Jul 10, 2008 at 7:31 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>   
>> Mohammed Gamal wrote:
>>     
>>> After updating my kvm-userspace tree to the latest git tree. I am no
>>> more able to run FreeDOS. The VM freezes after choosing any of the
>>> boot options. I am running both latest kvm.git and kvm-userspace.git
>>>
>>>       
>> Can you bisect to the commit that broke it?
>>
>> Regards,
>>
>> Anthony Liguori
>>     
>
> I did, it seems that commit 04c3265c95c12e7c6e73cfd07357c05db6a1bda8
> caused it. Everything works fine after I reverted it.
>   

Thats:

commit 04c3265c95c12e7c6e73cfd07357c05db6a1bda8
Author: Jan Kiszka <jan.kiszka@web.de>
Date:   Fri May 16 09:21:47 2008 +0200

    kvm: qemu: consolidate kvm_eat_signal
   
    With the io thread signals are rare.  Remove looping over
    kvm_eat_signal and fold everything into kvm_main_loop_wait.
   
    Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
    Signed-off-by: Avi Kivity <avi@qumranet.com>


Hrm, that's disturbing.  Unfortunately, the patch is a bit more than 
just code motion.  It does change the number of times the lock is 
released and makes some minor changes to the code.  Nothing obvious that 
would cause the breakage without digging into it.

How did you create your freedos image?  I'd like to try and figure out 
what the problem is here since it may be causing other issues.

Regards,

Anthony Liguori

> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  reply	other threads:[~2008-07-10 20:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 15:47 [Regression] kvm-userspace: VM freezes after booting FreeDOS Mohammed Gamal
2008-07-10 15:48 ` Mohammed Gamal
2008-07-10 16:31 ` Anthony Liguori
2008-07-10 19:52   ` Mohammed Gamal
2008-07-10 20:02     ` Anthony Liguori [this message]
2008-07-10 20:32       ` Mohammed Gamal
2008-07-10 20:33         ` Mohammed Gamal
2008-07-10 21:22         ` Jan Kiszka
2008-07-10 22:59           ` Mohammed Gamal
2008-07-11 10:53             ` Jan Kiszka
2008-07-11 14:55               ` Mohammed Gamal
2008-07-12 11:19                 ` Jan Kiszka
2008-07-13  7:54                   ` Avi Kivity
2008-07-13  9:09                     ` Jan Kiszka
2008-07-13  9:26                       ` Mohammed Gamal
2008-07-13 10:08                         ` Avi Kivity
2008-07-13  9:55                       ` Avi Kivity

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=48766AE0.2050400@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=m.gamal005@gmail.com \
    --cc=riel@surriel.com \
    /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