Re: [Xen-devel] LSI SAS2008 Option Rom Failure

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2012-07-31 at 10:35 +0100, Jan Beulich wrote:
> >>> On 31.07.12 at 11:04, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> > On Tue, 2012-07-31 at 08:35 +0100, David Erickson wrote:
> >> Just got back in town, following up on the prior discussion.  I
> >> successfully compiled the latest code (25688 and qemu upstream
> >> 5e3bc7144edd6e4fa2824944e5eb16c28197dd5a), but am still having
> >> problems during initialization of the card in the guest, in particular
> >> the unsupported delivery mode 3 which seems to cause interrupt related
> >> problems during init.
> > 
> > The log has "(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3"
> > 
> > mode 3 in this context appears to be dest__reserved_1, which corresponds
> > to the IOAPIC datasheet I'm looking at[0], which shows that DELMOD=3 is
> > reserved.
> > 
> > The specification update[1] doesn't seem to add anything in this regard.
> > 
> > So either I've missed another update, we are mis-emulating something
> > resulting in an invalid mode or Linux/the LSI ROM are using an
> > unspecified IOAPIC mode. Perhaps Jan or Andrew have some idea which it
> > is.
> 
> At a first glance I would assume this to be the same problem
> that was recently fixed for running with qemu-traditional by
> Stefano. See 
> http://xenbits.xen.org/gitweb/?p=staging/qemu-xen-unstable.git;a=commit;h=ce6d9b1b2f9c6a5ca2500e03d0ef8b453bc4bf53
> (and the earlier thread leading there; didn't check whether this
> applies to upstream qemu at all). Later he also provided a full
> patch, but I don't even see this in our traditional tree, yet -
> Ian(J)?

Isn't the link above our traditional tree?

Anyhow, it's a plausible theory.

David, as a workaround I think you can add "pci_msitranslate=0" to the
guest configuration file.

Ian.
> 
> Jan
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel