Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 22 Mar 2008 16:13:29 +0100 (CET)
From:      Oliver Fromme <olli@lurza.secnetix.de>
To:        nox@jelal.kn-bremen.de (Juergen Lock)
Cc:        freebsd-emulation@freebsd.org
Subject:   Re: qemu coredumps on RELENG_7
Message-ID:  <200803221513.m2MFDTXx058806@lurza.secnetix.de>
In-Reply-To: <200803202015.m2KKFTBX080186@saturn.kn-bremen.de>

next in thread | previous in thread | raw e-mail | index | archive | help

Juergen Lock wrote:
 > Oliver Fromme wrote:
 > > D Hill <d.hill@yournetplus.com> wrote:
 > > > Rick C. Petty wrote:
 > > > > Oliver Fromme wrote:
 > > > > > Kostik Belousov wrote:
 > > > > > > 
 > > > > > > Definitely,
 > > > > > > kldload aio
 > > > > > > before running qemu.
 > > > > > 
 > > > > > Thank you, that seems to solve the problem indeed.
 > > > > > Is that documented somewhere?  It's not in the manpage.
 > > > > > I think it should be in the manpage ...  would have
 > > > > > saved me quite some time.
 > > > > 
 > Actually it is also documented in the pkg-message of the port(s), but
 > apparently nobody reads that...

How are you supposed to read it when you install a bunch
of ports in batch mode, i.e. unattended (for example,
over night or during lunch break)?

Therefore I think that pkg-message is _not_ the correct
place for critical ionformation like that.

 > (OK I could patch a pointer to that
 > into the manpage, do other ports do that?)

There are several ports that patch port-specific things
into the manpage.  Prominent examples are gzip, jpeg,
bash, cdrtools and openssh-portable.

 >  Anyway, this was easier than I thought: (it didn't occur to me that
 > modfind(2) also finds modules that are statically linked into the kernel...)
 > 
 > Index: qemu/vl.c
 > @@ -8423,6 +8423,12 @@
 >      nb_nics = 0;
 >      /* default mac address of the first network interface */
 >  
 > +#ifdef __FreeBSD__
 > +    loadmodules(0, "aio", NULL);
 > +    if (modfind("aio") == -1)
 > +        fprintf(stderr, "warning: aio not (kld)loaded, may cause `Invalid system call' traps on disk IO\n");
 > +#endif

I prefer it didn't try to load the module itself.  That's
a decision I want to make myself.  But the message is
perfectly fine.  It would have saved me quite some time.

Thanks!

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

C++: "an octopus made by nailing extra legs onto a dog"
        -- Steve Taylor, 1998



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803221513.m2MFDTXx058806>