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

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

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.

[0] http://www.intel.com/design/chipsets/datashts/290566.htm
[1] http://www.intel.com/design/chipsets/specupdt/290710.htm

>   I've again attached the qemu-dm-log, and xl
> dmesg log files, and additionally screenshots of the guest dmesg and
> also for comparison starting the same livecd natively on the box.
> 
> As a second question, I am not getting a NIC inside the guest for
> network access when using QEMU upstream, I see vif's added to my host
> machine:
> 
> vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
> vif1.0-emu Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:500
>           RX bytes:0 (0.0 B)  TX bytes:1272 (1.2 KB)
> 
> But nothing corresponding inside the guest. My guest's config file has:
> vif = ['bridge=xenbr0, type=ioemu']

Do you have the necessary driver inside the guest? IIRC the default
emulated NIC is the rtl8139.

It looks like you've asked for EMU only so I'm not sure why you have got
a vif interface, that might be a bug.

You should also check that your domU kernel is not unplugging the
emulated NIC -- there should be log messages to that effect if it is. I
don't recall which guest kernel you have but you could try
"xen_emul_unplug=never" on the command line.

> 
> Any help appreciated on both questions.
> 
> Thanks,
> David
> 
> 
> On Thu, Jul 19, 2012 at 8:27 AM, David Erickson <halcyon1981@xxxxxxxxx> wrote:
> > That may be the problem, to make sure my environment matched ivo's for
> > compiling I was using rev 25567 which is prior to that commit.  We're
> > headed out of town right now but I will try the tip when I get back
> > and see if it solves that problem.  I'll also try sending a NIC
> > through per Ian's suggestion.  Also another quick question, it seems
> > that upstream changed the way that NICs are assigned at create time, I
> > was seeing VIF's (ala XenServer style) created in my ifconfig but
> > seemingly not properly attached to my VM, or at least it wasn't
> > DHCP'ing correctly.  Is there different syntax or something I need to
> > change network wise when using qemu upstream?
> >
> > Thanks all for the help!
> > David
> >
> > On Thu, Jul 19, 2012 at 5:00 AM, Stefano Stabellini
> > <stefano.stabellini@xxxxxxxxxxxxx> wrote:
> >> On Thu, 19 Jul 2012, Ian Campbell wrote:
> >>> Yes, starting with Ubuntu is a good idea.
> >>>
> >>> The last line of the dmesg is:
> >>> (XEN) vmsi.c:108:d32767 Unsupported delivery mode 3
> >>> which sounds interesting, might be something Stefano knows about?
> >>
> >> What is your Xen version?
> >> Make sure you have the commit:
> >>
> >> Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> >> Date:   Tue Jul 3 13:39:01 2012 +0100
> >>
> >>     xen: event channel remapping for emulated MSIs
> >>
> >>     Linux PV on HVM guests remap all the MSIs onto event channels,
> >>     including MSIs corresponding to QEMU's emulated devices.  This patch
> >>     makes sure that we handle correctly the case of emulated MSI that have
> >>     been remapped, sending a pirq to the guest instead.
> >>
> >>     Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> >>     Tested-by: Deep Debroy <ddebroy@xxxxxxxxx>
> >>     Committed-by: Keir Fraser <keir@xxxxxxx>



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