From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46962) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UWBIM-0004qM-Iz for qemu-devel@nongnu.org; Sat, 27 Apr 2013 16:00:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UWBIK-0005XN-TO for qemu-devel@nongnu.org; Sat, 27 Apr 2013 16:00:30 -0400 Received: from mail-lb0-f179.google.com ([209.85.217.179]:45832) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UWBIK-0005XI-MV for qemu-devel@nongnu.org; Sat, 27 Apr 2013 16:00:28 -0400 Received: by mail-lb0-f179.google.com with SMTP id t1so4580282lbd.24 for ; Sat, 27 Apr 2013 13:00:27 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1366164953.18069.111@driftwood> References: <1366164953.18069.111@driftwood> From: Artyom Tarasenko Date: Sat, 27 Apr 2013 22:00:06 +0200 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] Target-agnostic virtio? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rob Landley Cc: qemu-devel On Wed, Apr 17, 2013 at 4:15 AM, Rob Landley wrote: > On 04/14/2013 04:38:23 AM, Artyom Tarasenko wrote: >> >> On Sat, Apr 13, 2013 at 7:03 PM, Rob Landley wrote: >> > On 03/26/2013 02:34:50 AM, Artyom Tarasenko wrote: >> >> >> >> On Tue, Mar 26, 2013 at 1:52 AM, Rob Landley wrote: >> >> > Can the virtio things (serial, network, block, virtfs) be used on >> >> > arbitrary >> >> > targets yet? I.E. Can I use a virtio network device on arm, mips, >> >> > powerpc, >> >> > sparc... >> >> >> >> Yes. Moreover, for sparc64 the virtio network is currently the only >> >> way to have a network under Linux guest (and a virtio block is the >> >> only to have a disk under Linux guest). >> > >> > >> > Do you have an example kernel .config and qemu command line showing how >> > to >> > use virtio for those? (Or a working sparc64 image you can point me to?) >> >> Yes. Will send it to you as I get to my home machine. Can you make them >> available on your site? > > I plan to add a sparc64 target built from source to Aboriginal Linux. Good to hear that. The more use/test cases, the less bugs! Actually I was asking whether you would host a non-Aboriginal, foreign Debian kernel. But never mind, I figured it's better to fix QEMU to be able use a vanilla Debian kernel instead of building custom kernels. :-) So if you have more than one PCI / virtio device in your qemu-system-sparc64 setup, you may want to update your QEMU to today's git master. > For a lot of the 64-bit targets, actual 64 bit userspace support is > strangely lacking. For ppc64 they say to use ppc32, and I've been told that > about sparc64 as well. I don't know if this is an optimization or a > requirement. I have a 32 bit image, I'd like to test the 64 bit codepaths as > well... I guess it's rather an optimisation. At least I saw BusyBox working under QEMU before the sparc v8plus was fixed. Artyom -- Regards, Artyom Tarasenko linux/sparc and solaris/sparc under qemu blog: http://tyom.blogspot.com/search/label/qemu