qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Redundant VDE network
Date: Tue, 9 Dec 2014 09:37:21 +0000	[thread overview]
Message-ID: <CAJSP0QXR6eRvmGMYo1iKGgdpmgQZO=oLU-dVsLCk1Jqf3daNqA@mail.gmail.com> (raw)
In-Reply-To: <548696D3.90003@yandex.ru>

On Tue, Dec 9, 2014 at 6:29 AM, Dmitry Antipov <dmantipov@yandex.ru> wrote:
> On 12/08/2014 08:53 PM, Stefan Hajnoczi wrote:
>
>> Try:
>>
>> qemu-system-sparc -m 256 \
>>      -netdev vde,sock=/tmp/vde0,id=vde0 \
>>      -device ne2k_pci,netdev=vde0 \
>>      -netdev vde,sock=/tmp/vde1,id=vde1 \
>>      -device ne2k_pci,netdev=vde1 \
>>      -hda vm0.img
>
>
> This works just fine for qemu-system-x86, but not for SPARC with lance NIC:
>
> qemu-system-sparc -m 256 \
>       -netdev vde,sock=/tmp/vde0,id=vde0 -device lance,netdev=vde0 \
>       -netdev vde,sock=/tmp/vde1,id=vde1 -device lance,netdev=vde1 \
>       -hda vm0.img
>
> qemu-system-sparc: -device lance,netdev=vde0: Parameter 'driver' expects
> pluggable device type
>
> It looks like PCI/sysbus emulation is incomplete/broken on SPARC.
> Assuming that x86 is OK, what SPARC-specific stuff should I check?

Is there a reason why you are using the old 32-bit SPARC machine types
instead of the more modern 64-bit SPARC machine types?

$ sparc-softmmu/qemu-system-sparc -M help
Supported machines are:
LX                   Sun4m platform, SPARCstation LX
SPARCClassic         Sun4m platform, SPARCClassic
SPARCbook            Sun4m platform, SPARCbook
SS-10                Sun4m platform, SPARCstation 10
SS-20                Sun4m platform, SPARCstation 20
SS-4                 Sun4m platform, SPARCstation 4
SS-5                 Sun4m platform, SPARCstation 5 (default)
SS-600MP             Sun4m platform, SPARCserver 600MP
Voyager              Sun4m platform, SPARCstation Voyager
leon3_generic        Leon-3 generic
none                 empty machine

$ sparc64-softmmu/qemu-system-sparc64 -M help
Supported machines are:
Niagara              Sun4v platform, Niagara
none                 empty machine
sun4u                Sun4u platform (default)
sun4v                Sun4v platform

I guess the SS-5 default machine type you are running doesn't have a PCI bus?

By the way, I have not tested the command-line because Fedora does not
have a vde package.  You are in niche territory with both SPARC and
vde, expect to either debug things yourself or file bugs (they may not
be addressed in a timely fashion).  Just want to set expectations for
what you will find.

Stefan

  parent reply	other threads:[~2014-12-09  9:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 15:00 [Qemu-devel] Redundant VDE network Dmitry Antipov
2014-12-08 17:53 ` Stefan Hajnoczi
2014-12-08 18:05   ` Dmitry Antipov
2014-12-09  6:29   ` Dmitry Antipov
2014-12-09  9:31     ` Mark Cave-Ayland
2014-12-09  9:37     ` Stefan Hajnoczi [this message]
2014-12-09 12:56       ` Dmitry Antipov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJSP0QXR6eRvmGMYo1iKGgdpmgQZO=oLU-dVsLCk1Jqf3daNqA@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=dmantipov@yandex.ru \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).