From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: HVM DomU, msi_translate=0, MSI/MSI-X PCI passthrough fails. Date: Mon, 29 Nov 2010 11:36:35 -0500 Message-ID: <20101129163635.GA20417@dumpdata.com> References: <20101112171058.GA29875@campbell-lange.net> <20101112222215.GC26189@dumpdata.com> <3A9FD6B4-B741-4BAA-90C9-E3CA1143EA7A@campbell-lange.net> <20101115171543.GB7414@dumpdata.com> <20101115172309.GA30777@campbell-lange.net> <20101115174413.GA8227@dumpdata.com> <20101115175626.GA31636@campbell-lange.net> <20101124175926.GA17565@campbell-lange.net> <20101124202842.GA28222@dumpdata.com> <20101126111520.GA17221@campbell-lange.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20101126111520.GA17221@campbell-lange.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mark Adams , Stefano Stabellini , anthony.perard@citrix.com, yunhong.jiang@intel.com, yuan.b.liu@intel.com Cc: "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" , "JBeulich@novell.com" List-Id: xen-devel@lists.xenproject.org > > In my new test setup, I have seen some strange behaviour. 1 of the HVM's > (with identical config in dom0 and domU) suddenly would not allow the > igb driver to be loaded in domU, even though the device was visible in Let's create a new thread for this other issue. > lspci. Shutting the machine down, removing the power cord, waiting 5 > seconds then plugging it in again corrected that issue - Is this > possibly a motherboard bug? I have also disabled the SR-IOV > functionality in the BIOS incase this is causing any issues. > > In addition, to try to correct the MSI issue noted above, I have changed > my pci= line to the following: > > pci=[ '08:00.0,msitranslate=0', '08:00.1,msitranslate=0' ] With the msi_translate=1 turned on the DomU HVM guests did work, right? > > This has stopped the "already in use on device" log, and the devices > appear to show correctly in the domU. Is it safe to disable > msitranslate? as I understand it, its for allowing multifunction devices > to be seen as such in domU. Is that correct? > > I haven't been able to reproduce the dropped raid issue yet, but I am > awaiting delivery of the Red-Fone boxes (ISDN VoIP) which seem to cause > this due to their very high interrupt usage (2000 per second). OK. > > In the mean time, I can see the following in the qemu-dm logs now with > the msitranslate=0 enabled. Is it anything to worry about? Well, the "Error" ones are pretty bad, thought I am having a hard time understanding what it means. Lets copy some of the QEMU folks on this. > pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.0][Offset:14h][Length:4] > pt_ioport_map: e_phys=ffff pio_base=e880 len=32 index=2 first_map=0 > pt_ioport_map: e_phys=c220 pio_base=e880 len=32 index=2 first_map=0 > pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:06.0][Offset:14h][Length:4] > pt_ioport_map: e_phys=ffff pio_base=ec00 len=32 index=2 first_map=0 > pt_ioport_map: e_phys=c240 pio_base=ec00 len=32 index=2 first_map=0 > pt_msix_update_one: Update msix entry 0 with pirq 4f gvec 59 > pt_msix_update_one: Update msix entry 1 with pirq 4e gvec 61 > pt_msix_update_one: Update msix entry 2 with pirq 4d gvec 69 > pt_msix_update_one: Update msix entry 3 with pirq 4c gvec 71 > pt_msix_update_one: Update msix entry 4 with pirq 4b gvec 79 > pci_msix_writel: Error: Can't update msix entry 0 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 0 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 0 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 1 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 1 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 1 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 2 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 2 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 2 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 3 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 3 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 3 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 4 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 4 since MSI-X is already function. > pci_msix_writel: Error: Can't update msix entry 4 since MSI-X is already function. > > > > > Not yet. Need to serial log of the Linux kernel and the Xen hypervisor when your > > machine is toast. I mentioned in the previous email the key sequences - look on Google > > on how to pass in SysRQ if you are using a serial concentrator. > > I will do this when I can get the machine to crash. > > Best Regards, > Mark > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel