From: Stefan Weil <sw@weilnetz.de>
To: Vikas Desai <vikas.desai@outlook.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Compiling QEMU x86_64 for windows 64 bit
Date: Thu, 26 Sep 2013 23:13:58 +0200 [thread overview]
Message-ID: <5244A396.9060008@weilnetz.de> (raw)
In-Reply-To: <5244856E.2060007@weilnetz.de>
Am 26.09.2013 21:05, schrieb Stefan Weil:
> Am 26.09.2013 13:23, schrieb Vikas Desai:
>> Hi,
>>
>> After some further testing I found that even the 32 bit binaries from
>> Stefan fail with the same error. I tried the 32 bit binaries from by
>> Eric Lassauge for version 1.6 and they work well. I have tried both 32
>> and 64 bit binaries from Stefan on 2 different environments, both
>> failing with same errors.
>>
>> When I just run the binaries with no disk image or any other options,
>> I get a proper window with the BIOS going through all drives looking
>> for a bootable device. Only when I have a valid executable image I get
>> the error. Also, in case of the test linux binary I get a kernel panic
>> on linux but qemu does not crash.
>>
>> What should I do further to debug this?
>>
>> Hi Stefan,
>>
>> Could you share what tools you use for the build? Any hints on what
>> more could I try?
>>
>> Thanks,
>> Vikas
> Hi Vikas,
>
> I also get the corouting assertion when I start my precompiled QEMU
> binary with an ISO image (Debian i386 netinstall).
> The error can be reproduced with Wine on Linux, too.
>
> There is no error when QEMU was configured with --enable-debug (which
> disables optimisation),
> nor is there an error when I just run the BIOS code (no disk, no cdrom).
> This explains why I did not
> notice the regression for Windows earlier.
>
> So we have to find the first version which shows that regression, either
> by testing older installers
> or by running git bisect.
>
> Cheers,
> Stefan
Summary:
Latest qemu-system-i386 for Windows fails with an assertion
(qemu-coroutine-lock.c:99)
if something more complex than the BIOS is executed. It works when it is
configured with
--enable-debug. This behaviour is identical for 32 bit and 64 bit
executables and can also
be reproduced using Wine. Older versions also fail, but with SIGSEGV
instead of an assertion.
This is the result of git bisect:
402397843e20e35d6cb7c80837c7cfdb19ede591 is the first bad commit
commit 402397843e20e35d6cb7c80837c7cfdb19ede591
Author: Paolo Bonzini <pbonzini@redhat.com>
Date: Tue Feb 19 11:59:09 2013 +0100
coroutine: move pooling to common code
The coroutine pool code is duplicated between the ucontext and
sigaltstack backends, and absent from the win32 backend. But the
code can be shared easily by moving it to qemu-coroutine.c.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
When I configure latest QEMU with --disable-coroutine-pool, it works!
I'll build new installers with this option until there is a bug fix
available.
Thanks for your bug report.
Stefan
next prev parent reply other threads:[~2013-09-26 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 7:05 [Qemu-devel] Compiling Qemu x86_64 for windows 64 bit Vikas Desai
2013-09-26 11:23 ` Vikas Desai
2013-09-26 19:05 ` Stefan Weil
2013-09-26 21:13 ` Stefan Weil [this message]
2013-09-27 4:44 ` [Qemu-devel] Compiling QEMU " Vikas Desai
2013-09-27 6:33 ` [Qemu-devel] Compiling Instructions for " Vikas Desai
-- strict thread matches above, loose matches on Subject: below --
2013-09-26 7:18 [Qemu-devel] Compiling Qemu " Vikas Desai
2013-09-26 6:43 Vikas Desai
2013-09-26 7:09 ` Manu
2013-09-26 1:53 Vikas Desai
2013-09-26 5:42 ` Stefan Weil
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=5244A396.9060008@weilnetz.de \
--to=sw@weilnetz.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vikas.desai@outlook.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 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.