jonp Posted July 12, 2014 Share Posted July 12, 2014 All, Let me start by saying that this issue has been evading us for some time and we just recently found a way to recreate it consistently. For any individuals that are attempting to use Docker Containers AND PCI device pass through with KVM in a single host, please note: AUTO-STARTING YOUR CONTAINERS WILL CAUSE VFIO-BIND SCRIPTS TO RESPOND WITH A READ-ONLY ERROR TO THE DEVICE!!! Quite simply disabling auto-start of your containers until AFTER you've performed VFIO-BIND will resolve the problem. We have seen pretty consistent results in testing so far, but let us know if you're having problems. Quote Link to comment
botez Posted July 12, 2014 Share Posted July 12, 2014 This did the trick for me -- now I can do the vfio-bind. Thanks for the tip. Quote Link to comment
monkeytsar Posted August 14, 2014 Share Posted August 14, 2014 I don't have my docker containers set to auto start, i can disable docker all together and i still get this problem. root@Tower:~# vfio-bind 0000:07:00.0 ./vfio-bind: line 11: /sys/bus/pci/drivers/vfio-pci/new_id: Read-only file system I get it in XEN mode too now. Parsing config from windows.cfg libxl: error: libxl_pci.c:992:libxl__device_pci_reset: Failed to access reset path /sys/bus/pci/devices/0000:07:00.0/reset: Read-only file system Any Ideas? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.