From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48147) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOnLx-0005xi-5o for qemu-devel@nongnu.org; Tue, 02 Sep 2014 08:38:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XOnLp-0001kW-NR for qemu-devel@nongnu.org; Tue, 02 Sep 2014 08:38:29 -0400 Received: from s16892447.onlinehome-server.info ([82.165.15.123]:40672) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOnLp-0001ge-Gr for qemu-devel@nongnu.org; Tue, 02 Sep 2014 08:38:21 -0400 Received: from 5ec2778a.skybroadband.com ([94.194.119.138] helo=[192.168.1.81]) by s16892447.onlinehome-server.info with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from ) id 1XOnLc-0002XH-1A for qemu-devel@nongnu.org; Tue, 02 Sep 2014 13:38:09 +0100 Message-ID: <5405BA21.6070004@ilande.co.uk> Date: Tue, 02 Sep 2014 13:37:53 +0100 From: Mark Cave-Ayland MIME-Version: 1.0 References: <53FD7794.6030405@ilande.co.uk> In-Reply-To: <53FD7794.6030405@ilande.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] sparc64/virtio: unable to init msix vectors to 2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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.