Understanding the code path for admin.vm.device.pci.Attach

I tried to add traces to dig firther but could not find where vm.log.info() and friends end up. I could find traces in qubes.log that look like they’ve been produced by such calls, but no output reached this file in several months (upgrade from 4.0.4 to 4.1beta ?). I finally resorted to writing to a separate file, and found out a bit more from there, but I still don’t see when the PCI device attachment gets effectively done.

  • template and standalone VMs get their libvirt xml written out on disk into /var/lib/xen/, including attached any PCI devices
  • AppVM’s OTOH do not, as if theirs was generated each time from qubes.xml (not really sure why, or even if that’s 100% accurate - @marmarek do you confirm ? it would be great to be able to look at the generated libvirt configuration here too!)