pci passthru doesn't work: '/dev/vfio/70' is not accessible: No such file or directory

Bug #1636247 reported by Waldemar Znoinski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned

Bug Description

kolla mitaka

config_strategy: "COPY_ALWAYS"
kolla_base_distro: "ubuntu"
kolla_install_type: "source"
openstack_release: "3.0.0"
kolla_internal_vip_address: "10.237.223.34"
network_interface: "eno1"
neutron_external_interface: "enp8s0f1"
enable_haproxy: "no"
tempest_image_id:
tempest_flavor_ref_id:
tempest_public_network_id:
tempest_floating_network_name:

ERROR
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] return self._domain.createWithFlags(flags)
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/eventlet/tpool.py", line 186, in doit
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] result = proxy_call(self._autowrap, f, *args, **kwargs)
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/eventlet/tpool.py", line 144, in proxy_call
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] rv = execute(f, *args, **kwargs)
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/eventlet/tpool.py", line 125, in execute
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] six.reraise(c, e, tb)
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/eventlet/tpool.py", line 83, in tworker
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] rv = meth(*args, **kwargs)
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/libvirt.py", line 1065, in createWithFlags
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
2016-10-24 16:16:00.228 1 ERROR nova.compute.manager [instance: c526225d-d533-4a7b-9d43-453528d3c73e] libvirtError: Path '/dev/vfio/70' is not accessible: No such file or directory

it looks like after binding a PCI device to vfio driver it's not appearing in /dev/vfio/ inside nova_libvirt container
restarting the above container replicates the status of /dev/vfio/ from the host and pci_passthru of that device(s) is then possible, problem occurs again if a new PCI device is about to be passthru to the VMs

Changed in kolla:
assignee: nobody → Waldemar Znoinski (wznoinsk)
Changed in kolla:
status: New → Triaged
importance: Undecided → Medium
Changed in kolla:
milestone: none → ocata-3
Changed in kolla:
assignee: Waldemar Znoinski (wznoinsk) → nobody
Changed in kolla:
milestone: ocata-3 → ocata-rc1
Changed in kolla:
milestone: ocata-rc1 → pike-1
Changed in kolla:
milestone: pike-2 → pike-3
Changed in kolla:
milestone: pike-3 → pike-rc1
Changed in kolla:
milestone: pike-rc1 → queens-1
Changed in kolla:
milestone: queens-2 → queens-3
Changed in kolla:
milestone: queens-3 → queens-rc1
Changed in kolla:
milestone: queens-rc1 → queens-rc2
Changed in kolla:
milestone: queens-rc2 → rocky-1
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.