From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43622) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W3ReG-00054d-Q9 for qemu-devel@nongnu.org; Wed, 15 Jan 2014 09:40:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W3ReB-0000UJ-V3 for qemu-devel@nongnu.org; Wed, 15 Jan 2014 09:40:52 -0500 Received: from mail-la0-f42.google.com ([209.85.215.42]:44595) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W3ReB-0000UD-NF for qemu-devel@nongnu.org; Wed, 15 Jan 2014 09:40:47 -0500 Received: by mail-la0-f42.google.com with SMTP id n7so1486401lam.1 for ; Wed, 15 Jan 2014 06:40:40 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <52D69CDD.6000809@redhat.com> References: <1389775713-996-1-git-send-email-famz@redhat.com> <52D696F6.5020307@redhat.com> <52D69CDD.6000809@redhat.com> From: Peter Maydell Date: Wed, 15 Jan 2014 14:40:20 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH v16 0/9] Shared library module support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Kevin Wolf , Fam Zheng , Stefan Hajnoczi , Michael Tokarev , QEMU Developers , Alex Bligh , Miroslav Rezanina , =?UTF-8?Q?Llu=C3=ADs_Vilanova?= , Richard Henderson On 15 January 2014 14:36, Paolo Bonzini wrote: > Il 15/01/2014 15:20, Peter Maydell ha scritto: >>> > >>> > On RHEL6 I tried "qemu-system-x86_64 -cdrom >>> > http://boot.ipxe.org/ipxe.iso" and it worked, but it failed on Fedora. >>> > I don't know if it's a QEMU or curl bug. >> Doesn't work on MacOSX either: it says >> qemu-system-x86_64: -cdrom http://boot.ipxe.org/ipxe.iso: could not >> open disk image http://boot.ipxe.org/ipxe.iso: Unknown protocol > > Had you installed QEMU before starting it? Fam, I think you need a way > to override CONFIG_MODDIR (even an environment variable could do). No, I pretty much never install QEMU. I always run it out of a build directory. Module loading should IMHO work with similar semantics to the data dir we use for BIOS file loading: one of the places checked is relative to the executable path. Maybe we should also have better error messages for "I tried to load a module and this error is because I couldn't find one", so the user might be prompted to install the modules package his distro provides or investigate config if it's self-built, or whatever... >> (a non module build works, or at least sits there without giving an >> error message; I didn't feel like sitting there without a progress bar >> while it downloaded a whole ISO image, so I ^C'd it...) > > It's really hung. The ISO is just 1M. With RHEL6 it boots fine. Hrrm. I guess I should investigate that... thanks -- PMM