On x86 this looks pretty similar and at the place we have seen before:

45397      0.000073 readlink("/sys/bus/pci/devices/0000:21:00.1/iommu_group", 
"../../../../kernel/iommu_groups/"..., 4096) = 34 <0.000020>
45397      0.000053 openat(AT_FDCWD, "/dev/vfio/45", O_RDWR|O_CLOEXEC) = 31 
<0.000033>
45397      0.000060 ioctl(31, VFIO_GROUP_GET_STATUS, 0x7ffd774f80f8) = 0 
<0.000015>
45397      0.000041 openat(AT_FDCWD, "/dev/vfio/vfio", O_RDWR|O_CLOEXEC) = 32 
<0.000019>
45397      0.000046 ioctl(32, VFIO_GET_API_VERSION, 0x80002) = 0 <0.000011>
45397      0.000038 ioctl(32, VFIO_CHECK_EXTENSION, 0x3) = 1 <0.000012>
45397      0.000035 ioctl(31, VFIO_GROUP_SET_CONTAINER, 0x55758e6acec8) = 0 
<0.000011>
45397      0.000033 ioctl(32, VFIO_SET_IOMMU, 0x3) = 0 <0.000174>
45397      0.000199 ioctl(32, VFIO_DEVICE_GET_PCI_HOT_RESET_INFO or 
VFIO_IOMMU_GET_INFO or VFIO_IOMMU_SPAPR_TCE_GET_INFO, 0x7ffd774f8100) = 0 
<0.000012>
45397      0.000038 ioctl(14, KVM_CREATE_DEVICE, 0x7ffd774f8094) = 0 <0.000015>
45397      0.000039 ioctl(33, KVM_SET_DEVICE_ATTR, 0x7ffd774f80a0) = 0 
<0.000028>
45397      0.000054 ioctl(32, VFIO_DEVICE_PCI_HOT_RESET or VFIO_IOMMU_MAP_DMA, 
0x7ffd774f7f20) = 0 <0.000287>
45397      0.000312 ioctl(32, VFIO_DEVICE_PCI_HOT_RESET or VFIO_IOMMU_MAP_DMA, 
0x7ffd774f7f20) = 0 <0.000035>
45397      0.000058 ioctl(32, VFIO_DEVICE_PCI_HOT_RESET or VFIO_IOMMU_MAP_DMA, 
0x7ffd774f7f20) = 0 <0.000037>
45397      0.000060 ioctl(32, VFIO_DEVICE_PCI_HOT_RESET or VFIO_IOMMU_MAP_DMA, 
0x7ffd774f7f20) = 0 <0.334458>
45397      0.334593 ioctl(32, VFIO_DEVICE_PCI_HOT_RESET or VFIO_IOMMU_MAP_DMA, 
0x7ffd774f7f20) = 0 <0.000055>
45397      0.000088 ioctl(32, VFIO_DEVICE_PCI_HOT_RESET or VFIO_IOMMU_MAP_DMA 
<unfinished ...>
45402      9.654538 <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out) 
<10.000112>
45402      0.000144 madvise(0x7fd51236f000, 8368128, MADV_DONTNEED) = 0 
<0.000036>
45402      0.000076 exit(0)             = ?
45402      0.000074 +++ exited with 0 +++
45397     45.903415 <... ioctl resumed> , 0x7ffd774f7f20) = 0 <55.558237>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838575

Title:
  passthrough devices cause >17min boot delay

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Adding passthrough devices to a guest introduces a boot delay of > 17
  minutes. During this time libvirt reports the guest to be "paused".
  The delay does not seem to scale with the # of hostdevs - that is, 1
  hostdev causes about a 17min delay, while 16 only bumps that up to
  ~18min. Removing all hostdevs avoids the delay.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to