- Minor
Moving from 6.6.7 to either 6.7.0, 6.7.1 6.7.2 all have the same issue.
Everything works correctly, except starting a VM that has a GPU passed through. When starting this VM the system crashes.
I've attached diagnostics from both versions (6.6.7 and 6.7.2), just before starting the VM. Nothing was changed in the configuration between runs. There is another VM running fine in both cases. It has nothing passed through.
Also attached is the xml config of the problem VM.
I tailed the syslog in both versions when starting the VM, and they look the same.. In both there is some sort of DMA fault, but in 6.7.2, it works fine.
This is a tail of the syslog when starting the problem VM in 6.7.2:
Jul 5 09:33:23 Tower kernel: vfio-pci 0000:0a:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 5 09:33:23 Tower kernel: br0: port 3(vnet2) entered blocking state
Jul 5 09:33:23 Tower kernel: br0: port 3(vnet2) entered disabled state
Jul 5 09:33:23 Tower kernel: device vnet2 entered promiscuous mode
Jul 5 09:33:23 Tower kernel: br0: port 3(vnet2) entered blocking state
Jul 5 09:33:23 Tower kernel: br0: port 3(vnet2) entered forwarding state
Jul 5 09:33:24 Tower avahi-daemon[7313]: Joining mDNS multicast group on interface vnet2.IPv6 with address fe80::fc54:ff:fe13:8859.
Jul 5 09:33:24 Tower avahi-daemon[7313]: New relevant interface vnet2.IPv6 for mDNS.
Jul 5 09:33:24 Tower avahi-daemon[7313]: Registering new address record for fe80::fc54:ff:fe13:8859 on vnet2.*.
Jul 5 09:33:24 Tower kernel: vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x19@0x900
Jul 5 09:33:25 Tower kernel: vfio-pci 0000:00:1a.7: enabling device (0000 -> 0002)
Jul 5 09:33:25 Tower kernel: vfio_cap_init: 0000:00:1a.7 hiding cap 0xa
Jul 5 09:33:28 Tower kernel: vfio-pci 0000:0a:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 5 09:33:30 Tower kernel: DMAR: DRHD: handling fault status reg 2
Jul 5 09:33:30 Tower kernel: DMAR: [DMA Read] Request device [00:1a.7] fault addr eb000 [fault reason 06] PTE Read access is not set
Jul 5 09:33:30 Tower nginx: 2019/07/05 09:33:30 [crit] 7479#7479: *2093 connect() to unix:/var/tmp/Letsencrypt.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.101, server: , request: "GET /dockerterminal/Letsencrypt/ws HTTP/1.1", upstream: "http://unix:/var/tmp/Letsencrypt.sock:/ws", host: "tower"
Here is the tail of the sys log on startup of the same VM in 6.6.7 for comparison.
Jul 5 09:51:28 Tower kernel: vfio-pci 0000:0a:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 5 09:51:28 Tower kernel: br0: port 3(vnet2) entered blocking state
Jul 5 09:51:28 Tower kernel: br0: port 3(vnet2) entered disabled state
Jul 5 09:51:28 Tower kernel: device vnet2 entered promiscuous mode
Jul 5 09:51:28 Tower kernel: br0: port 3(vnet2) entered blocking state
Jul 5 09:51:28 Tower kernel: br0: port 3(vnet2) entered forwarding state
Jul 5 09:51:29 Tower avahi-daemon[6629]: Joining mDNS multicast group on interface vnet2.IPv6 with address fe80::fc54:ff:fe13:8859.
Jul 5 09:51:29 Tower avahi-daemon[6629]: New relevant interface vnet2.IPv6 for mDNS.
Jul 5 09:51:29 Tower avahi-daemon[6629]: Registering new address record for fe80::fc54:ff:fe13:8859 on vnet2.*.
Jul 5 09:51:29 Tower kernel: vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x19@0x900
Jul 5 09:51:30 Tower kernel: vfio-pci 0000:00:1a.7: enabling device (0000 -> 0002)
Jul 5 09:51:30 Tower kernel: vfio_cap_init: 0000:00:1a.7 hiding cap 0xa
Jul 5 09:51:32 Tower kernel: vfio-pci 0000:0a:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 5 09:51:34 Tower kernel: DMAR: DRHD: handling fault status reg 2
Jul 5 09:51:34 Tower kernel: DMAR: [DMA Read] Request device [00:1a.7] fault addr eb000 [fault reason 06] PTE Read access is not set
I've tried with and without "iommu=pt" in syslinux config.
Anybody have any ideas? Thanks
tower-diagnostics-6.7.2-20190705-1324.zip tower-diagnostics-6.6.7-20190705-0918.zip Problem VM Config.xml