Describe the usage of devices 5853:0002 and 5853:C000. Signed-off-by: Frediano Ziglio <frediano.zig...@cloud.com> --- docs/man/xen-pci-device-reservations.7.pod | 9 +++++++++ 1 file changed, 9 insertions(+)
diff --git a/docs/man/xen-pci-device-reservations.7.pod b/docs/man/xen-pci-device-reservations.7.pod index 9ddf3a18ad..62f3bd2105 100644 --- a/docs/man/xen-pci-device-reservations.7.pod +++ b/docs/man/xen-pci-device-reservations.7.pod @@ -10,6 +10,8 @@ use of this is with device ID 0x0001 to advertise the Xen Platform PCI device - the presence of this virtual device enables a guest Operating System (subject to the availability of suitable drivers) to make use of paravirtualisation features such as disk and network devices etc. +XenServer, for Windows machines, presents Xen Platform device with device +ID 0x0002 instead of 0x0001. Some Xen vendors wish to provide alternative and/or additional guest drivers that can bind to virtual devices[1]. This may be done using the Xen PCI @@ -86,4 +88,11 @@ and unplug protocol. libxl provides support for creation of a single additional xen-pvdevice. See the vendor_device parameter in xl.cfg(5). +=item 2. + +XenServer, for Windows machines, presents a device with ID 0xC000. +This device is a placeholders for Windows update. +Device 0xC000 is presented with a Xen Platform PCI device, usually with ID +0x0002. + =back -- 2.34.1
