Re: [Qemu-devel] Target-agnostic virtio?

[Blue Swirl]

On Wed, Apr 17, 2013 at 2:15 AM, Rob Landley <address@hidden> wrote:
> On 04/14/2013 04:38:23 AM, Artyom Tarasenko wrote:
>>
>> On Sat, Apr 13, 2013 at 7:03 PM, Rob Landley <address@hidden> wrote:
>> > On 03/26/2013 02:34:50 AM, Artyom Tarasenko wrote:
>> >>
>> >> On Tue, Mar 26, 2013 at 1:52 AM, Rob Landley <address@hidden> 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.
>
> 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...

It's a sort of optimization, the pointers are smaller. OpenBSD/sparc64
takes a different approach, every binary is 64 bits. Would it be hard
to make Aboriginal *BSD? ;-)

>
>
>> I have a Debian Wheezy RC1 / SPARC64 How-To, it would be nice to link to
>> the .config and kernel, so people would be able to install it just by
>> a few clicks.
>
>
> I have http://landley.net/aboriginal/about.html
>
> Rob
>