From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:49181) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URn69-0007KH-Ix for qemu-devel@nongnu.org; Mon, 15 Apr 2013 13:21:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1URn67-0005KJ-Ly for qemu-devel@nongnu.org; Mon, 15 Apr 2013 13:21:45 -0400 Received: from mail-ia0-x22e.google.com ([2607:f8b0:4001:c02::22e]:37198) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URn67-0005Jv-Hk for qemu-devel@nongnu.org; Mon, 15 Apr 2013 13:21:43 -0400 Received: by mail-ia0-f174.google.com with SMTP id o25so1777631iad.33 for ; Mon, 15 Apr 2013 10:21:42 -0700 (PDT) Date: Mon, 15 Apr 2013 12:21:37 -0500 From: Rob Landley In-Reply-To: (from atar4qemu@gmail.com on Sun Apr 14 14:49:53 2013) Message-Id: <1366046497.18069.102@driftwood> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Target-agnostic virtio? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Artyom Tarasenko Cc: Mark Cave-Ayland , qemu-devel On 04/14/2013 02:49:53 PM, Artyom Tarasenko wrote: > On Sun, Apr 14, 2013 at 11:59 AM, Mark Cave-Ayland > wrote: > > On 14/04/13 10:38, Artyom Tarasenko wrote: > > > >>> Do you have an example kernel .config and qemu command line =20 > showing how > >>> to > >>> use virtio for those? (Or a working sparc64 image you can point =20 > me to?) > >> > >> > >> Yes. Will send it to you as I get to my home machine. Can you make =20 > them > >> available on your site? > > > > > > Note that there is a section of test kernel images on the QEMU site =20 > at > > http://wiki.qemu.org/Testing, so if you could upload it to there =20 > that would > > be great :) >=20 > I don't see how to upload files. Can only edit the page. I've got build scripts that reproducibly create bootable system images =20 (with native compilers capable of building linux from scratch) for =20 several different variants of arm, mips, ppc32, sparc32, sh4, x86, and =20 x86-64. (It also builds m68k that runs under aranym but not qemu.) http://landley.net/aboriginal/about.html Basically go to http://landley.net/aboriginal/bin and grab a =20 system-image-*.tar.bz2 and ./run-emulator.sh in there. If you want an =20 extracted root-filesystem-*.tar.bz2 that's in there too, and the =20 various config files used to make it should be in /usr/src under there. If you want to build from source, grab the =20 http://landley.net/aboriginal/downloads most recent tarball, extract =20 it, and "./build.sh sparc" or similar. (If it breaks, tell me. I =20 collect reproducible bug reports.) I put out a new release about each time a kernel comes out. I don't =20 announce 'em here because I didn't think you were interested... > >> I have a Debian Wheezy RC1 / SPARC64 How-To, it would be nice to =20 > link to > >> the .config and kernel, so people would be able to install it just =20 > by > >> a few clicks. > > > > This is very interesting - could you post a link to the how-to? >=20 > I temporarily put it offline till I find a hosting for the kernel. For > some reason the standard Wheezy/sparc64 kernel is not stable under > QEMU. How is your kernel nonstandard, and what's the instability? I booted =20 the one you sent me but it went: netconsole: network logging started VFS: Cannot open root device "vda1" or unknown-block(253,1): error -6 Please append a correct "root=3D" boot option; here are the available =20 partitions: fd00 28212 vda driver: virtio_blk Kernel panic - not syncing: VFS: Unable to mount root fs on =20 unknown-block(253,1) Call Trace: Probably because the sparc root filesystem I have lying around is =20 squashfs. I can rebuild with ext2 but not on my lunch break. (I cleaned =20 out the build dir so it has to build the cross toolchains first, =20 underpowered netbook, takes a while...) I have various patches I need to apply to get stuff to work at http://landley.net/hg/aboriginal/file/tip/sources/patches and am always =20 working out more. (I push them upstream when I can, but the maintainers =20 aren't always interested.) (Currently the project is migrating from uClibc to musl libc, in part =20 because I can fish target support out of klibc and apply it to musl in =20 a way I can't for uClibc, so I can _finally_ get s390 and such to =20 work... But day job and my other projects eat lots of time so it goes =20 slowly...) Rob=