Date: Sun, 5 Aug 2007 21:57:39 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: John Nielsen <lists@jnielsen.net> Cc: freebsd-emulation@freebsd.org Subject: Re: qemu issues Message-ID: <20070806025738.GH77822@dan.emsphone.com> In-Reply-To: <200708052253.10904.lists@jnielsen.net> References: <20070805215329.07f0a062@vixen42> <200708052253.10904.lists@jnielsen.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Aug 05), John Nielsen said: > On Sunday 05 August 2007, Zane C.B. wrote: > > Any time I've used qemu recently, it exits with a 140 and prints out > > "Bad system call". > > > > Any ideas? > > Don't forget to load the aio kernel module on your host. Wouldn't returning ENOSYS be a lost nicer to the calling process than signaling SIGSYS? I always think of SIGSYS as a hint that you're trying to run a binary from a completely different OS, rather than just trying to use a valid syscall that just hasn't been enabled. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070806025738.GH77822>