* [Qemu-devel] sparc64/virtio: unable to init msix vectors to 2
@ 2014-08-27 6:15 Mark Cave-Ayland
2014-09-02 12:37 ` Mark Cave-Ayland
0 siblings, 1 reply; 2+ messages in thread
From: Mark Cave-Ayland @ 2014-08-27 6:15 UTC (permalink / raw)
To: qemu-devel
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.
Many thanks,
Mark.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] sparc64/virtio: unable to init msix vectors to 2
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
0 siblings, 0 replies; 2+ messages in thread
From: Mark Cave-Ayland @ 2014-09-02 12:37 UTC (permalink / raw)
To: qemu-devel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-09-02 12:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).