From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] sparc64/virtio: unable to init msix vectors to 2
Date: Tue, 02 Sep 2014 13:37:53 +0100 [thread overview]
Message-ID: <5405BA21.6070004@ilande.co.uk> (raw)
In-Reply-To: <53FD7794.6030405@ilande.co.uk>
On 27/08/14 07:15, Mark Cave-Ayland wrote:
> Hi all,
>
> When creating a qemu-system-sparc64 machine with a virtio interface,
> both QEMU 2.1.0 and current git master emit the above warning:
>
> $ ./qemu-system-sparc64 -drive file=/tmp/file.txt,if=virtio,index=0
> -nographic
> qemu-system-sparc64: -drive file=/tmp/file.txt,if=virtio,index=0: unable
> to init msix vectors to 2
> OpenBIOS for Sparc64
> Configuration device id QEMU version 1 machine id 0
> kernel cmdline
> CPUs: 1 x SUNW,UltraSPARC-IIi
> UUID: 00000000-0000-0000-0000-000000000000
> Welcome to OpenBIOS v1.1 built on Aug 26 2014 12:48
> Type 'help' for detailed information
> Trying disk:a...
> No valid state has been set by load or init-program
>
> 0 >
>
> Is this harmless? At a superficial level, the interface seems to work if
> you boot with a virtio-enabled -kernel.
Ping? A quick look at the source code indicates that MSI setup for
virtio is only performed if nvectors > 0, and since the default value is
2 then this is why the error appears on the console.
From reading the relevant datasheets, I see no mention of MSI
interrupts which makes me think they may not be supported by the Sun
sabre bridge that QEMU emulates.
ATB,
Mark.
prev parent reply other threads:[~2014-09-02 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 6:15 [Qemu-devel] sparc64/virtio: unable to init msix vectors to 2 Mark Cave-Ayland
2014-09-02 12:37 ` Mark Cave-Ayland [this message]
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=5405BA21.6070004@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.