qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] unable to boot systemrescuecd with tcg only?


From: Richard Henderson
Subject: Re: [Qemu-devel] unable to boot systemrescuecd with tcg only?
Date: Wed, 17 Apr 2013 09:37:54 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5

On 2013-04-16 00:32, Aurelien Jarno wrote:
On Tue, Apr 16, 2013 at 12:03:10AM +0200, Aurelien Jarno wrote:
On Tue, Apr 16, 2013 at 12:36:36AM +0300, Michael S. Tsirkin wrote:
On Mon, Apr 15, 2013 at 06:17:18PM +0200, Paolo Bonzini wrote:
Il 15/04/2013 17:02, Paolo Bonzini ha scritto:
Il 15/04/2013 11:18, Michael S. Tsirkin ha scritto:
On Mon, Apr 15, 2013 at 11:53:12AM +0300, Michael S. Tsirkin wrote:
Get system rescue CD version 2.8.0 here:
http://www.sysresccd.org/Sysresccd-versions

Verify md5 checksum: 450305b2c3ac12d5c97ff849ca178586

Note: tried version 2.1.0, that boots fine.
Tried version 3.5.0, that hangs on boot
(or maybe it's just too slow? gave up after 15 min).
In all cases -enable-kvm makes it work fine.

Reproduced it too (by chance :)) with Fedora 16.  Trying to bisect now.

Hmm, no, must be a different thing.  It was in a "seemingly innocuous"
patch at the top of my tree, and system rescue CD works for me.

2.0.8?

Hmm maybe the issue is I'm on a 32 bit host ...


It's an important information. With it I am able to reproduce the issue.


I have bisected the issue to:

| f437d0a3c24e471a855da33a086fe529e09a06af is the first bad commit
| commit f437d0a3c24e471a855da33a086fe529e09a06af
| Author: Richard Henderson <address@hidden>
| Date:   Tue Feb 19 21:06:31 2013 -0800
|
|     target-i386: Use movcond to implement shiftd.
|
|     With this being all straight-line code, it can get deleted
|     when the cc variables die.
|
|     Signed-off-by: Richard Henderson <address@hidden>


Ah. I'll see what I can do. Downloading 350M might not be possible while I'm traveling though, so any help producing a reduced test case would be appreciated.


r~



reply via email to

[Prev in Thread] Current Thread [Next in Thread]