-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Marek Marczykowski-Górecki: > On Wed, Jun 29, 2016 at 11:41:13PM +0200, HW42 wrote: >> HW42: >>> Marek Marczykowski-Górecki: >>>> On Tue, May 31, 2016 at 05:39:20AM +0200, HW42 wrote: >>>>> Marek Marczykowski-Górecki: >>>>>> On Sun, May 29, 2016 at 04:48:18AM +0200, HW42 wrote: >>>>>>> Andrew David Wong: >>>>>>>> On 2016-05-28 11:16, HW42 wrote: >>>>>>>>> Hi, >>>>>>>> >>>>>>>>> with Xen 4.6.1-15.fc20 (which got recently uploaded to the testing >>>>>>>>> repo) VMs with attached PCI devices don't boot anymore (at least on >>>>>>>>> my machine). >>>>>>>> >>>>>>>>> When I try to boot a VM with attached PCI devices it crashes >>>>>>>>> immediately. Attached the xen dmesg log of a crash. >>>>>>>> >>>>>>>>> Both dom0 and the VM are running the 4.1.24-9.pvops.qubes kernel. >>>>>> >>>>>> Exactly the same versions works fine for me... >>>>>> >>>>>> Do you have anything in console log of that VM? If not, try starting it >>>>>> in debug mode (this enables earlyprintk). >>> >>>>> Even with debug mode nothing on console. >>> >>>>> Interestingly attaching during runtime seems to work. >>> >>>> Even when no device was attached at startup at all? >>> >>> Yes. But I forgot to mention that to actually work I needed to change >>> the kernel options. When booting without any attached device and the >>> default kernel options I got this error when attaching a device at >>> runtime: >>> >>> kernel: xen:swiotlb_xen: Warning: only able to allocate 1 MB for software >>> IO TLB >>> kernel: xen:swiotlb_xen: Cannot allocate Xen-SWIOTLB buffer >>> (rc:-12) >>> >>> So I added the 'iommu=soft swiotlb=8192' manually. Then I could attach >>> the device at runtime and it worked. >>> >>>> Try booting with attached device, but with empty kernel options (remove >>>> default "iommu=soft swiotlb=8192"). >>> >>> Crashes like with the default options. >>> >>>> If this doesn't help, try Xen 4.6.1-15.56.fc20 from unstable repo, it >>>> has e820_host option disabled (almost the only change between those >>>> packages, besides Xen version itself). Sources are here: >>>> https://github.com/marmarek/qubes-vmm-xen/tree/bug2038 >>> >>> This version works! > >> When upgrading to R3.2 I discovered that this problem only seems to >> exists when booting with AEM. I.e.: > >> AEM, pci_e820_host=True => doesn't work >> AEM, pci_e820_host=False => works >> without AEM => works > > Interesting, are you also affected by the other memory related problem > with tboot (requirement of min_ram option to see all the memory)?
No, min_ram=0x2000000 doesn't seem to change anything. With tboot Xen uses about 6 MB less memory, which seems fine. -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXdFZQAAoJEOSsySeKZGgWfxEP/iNWzXxzYdOFAiVH8Qa+S2dN 5GnHi3UgImzEuXF0lGDIG5tcQdRddbXliCl49OWna2FZDgx/Cdhvpj8qM2N7bhAZ nSUZoPisSoHMGmM4TNXXHNKSfeL03dvzFcfFANJTk1TYjL10/97W28QCy1P7IPea xCuloTLthiq91RFbBjSy4ruNS/ApRIm8QikIMNbs+AvQCQex4wQaZ/SDr064qrqP yHD2FFTamabn+Oej2pueNPCH+9b9ox19V4m3VN/odUsKj1sh2jgm/s6KTUET2UFp 8XSjyXHv3cqQZIa8CpZnn9J74n3yo4+7MRKeXX62qwustZJR9FD3Hb7lHSLSCu0t wQHIH4NQ5Eec63fxuhhjY/B4e+W8iV+x7GlgJ+3cR2vVdYqmC08ZKd0rbZ1C86Vl kE5X+zWQ6+SxACL9UWh4xIHQNAyL3KXV2VkQNq3lUJ7p1t6km6PYsURbTVcPOoRW MgLrtZ+3t7ZMwd5zdxHR9P8rpCfwazNUv9MLCpW/ko15yxRQRLK9fDllDLKtGlMJ rsyXIflzYkM5ANuCtCY+n0BVgL4xL/mX4vazgQL99rIkMB6HhEJFRl7g2yjojAAc Ect6iopW+lh4pOfkHGn1LlUM4OXME0f9wvfmqLWM9IsT5JW59FTB2Rn8isPKrG5+ aRCTXPh+llOWrxQ/jbXv =PKTJ -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/f2b54bc0-8651-0809-89d9-534d71f47a41%40ipsumj.de. For more options, visit https://groups.google.com/d/optout.
