[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] Add Xen platform PCI device version 2.

> -----Original Message-----
> From: Tim Deegan [mailto:tim@xxxxxxx]
> Sent: 19 June 2013 16:46
> To: Paul Durrant
> Cc: James Harper; Ian Campbell; qemu-devel@xxxxxxxxxx; xen-
> devel@xxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [PATCH] Add Xen platform PCI device version 2.
> At 11:23 +0000 on 19 Jun (1371641017), Paul Durrant wrote:
> > The problem is that the old Citrix PV drivers bind their version of
> > xenvbd directly to the platform device (id=1). The new PV drivers bind
> > their xenbus driver to their platform device, because to go onto
> > Windows Update you cannot have an installer and therefore cannot bind
> > to a root enumerated node. Now, if I post a version of xenbus onto
> > Windows Update that binds to id=1 then I cannot prevent VMs installed
> > with the old PV drivers from downloading the new version of xenbus and
> > using that (since it is newer)
> Is there room in the versioning to make sure that the drivers you push
> via Windows Update are always 'older' than any other PV drivers
> currently in circulation?

The scoring rules are quite complex and I have a feeling that Windows will 
always select a newer (by date) version of a driver. I'd need to check.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.