From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony PERARD Subject: Re: LSI SAS2008 Option Rom Failure Date: Thu, 19 Jul 2012 11:57:10 +0100 Message-ID: <5007E806.3070404@citrix.com> References: <1342682536.18848.50.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1342682536.18848.50.camel@dagon.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Stefano Stabellini , David Erickson , jacek burghardt , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 19/07/12 08:22, Ian Campbell wrote: > On Thu, 2012-07-19 at 04:56 +0100, David Erickson wrote: >> Ok solved the compilation problem, the issue is the upstream configure >> script is testing for xen by compiling code that includes xs.h, >> however xs.h now throws a deprecated warning, and the configure script >> compiles with the flag that makes any warning an error. The solution >> is to replace all instances of xs.h in >> xen-unstable.hg/tools/qemu-xen-dir/configure with xenstore.h after the >> make has failed, then run it again and it will work. > > I think Anthony sent a patch upstream for this, but I suppose it hasn't > been committed yet -- Anthony is that right? Actually, no. I saw this issue (with the configure) only this week but haven't done anything for it, yet. Instead of modify configure, you could try to pass --disable-werror to configure. That actually why I haven't see the issue before. >> This also resolved the option/expansion ROM issue I was seeing, but >> unfortunately simultaneously caused the card to no longer function >> within the VM. The error I'm seeing now from dom0 is: >> >> cat /var/log/xen/qemu-dm-ubuntu.log >> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed >> (22 = Invalid argument): Internal error >> xen be: qdisk-5632: xc_gnttab_set_max_grants failed: Invalid argument > > AFAIK this one is harmless but could be fixed by updating your dom0 > kernel. > >> [00:05.0] pci_msix_write: Error: Can't update msix entry 0 since MSI-X >> is already enabled. >> [00:05.0] pci_msix_write: Error: Can't update msix entry 0 since MSI-X >> is already enabled. >> [00:05.0] pci_msix_write: Error: Can't update msix entry 0 since MSI-X >> is already enabled. >> [00:05.0] pci_msix_write: Error: Can't update msix entry 0 since MSI-X >> is already enabled. > > Anthony/Stefano, are MSIs supposed to work with upstream Qemu (the > upstream branch)? I think there should work, yes. > David also previous tried our branch of upstream qemu and had problems > there too -- I thought we'd backported the basic PCI passthrough support > but he was seeing > libxl: error: libxl_qmp.c:288:qmp_handle_error_response: > received an > error message from QMP server: Parameter 'driver' expects a > driver > name > (see upthread for more details) This is because the pci passthrough is not compiled in QEMU. I could maybe try to improve this error message. -- Anthony PERARD