david.venhoff/QEMU-Nyx-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update pci-bridge-seat section in docs/multiseat.txt

Browse Source 
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
This commit is contained in:
Gerd Hoffmann 2015-07-01 10:59:47 +02:00
parent 5cce173323
commit 496eacaa67
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/multiseat.txt
View File

@ -123,7 +123,7 @@ Background info is here:
guest side with pci-bridge-seat guest side with pci-bridge-seat
------------------------------- -------------------------------
Qemu version FIXME and newer has a new pci-bridge-seat device which Qemu version 2.4 and newer has a new pci-bridge-seat device which
can be used instead of pci-bridge. Just swap the device name in the can be used instead of pci-bridge. Just swap the device name in the
qemu command line above. The only difference between the two devices qemu command line above. The only difference between the two devices
is the pci id. We can match the pci id instead of the device path is the pci id. We can match the pci id instead of the device path
@ -134,9 +134,10 @@ configuration:
SUBSYSTEM=="pci", ATTR{vendor}=="0x1b36", ATTR{device}=="0x000a", \ SUBSYSTEM=="pci", ATTR{vendor}=="0x1b36", ATTR{device}=="0x000a", \
TAG+="seat", ENV{ID_AUTOSEAT}="1" TAG+="seat", ENV{ID_AUTOSEAT}="1"
Patch with this rule will be submitted to upstream udev/systemd, so Patch with this rule has been submitted to upstream udev/systemd, was
long-term, when systemd with this lands in distros, things will work accepted and and should be included in the next systemd release (222).
just fine without any manual guest configuration. So, if your guest has this or a newer version, multiseat will work just
fine without any manual guest configuration.
Enjoy! Enjoy!