From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:39481) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uci9j-00025v-GM for qemu-devel@nongnu.org; Wed, 15 May 2013 16:18:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uci9e-0006Sl-PR for qemu-devel@nongnu.org; Wed, 15 May 2013 16:18:35 -0400 Received: from mail-lb0-f176.google.com ([209.85.217.176]:59633) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uci9e-0006Sf-IT for qemu-devel@nongnu.org; Wed, 15 May 2013 16:18:30 -0400 Received: by mail-lb0-f176.google.com with SMTP id x10so2316823lbi.21 for ; Wed, 15 May 2013 13:18:29 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <79FF3BBC-C36C-4654-B661-7DE366D2D758@gmail.com> References: <20121229222619.26431.54663.malonedeb@soybean.canonical.com> <20130514105854.8523.19718.malone@gac.canonical.com> <79FF3BBC-C36C-4654-B661-7DE366D2D758@gmail.com> From: Peter Maydell Date: Wed, 15 May 2013 21:18:09 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [Bug 1094564] Re: images used as scsi disks not readable (qemu-system-arm, macos 10.8) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bug 1094564 <1094564@bugs.launchpad.net> Cc: qemu-devel@nongnu.org On 15 May 2013 19:02, Joss Reeves wrote: > Thanks so much for the patch and including me on the thread. I can > confirm that it did fix the problem running on a Linux host, but the OS > X bug cited by myself and the OP still remains elusive. It's rather > puzzling as I pulled from HEAD and built using the same options on both. QEMU itself actually hangs in my tests (the main loop is waiting to lock the iothread but it never does; the cpu thread seems to be stuck trying to do a bdrv_aio_cancel for the scsi device model). This should never happen, regardless of what the guest does... I suspect that if you configure on linux with --with-coroutine=sigaltstack you might then find they both behave the same (MacOSX can't do the ucontext coroutines we default to on linux). OTOH it might also involve some of MacOSX's slightly different signal behaviour. I'll continue to prod, though past experience is that MacOSX gdb is weirdly broken and things behave differently when run under it, which doesn't help :-( -- PMM