From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45829) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNjbr-0006yR-KV for qemu-devel@nongnu.org; Mon, 25 Jan 2016 11:03:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aNjbj-0001zn-MP for qemu-devel@nongnu.org; Mon, 25 Jan 2016 11:03:19 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46389) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNjbj-0001zY-Hh for qemu-devel@nongnu.org; Mon, 25 Jan 2016 11:03:11 -0500 References: <56A53AFB.20809@btg.co.nz> From: Cole Robinson Message-ID: <56A6473D.7090109@redhat.com> Date: Mon, 25 Jan 2016 11:03:09 -0500 MIME-Version: 1.0 In-Reply-To: <56A53AFB.20809@btg.co.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Windows Update Virtio Drivers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: James Watson , qemu-devel@nongnu.org On 01/24/2016 03:58 PM, James Watson wrote: > Hi, > > Over the last few months there have been various windows updates available > that cater for the virtio drivers required to run a virtualized windows guest > on Linux host, such as the fedora (latest branch) and suse virtio drivers. > This is been a hit and miss in terms of what works and in the case of the suse > drivers it actually broke some guests. > > Does any company or person have a plan to submit and maintain tested virtio > drivers through windows update program to avoid that randomness in submission > that is currently happening? > I don't think the suse or RH drivers were ever meant to be distributed with microsoft update, so I suspect this was a mistake or change on the Microsoft side. I believe other RH people are following up with Microsoft to figure out what happened. - Cole