Hi Michael,
It looks like this was never applied. Can it be, please?
On Wed, Dec 20, 2017 at 9:24 AM, Michael S. Tsirkin wrote:
> On Wed, Dec 13, 2017 at 10:07:12AM +, Stefan Hajnoczi wrote:
> > On Wed, Dec 13, 2017 at 12:26:44AM -0800, Ben Warren via Qemu-devel
> wrote:
On Wed, Dec 13, 2017 at 10:07:12AM +, Stefan Hajnoczi wrote:
> On Wed, Dec 13, 2017 at 12:26:44AM -0800, Ben Warren via Qemu-devel wrote:
> > From: Ben Warren
> >
> > Now that virtio-win guest drivers provided by non-Redhat vendors need to
> > use a different
On Tue, Dec 19, 2017 at 09:11:31PM -0800, Ben Warren wrote:
> Hi Michael,
>
> > On Dec 19, 2017, at 8:27 PM, Michael S. Tsirkin wrote:
> >
> > On Wed, Dec 13, 2017 at 12:26:44AM -0800, b...@skyportsystems.com wrote:
> >> From: Ben Warren
> >>
> >> Now
Hi Michael,
> On Dec 19, 2017, at 8:27 PM, Michael S. Tsirkin wrote:
>
> On Wed, Dec 13, 2017 at 12:26:44AM -0800, b...@skyportsystems.com wrote:
>> From: Ben Warren
>>
>> Now that virtio-win guest drivers provided by non-Redhat vendors need to
>> use
On Wed, Dec 13, 2017 at 12:26:44AM -0800, b...@skyportsystems.com wrote:
> From: Ben Warren
>
> Now that virtio-win guest drivers provided by non-Redhat vendors need to
> use a different Subsystem Vendor ID value, a way is needed to set this
> parameter on the host.
On Wed, Dec 13, 2017 at 12:26:44AM -0800, Ben Warren via Qemu-devel wrote:
> From: Ben Warren
>
> Now that virtio-win guest drivers provided by non-Redhat vendors need to
> use a different Subsystem Vendor ID value, a way is needed to set this
> parameter on the host.
From: Ben Warren
Now that virtio-win guest drivers provided by non-Redhat vendors need to
use a different Subsystem Vendor ID value, a way is needed to set this
parameter on the host. This works with all of the PCI-based devices,
such as NetKVM, viostor, vioscsi,