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

[David Erickson <halcyon1981@xxxxxxxxx>]

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.

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

I've attached the output of xl dmesg and the screenshot of the dmesg
error within my test Ubuntu domu (I don't know how to debug Solaris as
well so I figure Ubuntu is a good place to verify pass through
functionality first).  My domU VM conf file:

builder='hvm'
device_model_version="qemu-xen"
bios="seabios"
memory = 2048
vcpus=2
name = "ubuntu"
vif = ['bridge=xenbr0, type=ioemu']
disk = [
        'file:/home/derickso/ubuntu-11.10-desktop-amd64.iso,ioemu:hdc:cdrom,r'
        ]
boot="d"
vnc=1
vnclisten="0.0.0.0"
vncdisplay=1
#pci=['02:00.0']
pci=['02:00.0,msitranslate=1,power_mgmt=1,permissive=1']
xen_platform_pci=1

I tried both ways for configuring the PCI pass through, and
disabling/enabling xen_platform_pci, didn't make a difference.

Suggestions welcome!

Thanks,
David


On Wed, Jul 18, 2012 at 6:32 PM, jacek burghardt
<jaceksburghardt@xxxxxxxxx> wrote:
> There is solution
> http://xen.1045712.n5.nabble.com/Upstream-Qemu-With-Xen-configuration-problem-td4561779.html
> I wish somone create patch so latest qemu can be compiled with xen unstable.
> The qemu has script that does all the work compiling it but the latest
> version is missing it.
> On Wed, Jul 18, 2012 at 7:02 PM, David Erickson <halcyon1981@xxxxxxxxx>
> wrote:
>>
>> On Wed, Jul 18, 2012 at 5:56 PM, David Erickson <halcyon1981@xxxxxxxxx>
>> wrote:
>> > On Wed, Jul 18, 2012 at 5:24 PM, ivo <shandivo@xxxxxxxxx> wrote:
>> >>
>> >>
>> >> On Thu, Jul 19, 2012 at 2:18 AM, David Erickson <halcyon1981@xxxxxxxxx>
>> >> wrote:
>> >>>
>> >>> I also alternatively tried putting the following into
>> >>> xen-unstable.hg/.config:
>> >>> QEMU_UPSTREAM_URL = git://git.qemu.org/qemu.git
>> >>> QEMU_UPSTREAM_REVISION = master
>> >>>
>> >>> Then executed make world, which doesn't have the above problems of
>> >>> checkout, but during the build has the following error in the
>> >>> qemu-xen-dir-remote:
>> >>>
>> >>> ERROR
>> >>> ERROR: User requested feature xen
>> >>> ERROR: configure was not able to find it
>> >>> ERROR
>> >>>
>> >>> Thanks,
>> >>> David
>> >>
>> >>
>> >> I never had problems with qemu-upstream. Try with a clean xen-unstable
>> >> dir.
>> >> (re-download it)
>> >
>> > Weird, I also am on Ubuntu 12.04, I did a clean checkout of that
>> > revision:
>> >
>> >
>> > hg clone -r 25567 http://xenbits.xen.org/hg/xen-unstable.hg
>> > cp .config xen-unstable.hg
>> > cd xen-unstable.hg
>> > cat .config:
>> > PYTHON_PREFIX_ARG=
>> > QEMU_UPSTREAM_URL = git://git.qemu.org/qemu.git
>> > QEMU_UPSTREAM_REVISION = master
>> > ./configure
>> > make world
>> >
>> > then it cruises along for awhile and errors at:
>> > make[3]: Entering directory `/home/derickso/xen-unstable.hg/tools'
>> > if test -d git://git.qemu.org/qemu.git ; then \
>> >                 mkdir -p qemu-xen-dir; \
>> >         else \
>> >                 export GIT=git; \
>> >
>> > /home/derickso/xen-unstable.hg/tools/../scripts/git-checkout.sh
>> > git://git.qemu.org/qemu.git master qemu-xen-dir ; \
>> >         fi
>> > if test -d git://git.qemu.org/qemu.git ; then \
>> >                 source=git://git.qemu.org/qemu.git; \
>> >         else \
>> >                 source=.; \
>> >         fi; \
>> >         cd qemu-xen-dir; \
>> >         $source/configure --enable-xen --target-list=i386-softmmu \
>> >                 --source-path=$source \
>> >
>> > --extra-cflags="-I/home/derickso/xen-unstable.hg/tools/../tools/include \
>> >                 -I/home/derickso/xen-unstable.hg/tools/../tools/libxc \
>> >                 -I/home/derickso/xen-unstable.hg/tools/../tools/xenstore
>> > \
>> >
>> > -I/home/derickso/xen-unstable.hg/tools/../tools/xenstore/compat \
>> >                 " \
>> >
>> > --extra-ldflags="-L/home/derickso/xen-unstable.hg/tools/../tools/libxc \
>> >
>> > -L/home/derickso/xen-unstable.hg/tools/../tools/xenstore" \
>> >                 --bindir=/usr/lib/xen/bin \
>> >                 --datadir=/usr/share/qemu-xen \
>> >                 --disable-kvm \
>> >                 --python=python \
>> >                 ; \
>> >         make all
>> > ERROR
>> > ERROR: User requested feature xen
>> > ERROR: configure was not able to find it
>> > ERROR
>> > make[4]: Entering directory
>> > `/home/derickso/xen-unstable.hg/tools/qemu-xen-dir-remote'
>> > Please call configure before running make!
>> > make[4]: *** [config-host.mak] Error 1
>> > make[4]: Leaving directory
>> > `/home/derickso/xen-unstable.hg/tools/qemu-xen-dir-remote'
>> > make[3]: *** [subdir-all-qemu-xen-dir] Error 2
>> > make[3]: Leaving directory `/home/derickso/xen-unstable.hg/tools'
>> > make[2]: *** [subdirs-install] Error 2
>> > make[2]: Leaving directory `/home/derickso/xen-unstable.hg/tools'
>> > make[1]: *** [install-tools] Error 2
>> > make[1]: Leaving directory `/home/derickso/xen-unstable.hg'
>> > make: *** [world] Error 2
>>
>> Have you tried a clean build lately? I wonder if something in qemu's
>> upstream has changed since you built that is breaking it.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-devel
>
>

Attachment: guest-dmesg.png
Description: PNG image

Attachment: xl-dmesg.log
Description: Binary data

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