[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

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.  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

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          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
          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']

Any help appreciated on both questions.


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>

Attachment: ubuntu_native_dmesg.png
Description: PNG image

Attachment: ubuntu_guest_dmesg.png
Description: PNG image

Attachment: ubuntu_qemu-dm-log
Description: Binary data

Attachment: ubuntu_xl_dmesg
Description: Binary data

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.