Re: LSI SAS2008 Option Rom Failure

Re: LSI SAS2008 Option Rom Failure

[ivo]

[-- Attachment #1.1: Type: text/plain, Size: 391 bytes --]

I should also mention I've seen the following messages that probably aren't
good when using the xen-qemu device model and pass-thru.  On startup:

libxl: error: libxl_qmp.c:288:qmp_handle_error_response: received an error
message from QMP server: Parameter 'driver' expects a driver name

I solved this by using the latest version of qemu-devel git:


http://wiki.xen.org/wiki/QEMU_Upstream

[-- Attachment #1.2: Type: text/html, Size: 1471 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Wed, Jul 18, 2012 at 2:02 PM, ivo <shandivo@gmail.com> wrote:
> I should also mention I've seen the following messages that probably aren't
> good when using the xen-qemu device model and pass-thru.  On startup:
>
> libxl: error: libxl_qmp.c:288:qmp_handle_error_response: received an error
> message from QMP server: Parameter 'driver' expects a driver name
>
> I solved this by using the latest version of qemu-devel git:
>
>
> http://wiki.xen.org/wiki/QEMU_Upstream

Hi Ivo-
Can you mention how you built it?  I checked out xen-unstable, tried
modifying the Config.mk to change the QEMU_UPSTREAM_URL variable,
however when I built with this new url it complained when it tried to
checkout the qemu traditional because the revision doesn't exist at
that url.  So instead I built normally, then went into
tools/qemu-xen-dir and added the git remote for qemu unstable, checked
out the master branch, ran ./configure, then backed up to the main
xen-unstable.hg folder and did sudo make dist and sudo make install.
When I then started the VM with the config containing device model
qemu-xen nothing changed.  I then added the line:

device_model_override="/home/derickso/xen-unstable.hg/tools/qemu-xen-dir/i386-softmmu/qemu-system-i386"

And started the VM, but got a bunch of errors:

derickso@xen:~/xen-unstable.hg/tools/qemu-xen-dir/i386-softmmu$ sudo
xl -v create /etc/xen/ubuntu.conf -V
Parsing config from /etc/xen/ubuntu.conf
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9dcc8
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19dcc8
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019dcc8
  TOTAL:         0000000000000000->000000007f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fb
  1GB PAGES: 0x0000000000000000
xc: detail: elf_load_binary: phdr 0 at 0x0x7f77f2409000 -> 0x0x7f77f249db4d
libxl: error: libxl_dm.c:1096:device_model_spawn_outcome: domain 2
device model: spawn failed (rc=-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:
No such file or directory
libxl: error: libxl_exec.c:227:libxl__wait_for_offspring: Device Model not ready
vncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server

Any suggestions?

Thanks,
David

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Wed, Jul 18, 2012 at 4:52 PM, David Erickson <halcyon1981@gmail.com> wrote:
> On Wed, Jul 18, 2012 at 2:02 PM, ivo <shandivo@gmail.com> wrote:
>> I should also mention I've seen the following messages that probably aren't
>> good when using the xen-qemu device model and pass-thru.  On startup:
>>
>> libxl: error: libxl_qmp.c:288:qmp_handle_error_response: received an error
>> message from QMP server: Parameter 'driver' expects a driver name
>>
>> I solved this by using the latest version of qemu-devel git:
>>
>>
>> http://wiki.xen.org/wiki/QEMU_Upstream
>
> Hi Ivo-
> Can you mention how you built it?  I checked out xen-unstable, tried
> modifying the Config.mk to change the QEMU_UPSTREAM_URL variable,
> however when I built with this new url it complained when it tried to
> checkout the qemu traditional because the revision doesn't exist at
> that url.  So instead I built normally, then went into
> tools/qemu-xen-dir and added the git remote for qemu unstable, checked
> out the master branch, ran ./configure, then backed up to the main
> xen-unstable.hg folder and did sudo make dist and sudo make install.
> When I then started the VM with the config containing device model
> qemu-xen nothing changed.  I then added the line:
>
> device_model_override="/home/derickso/xen-unstable.hg/tools/qemu-xen-dir/i386-softmmu/qemu-system-i386"
>
> And started the VM, but got a bunch of errors:
>
> derickso@xen:~/xen-unstable.hg/tools/qemu-xen-dir/i386-softmmu$ sudo
> xl -v create /etc/xen/ubuntu.conf -V
> Parsing config from /etc/xen/ubuntu.conf
> xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9dcc8
> xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19dcc8
> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>   Loader:        0000000000100000->000000000019dcc8
>   TOTAL:         0000000000000000->000000007f800000
>   ENTRY ADDRESS: 0000000000100000
> xc: info: PHYSICAL MEMORY ALLOCATION:
>   4KB PAGES: 0x0000000000000200
>   2MB PAGES: 0x00000000000003fb
>   1GB PAGES: 0x0000000000000000
> xc: detail: elf_load_binary: phdr 0 at 0x0x7f77f2409000 -> 0x0x7f77f249db4d
> libxl: error: libxl_dm.c:1096:device_model_spawn_outcome: domain 2
> device model: spawn failed (rc=-3)
> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:
> No such file or directory
> libxl: error: libxl_exec.c:227:libxl__wait_for_offspring: Device Model not ready
> vncviewer: ConnectToTcpAddr: connect: Connection refused
> Unable to connect to VNC server
>
> Any suggestions?

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

Re: LSI SAS2008 Option Rom Failure

[ivo]

[-- Attachment #1.1: Type: text/plain, Size: 618 bytes --]

On Thu, Jul 19, 2012 at 2:18 AM, David Erickson <halcyon1981@gmail.com>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)

[-- Attachment #1.2: Type: text/html, Size: 984 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Wed, Jul 18, 2012 at 5:24 PM, ivo <shandivo@gmail.com> wrote:
>
>
> On Thu, Jul 19, 2012 at 2:18 AM, David Erickson <halcyon1981@gmail.com>
> 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

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Wed, Jul 18, 2012 at 5:56 PM, David Erickson <halcyon1981@gmail.com> wrote:
> On Wed, Jul 18, 2012 at 5:24 PM, ivo <shandivo@gmail.com> wrote:
>>
>>
>> On Thu, Jul 19, 2012 at 2:18 AM, David Erickson <halcyon1981@gmail.com>
>> 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.

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

[-- Attachment #1: Type: text/plain, Size: 6297 bytes --]

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@gmail.com> 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@gmail.com>
> wrote:
>>
>> On Wed, Jul 18, 2012 at 5:56 PM, David Erickson <halcyon1981@gmail.com>
>> wrote:
>> > On Wed, Jul 18, 2012 at 5:24 PM, ivo <shandivo@gmail.com> wrote:
>> >>
>> >>
>> >> On Thu, Jul 19, 2012 at 2:18 AM, David Erickson <halcyon1981@gmail.com>
>> >> 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@lists.xen.org
>> http://lists.xen.org/xen-devel
>
>

[-- Attachment #2: guest-dmesg.png --]
[-- Type: image/png, Size: 207972 bytes --]

[-- Attachment #3: xl-dmesg.log --]
[-- Type: application/octet-stream, Size: 5476 bytes --]

(XEN) HVM2: HVM Loader
(XEN) HVM2: Detected Xen v4.2-unstable
(XEN) HVM2: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM2: System requested SeaBIOS
(XEN) HVM2: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom2 PCI link 0 changed 0 -> 5
(XEN) HVM2: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom2 PCI link 1 changed 0 -> 10
(XEN) HVM2: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom2 PCI link 2 changed 0 -> 11
(XEN) HVM2: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom2 PCI link 3 changed 0 -> 5
(XEN) HVM2: PCI-ISA link 3 routed to IRQ5
(XEN) HVM2: pci dev 01:3 INTA->IRQ10
(XEN) HVM2: pci dev 03:0 INTA->IRQ5
(XEN) HVM2: pci dev 04:0 INTA->IRQ5
(XEN) HVM2: pci dev 05:0 INTA->IRQ10
(XEN) HVM2: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM2: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM2: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM2: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM2: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM2: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM2: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM2: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM2: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM2: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM2: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM2: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom2 gport=c200 mport=d000 nr=100
(XEN) HVM2: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM2: Multiprocessor initialisation:
(XEN) HVM2:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM2:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM2: Testing HVM environment:
(XEN) HVM2:  - REP INSB across page boundaries ... passed
(XEN) HVM2:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM2: Passed 2 of 2 tests
(XEN) HVM2: Writing SMBIOS tables ...
(XEN) HVM2: Loading SeaBIOS ...
(XEN) HVM2: Creating MP tables ...
(XEN) HVM2: Loading ACPI ...
(XEN) HVM2: vm86 TSS at fc00a080
(XEN) HVM2: BIOS map:
(XEN) HVM2:  10000-100d3: Scratch space
(XEN) HVM2:  e0000-fffff: Main BIOS
(XEN) HVM2: E820 table:
(XEN) HVM2:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM2:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM2:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM2:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM2:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM2:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM2: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d2 entering stdvga and caching modes
(XEN) memory_map:add: dom2 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom2 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d2 leaving stdvga
(XEN) stdvga.c:147:d2 entering stdvga and caching modes
(XEN) irq.c:350: Dom2 callback via changed to Direct Vector 0xf3
(XEN) memory_map:remove: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom2 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom2 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom2 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom2 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom2 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom2 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom2 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom2 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom2 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom2 gport=c200 mport=d000 nr=100
(XEN) irq.c:270: Dom2 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom2 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom2 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom2 PCI link 3 changed 5 -> 0
(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3


[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

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?

> 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)?

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)

David, it might be worth trying a simpler devie pass through first just
to validate the basic functionality is working for you. Usually a NIC or
a USB controller is  pretty good simple case.

If you try a NIC then you could also try PXE booting from it, which will
exercise the option ROM support, which should be simpler than the option
ROM used by a RAID controller.

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

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?

Ian.

Re: LSI SAS2008 Option Rom Failure

[Anthony PERARD]

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

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Thu, 2012-07-19 at 11:57 +0100, Anthony PERARD wrote:
> 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.

OK.

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

Should this be enabled in our build system and/or referenced in the
wiki?

Re: LSI SAS2008 Option Rom Failure

[Anthony PERARD]

On 19/07/12 12:07, Ian Campbell wrote:
> On Thu, 2012-07-19 at 11:57 +0100, Anthony PERARD wrote:
>> On 19/07/12 08:22, Ian Campbell wrote:
>>> 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.
>
> Should this be enabled in our build system and/or referenced in the
> wiki?

This should not be needed as it is enable by default if possible. But I 
don't know what went wrong here :(.

Otherwise, to be sure that pci passthrough is compiled in, use the 
--enable-xen-pci-passthrough configure option.

-- 
Anthony PERARD

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Thu, 2012-07-19 at 12:31 +0100, Anthony PERARD wrote:
> On 19/07/12 12:07, Ian Campbell wrote:
> > On Thu, 2012-07-19 at 11:57 +0100, Anthony PERARD wrote:
> >> On 19/07/12 08:22, Ian Campbell wrote:
> >>> 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.
> >
> > Should this be enabled in our build system and/or referenced in the
> > wiki?
> 
> This should not be needed as it is enable by default if possible. But I 
> don't know what went wrong here :(.

Missing dependency? e.g. libpci-devel?

> Otherwise, to be sure that pci passthrough is compiled in, use the 
> --enable-xen-pci-passthrough configure option.

We should enable this option in our build system so that we get a
consistent set of features not dependent on the vagaries of the
underlying system. If there are libraries which we require we should
check for them in out configure script.

Ian.

> 

Re: LSI SAS2008 Option Rom Failure

[Anthony PERARD]

On Thu, Jul 19, 2012 at 12:38 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>
>> This should not be needed as it is enable by default if possible. But I
>> don't know what went wrong here :(.
>
> Missing dependency? e.g. libpci-devel?

The only check are, if configured for linux, if xen is enable and if
xen is >= 3.4. We don't use libpci with QEMU upstream.

-- 
Anthony PERARD

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Thu, 2012-07-19 at 12:44 +0100, Anthony PERARD wrote:
> On Thu, Jul 19, 2012 at 12:38 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> >
> >> This should not be needed as it is enable by default if possible. But I
> >> don't know what went wrong here :(.
> >
> > Missing dependency? e.g. libpci-devel?
> 
> The only check are, if configured for linux, if xen is enable and if
> xen is >= 3.4. We don't use libpci with QEMU upstream.

Hrm, perhaps David can provide some logs. What files from the qemu
source tree would give a hint? Is there a config.log?

Re: LSI SAS2008 Option Rom Failure

[Stefano Stabellini]

On Thu, 19 Jul 2012, Ian Campbell wrote:
> On Thu, 2012-07-19 at 12:31 +0100, Anthony PERARD wrote:
> > On 19/07/12 12:07, Ian Campbell wrote:
> > > On Thu, 2012-07-19 at 11:57 +0100, Anthony PERARD wrote:
> > >> On 19/07/12 08:22, Ian Campbell wrote:
> > >>> 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.
> > >
> > > Should this be enabled in our build system and/or referenced in the
> > > wiki?
> > 
> > This should not be needed as it is enable by default if possible. But I 
> > don't know what went wrong here :(.
> 
> Missing dependency? e.g. libpci-devel?
> 
> > Otherwise, to be sure that pci passthrough is compiled in, use the 
> > --enable-xen-pci-passthrough configure option.
> 
> We should enable this option in our build system so that we get a
> consistent set of features not dependent on the vagaries of the
> underlying system. If there are libraries which we require we should
> check for them in out configure script.

I didn't backport pci passthrough to qemu-upstream-unstable so that
option wouldn't be available there

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Thu, 2012-07-19 at 12:48 +0100, Stefano Stabellini wrote:
> On Thu, 19 Jul 2012, Ian Campbell wrote:
> > On Thu, 2012-07-19 at 12:31 +0100, Anthony PERARD wrote:
> > > On 19/07/12 12:07, Ian Campbell wrote:
> > > > On Thu, 2012-07-19 at 11:57 +0100, Anthony PERARD wrote:
> > > >> On 19/07/12 08:22, Ian Campbell wrote:
> > > >>> 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.
> > > >
> > > > Should this be enabled in our build system and/or referenced in the
> > > > wiki?
> > > 
> > > This should not be needed as it is enable by default if possible. But I 
> > > don't know what went wrong here :(.
> > 
> > Missing dependency? e.g. libpci-devel?
> > 
> > > Otherwise, to be sure that pci passthrough is compiled in, use the 
> > > --enable-xen-pci-passthrough configure option.
> > 
> > We should enable this option in our build system so that we get a
> > consistent set of features not dependent on the vagaries of the
> > underlying system. If there are libraries which we require we should
> > check for them in out configure script.
> 
> I didn't backport pci passthrough to qemu-upstream-unstable so that
> option wouldn't be available there

Aha, I thought you had, nevermind then.

Re: LSI SAS2008 Option Rom Failure

[Stefano Stabellini]

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@eu.citrix.com>
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@eu.citrix.com>
    Tested-by: Deep Debroy <ddebroy@gmail.com>
    Committed-by: Keir Fraser <keir@xen.org>

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

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@eu.citrix.com> 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@eu.citrix.com>
> 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@eu.citrix.com>
>     Tested-by: Deep Debroy <ddebroy@gmail.com>
>     Committed-by: Keir Fraser <keir@xen.org>

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

[-- Attachment #1: Type: text/plain, Size: 3433 bytes --]

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
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']

Any help appreciated on both questions.

Thanks,
David


On Thu, Jul 19, 2012 at 8:27 AM, David Erickson <halcyon1981@gmail.com> 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@eu.citrix.com> 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@eu.citrix.com>
>> 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@eu.citrix.com>
>>     Tested-by: Deep Debroy <ddebroy@gmail.com>
>>     Committed-by: Keir Fraser <keir@xen.org>

[-- Attachment #2: ubuntu_native_dmesg.png --]
[-- Type: image/png, Size: 517657 bytes --]

[-- Attachment #3: ubuntu_guest_dmesg.png --]
[-- Type: image/png, Size: 207885 bytes --]

[-- Attachment #4: ubuntu_qemu-dm-log --]
[-- Type: application/octet-stream, Size: 543 bytes --]

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.


[-- Attachment #5: ubuntu_xl_dmesg --]
[-- Type: application/octet-stream, Size: 5476 bytes --]

(XEN) HVM8: HVM Loader
(XEN) HVM8: Detected Xen v4.2-unstable
(XEN) HVM8: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM8: System requested SeaBIOS
(XEN) HVM8: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom8 PCI link 0 changed 0 -> 5
(XEN) HVM8: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom8 PCI link 1 changed 0 -> 10
(XEN) HVM8: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom8 PCI link 2 changed 0 -> 11
(XEN) HVM8: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom8 PCI link 3 changed 0 -> 5
(XEN) HVM8: PCI-ISA link 3 routed to IRQ5
(XEN) HVM8: pci dev 01:3 INTA->IRQ10
(XEN) HVM8: pci dev 03:0 INTA->IRQ5
(XEN) HVM8: pci dev 04:0 INTA->IRQ5
(XEN) HVM8: pci dev 05:0 INTA->IRQ10
(XEN) HVM8: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM8: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM8: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM8: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM8: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM8: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM8: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM8: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM8: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM8: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM8: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM8: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom8 gport=c200 mport=d000 nr=100
(XEN) HVM8: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM8: Multiprocessor initialisation:
(XEN) HVM8:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM8:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM8: Testing HVM environment:
(XEN) HVM8:  - REP INSB across page boundaries ... passed
(XEN) HVM8:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM8: Passed 2 of 2 tests
(XEN) HVM8: Writing SMBIOS tables ...
(XEN) HVM8: Loading SeaBIOS ...
(XEN) HVM8: Creating MP tables ...
(XEN) HVM8: Loading ACPI ...
(XEN) HVM8: vm86 TSS at fc00a080
(XEN) HVM8: BIOS map:
(XEN) HVM8:  10000-100d3: Scratch space
(XEN) HVM8:  e0000-fffff: Main BIOS
(XEN) HVM8: E820 table:
(XEN) HVM8:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM8:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM8:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM8:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM8:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM8:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM8: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d8 entering stdvga and caching modes
(XEN) memory_map:add: dom8 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom8 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d8 leaving stdvga
(XEN) stdvga.c:147:d8 entering stdvga and caching modes
(XEN) irq.c:375: Dom8 callback via changed to Direct Vector 0xf3
(XEN) memory_map:remove: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom8 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom8 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom8 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom8 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom8 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom8 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom8 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom8 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom8 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom8 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom8 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom8 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom8 gport=c200 mport=d000 nr=100
(XEN) irq.c:270: Dom8 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom8 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom8 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom8 PCI link 3 changed 5 -> 0
(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3


[-- Attachment #6: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

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@gmail.com> 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@eu.citrix.com> 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@eu.citrix.com>
> >> 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@eu.citrix.com>
> >>     Tested-by: Deep Debroy <ddebroy@gmail.com>
> >>     Committed-by: Keir Fraser <keir@xen.org>

Re: LSI SAS2008 Option Rom Failure

[Jan Beulich]

>>> On 31.07.12 at 11:04, Ian Campbell <Ian.Campbell@citrix.com> 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)?

Jan

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Tue, 2012-07-31 at 10:35 +0100, Jan Beulich wrote:
> >>> On 31.07.12 at 11:04, Ian Campbell <Ian.Campbell@citrix.com> 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
> 

Re: LSI SAS2008 Option Rom Failure

[Jan Beulich]

>>> On 31.07.12 at 11:41, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Tue, 2012-07-31 at 10:35 +0100, Jan Beulich wrote:
>> >>> On 31.07.12 at 11:04, Ian Campbell <Ian.Campbell@citrix.com> 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=ce6 
> d9b1b2f9c6a5ca2500e03d0ef8b453bc4bf53
>> (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?

Yes, as I wrote. The implication was that this and/or the more
complete fix may need porting to the upstream one.

Jan

Re: LSI SAS2008 Option Rom Failure

[Anthony PERARD]

On Tue, Jul 31, 2012 at 10:47 AM, Jan Beulich <JBeulich@suse.com> wrote:
>
> Yes, as I wrote. The implication was that this and/or the more
> complete fix may need porting to the upstream one.

I did not upstream the code for the MSI translation to QEMU upstream.
So nothing to fix :).

-- 
Anthony PERARD

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Tue, Jul 31, 2012 at 2:41 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Tue, 2012-07-31 at 10:35 +0100, Jan Beulich wrote:
>> >>> On 31.07.12 at 11:04, Ian Campbell <Ian.Campbell@citrix.com> 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.
>

Gave this a go, same problem, will try the further logging suggested below next.

Re: LSI SAS2008 Option Rom Failure

[Stefano Stabellini]

On Tue, 31 Jul 2012, Jan Beulich wrote:
> >>> On 31.07.12 at 11:04, Ian Campbell <Ian.Campbell@citrix.com> 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)?
 
This is the patch and doesn't seem to be in qemu-xen-traditional:

http://marc.info/?l=xen-devel&m=134096922121958

However qemu-xen-upstream doesn't have msi_translate at all, so it
cannot be the issue.

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

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

I believe I should have the driver, the test guest I am using is just
an Ubuntu 11.10 desktop live cd.  Which command line would I put
"xen_emul_unplug=never"? the guest's kernel boot line?  Also I was
somewhat surprised to see xen messages in the guest's kernel dmesg
given that it is running HVM, unless it has somehow detected it is
running on top of Xen.  If there is an alternative vif line I should
use I'm happy to change it.

Thanks-
David

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Tue, 2012-07-31 at 16:28 +0100, David Erickson wrote:
> >>
> >> 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.
> 
> I believe I should have the driver, the test guest I am using is just
> an Ubuntu 11.10 desktop live cd.  Which command line would I put
> "xen_emul_unplug=never"? the guest's kernel boot line?

Yes.

>   Also I was
> somewhat surprised to see xen messages in the guest's kernel dmesg
> given that it is running HVM, unless it has somehow detected it is
> running on top of Xen.

Modern kernels have a feature called "PVHVM" which allows for PV
features, such as device drivers, even for HVM guests. I don't know if
11.10 has that turned on / functional or not.

>   If there is an alternative vif line I should
> use I'm happy to change it.

You could try dropping the type=ioemu.

Ian

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Tue, Jul 31, 2012 at 8:35 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Tue, 2012-07-31 at 16:28 +0100, David Erickson wrote:
>> >>
>> >> 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.
>>
>> I believe I should have the driver, the test guest I am using is just
>> an Ubuntu 11.10 desktop live cd.  Which command line would I put
>> "xen_emul_unplug=never"? the guest's kernel boot line?
>
> Yes.
>
>>   Also I was
>> somewhat surprised to see xen messages in the guest's kernel dmesg
>> given that it is running HVM, unless it has somehow detected it is
>> running on top of Xen.
>
> Modern kernels have a feature called "PVHVM" which allows for PV
> features, such as device drivers, even for HVM guests. I don't know if
> 11.10 has that turned on / functional or not.

I took a closer look at the guests's dmesg output and indeed it says
"Booting paravirtualized kernel on Xen HVM"

>
>>   If there is an alternative vif line I should
>> use I'm happy to change it.
>
> You could try dropping the type=ioemu.

Gave this a try, still am seeing the vif interfaces on the host,
nothing in the guest.  Also I combed through the dmesg on the guest
and didn't see anything about any network interfaces, and nothing
about being plugged/unplugged either.  There is the following line in
my xen-hotplug.log, if it is relevant:

@xen:/var/log/xen$ sudo cat xen-hotplug.log
RTNETLINK answers: Operation not supported

Re: LSI SAS2008 Option Rom Failure

[Stefano Stabellini]

On Tue, 31 Jul 2012, 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.  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.

"unsupported delivery mode 3" means that the Linux guest is trying to
remap the MSI onto an event channel but Xen is still trying to deliver
the MSI using the emulated code path anyway.

Adding

#define XEN_PT_LOGGING_ENABLED 1

at the top of hw/xen_pt.h and posting the additional QEMU logs could
be helpful.

The full Xen logs might also be useful. I would add some more tracing to
the hypervisor too:

diff --git a/xen/drivers/passthrough/io.c b/xen/drivers/passthrough/io.c
index b5975d1..08f4ab7 100644
--- a/xen/drivers/passthrough/io.c
+++ b/xen/drivers/passthrough/io.c
@@ -474,6 +474,11 @@ static void hvm_pci_msi_assert(
 {
     struct pirq *pirq = dpci_pirq(pirq_dpci);
 
+    printk("DEBUG %s pirq=%d hvm_domain_use_pirq=%d emuirq=%d\n", __func__,
+            pirq->pirq,
+            hvm_domain_use_pirq(d, pirq),
+            pirq->arch.hvm.emuirq);
+
     if ( hvm_domain_use_pirq(d, pirq) )
         send_guest_pirq(d, pirq);
     else

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

On Tue, Jul 31, 2012 at 4:39 AM, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
> On Tue, 31 Jul 2012, 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.  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.
>
> "unsupported delivery mode 3" means that the Linux guest is trying to
> remap the MSI onto an event channel but Xen is still trying to deliver
> the MSI using the emulated code path anyway.
>
> Adding
>
> #define XEN_PT_LOGGING_ENABLED 1
>
> at the top of hw/xen_pt.h and posting the additional QEMU logs could
> be helpful.
>
> The full Xen logs might also be useful. I would add some more tracing to
> the hypervisor too:
>
> diff --git a/xen/drivers/passthrough/io.c b/xen/drivers/passthrough/io.c
> index b5975d1..08f4ab7 100644
> --- a/xen/drivers/passthrough/io.c
> +++ b/xen/drivers/passthrough/io.c
> @@ -474,6 +474,11 @@ static void hvm_pci_msi_assert(
>  {
>      struct pirq *pirq = dpci_pirq(pirq_dpci);
>
> +    printk("DEBUG %s pirq=%d hvm_domain_use_pirq=%d emuirq=%d\n", __func__,
> +            pirq->pirq,
> +            hvm_domain_use_pirq(d, pirq),
> +            pirq->arch.hvm.emuirq);
> +
>      if ( hvm_domain_use_pirq(d, pirq) )
>          send_guest_pirq(d, pirq);
>      else

Hi Stefano-
I made the modifications (it looks like that DEFINE hasn't been used
in awhile, caused a few compilation issues, I had to prefix most of
the logged variables with s->hostaddr.), and am attaching the
qemu-dm-ubuntu.log and dmesg from xl.  You referred to full Xen logs,
where do I find those at?

Thanks,
David

[-- Attachment #2: xl_dmesg.log --]
[-- Type: application/octet-stream, Size: 15958 bytes --]

 __  __            _  _    ____                     _        _     _      
 \ \/ /___ _ __   | || |  |___ \    _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \  | || |_   __) |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | | |__   _| / __/|__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_|    |_|(_)_____|   \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                          
(XEN) Xen version 4.2-unstable (derickso@hsd1.ca.comcast.net) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) Tue Jul 31 08:47:04 PDT 2012
(XEN) Latest ChangeSet: Fri Jul 27 12:22:13 2012 +0200 25688:e6266fc76d08
(XEN) Bootloader: GRUB 1.99-21ubuntu3.1
(XEN) Command line: placeholder dom0_mem=4096M xsave=0
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009c800 (usable)
(XEN)  000000000009c800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000ddd07000 (usable)
(XEN)  00000000ddd07000 - 00000000dddbb000 (reserved)
(XEN)  00000000dddbb000 - 00000000dddbc000 (ACPI data)
(XEN)  00000000dddbc000 - 00000000dded7000 (ACPI NVS)
(XEN)  00000000dded7000 - 00000000def92000 (reserved)
(XEN)  00000000def92000 - 00000000def93000 (usable)
(XEN)  00000000def93000 - 00000000defd6000 (ACPI NVS)
(XEN)  00000000defd6000 - 00000000df800000 (usable)
(XEN)  00000000f8000000 - 00000000fc000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fed00000 - 00000000fed04000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000420000000 (usable)
(XEN) ACPI: RSDP 000F0490, 0024 (r2 ALASKA)
(XEN) ACPI: XSDT DDEC7090, 009C (r1 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: FACP DDED1CA0, 00F4 (r4 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: DSDT DDEC71C0, AADA (r2 ALASKA    A M I       6F INTL 20051117)
(XEN) ACPI: FACS DDED5F80, 0040
(XEN) ACPI: APIC DDED1D98, 0092 (r3 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: FPDT DDED1E30, 0044 (r1 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: MCFG DDED1E78, 003C (r1 ALASKA    A M I  1072009 MSFT       97)
(XEN) ACPI: PRAD DDED1EB8, 00BE (r2 PRADID  PRADTID        1 MSFT  3000001)
(XEN) ACPI: HPET DDED1F78, 0038 (r1 ALASKA    A M I  1072009 AMI.        5)
(XEN) ACPI: SSDT DDED1FB0, 036D (r1 SataRe SataTabl     1000 INTL 20091112)
(XEN) ACPI: SPMI DDED2320, 0040 (r5 A M I   OEMSPMI        0 AMI.        0)
(XEN) ACPI: SSDT DDED2360, 09A4 (r1  PmRef  Cpu0Ist     3000 INTL 20051117)
(XEN) ACPI: SSDT DDED2D08, 0A88 (r1  PmRef    CpuPm     3000 INTL 20051117)
(XEN) ACPI: DMAR DDED3790, 0078 (r1 INTEL      SNB         1 INTL        1)
(XEN) ACPI: EINJ DDED3808, 0130 (r1    AMI AMI EINJ        0             0)
(XEN) ACPI: ERST DDED3938, 0210 (r1  AMIER AMI ERST        0             0)
(XEN) ACPI: HEST DDED3B48, 00A8 (r1    AMI AMI HEST        0             0)
(XEN) ACPI: BERT DDED3BF0, 0030 (r1    AMI AMI BERT        0             0)
(XEN) System RAM: 16356MB (16749368kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000000420000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000fd7b0
(XEN) DMI 2.7 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT - dded5f80/0000000000000000, using 32
(XEN) ACPI:                  wakeup_vec[dded5f8c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
(XEN) Processor #4 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
(XEN) Processor #6 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
(XEN) Processor #1 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
(XEN) Processor #3 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
(XEN) Processor #5 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
(XEN) Processor #7 7:10 APIC version 21
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) ERST table is invalid
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 8 CPUs (0 hotplug CPUs)
(XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X
(XEN) Switched to APIC driver x2apic_cluster.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3292.617 MHz processor.
(XEN) Initing memory sharing.
(XEN) mce_intel.c:1239: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extended MCE MSR 0
(XEN) Intel machine check reporting enabled
(XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f
(XEN) PCI: MCFG area at f8000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-3f
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) TSC deadline timer enabled
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 64 KiB.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN)  - Unrestricted Guest
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB
(XEN) Brought up 8 CPUs
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0xac5000
(XEN) elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xe60e0
(XEN) elf_parse_binary: phdr: paddr=0x1ce7000 memsz=0x14480
(XEN) elf_parse_binary: phdr: paddr=0x1cfc000 memsz=0x362000
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x205e000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff81cfc200
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xffffffff80000000
(XEN)     elf_paddr_offset = 0x0
(XEN)     virt_offset      = 0xffffffff80000000
(XEN)     virt_kstart      = 0xffffffff81000000
(XEN)     virt_kend        = 0xffffffff8205e000
(XEN)     virt_entry       = 0xffffffff81cfc200
(XEN)     p2m_base         = 0xffffffffffffffff
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x205e000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000040c000000->0000000410000000 (1022357 pages to be allocated)
(XEN)  Init. ramdisk: 000000041d995000->000000041ffff200
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff8205e000
(XEN)  Init. ramdisk: ffffffff8205e000->ffffffff846c8200
(XEN)  Phys-Mach map: ffffffff846c9000->ffffffff84ec9000
(XEN)  Start info:    ffffffff84ec9000->ffffffff84ec94b4
(XEN)  Page tables:   ffffffff84eca000->ffffffff84ef5000
(XEN)  Boot stack:    ffffffff84ef5000->ffffffff84ef6000
(XEN)  TOTAL:         ffffffff80000000->ffffffff85000000
(XEN)  ENTRY ADDRESS: ffffffff81cfc200
(XEN) Dom0 has maximum 8 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81ac5000
(XEN) elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81ce60e0
(XEN) elf_load_binary: phdr 2 at 0xffffffff81ce7000 -> 0xffffffff81cfb480
(XEN) elf_load_binary: phdr 3 at 0xffffffff81cfc000 -> 0xffffffff81dd2000
(XEN) Scrubbing Free RAM: ........................................................................................................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 240kB init memory.
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:01.0
(XEN) PCI add device 0000:00:01.1
(XEN) PCI add device 0000:00:06.0
(XEN) PCI add device 0000:00:1a.0
(XEN) PCI add device 0000:00:1c.0
(XEN) PCI add device 0000:00:1c.6
(XEN) PCI add device 0000:00:1d.0
(XEN) PCI add device 0000:00:1e.0
(XEN) PCI add device 0000:00:1f.0
(XEN) PCI add device 0000:00:1f.2
(XEN) PCI add device 0000:00:1f.3
(XEN) PCI add device 0000:01:00.0
(XEN) PCI add device 0000:01:00.1
(XEN) PCI add device 0000:02:00.0
(XEN) PCI add device 0000:04:00.0
(XEN) PCI add device 0000:05:00.0
(XEN) PCI add device 0000:06:00.0
(XEN) HVM1: HVM Loader
(XEN) HVM1: Detected Xen v4.2-unstable
(XEN) HVM1: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM1: System requested SeaBIOS
(XEN) HVM1: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom1 PCI link 0 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom1 PCI link 1 changed 0 -> 10
(XEN) HVM1: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom1 PCI link 2 changed 0 -> 11
(XEN) HVM1: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom1 PCI link 3 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 3 routed to IRQ5
(XEN) HVM1: pci dev 01:3 INTA->IRQ10
(XEN) HVM1: pci dev 03:0 INTA->IRQ5
(XEN) HVM1: pci dev 04:0 INTA->IRQ5
(XEN) HVM1: pci dev 05:0 INTA->IRQ10
(XEN) HVM1: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM1: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM1: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM1: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM1: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM1: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM1: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM1: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM1: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM1: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM1: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom1 gport=c200 mport=d000 nr=100
(XEN) HVM1: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM1: Multiprocessor initialisation:
(XEN) HVM1:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM1:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM1: Testing HVM environment:
(XEN) HVM1:  - REP INSB across page boundaries ... passed
(XEN) HVM1:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM1: Passed 2 of 2 tests
(XEN) HVM1: Writing SMBIOS tables ...
(XEN) HVM1: Loading SeaBIOS ...
(XEN) HVM1: Creating MP tables ...
(XEN) HVM1: Loading ACPI ...
(XEN) HVM1: vm86 TSS at fc00a080
(XEN) HVM1: BIOS map:
(XEN) HVM1:  10000-100d3: Scratch space
(XEN) HVM1:  e0000-fffff: Main BIOS
(XEN) HVM1: E820 table:
(XEN) HVM1:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM1:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM1:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM1:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM1:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM1:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM1: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d1 entering stdvga and caching modes
(XEN) memory_map:add: dom1 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom1 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d1 leaving stdvga
(XEN) stdvga.c:147:d1 entering stdvga and caching modes
(XEN) irq.c:375: Dom1 callback via changed to Direct Vector 0xf3
(XEN) memory_map:remove: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom1 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom1 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom1 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom1 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom1 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom1 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom1 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom1 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom1 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom1 gport=c200 mport=d000 nr=100
(XEN) irq.c:270: Dom1 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom1 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom1 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom1 PCI link 3 changed 5 -> 0
(XEN) DEBUG hvm_pci_msi_assert pirq=4 hvm_domain_use_pirq=0 emuirq=-1
(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3

[-- Attachment #3: qemu-dm-ubuntu.log --]
[-- Type: application/octet-stream, Size: 1613 bytes --]

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] xen_pt_initfn: Assigning real physical device 02:00.0 to devfn 0x28
[00:05.0] xen_pt_register_regions: IO region 0 registered (size=0x00000100 base_addr=0x0000d000 type: 0x1)
[00:05.0] xen_pt_register_regions: IO region 1 registered (size=0x00004000 base_addr=0xf7ac0000 type: 0)
[00:05.0] xen_pt_register_regions: IO region 3 registered (size=0x00040000 base_addr=0xf7a80000 type: 0)
[00:05.0] xen_pt_register_regions: Expansion ROM registered (size=0x00080000 base_addr=0xf7a00000)
[00:05.0] xen_pt_msix_init: get MSI-X table BAR base 0xf7ac0000
[00:05.0] xen_pt_msix_init: table_off = 0x2000, total_entries = 15
[00:05.0] xen_pt_msix_init: mapping physical MSI-X table to 0x7fe7e8628000
[00:05.0] xen_pt_pci_intx: intx=1
[00:05.0] xen_pt_initfn: Real physical device 02:00.0 registered successfuly!
[00:05.0] xen_pt_msixctrl_reg_write: enable MSI-X
[00:05.0] msi_msix_setup: requested pirq 4 for MSI-X (vec: 0, entry: 0)
[00:05.0] msi_msix_update: Updating MSI-X with pirq 4 gvec 0 gflags 0x3037 (entry: 0)
[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.
[00:05.0] xen_pt_msixctrl_reg_write: disable MSI-X

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[Stefano Stabellini]

On Tue, 31 Jul 2012, David Erickson wrote:
> On Tue, Jul 31, 2012 at 4:39 AM, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
> > On Tue, 31 Jul 2012, 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.  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.
> >
> > "unsupported delivery mode 3" means that the Linux guest is trying to
> > remap the MSI onto an event channel but Xen is still trying to deliver
> > the MSI using the emulated code path anyway.
> >
> > Adding
> >
> > #define XEN_PT_LOGGING_ENABLED 1
> >
> > at the top of hw/xen_pt.h and posting the additional QEMU logs could
> > be helpful.
> >
> > The full Xen logs might also be useful. I would add some more tracing to
> > the hypervisor too:
> >
> > diff --git a/xen/drivers/passthrough/io.c b/xen/drivers/passthrough/io.c
> > index b5975d1..08f4ab7 100644
> > --- a/xen/drivers/passthrough/io.c
> > +++ b/xen/drivers/passthrough/io.c
> > @@ -474,6 +474,11 @@ static void hvm_pci_msi_assert(
> >  {
> >      struct pirq *pirq = dpci_pirq(pirq_dpci);
> >
> > +    printk("DEBUG %s pirq=%d hvm_domain_use_pirq=%d emuirq=%d\n", __func__,
> > +            pirq->pirq,
> > +            hvm_domain_use_pirq(d, pirq),
> > +            pirq->arch.hvm.emuirq);
> > +
> >      if ( hvm_domain_use_pirq(d, pirq) )
> >          send_guest_pirq(d, pirq);
> >      else
> 
> Hi Stefano-
> I made the modifications (it looks like that DEFINE hasn't been used
> in awhile, caused a few compilation issues, I had to prefix most of
> the logged variables with s->hostaddr.), and am attaching the
> qemu-dm-ubuntu.log and dmesg from xl.  You referred to full Xen logs,
> where do I find those at?

Thanks for the logs!
You can get the full Xen logs from the serial console but you can also
grab the last few lines with "xl dmesg", like you did and it seems to be
enough in this case.


The initial MSI remapping has been done:

[00:05.0] msi_msix_setup: requested pirq 4 for MSI-X (vec: 0, entry: 0)
[00:05.0] msi_msix_update: Updating MSI-X with pirq 4 gvec 0 gflags 0x3037 (entry: 0)

But the guest is not issuing the EVTCHNOP_bind_pirq hypercall that is
necessary to be able to receive event notifications (emuirq=-1 in the
Xen logs).

Now we need to figure out why: we still need more logs, this time on the
guest side.
What is the kernel version that you are using in the guest?
Could you please add "debug loglevel=9" to the guest kernel command line
and then post the guest dmesg again? 
It would be great if you could use the emulated serial to get the logs
rather than a picture. You can do that by adding serial='pty' to the VM
config file and console=ttyS0 to the guest command line.
This additional Xen change could also tell us if the EVTCHNOP_bind_pirq
has been done:


diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
index 53777f8..d65a97a 100644
--- a/xen/common/event_channel.c
+++ b/xen/common/event_channel.c
@@ -405,6 +405,8 @@ static long evtchn_bind_pirq(evtchn_bind_pirq_t *bind)
 #ifdef CONFIG_X86
     if ( is_hvm_domain(d) && domain_pirq_to_irq(d, pirq) > 0 )
         map_domain_emuirq_pirq(d, pirq, IRQ_PT);
+    printk("DEBUG %s %d pirq=%d irq=%d emuirq=%d\n", __func__, __LINE__,
+            pirq, domain_pirq_to_irq(d, pirq), domain_pirq_to_emuirq(d, pirq));
 #endif
 
  out:

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

[-- Attachment #1: Type: text/plain, Size: 8107 bytes --]

On Wed, Aug 1, 2012 at 4:13 AM, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
> On Tue, 31 Jul 2012, David Erickson wrote:
>> On Tue, Jul 31, 2012 at 4:39 AM, Stefano Stabellini
>> <stefano.stabellini@eu.citrix.com> wrote:
>> > On Tue, 31 Jul 2012, 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.  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.
>> >
>> > "unsupported delivery mode 3" means that the Linux guest is trying to
>> > remap the MSI onto an event channel but Xen is still trying to deliver
>> > the MSI using the emulated code path anyway.
>> >
>> > Adding
>> >
>> > #define XEN_PT_LOGGING_ENABLED 1
>> >
>> > at the top of hw/xen_pt.h and posting the additional QEMU logs could
>> > be helpful.
>> >
>> > The full Xen logs might also be useful. I would add some more tracing to
>> > the hypervisor too:
>> >
>> > diff --git a/xen/drivers/passthrough/io.c b/xen/drivers/passthrough/io.c
>> > index b5975d1..08f4ab7 100644
>> > --- a/xen/drivers/passthrough/io.c
>> > +++ b/xen/drivers/passthrough/io.c
>> > @@ -474,6 +474,11 @@ static void hvm_pci_msi_assert(
>> >  {
>> >      struct pirq *pirq = dpci_pirq(pirq_dpci);
>> >
>> > +    printk("DEBUG %s pirq=%d hvm_domain_use_pirq=%d emuirq=%d\n", __func__,
>> > +            pirq->pirq,
>> > +            hvm_domain_use_pirq(d, pirq),
>> > +            pirq->arch.hvm.emuirq);
>> > +
>> >      if ( hvm_domain_use_pirq(d, pirq) )
>> >          send_guest_pirq(d, pirq);
>> >      else
>>
>> Hi Stefano-
>> I made the modifications (it looks like that DEFINE hasn't been used
>> in awhile, caused a few compilation issues, I had to prefix most of
>> the logged variables with s->hostaddr.), and am attaching the
>> qemu-dm-ubuntu.log and dmesg from xl.  You referred to full Xen logs,
>> where do I find those at?
>
> Thanks for the logs!
> You can get the full Xen logs from the serial console but you can also
> grab the last few lines with "xl dmesg", like you did and it seems to be
> enough in this case.
>
>
> The initial MSI remapping has been done:
>
> [00:05.0] msi_msix_setup: requested pirq 4 for MSI-X (vec: 0, entry: 0)
> [00:05.0] msi_msix_update: Updating MSI-X with pirq 4 gvec 0 gflags 0x3037 (entry: 0)
>
> But the guest is not issuing the EVTCHNOP_bind_pirq hypercall that is
> necessary to be able to receive event notifications (emuirq=-1 in the
> Xen logs).
>
> Now we need to figure out why: we still need more logs, this time on the
> guest side.
> What is the kernel version that you are using in the guest?
> Could you please add "debug loglevel=9" to the guest kernel command line
> and then post the guest dmesg again?
> It would be great if you could use the emulated serial to get the logs
> rather than a picture. You can do that by adding serial='pty' to the VM
> config file and console=ttyS0 to the guest command line.
> This additional Xen change could also tell us if the EVTCHNOP_bind_pirq
> has been done:
>
>
> diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
> index 53777f8..d65a97a 100644
> --- a/xen/common/event_channel.c
> +++ b/xen/common/event_channel.c
> @@ -405,6 +405,8 @@ static long evtchn_bind_pirq(evtchn_bind_pirq_t *bind)
>  #ifdef CONFIG_X86
>      if ( is_hvm_domain(d) && domain_pirq_to_irq(d, pirq) > 0 )
>          map_domain_emuirq_pirq(d, pirq, IRQ_PT);
> +    printk("DEBUG %s %d pirq=%d irq=%d emuirq=%d\n", __func__, __LINE__,
> +            pirq, domain_pirq_to_irq(d, pirq), domain_pirq_to_emuirq(d, pirq));
>  #endif
>
>   out:

The guest is an Ubuntu 11.10 livecd, kernel version 3.0.0-12-generic.
I've also attached all the logs, thanks for the tip on the serial
console, very useful.

Additionally I've attached logs for booting a solaris livecd (my
ultimate goal is to use this HBA card in Solaris), with the serial
console tip I was able to capture its kernel boot as well.

Lastly I still also have the issue where no NIC is being presented
enabled in the guests, my assumption is this is because of the error
in xen-hotplug.log: "RTNETLINK answers: Operation not supported", is
there some way to debug this? I checked my dom0's dmesg and this is
what I get when I boot the Ubuntu livecd VM:

[ 2506.619039] device vif8.0 entered promiscuous mode
[ 2506.624304] ADDRCONF(NETDEV_UP): vif8.0: link is not ready
[ 2506.777865] device vif8.0-emu entered promiscuous mode
[ 2506.783073] xenbr0: port 3(vif8.0-emu) entering forwarding state
[ 2506.783079] xenbr0: port 3(vif8.0-emu) entering forwarding state
[ 2506.895379] pciback 0000:02:00.0: restoring config space at offset
0xf (was 0x100, writing 0x10a)
[ 2506.895393] pciback 0000:02:00.0: restoring config space at offset
0xc (was 0x0, writing 0xf7a00000)
[ 2506.895410] pciback 0000:02:00.0: restoring config space at offset
0x7 (was 0x4, writing 0xf7a80004)
[ 2506.895420] pciback 0000:02:00.0: restoring config space at offset
0x5 (was 0x4, writing 0xf7ac0004)
[ 2506.895428] pciback 0000:02:00.0: restoring config space at offset
0x4 (was 0x1, writing 0xd001)
[ 2506.895435] pciback 0000:02:00.0: restoring config space at offset
0x3 (was 0x0, writing 0x10)
[ 2507.056216] xen-pciback: vpci: 0000:02:00.0: assign to virtual slot 0
[ 2507.056398] pciback 0000:02:00.0: device has been assigned to
another domain! Over-writting the ownership, but beware.
[ 2517.191338] vif8.0-emu: no IPv6 routers present
[ 2521.799320] xenbr0: port 3(vif8.0-emu) entering forwarding state

and here is my ifconfig while ubuntu is booted (without VMs it doesn't
have the vifs):
eth0      Link encap:Ethernet  HWaddr 00:e0:81:cb:db:74
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:71977 errors:0 dropped:0 overruns:0 frame:0
          TX packets:126629 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5472933 (5.4 MB)  TX bytes:57934759 (57.9 MB)
          Interrupt:16 Memory:f7900000-f7920000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4002 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4002 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:26667388 (26.6 MB)  TX bytes:26667388 (26.6 MB)

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

vif8.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:172 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 B)  TX bytes:26220 (26.2 KB)

xenbr0    Link encap:Ethernet  HWaddr 00:e0:81:cb:db:74
          inet addr:192.168.1.7  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:81ff:fecb:db74/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:71245 errors:0 dropped:0 overruns:0 frame:0
          TX packets:98995 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3595409 (3.5 MB)  TX bytes:55909320 (55.9 MB)

And the line from my ubuntu.conf:
vif = ['bridge=xenbr0']

Thanks-
David

[-- Attachment #2: xen-hotplug.log --]
[-- Type: application/octet-stream, Size: 43 bytes --]

RTNETLINK answers: Operation not supported

[-- Attachment #3: qemu-dm-ubuntu.log --]
[-- Type: application/octet-stream, Size: 1650 bytes --]

char device redirected to /dev/pts/2
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] xen_pt_initfn: Assigning real physical device 02:00.0 to devfn 0x28
[00:05.0] xen_pt_register_regions: IO region 0 registered (size=0x00000100 base_addr=0x0000d000 type: 0x1)
[00:05.0] xen_pt_register_regions: IO region 1 registered (size=0x00004000 base_addr=0xf7ac0000 type: 0)
[00:05.0] xen_pt_register_regions: IO region 3 registered (size=0x00040000 base_addr=0xf7a80000 type: 0)
[00:05.0] xen_pt_register_regions: Expansion ROM registered (size=0x00080000 base_addr=0xf7a00000)
[00:05.0] xen_pt_msix_init: get MSI-X table BAR base 0xf7ac0000
[00:05.0] xen_pt_msix_init: table_off = 0x2000, total_entries = 15
[00:05.0] xen_pt_msix_init: mapping physical MSI-X table to 0x7fb4d02ca000
[00:05.0] xen_pt_pci_intx: intx=1
[00:05.0] xen_pt_initfn: Real physical device 02:00.0 registered successfuly!
[00:05.0] xen_pt_msixctrl_reg_write: enable MSI-X
[00:05.0] msi_msix_setup: requested pirq 4 for MSI-X (vec: 0, entry: 0)
[00:05.0] msi_msix_update: Updating MSI-X with pirq 4 gvec 0 gflags 0x3037 (entry: 0)
[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.
[00:05.0] xen_pt_msixctrl_reg_write: disable MSI-X

[-- Attachment #4: ubuntu_guest_boot.log --]
[-- Type: application/octet-stream, Size: 40169 bytes --]

[-- Attachment #5: ubuntu_guest_xl_dmesg.log --]
[-- Type: application/octet-stream, Size: 37735 bytes --]

 __  __            _  _    ____                     _        _     _      
 \ \/ /___ _ __   | || |  |___ \    _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \  | || |_   __) |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | | |__   _| / __/|__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_|    |_|(_)_____|   \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                          
(XEN) Xen version 4.2-unstable (derickso@hsd1.ca.comcast.net) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) Tue Jul 31 08:47:04 PDT 2012
(XEN) Latest ChangeSet: Fri Jul 27 12:22:13 2012 +0200 25688:e6266fc76d08
(XEN) Bootloader: GRUB 1.99-21ubuntu3.1
(XEN) Command line: placeholder dom0_mem=4096M xsave=0
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009c800 (usable)
(XEN)  000000000009c800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000ddd07000 (usable)
(XEN)  00000000ddd07000 - 00000000dddbb000 (reserved)
(XEN)  00000000dddbb000 - 00000000dddbc000 (ACPI data)
(XEN)  00000000dddbc000 - 00000000dded7000 (ACPI NVS)
(XEN)  00000000dded7000 - 00000000def92000 (reserved)
(XEN)  00000000def92000 - 00000000def93000 (usable)
(XEN)  00000000def93000 - 00000000defd6000 (ACPI NVS)
(XEN)  00000000defd6000 - 00000000df800000 (usable)
(XEN)  00000000f8000000 - 00000000fc000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fed00000 - 00000000fed04000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000420000000 (usable)
(XEN) ACPI: RSDP 000F0490, 0024 (r2 ALASKA)
(XEN) ACPI: XSDT DDEC7090, 009C (r1 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: FACP DDED1CA0, 00F4 (r4 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: DSDT DDEC71C0, AADA (r2 ALASKA    A M I       6F INTL 20051117)
(XEN) ACPI: FACS DDED5F80, 0040
(XEN) ACPI: APIC DDED1D98, 0092 (r3 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: FPDT DDED1E30, 0044 (r1 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: MCFG DDED1E78, 003C (r1 ALASKA    A M I  1072009 MSFT       97)
(XEN) ACPI: PRAD DDED1EB8, 00BE (r2 PRADID  PRADTID        1 MSFT  3000001)
(XEN) ACPI: HPET DDED1F78, 0038 (r1 ALASKA    A M I  1072009 AMI.        5)
(XEN) ACPI: SSDT DDED1FB0, 036D (r1 SataRe SataTabl     1000 INTL 20091112)
(XEN) ACPI: SPMI DDED2320, 0040 (r5 A M I   OEMSPMI        0 AMI.        0)
(XEN) ACPI: SSDT DDED2360, 09A4 (r1  PmRef  Cpu0Ist     3000 INTL 20051117)
(XEN) ACPI: SSDT DDED2D08, 0A88 (r1  PmRef    CpuPm     3000 INTL 20051117)
(XEN) ACPI: DMAR DDED3790, 0078 (r1 INTEL      SNB         1 INTL        1)
(XEN) ACPI: EINJ DDED3808, 0130 (r1    AMI AMI EINJ        0             0)
(XEN) ACPI: ERST DDED3938, 0210 (r1  AMIER AMI ERST        0             0)
(XEN) ACPI: HEST DDED3B48, 00A8 (r1    AMI AMI HEST        0             0)
(XEN) ACPI: BERT DDED3BF0, 0030 (r1    AMI AMI BERT        0             0)
(XEN) System RAM: 16356MB (16749368kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000000420000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000fd7b0
(XEN) DMI 2.7 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT - dded5f80/0000000000000000, using 32
(XEN) ACPI:                  wakeup_vec[dded5f8c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
(XEN) Processor #4 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
(XEN) Processor #6 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
(XEN) Processor #1 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
(XEN) Processor #3 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
(XEN) Processor #5 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
(XEN) Processor #7 7:10 APIC version 21
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) ERST table is invalid
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 8 CPUs (0 hotplug CPUs)
(XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X
(XEN) Switched to APIC driver x2apic_cluster.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3292.578 MHz processor.
(XEN) Initing memory sharing.
(XEN) mce_intel.c:1239: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extended MCE MSR 0
(XEN) Intel machine check reporting enabled
(XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f
(XEN) PCI: MCFG area at f8000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-3f
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) TSC deadline timer enabled
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 64 KiB.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN)  - Unrestricted Guest
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB
(XEN) Brought up 8 CPUs
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0xac5000
(XEN) elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xe60e0
(XEN) elf_parse_binary: phdr: paddr=0x1ce7000 memsz=0x14480
(XEN) elf_parse_binary: phdr: paddr=0x1cfc000 memsz=0x362000
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x205e000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff81cfc200
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xffffffff80000000
(XEN)     elf_paddr_offset = 0x0
(XEN)     virt_offset      = 0xffffffff80000000
(XEN)     virt_kstart      = 0xffffffff81000000
(XEN)     virt_kend        = 0xffffffff8205e000
(XEN)     virt_entry       = 0xffffffff81cfc200
(XEN)     p2m_base         = 0xffffffffffffffff
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x205e000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000040c000000->0000000410000000 (1022357 pages to be allocated)
(XEN)  Init. ramdisk: 000000041d995000->000000041ffff200
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff8205e000
(XEN)  Init. ramdisk: ffffffff8205e000->ffffffff846c8200
(XEN)  Phys-Mach map: ffffffff846c9000->ffffffff84ec9000
(XEN)  Start info:    ffffffff84ec9000->ffffffff84ec94b4
(XEN)  Page tables:   ffffffff84eca000->ffffffff84ef5000
(XEN)  Boot stack:    ffffffff84ef5000->ffffffff84ef6000
(XEN)  TOTAL:         ffffffff80000000->ffffffff85000000
(XEN)  ENTRY ADDRESS: ffffffff81cfc200
(XEN) Dom0 has maximum 8 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81ac5000
(XEN) elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81ce60e0
(XEN) elf_load_binary: phdr 2 at 0xffffffff81ce7000 -> 0xffffffff81cfb480
(XEN) elf_load_binary: phdr 3 at 0xffffffff81cfc000 -> 0xffffffff81dd2000
(XEN) Scrubbing Free RAM: ........................................................................................................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 240kB init memory.
(XEN) DEBUG evtchn_bind_pirq 408 pirq=9 irq=9 emuirq=472850432
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:01.0
(XEN) PCI add device 0000:00:01.1
(XEN) PCI add device 0000:00:06.0
(XEN) PCI add device 0000:00:1a.0
(XEN) PCI add device 0000:00:1c.0
(XEN) PCI add device 0000:00:1c.6
(XEN) PCI add device 0000:00:1d.0
(XEN) PCI add device 0000:00:1e.0
(XEN) PCI add device 0000:00:1f.0
(XEN) PCI add device 0000:00:1f.2
(XEN) PCI add device 0000:00:1f.3
(XEN) PCI add device 0000:01:00.0
(XEN) PCI add device 0000:01:00.1
(XEN) PCI add device 0000:02:00.0
(XEN) PCI add device 0000:04:00.0
(XEN) PCI add device 0000:05:00.0
(XEN) PCI add device 0000:06:00.0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=276 irq=28 emuirq=-607835121
(XEN) DEBUG evtchn_bind_pirq 408 pirq=16 irq=16 emuirq=281805571
(XEN) DEBUG evtchn_bind_pirq 408 pirq=8 irq=8 emuirq=0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=275 irq=29 emuirq=1996518789
(XEN) DEBUG evtchn_bind_pirq 408 pirq=274 irq=30 emuirq=132368
(XEN) DEBUG evtchn_bind_pirq 408 pirq=273 irq=31 emuirq=496581248
(XEN) HVM1: HVM Loader
(XEN) HVM1: Detected Xen v4.2-unstable
(XEN) HVM1: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM1: System requested SeaBIOS
(XEN) HVM1: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom1 PCI link 0 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom1 PCI link 1 changed 0 -> 10
(XEN) HVM1: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom1 PCI link 2 changed 0 -> 11
(XEN) HVM1: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom1 PCI link 3 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 3 routed to IRQ5
(XEN) HVM1: pci dev 01:3 INTA->IRQ10
(XEN) HVM1: pci dev 03:0 INTA->IRQ5
(XEN) HVM1: pci dev 04:0 INTA->IRQ5
(XEN) HVM1: pci dev 05:0 INTA->IRQ10
(XEN) HVM1: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM1: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM1: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM1: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM1: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM1: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM1: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM1: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM1: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM1: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM1: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom1 gport=c200 mport=d000 nr=100
(XEN) HVM1: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM1: Multiprocessor initialisation:
(XEN) HVM1:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM1:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM1: Testing HVM environment:
(XEN) HVM1:  - REP INSB across page boundaries ... passed
(XEN) HVM1:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM1: Passed 2 of 2 tests
(XEN) HVM1: Writing SMBIOS tables ...
(XEN) HVM1: Loading SeaBIOS ...
(XEN) HVM1: Creating MP tables ...
(XEN) HVM1: Loading ACPI ...
(XEN) HVM1: vm86 TSS at fc00a080
(XEN) HVM1: BIOS map:
(XEN) HVM1:  10000-100d3: Scratch space
(XEN) HVM1:  e0000-fffff: Main BIOS
(XEN) HVM1: E820 table:
(XEN) HVM1:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM1:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM1:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM1:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM1:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM1:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM1: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d1 entering stdvga and caching modes
(XEN) memory_map:add: dom1 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom1 gfn=f3000 mfn=f7a00 nr=80
(XEN) HVM2: HVM Loader
(XEN) HVM2: Detected Xen v4.2-unstable
(XEN) HVM2: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM2: System requested SeaBIOS
(XEN) HVM2: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom2 PCI link 0 changed 0 -> 5
(XEN) HVM2: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom2 PCI link 1 changed 0 -> 10
(XEN) HVM2: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom2 PCI link 2 changed 0 -> 11
(XEN) HVM2: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom2 PCI link 3 changed 0 -> 5
(XEN) HVM2: PCI-ISA link 3 routed to IRQ5
(XEN) HVM2: pci dev 01:3 INTA->IRQ10
(XEN) HVM2: pci dev 03:0 INTA->IRQ5
(XEN) HVM2: pci dev 04:0 INTA->IRQ5
(XEN) HVM2: pci dev 05:0 INTA->IRQ10
(XEN) HVM2: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM2: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM2: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM2: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM2: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM2: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM2: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM2: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM2: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM2: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM2: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM2: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom2 gport=c200 mport=d000 nr=100
(XEN) HVM2: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM2: Multiprocessor initialisation:
(XEN) HVM2:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM2:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM2: Testing HVM environment:
(XEN) HVM2:  - REP INSB across page boundaries ... passed
(XEN) HVM2:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM2: Passed 2 of 2 tests
(XEN) HVM2: Writing SMBIOS tables ...
(XEN) HVM2: Loading SeaBIOS ...
(XEN) HVM2: Creating MP tables ...
(XEN) HVM2: Loading ACPI ...
(XEN) HVM2: vm86 TSS at fc00a080
(XEN) HVM2: BIOS map:
(XEN) HVM2:  10000-100d3: Scratch space
(XEN) HVM2:  e0000-fffff: Main BIOS
(XEN) HVM2: E820 table:
(XEN) HVM2:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM2:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM2:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM2:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM2:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM2:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM2: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d2 entering stdvga and caching modes
(XEN) memory_map:add: dom2 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom2 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d2 leaving stdvga
(XEN) HVM3: HVM Loader
(XEN) HVM3: Detected Xen v4.2-unstable
(XEN) HVM3: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM3: System requested SeaBIOS
(XEN) HVM3: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom3 PCI link 0 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom3 PCI link 1 changed 0 -> 10
(XEN) HVM3: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom3 PCI link 2 changed 0 -> 11
(XEN) HVM3: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom3 PCI link 3 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 3 routed to IRQ5
(XEN) HVM3: pci dev 01:3 INTA->IRQ10
(XEN) HVM3: pci dev 03:0 INTA->IRQ5
(XEN) HVM3: pci dev 04:0 INTA->IRQ5
(XEN) HVM3: pci dev 05:0 INTA->IRQ10
(XEN) HVM3: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM3: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM3: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM3: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM3: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM3: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM3: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM3: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM3: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM3: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM3: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM3: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) HVM3: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM3: Multiprocessor initialisation:
(XEN) HVM3:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM3:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM3: Testing HVM environment:
(XEN) HVM3:  - REP INSB across page boundaries ... passed
(XEN) HVM3:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM3: Passed 2 of 2 tests
(XEN) HVM3: Writing SMBIOS tables ...
(XEN) HVM3: Loading SeaBIOS ...
(XEN) HVM3: Creating MP tables ...
(XEN) HVM3: Loading ACPI ...
(XEN) HVM3: vm86 TSS at fc00a080
(XEN) HVM3: BIOS map:
(XEN) HVM3:  10000-100d3: Scratch space
(XEN) HVM3:  e0000-fffff: Main BIOS
(XEN) HVM3: E820 table:
(XEN) HVM3:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM3:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM3:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM3:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM3:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM3:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM3: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d3 entering stdvga and caching modes
(XEN) memory_map:add: dom3 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom3 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d3 leaving stdvga
(XEN) stdvga.c:147:d3 entering stdvga and caching modes
(XEN) irq.c:375: Dom3 callback via changed to Direct Vector 0xf3
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) irq.c:270: Dom3 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom3 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom3 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom3 PCI link 3 changed 5 -> 0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=19 irq=0 emuirq=1
(XEN) DEBUG evtchn_bind_pirq 408 pirq=17 irq=0 emuirq=8
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) DEBUG evtchn_bind_pirq 408 pirq=20 irq=0 emuirq=6
(XEN) DEBUG evtchn_bind_pirq 408 pirq=55 irq=-1 emuirq=-1
(XEN) DEBUG hvm_pci_msi_assert pirq=4 hvm_domain_use_pirq=0 emuirq=-1
(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3
(XEN) DEBUG evtchn_bind_pirq 408 pirq=22 irq=0 emuirq=7
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) HVM4: HVM Loader
(XEN) HVM4: Detected Xen v4.2-unstable
(XEN) HVM4: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM4: System requested SeaBIOS
(XEN) HVM4: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom4 PCI link 0 changed 0 -> 5
(XEN) HVM4: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom4 PCI link 1 changed 0 -> 10
(XEN) HVM4: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom4 PCI link 2 changed 0 -> 11
(XEN) HVM4: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom4 PCI link 3 changed 0 -> 5
(XEN) HVM4: PCI-ISA link 3 routed to IRQ5
(XEN) HVM4: pci dev 01:3 INTA->IRQ10
(XEN) HVM4: pci dev 03:0 INTA->IRQ5
(XEN) HVM4: pci dev 04:0 INTA->IRQ5
(XEN) HVM4: pci dev 05:0 INTA->IRQ10
(XEN) HVM4: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM4: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM4: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM4: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM4: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM4: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM4: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM4: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM4: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM4: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM4: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM4: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) HVM4: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM4: Multiprocessor initialisation:
(XEN) HVM4:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: Testing HVM environment:
(XEN) HVM4:  - REP INSB across page boundaries ... passed
(XEN) HVM4:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM4: Passed 2 of 2 tests
(XEN) HVM4: Writing SMBIOS tables ...
(XEN) HVM4: Loading SeaBIOS ...
(XEN) HVM4: Creating MP tables ...
(XEN) HVM4: Loading ACPI ...
(XEN) HVM4: vm86 TSS at fc00a080
(XEN) HVM4: BIOS map:
(XEN) HVM4:  10000-100d3: Scratch space
(XEN) HVM4:  e0000-fffff: Main BIOS
(XEN) HVM4: E820 table:
(XEN) HVM4:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM4:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM4:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM4:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM4:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM4:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM4: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d4 entering stdvga and caching modes
(XEN) memory_map:add: dom4 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom4 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d4 leaving stdvga
(XEN) stdvga.c:147:d4 entering stdvga and caching modes
(XEN) irq.c:375: Dom4 callback via changed to Direct Vector 0xf3
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) irq.c:270: Dom4 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom4 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom4 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom4 PCI link 3 changed 5 -> 0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=19 irq=0 emuirq=1
(XEN) DEBUG evtchn_bind_pirq 408 pirq=17 irq=0 emuirq=8
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) DEBUG evtchn_bind_pirq 408 pirq=20 irq=0 emuirq=6
(XEN) DEBUG evtchn_bind_pirq 408 pirq=55 irq=-1 emuirq=-1
(XEN) DEBUG hvm_pci_msi_assert pirq=4 hvm_domain_use_pirq=0 emuirq=-1
(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3
(XEN) DEBUG evtchn_bind_pirq 408 pirq=22 irq=0 emuirq=7
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) HVM5: HVM Loader
(XEN) HVM5: Detected Xen v4.2-unstable
(XEN) HVM5: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM5: System requested SeaBIOS
(XEN) HVM5: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom5 PCI link 0 changed 0 -> 5
(XEN) HVM5: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom5 PCI link 1 changed 0 -> 10
(XEN) HVM5: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom5 PCI link 2 changed 0 -> 11
(XEN) HVM5: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom5 PCI link 3 changed 0 -> 5
(XEN) HVM5: PCI-ISA link 3 routed to IRQ5
(XEN) HVM5: pci dev 01:3 INTA->IRQ10
(XEN) HVM5: pci dev 03:0 INTA->IRQ5
(XEN) HVM5: pci dev 04:0 INTA->IRQ5
(XEN) HVM5: pci dev 05:0 INTA->IRQ10
(XEN) HVM5: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM5: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM5: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom5 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM5: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM5: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM5: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom5 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom5 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM5: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM5: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM5: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM5: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM5: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM5: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom5 gport=c200 mport=d000 nr=100
(XEN) HVM5: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM5: Multiprocessor initialisation:
(XEN) HVM5:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: Testing HVM environment:
(XEN) HVM5:  - REP INSB across page boundaries ... passed
(XEN) HVM5:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM5: Passed 2 of 2 tests
(XEN) HVM5: Writing SMBIOS tables ...
(XEN) HVM5: Loading SeaBIOS ...
(XEN) HVM5: Creating MP tables ...
(XEN) HVM5: Loading ACPI ...
(XEN) HVM5: vm86 TSS at fc00a080
(XEN) HVM5: BIOS map:
(XEN) HVM5:  10000-100d3: Scratch space
(XEN) HVM5:  e0000-fffff: Main BIOS
(XEN) HVM5: E820 table:
(XEN) HVM5:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM5:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM5:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM5:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM5:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM5:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM5: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d5 entering stdvga and caching modes
(XEN) memory_map:add: dom5 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom5 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d5 leaving stdvga
(XEN) HVM6: HVM Loader
(XEN) HVM6: Detected Xen v4.2-unstable
(XEN) HVM6: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM6: System requested SeaBIOS
(XEN) HVM6: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom6 PCI link 0 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom6 PCI link 1 changed 0 -> 10
(XEN) HVM6: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom6 PCI link 2 changed 0 -> 11
(XEN) HVM6: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom6 PCI link 3 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 3 routed to IRQ5
(XEN) HVM6: pci dev 01:3 INTA->IRQ10
(XEN) HVM6: pci dev 03:0 INTA->IRQ5
(XEN) HVM6: pci dev 04:0 INTA->IRQ5
(XEN) HVM6: pci dev 05:0 INTA->IRQ10
(XEN) HVM6: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM6: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM6: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM6: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM6: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM6: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM6: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM6: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM6: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM6: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM6: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM6: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) HVM6: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM6: Multiprocessor initialisation:
(XEN) HVM6:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: Testing HVM environment:
(XEN) HVM6:  - REP INSB across page boundaries ... passed
(XEN) HVM6:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM6: Passed 2 of 2 tests
(XEN) HVM6: Writing SMBIOS tables ...
(XEN) HVM6: Loading SeaBIOS ...
(XEN) HVM6: Creating MP tables ...
(XEN) HVM6: Loading ACPI ...
(XEN) HVM6: vm86 TSS at fc00a080
(XEN) HVM6: BIOS map:
(XEN) HVM6:  10000-100d3: Scratch space
(XEN) HVM6:  e0000-fffff: Main BIOS
(XEN) HVM6: E820 table:
(XEN) HVM6:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM6:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM6:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM6:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM6:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM6:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM6: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d6 entering stdvga and caching modes
(XEN) memory_map:add: dom6 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom6 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d6 leaving stdvga
(XEN) stdvga.c:147:d6 entering stdvga and caching modes
(XEN) irq.c:375: Dom6 callback via changed to Direct Vector 0xf3
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) irq.c:270: Dom6 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom6 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom6 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom6 PCI link 3 changed 5 -> 0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=19 irq=0 emuirq=1
(XEN) DEBUG evtchn_bind_pirq 408 pirq=17 irq=0 emuirq=8
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) DEBUG evtchn_bind_pirq 408 pirq=20 irq=0 emuirq=6
(XEN) DEBUG evtchn_bind_pirq 408 pirq=55 irq=-1 emuirq=-1
(XEN) DEBUG hvm_pci_msi_assert pirq=4 hvm_domain_use_pirq=0 emuirq=-1
(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3
(XEN) DEBUG evtchn_bind_pirq 408 pirq=22 irq=0 emuirq=7
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4

[-- Attachment #6: qemu-dm-solaris.log --]
[-- Type: application/octet-stream, Size: 1204 bytes --]

char device redirected to /dev/pts/2
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 = Invalid argument): Internal error
xen be: qdisk-768: xc_gnttab_set_max_grants failed: Invalid argument
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] xen_pt_initfn: Assigning real physical device 02:00.0 to devfn 0x28
[00:05.0] xen_pt_register_regions: IO region 0 registered (size=0x00000100 base_addr=0x0000d000 type: 0x1)
[00:05.0] xen_pt_register_regions: IO region 1 registered (size=0x00004000 base_addr=0xf7ac0000 type: 0)
[00:05.0] xen_pt_register_regions: IO region 3 registered (size=0x00040000 base_addr=0xf7a80000 type: 0)
[00:05.0] xen_pt_register_regions: Expansion ROM registered (size=0x00080000 base_addr=0xf7a00000)
[00:05.0] xen_pt_msix_init: get MSI-X table BAR base 0xf7ac0000
[00:05.0] xen_pt_msix_init: table_off = 0x2000, total_entries = 15
[00:05.0] xen_pt_msix_init: mapping physical MSI-X table to 0x7fc528489000
[00:05.0] xen_pt_pci_intx: intx=1
[00:05.0] xen_pt_initfn: Real physical device 02:00.0 registered successfuly!

[-- Attachment #7: solaris_guest_boot.log --]
[-- Type: application/octet-stream, Size: 3274 bytes --]

[-- Attachment #8: solaris_guest_xl_dmesg.log --]
[-- Type: application/octet-stream, Size: 42405 bytes --]

 __  __            _  _    ____                     _        _     _      
 \ \/ /___ _ __   | || |  |___ \    _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \  | || |_   __) |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | | |__   _| / __/|__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_|    |_|(_)_____|   \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                          
(XEN) Xen version 4.2-unstable (derickso@hsd1.ca.comcast.net) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) Tue Jul 31 08:47:04 PDT 2012
(XEN) Latest ChangeSet: Fri Jul 27 12:22:13 2012 +0200 25688:e6266fc76d08
(XEN) Bootloader: GRUB 1.99-21ubuntu3.1
(XEN) Command line: placeholder dom0_mem=4096M xsave=0
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009c800 (usable)
(XEN)  000000000009c800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000ddd07000 (usable)
(XEN)  00000000ddd07000 - 00000000dddbb000 (reserved)
(XEN)  00000000dddbb000 - 00000000dddbc000 (ACPI data)
(XEN)  00000000dddbc000 - 00000000dded7000 (ACPI NVS)
(XEN)  00000000dded7000 - 00000000def92000 (reserved)
(XEN)  00000000def92000 - 00000000def93000 (usable)
(XEN)  00000000def93000 - 00000000defd6000 (ACPI NVS)
(XEN)  00000000defd6000 - 00000000df800000 (usable)
(XEN)  00000000f8000000 - 00000000fc000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fed00000 - 00000000fed04000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000420000000 (usable)
(XEN) ACPI: RSDP 000F0490, 0024 (r2 ALASKA)
(XEN) ACPI: XSDT DDEC7090, 009C (r1 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: FACP DDED1CA0, 00F4 (r4 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: DSDT DDEC71C0, AADA (r2 ALASKA    A M I       6F INTL 20051117)
(XEN) ACPI: FACS DDED5F80, 0040
(XEN) ACPI: APIC DDED1D98, 0092 (r3 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: FPDT DDED1E30, 0044 (r1 ALASKA    A M I  1072009 AMI     10013)
(XEN) ACPI: MCFG DDED1E78, 003C (r1 ALASKA    A M I  1072009 MSFT       97)
(XEN) ACPI: PRAD DDED1EB8, 00BE (r2 PRADID  PRADTID        1 MSFT  3000001)
(XEN) ACPI: HPET DDED1F78, 0038 (r1 ALASKA    A M I  1072009 AMI.        5)
(XEN) ACPI: SSDT DDED1FB0, 036D (r1 SataRe SataTabl     1000 INTL 20091112)
(XEN) ACPI: SPMI DDED2320, 0040 (r5 A M I   OEMSPMI        0 AMI.        0)
(XEN) ACPI: SSDT DDED2360, 09A4 (r1  PmRef  Cpu0Ist     3000 INTL 20051117)
(XEN) ACPI: SSDT DDED2D08, 0A88 (r1  PmRef    CpuPm     3000 INTL 20051117)
(XEN) ACPI: DMAR DDED3790, 0078 (r1 INTEL      SNB         1 INTL        1)
(XEN) ACPI: EINJ DDED3808, 0130 (r1    AMI AMI EINJ        0             0)
(XEN) ACPI: ERST DDED3938, 0210 (r1  AMIER AMI ERST        0             0)
(XEN) ACPI: HEST DDED3B48, 00A8 (r1    AMI AMI HEST        0             0)
(XEN) ACPI: BERT DDED3BF0, 0030 (r1    AMI AMI BERT        0             0)
(XEN) System RAM: 16356MB (16749368kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000000420000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000fd7b0
(XEN) DMI 2.7 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT - dded5f80/0000000000000000, using 32
(XEN) ACPI:                  wakeup_vec[dded5f8c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
(XEN) Processor #4 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
(XEN) Processor #6 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
(XEN) Processor #1 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
(XEN) Processor #3 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
(XEN) Processor #5 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
(XEN) Processor #7 7:10 APIC version 21
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) ERST table is invalid
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 8 CPUs (0 hotplug CPUs)
(XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X
(XEN) Switched to APIC driver x2apic_cluster.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3292.578 MHz processor.
(XEN) Initing memory sharing.
(XEN) mce_intel.c:1239: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extended MCE MSR 0
(XEN) Intel machine check reporting enabled
(XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f
(XEN) PCI: MCFG area at f8000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-3f
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) TSC deadline timer enabled
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 64 KiB.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN)  - Unrestricted Guest
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB
(XEN) Brought up 8 CPUs
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0xac5000
(XEN) elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xe60e0
(XEN) elf_parse_binary: phdr: paddr=0x1ce7000 memsz=0x14480
(XEN) elf_parse_binary: phdr: paddr=0x1cfc000 memsz=0x362000
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x205e000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff81cfc200
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xffffffff80000000
(XEN)     elf_paddr_offset = 0x0
(XEN)     virt_offset      = 0xffffffff80000000
(XEN)     virt_kstart      = 0xffffffff81000000
(XEN)     virt_kend        = 0xffffffff8205e000
(XEN)     virt_entry       = 0xffffffff81cfc200
(XEN)     p2m_base         = 0xffffffffffffffff
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x205e000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000040c000000->0000000410000000 (1022357 pages to be allocated)
(XEN)  Init. ramdisk: 000000041d995000->000000041ffff200
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff8205e000
(XEN)  Init. ramdisk: ffffffff8205e000->ffffffff846c8200
(XEN)  Phys-Mach map: ffffffff846c9000->ffffffff84ec9000
(XEN)  Start info:    ffffffff84ec9000->ffffffff84ec94b4
(XEN)  Page tables:   ffffffff84eca000->ffffffff84ef5000
(XEN)  Boot stack:    ffffffff84ef5000->ffffffff84ef6000
(XEN)  TOTAL:         ffffffff80000000->ffffffff85000000
(XEN)  ENTRY ADDRESS: ffffffff81cfc200
(XEN) Dom0 has maximum 8 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81ac5000
(XEN) elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81ce60e0
(XEN) elf_load_binary: phdr 2 at 0xffffffff81ce7000 -> 0xffffffff81cfb480
(XEN) elf_load_binary: phdr 3 at 0xffffffff81cfc000 -> 0xffffffff81dd2000
(XEN) Scrubbing Free RAM: ........................................................................................................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 240kB init memory.
(XEN) DEBUG evtchn_bind_pirq 408 pirq=9 irq=9 emuirq=472850432
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:01.0
(XEN) PCI add device 0000:00:01.1
(XEN) PCI add device 0000:00:06.0
(XEN) PCI add device 0000:00:1a.0
(XEN) PCI add device 0000:00:1c.0
(XEN) PCI add device 0000:00:1c.6
(XEN) PCI add device 0000:00:1d.0
(XEN) PCI add device 0000:00:1e.0
(XEN) PCI add device 0000:00:1f.0
(XEN) PCI add device 0000:00:1f.2
(XEN) PCI add device 0000:00:1f.3
(XEN) PCI add device 0000:01:00.0
(XEN) PCI add device 0000:01:00.1
(XEN) PCI add device 0000:02:00.0
(XEN) PCI add device 0000:04:00.0
(XEN) PCI add device 0000:05:00.0
(XEN) PCI add device 0000:06:00.0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=276 irq=28 emuirq=-607835121
(XEN) DEBUG evtchn_bind_pirq 408 pirq=16 irq=16 emuirq=281805571
(XEN) DEBUG evtchn_bind_pirq 408 pirq=8 irq=8 emuirq=0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=275 irq=29 emuirq=1996518789
(XEN) DEBUG evtchn_bind_pirq 408 pirq=274 irq=30 emuirq=132368
(XEN) DEBUG evtchn_bind_pirq 408 pirq=273 irq=31 emuirq=496581248
(XEN) HVM1: HVM Loader
(XEN) HVM1: Detected Xen v4.2-unstable
(XEN) HVM1: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM1: System requested SeaBIOS
(XEN) HVM1: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom1 PCI link 0 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom1 PCI link 1 changed 0 -> 10
(XEN) HVM1: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom1 PCI link 2 changed 0 -> 11
(XEN) HVM1: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom1 PCI link 3 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 3 routed to IRQ5
(XEN) HVM1: pci dev 01:3 INTA->IRQ10
(XEN) HVM1: pci dev 03:0 INTA->IRQ5
(XEN) HVM1: pci dev 04:0 INTA->IRQ5
(XEN) HVM1: pci dev 05:0 INTA->IRQ10
(XEN) HVM1: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM1: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM1: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom1 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM1: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM1: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM1: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom1 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom1 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM1: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM1: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM1: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM1: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM1: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom1 gport=c200 mport=d000 nr=100
(XEN) HVM1: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM1: Multiprocessor initialisation:
(XEN) HVM1:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM1:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM1: Testing HVM environment:
(XEN) HVM1:  - REP INSB across page boundaries ... passed
(XEN) HVM1:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM1: Passed 2 of 2 tests
(XEN) HVM1: Writing SMBIOS tables ...
(XEN) HVM1: Loading SeaBIOS ...
(XEN) HVM1: Creating MP tables ...
(XEN) HVM1: Loading ACPI ...
(XEN) HVM1: vm86 TSS at fc00a080
(XEN) HVM1: BIOS map:
(XEN) HVM1:  10000-100d3: Scratch space
(XEN) HVM1:  e0000-fffff: Main BIOS
(XEN) HVM1: E820 table:
(XEN) HVM1:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM1:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM1:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM1:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM1:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM1:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM1: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d1 entering stdvga and caching modes
(XEN) memory_map:add: dom1 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom1 gfn=f3000 mfn=f7a00 nr=80
(XEN) HVM2: HVM Loader
(XEN) HVM2: Detected Xen v4.2-unstable
(XEN) HVM2: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM2: System requested SeaBIOS
(XEN) HVM2: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom2 PCI link 0 changed 0 -> 5
(XEN) HVM2: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom2 PCI link 1 changed 0 -> 10
(XEN) HVM2: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom2 PCI link 2 changed 0 -> 11
(XEN) HVM2: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom2 PCI link 3 changed 0 -> 5
(XEN) HVM2: PCI-ISA link 3 routed to IRQ5
(XEN) HVM2: pci dev 01:3 INTA->IRQ10
(XEN) HVM2: pci dev 03:0 INTA->IRQ5
(XEN) HVM2: pci dev 04:0 INTA->IRQ5
(XEN) HVM2: pci dev 05:0 INTA->IRQ10
(XEN) HVM2: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM2: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM2: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom2 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM2: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM2: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM2: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom2 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom2 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM2: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM2: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM2: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM2: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM2: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM2: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom2 gport=c200 mport=d000 nr=100
(XEN) HVM2: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM2: Multiprocessor initialisation:
(XEN) HVM2:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM2:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM2: Testing HVM environment:
(XEN) HVM2:  - REP INSB across page boundaries ... passed
(XEN) HVM2:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM2: Passed 2 of 2 tests
(XEN) HVM2: Writing SMBIOS tables ...
(XEN) HVM2: Loading SeaBIOS ...
(XEN) HVM2: Creating MP tables ...
(XEN) HVM2: Loading ACPI ...
(XEN) HVM2: vm86 TSS at fc00a080
(XEN) HVM2: BIOS map:
(XEN) HVM2:  10000-100d3: Scratch space
(XEN) HVM2:  e0000-fffff: Main BIOS
(XEN) HVM2: E820 table:
(XEN) HVM2:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM2:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM2:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM2:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM2:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM2:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM2: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d2 entering stdvga and caching modes
(XEN) memory_map:add: dom2 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom2 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d2 leaving stdvga
(XEN) HVM3: HVM Loader
(XEN) HVM3: Detected Xen v4.2-unstable
(XEN) HVM3: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM3: System requested SeaBIOS
(XEN) HVM3: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom3 PCI link 0 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom3 PCI link 1 changed 0 -> 10
(XEN) HVM3: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom3 PCI link 2 changed 0 -> 11
(XEN) HVM3: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom3 PCI link 3 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 3 routed to IRQ5
(XEN) HVM3: pci dev 01:3 INTA->IRQ10
(XEN) HVM3: pci dev 03:0 INTA->IRQ5
(XEN) HVM3: pci dev 04:0 INTA->IRQ5
(XEN) HVM3: pci dev 05:0 INTA->IRQ10
(XEN) HVM3: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM3: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM3: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM3: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM3: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM3: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM3: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM3: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM3: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM3: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM3: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM3: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) HVM3: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM3: Multiprocessor initialisation:
(XEN) HVM3:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM3:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM3: Testing HVM environment:
(XEN) HVM3:  - REP INSB across page boundaries ... passed
(XEN) HVM3:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM3: Passed 2 of 2 tests
(XEN) HVM3: Writing SMBIOS tables ...
(XEN) HVM3: Loading SeaBIOS ...
(XEN) HVM3: Creating MP tables ...
(XEN) HVM3: Loading ACPI ...
(XEN) HVM3: vm86 TSS at fc00a080
(XEN) HVM3: BIOS map:
(XEN) HVM3:  10000-100d3: Scratch space
(XEN) HVM3:  e0000-fffff: Main BIOS
(XEN) HVM3: E820 table:
(XEN) HVM3:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM3:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM3:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM3:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM3:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM3:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM3: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d3 entering stdvga and caching modes
(XEN) memory_map:add: dom3 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom3 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d3 leaving stdvga
(XEN) stdvga.c:147:d3 entering stdvga and caching modes
(XEN) irq.c:375: Dom3 callback via changed to Direct Vector 0xf3
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom3 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom3 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom3 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom3 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom3 gport=c200 mport=d000 nr=100
(XEN) irq.c:270: Dom3 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom3 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom3 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom3 PCI link 3 changed 5 -> 0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=19 irq=0 emuirq=1
(XEN) DEBUG evtchn_bind_pirq 408 pirq=17 irq=0 emuirq=8
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) DEBUG evtchn_bind_pirq 408 pirq=20 irq=0 emuirq=6
(XEN) DEBUG evtchn_bind_pirq 408 pirq=55 irq=-1 emuirq=-1
(XEN) DEBUG hvm_pci_msi_assert pirq=4 hvm_domain_use_pirq=0 emuirq=-1
(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3
(XEN) DEBUG evtchn_bind_pirq 408 pirq=22 irq=0 emuirq=7
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) HVM4: HVM Loader
(XEN) HVM4: Detected Xen v4.2-unstable
(XEN) HVM4: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM4: System requested SeaBIOS
(XEN) HVM4: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom4 PCI link 0 changed 0 -> 5
(XEN) HVM4: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom4 PCI link 1 changed 0 -> 10
(XEN) HVM4: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom4 PCI link 2 changed 0 -> 11
(XEN) HVM4: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom4 PCI link 3 changed 0 -> 5
(XEN) HVM4: PCI-ISA link 3 routed to IRQ5
(XEN) HVM4: pci dev 01:3 INTA->IRQ10
(XEN) HVM4: pci dev 03:0 INTA->IRQ5
(XEN) HVM4: pci dev 04:0 INTA->IRQ5
(XEN) HVM4: pci dev 05:0 INTA->IRQ10
(XEN) HVM4: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM4: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM4: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM4: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM4: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM4: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM4: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM4: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM4: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM4: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM4: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM4: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) HVM4: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM4: Multiprocessor initialisation:
(XEN) HVM4:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM4: Testing HVM environment:
(XEN) HVM4:  - REP INSB across page boundaries ... passed
(XEN) HVM4:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM4: Passed 2 of 2 tests
(XEN) HVM4: Writing SMBIOS tables ...
(XEN) HVM4: Loading SeaBIOS ...
(XEN) HVM4: Creating MP tables ...
(XEN) HVM4: Loading ACPI ...
(XEN) HVM4: vm86 TSS at fc00a080
(XEN) HVM4: BIOS map:
(XEN) HVM4:  10000-100d3: Scratch space
(XEN) HVM4:  e0000-fffff: Main BIOS
(XEN) HVM4: E820 table:
(XEN) HVM4:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM4:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM4:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM4:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM4:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM4:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM4: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d4 entering stdvga and caching modes
(XEN) memory_map:add: dom4 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom4 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d4 leaving stdvga
(XEN) stdvga.c:147:d4 entering stdvga and caching modes
(XEN) irq.c:375: Dom4 callback via changed to Direct Vector 0xf3
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom4 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom4 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom4 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom4 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom4 gport=c200 mport=d000 nr=100
(XEN) irq.c:270: Dom4 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom4 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom4 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom4 PCI link 3 changed 5 -> 0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=19 irq=0 emuirq=1
(XEN) DEBUG evtchn_bind_pirq 408 pirq=17 irq=0 emuirq=8
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) DEBUG evtchn_bind_pirq 408 pirq=20 irq=0 emuirq=6
(XEN) DEBUG evtchn_bind_pirq 408 pirq=55 irq=-1 emuirq=-1
(XEN) DEBUG hvm_pci_msi_assert pirq=4 hvm_domain_use_pirq=0 emuirq=-1
(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3
(XEN) DEBUG evtchn_bind_pirq 408 pirq=22 irq=0 emuirq=7
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) HVM5: HVM Loader
(XEN) HVM5: Detected Xen v4.2-unstable
(XEN) HVM5: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM5: System requested SeaBIOS
(XEN) HVM5: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom5 PCI link 0 changed 0 -> 5
(XEN) HVM5: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom5 PCI link 1 changed 0 -> 10
(XEN) HVM5: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom5 PCI link 2 changed 0 -> 11
(XEN) HVM5: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom5 PCI link 3 changed 0 -> 5
(XEN) HVM5: PCI-ISA link 3 routed to IRQ5
(XEN) HVM5: pci dev 01:3 INTA->IRQ10
(XEN) HVM5: pci dev 03:0 INTA->IRQ5
(XEN) HVM5: pci dev 04:0 INTA->IRQ5
(XEN) HVM5: pci dev 05:0 INTA->IRQ10
(XEN) HVM5: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM5: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM5: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom5 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM5: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM5: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM5: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom5 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom5 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM5: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM5: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM5: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM5: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM5: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM5: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom5 gport=c200 mport=d000 nr=100
(XEN) HVM5: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM5: Multiprocessor initialisation:
(XEN) HVM5:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: Testing HVM environment:
(XEN) HVM5:  - REP INSB across page boundaries ... passed
(XEN) HVM5:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM5: Passed 2 of 2 tests
(XEN) HVM5: Writing SMBIOS tables ...
(XEN) HVM5: Loading SeaBIOS ...
(XEN) HVM5: Creating MP tables ...
(XEN) HVM5: Loading ACPI ...
(XEN) HVM5: vm86 TSS at fc00a080
(XEN) HVM5: BIOS map:
(XEN) HVM5:  10000-100d3: Scratch space
(XEN) HVM5:  e0000-fffff: Main BIOS
(XEN) HVM5: E820 table:
(XEN) HVM5:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM5:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM5:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM5:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM5:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM5:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM5: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d5 entering stdvga and caching modes
(XEN) memory_map:add: dom5 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom5 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d5 leaving stdvga
(XEN) HVM6: HVM Loader
(XEN) HVM6: Detected Xen v4.2-unstable
(XEN) HVM6: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM6: System requested SeaBIOS
(XEN) HVM6: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom6 PCI link 0 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom6 PCI link 1 changed 0 -> 10
(XEN) HVM6: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom6 PCI link 2 changed 0 -> 11
(XEN) HVM6: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom6 PCI link 3 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 3 routed to IRQ5
(XEN) HVM6: pci dev 01:3 INTA->IRQ10
(XEN) HVM6: pci dev 03:0 INTA->IRQ5
(XEN) HVM6: pci dev 04:0 INTA->IRQ5
(XEN) HVM6: pci dev 05:0 INTA->IRQ10
(XEN) HVM6: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM6: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM6: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM6: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM6: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM6: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM6: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM6: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM6: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM6: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM6: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM6: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) HVM6: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM6: Multiprocessor initialisation:
(XEN) HVM6:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: Testing HVM environment:
(XEN) HVM6:  - REP INSB across page boundaries ... passed
(XEN) HVM6:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM6: Passed 2 of 2 tests
(XEN) HVM6: Writing SMBIOS tables ...
(XEN) HVM6: Loading SeaBIOS ...
(XEN) HVM6: Creating MP tables ...
(XEN) HVM6: Loading ACPI ...
(XEN) HVM6: vm86 TSS at fc00a080
(XEN) HVM6: BIOS map:
(XEN) HVM6:  10000-100d3: Scratch space
(XEN) HVM6:  e0000-fffff: Main BIOS
(XEN) HVM6: E820 table:
(XEN) HVM6:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM6:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM6:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM6:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM6:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM6:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM6: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d6 entering stdvga and caching modes
(XEN) memory_map:add: dom6 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom6 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d6 leaving stdvga
(XEN) stdvga.c:147:d6 entering stdvga and caching modes
(XEN) irq.c:375: Dom6 callback via changed to Direct Vector 0xf3
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom6 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) irq.c:270: Dom6 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom6 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom6 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom6 PCI link 3 changed 5 -> 0
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=18 irq=0 emuirq=12
(XEN) DEBUG evtchn_bind_pirq 408 pirq=19 irq=0 emuirq=1
(XEN) DEBUG evtchn_bind_pirq 408 pirq=17 irq=0 emuirq=8
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) DEBUG evtchn_bind_pirq 408 pirq=20 irq=0 emuirq=6
(XEN) DEBUG evtchn_bind_pirq 408 pirq=55 irq=-1 emuirq=-1
(XEN) DEBUG hvm_pci_msi_assert pirq=4 hvm_domain_use_pirq=0 emuirq=-1
(XEN) vmsi.c:108:d32767 Unsupported delivery mode 3
(XEN) DEBUG evtchn_bind_pirq 408 pirq=22 irq=0 emuirq=7
(XEN) DEBUG evtchn_bind_pirq 408 pirq=21 irq=0 emuirq=4
(XEN) HVM7: HVM Loader
(XEN) HVM7: Detected Xen v4.2-unstable
(XEN) HVM7: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM7: System requested SeaBIOS
(XEN) HVM7: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom7 PCI link 0 changed 0 -> 5
(XEN) HVM7: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom7 PCI link 1 changed 0 -> 10
(XEN) HVM7: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom7 PCI link 2 changed 0 -> 11
(XEN) HVM7: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom7 PCI link 3 changed 0 -> 5
(XEN) HVM7: PCI-ISA link 3 routed to IRQ5
(XEN) HVM7: pci dev 01:3 INTA->IRQ10
(XEN) HVM7: pci dev 03:0 INTA->IRQ5
(XEN) HVM7: pci dev 04:0 INTA->IRQ5
(XEN) HVM7: pci dev 05:0 INTA->IRQ10
(XEN) HVM7: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM7: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM7: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom7 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM7: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) HVM7: pci dev 02:0 bar 30 size 00010000: f30c0000
(XEN) HVM7: pci dev 04:0 bar 30 size 00010000: f30d0000
(XEN) memory_map:add: dom7 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom7 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) HVM7: pci dev 05:0 bar 14 size 00004000: f30e0004
(XEN) HVM7: pci dev 02:0 bar 14 size 00001000: f30e4000
(XEN) HVM7: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM7: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM7: pci dev 04:0 bar 14 size 00000100: f30e5000
(XEN) HVM7: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom7 gport=c200 mport=d000 nr=100
(XEN) HVM7: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM7: Multiprocessor initialisation:
(XEN) HVM7:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM7:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM7: Testing HVM environment:
(XEN) HVM7:  - REP INSB across page boundaries ... passed
(XEN) HVM7:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM7: Passed 2 of 2 tests
(XEN) HVM7: Writing SMBIOS tables ...
(XEN) HVM7: Loading SeaBIOS ...
(XEN) HVM7: Creating MP tables ...
(XEN) HVM7: Loading ACPI ...
(XEN) HVM7: vm86 TSS at fc00a080
(XEN) HVM7: BIOS map:
(XEN) HVM7:  10000-100d3: Scratch space
(XEN) HVM7:  e0000-fffff: Main BIOS
(XEN) HVM7: E820 table:
(XEN) HVM7:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM7:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM7:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM7:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM7:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM7:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM7: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d7 entering stdvga and caching modes
(XEN) memory_map:add: dom7 gfn=f3000 mfn=f7a00 nr=80
(XEN) memory_map:remove: dom7 gfn=f3000 mfn=f7a00 nr=80
(XEN) stdvga.c:151:d7 leaving stdvga
(XEN) memory_map:remove: dom7 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom7 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom7 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom7 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom7 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom7 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom7 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom7 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom7 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom7 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom7 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom7 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom7 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom7 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom7 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom7 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom7 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom7 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom7 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom7 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom7 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom7 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom7 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom7 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom7 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:remove: dom7 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom7 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:remove: dom7 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom7 gfn=f3080 mfn=f7a80 nr=40
(XEN) memory_map:add: dom7 gfn=f30e0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom7 gfn=f30e3 mfn=f7ac3 nr=1
(XEN) ioport_map:add: dom7 gport=c200 mport=d000 nr=100

[-- Attachment #9: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Wed, 2012-08-01 at 18:52 +0100, David Erickson wrote:
> my assumption is this is because of the error
> in xen-hotplug.log: "RTNETLINK answers: Operation not supported",

That's a benign warning AFAIK.

> and here is my ifconfig while ubuntu is booted (without VMs it doesn't
> have the vifs):

This all looks fine. I think you need to be investigating the network
configuration inside the guest. Does the eth* device exist, is it
configured etc

In your Ubuntu boot log I see:
        [    0.000000] Hypervisor detected: Xen HVM
        [    0.000000] Xen version 4.2.
        [    0.000000] Xen Platform PCI: I/O protocol version 1
        [    0.000000] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs.
        [    0.000000] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks.

which means you will need the xen-netfront driver to be loaded, I don't
see any logs to that effect. What does lsmod say? What about "ifconfig
-a". Does the driver even exist on the live cd under /lib/modules
somewhere?

It's a bit odd that you still have vifX.Y-emu in dom0 given that the
emulated device is supposed to have been unplugged. I wonder if that is
a (separate) bug with emu device unplug. Which qemu was this again?

If you added xen_emul_unplug=never to your guest command line then you
would avoid this unplug and you should have an emulated NIC available
instead.

Ian.

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]

On Thu, Aug 2, 2012 at 12:45 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Wed, 2012-08-01 at 18:52 +0100, David Erickson wrote:
>> my assumption is this is because of the error
>> in xen-hotplug.log: "RTNETLINK answers: Operation not supported",
>
> That's a benign warning AFAIK.
>
>> and here is my ifconfig while ubuntu is booted (without VMs it doesn't
>> have the vifs):
>
> This all looks fine. I think you need to be investigating the network
> configuration inside the guest. Does the eth* device exist, is it
> configured etc
>
> In your Ubuntu boot log I see:
>         [    0.000000] Hypervisor detected: Xen HVM
>         [    0.000000] Xen version 4.2.
>         [    0.000000] Xen Platform PCI: I/O protocol version 1
>         [    0.000000] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs.
>         [    0.000000] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks.
>
> which means you will need the xen-netfront driver to be loaded, I don't
> see any logs to that effect. What does lsmod say? What about "ifconfig
> -a". Does the driver even exist on the live cd under /lib/modules
> somewhere?


Hi Ian-
I've attached a log with the list of modules matching front,
xen-netfront.ko is definitely there, but lsmod doesn't show it loaded.
 And ifconfig shows nothing other than the loopback interface.

> It's a bit odd that you still have vifX.Y-emu in dom0 given that the
> emulated device is supposed to have been unplugged. I wonder if that is
> a (separate) bug with emu device unplug. Which qemu was this again?

Upstream, commit 5e3bc7144edd6e4fa2824944e5eb16c28197dd5a from 7/30

> If you added xen_emul_unplug=never to your guest command line then you
> would avoid this unplug and you should have an emulated NIC available
> instead.

Verified this did work.

Thanks,
David

[-- Attachment #2: ubuntu_guest_boot.log --]
[-- Type: application/octet-stream, Size: 1603 bytes --]

ubuntu@ubuntu:~$ lsmod
Module                  Size  Used by
bnep                   18436  2 
rfcomm                 47946  0 
bluetooth             166112  10 bnep,rfcomm
dm_crypt               23199  0 
lp                     17799  0 
ppdev                  17113  0 
psmouse                73882  0 
parport_pc             36962  1 
parport                46562  3 lp,ppdev,parport_pc
serio_raw              13166  0 
i2c_piix4              13301  0 
xen_platform_pci       12885  0 [permanent]
binfmt_misc            17540  1 
squashfs               36799  1 
overlayfs              28267  1 
nls_utf8               12557  1 
isofs                  40253  1 
dm_raid45              78155  0 
xor                    12894  1 dm_raid45
dm_mirror              22203  0 
dm_region_hash         20918  1 dm_mirror
dm_log                 18564  3 dm_raid45,dm_mirror,dm_region_hash
btrfs                 648895  0 
zlib_deflate           27139  1 btrfs
libcrc32c              12644  1 btrfs
mpt2sas               152860  0 
floppy                 70365  0 
scsi_transport_sas     40558  1 mpt2sas
raid_class             13622  1 mpt2sas
ubuntu@ubuntu:~$ ifconfig -a
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2496 (2.4 KB)  TX bytes:2496 (2.4 KB)


[-- Attachment #3: find.log --]
[-- Type: application/octet-stream, Size: 455 bytes --]

./3.0.0-12-generic/kernel/drivers/block/xen-blkfront.ko
./3.0.0-12-generic/kernel/drivers/input/misc/xen-kbdfront.ko
./3.0.0-12-generic/kernel/drivers/media/dvb/frontends
./3.0.0-12-generic/kernel/drivers/net/xen-netfront.ko
./3.0.0-12-generic/kernel/drivers/pci/xen-pcifront.ko
./3.0.0-12-generic/kernel/drivers/staging/frontier
./3.0.0-12-generic/kernel/drivers/video/xen-fbfront.ko
./3.0.0-12-generic/kernel/drivers/xen/xenbus/xenbus_probe_frontend.ko

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Thu, 2012-08-02 at 17:24 +0100, David Erickson wrote:
> On Thu, Aug 2, 2012 at 12:45 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> I've attached a log with the list of modules matching front,
> xen-netfront.ko is definitely there, but lsmod doesn't show it loaded.#

So did you try manually loading it?

[...]
> > If you added xen_emul_unplug=never to your guest command line then you
> > would avoid this unplug and you should have an emulated NIC available
> > instead.
> 
> Verified this did work.

Great.

> 
> Thanks,
> David

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Thu, Aug 2, 2012 at 9:45 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Thu, 2012-08-02 at 17:24 +0100, David Erickson wrote:
>> On Thu, Aug 2, 2012 at 12:45 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> I've attached a log with the list of modules matching front,
>> xen-netfront.ko is definitely there, but lsmod doesn't show it loaded.#
>
> So did you try manually loading it?

I did, I got:
insmod: error inserting
'/lib/modules/3.0.0-12-generic/kernel/drivers/net/xen-netfront.ko': -1
Unknown symbol in module

Presumably it depends on other not-loaded kernel modules, do you know which?

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Thu, Aug 2, 2012 at 10:10 AM, David Erickson <halcyon1981@gmail.com> wrote:
> On Thu, Aug 2, 2012 at 9:45 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> On Thu, 2012-08-02 at 17:24 +0100, David Erickson wrote:
>>> On Thu, Aug 2, 2012 at 12:45 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>>> I've attached a log with the list of modules matching front,
>>> xen-netfront.ko is definitely there, but lsmod doesn't show it loaded.#
>>
>> So did you try manually loading it?
>
> I did, I got:
> insmod: error inserting
> '/lib/modules/3.0.0-12-generic/kernel/drivers/net/xen-netfront.ko': -1
> Unknown symbol in module
>
> Presumably it depends on other not-loaded kernel modules, do you know which?

As a followup I ran the following:

ubuntu@ubuntu:~$ sudo modprobe xen-netfront
ubuntu@ubuntu:~$ [  238.408574] vbd vbd-5632: 19 xenbus_dev_probe on
device/vbd/5632
[  238.433304] vbd vbd-5632: failed to write error node for
device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632)

ubuntu@ubuntu:~$ sudo lsmod
Module                  Size  Used by
xen_blkfront           26261  0
xen_netfront           26671  0
xenbus_probe_frontend    13232  2 xen_blkfront,xen_netfront,[permanent]
bnep                   18436  2
rfcomm                 47946  0
bluetooth             166112  10 bnep,rfcomm
dm_crypt               23199  0
lp                     17799  0
ppdev                  17113  0
parport_pc             36962  1
parport                46562  3 lp,ppdev,parport_pc
psmouse                73882  0
serio_raw              13166  0
i2c_piix4              13301  0
xen_platform_pci       12885  0 [permanent]
binfmt_misc            17540  1
squashfs               36799  1
overlayfs              28267  1
nls_utf8               12557  1
isofs                  40253  1
dm_raid45              78155  0
xor                    12894  1 dm_raid45
dm_mirror              22203  0
dm_region_hash         20918  1 dm_mirror
dm_log                 18564  3 dm_raid45,dm_mirror,dm_region_hash
btrfs                 648895  0
zlib_deflate           27139  1 btrfs
libcrc32c              12644  1 btrfs
floppy                 70365  0
mpt2sas               152860  0
scsi_transport_sas     40558  1 mpt2sas
raid_class             13622  1 mpt2sas
ubuntu@ubuntu:~$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:3e:68:15:49
          inet addr:192.168.1.126  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::216:3eff:fe68:1549/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:54 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5952 (5.9 KB)  TX bytes:9522 (9.5 KB)
          Interrupt:75

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:96 errors:0 dropped:0 overruns:0 frame:0
          TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7392 (7.3 KB)  TX bytes:7392 (7.3 KB)

So it looks like it loaded (with some errors, are those problems?),
but still not sure why it didn't auto load on boot.

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Thu, 2012-08-02 at 18:12 +0100, David Erickson wrote:

> ubuntu@ubuntu:~$ sudo modprobe xen-netfront
> ubuntu@ubuntu:~$ [  238.408574] vbd vbd-5632: 19 xenbus_dev_probe on
> device/vbd/5632
> [  238.433304] vbd vbd-5632: failed to write error node for
> device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632)
> 
> ubuntu@ubuntu:~$ sudo lsmod
> Module                  Size  Used by
> xen_blkfront           26261  0
> xen_netfront           26671  0
> xenbus_probe_frontend    13232  2 xen_blkfront,xen_netfront,[permanent]
[...]
> ubuntu@ubuntu:~$ ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:16:3e:68:15:49
[...]
> So it looks like it loaded

Great.

>  (with some errors, are those problems?),

Strangely those were vbd (aka disk) errors.

> but still not sure why it didn't auto load on boot.

xenbus_probe_frontend is a module. It should either be built in or
Ubuntu's tools (primarily the one which builds initrds, but perhaps also
something in  the live-cd suite) need to learn to load it manually at
the appropriate times. It's a tiny module so we would generally
recommend building it in.

You should file this as a bug against Ubuntu, I think. I'd have sworn
this had been reported to them before but perhaps it has regressed.

Ian.

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

[-- Attachment #1: Type: text/plain, Size: 4985 bytes --]

On Wed, Aug 1, 2012 at 10:52 AM, David Erickson <halcyon1981@gmail.com> wrote:
> On Wed, Aug 1, 2012 at 4:13 AM, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
>> On Tue, 31 Jul 2012, David Erickson wrote:
>>> On Tue, Jul 31, 2012 at 4:39 AM, Stefano Stabellini
>>> <stefano.stabellini@eu.citrix.com> wrote:
>>> > On Tue, 31 Jul 2012, 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.  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.
>>> >
>>> > "unsupported delivery mode 3" means that the Linux guest is trying to
>>> > remap the MSI onto an event channel but Xen is still trying to deliver
>>> > the MSI using the emulated code path anyway.
>>> >
>>> > Adding
>>> >
>>> > #define XEN_PT_LOGGING_ENABLED 1
>>> >
>>> > at the top of hw/xen_pt.h and posting the additional QEMU logs could
>>> > be helpful.
>>> >
>>> > The full Xen logs might also be useful. I would add some more tracing to
>>> > the hypervisor too:
>>> >
>>> > diff --git a/xen/drivers/passthrough/io.c b/xen/drivers/passthrough/io.c
>>> > index b5975d1..08f4ab7 100644
>>> > --- a/xen/drivers/passthrough/io.c
>>> > +++ b/xen/drivers/passthrough/io.c
>>> > @@ -474,6 +474,11 @@ static void hvm_pci_msi_assert(
>>> >  {
>>> >      struct pirq *pirq = dpci_pirq(pirq_dpci);
>>> >
>>> > +    printk("DEBUG %s pirq=%d hvm_domain_use_pirq=%d emuirq=%d\n", __func__,
>>> > +            pirq->pirq,
>>> > +            hvm_domain_use_pirq(d, pirq),
>>> > +            pirq->arch.hvm.emuirq);
>>> > +
>>> >      if ( hvm_domain_use_pirq(d, pirq) )
>>> >          send_guest_pirq(d, pirq);
>>> >      else
>>>
>>> Hi Stefano-
>>> I made the modifications (it looks like that DEFINE hasn't been used
>>> in awhile, caused a few compilation issues, I had to prefix most of
>>> the logged variables with s->hostaddr.), and am attaching the
>>> qemu-dm-ubuntu.log and dmesg from xl.  You referred to full Xen logs,
>>> where do I find those at?
>>
>> Thanks for the logs!
>> You can get the full Xen logs from the serial console but you can also
>> grab the last few lines with "xl dmesg", like you did and it seems to be
>> enough in this case.
>>
>>
>> The initial MSI remapping has been done:
>>
>> [00:05.0] msi_msix_setup: requested pirq 4 for MSI-X (vec: 0, entry: 0)
>> [00:05.0] msi_msix_update: Updating MSI-X with pirq 4 gvec 0 gflags 0x3037 (entry: 0)
>>
>> But the guest is not issuing the EVTCHNOP_bind_pirq hypercall that is
>> necessary to be able to receive event notifications (emuirq=-1 in the
>> Xen logs).
>>
>> Now we need to figure out why: we still need more logs, this time on the
>> guest side.
>> What is the kernel version that you are using in the guest?
>> Could you please add "debug loglevel=9" to the guest kernel command line
>> and then post the guest dmesg again?
>> It would be great if you could use the emulated serial to get the logs
>> rather than a picture. You can do that by adding serial='pty' to the VM
>> config file and console=ttyS0 to the guest command line.
>> This additional Xen change could also tell us if the EVTCHNOP_bind_pirq
>> has been done:
>>
>>
>> diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
>> index 53777f8..d65a97a 100644
>> --- a/xen/common/event_channel.c
>> +++ b/xen/common/event_channel.c
>> @@ -405,6 +405,8 @@ static long evtchn_bind_pirq(evtchn_bind_pirq_t *bind)
>>  #ifdef CONFIG_X86
>>      if ( is_hvm_domain(d) && domain_pirq_to_irq(d, pirq) > 0 )
>>          map_domain_emuirq_pirq(d, pirq, IRQ_PT);
>> +    printk("DEBUG %s %d pirq=%d irq=%d emuirq=%d\n", __func__, __LINE__,
>> +            pirq, domain_pirq_to_irq(d, pirq), domain_pirq_to_emuirq(d, pirq));
>>  #endif
>>
>>   out:
>
> The guest is an Ubuntu 11.10 livecd, kernel version 3.0.0-12-generic.
> I've also attached all the logs, thanks for the tip on the serial
> console, very useful.
>
> Additionally I've attached logs for booting a solaris livecd (my
> ultimate goal is to use this HBA card in Solaris), with the serial
> console tip I was able to capture its kernel boot as well.

I'm attaching another log from Solaris' kernel debugger, I'm not sure
how helpful it is but I found it interesting that it didn't detect an
Intel IOMMU/ACPI table and unloaded it, then tried AMD - and I'm new
to Solaris but comparing this log to one without PCI Passthrough, the
npe module never gets loaded without PCI passthrough, so I assume it
failed while setting up the AMD IOMMU module then loaded the npe
module to report the error.

-D

[-- Attachment #2: solaris_kernel_panic.log --]
[-- Type: application/octet-stream, Size: 6621 bytes --]

load 'misc/busra' id 20 loaded @ 0xfffffffff7920000/0xfffffffffbe5a38a size 1024
8/96
load 'misc/iovcfg' id 21 loaded @ 0xfffffffff7923000/0xfffffffffbe5a412 size 122
08/488
load 'misc/pcie' id 19 loaded @ 0xfffffffff78dd000/0xfffffffffbe59ae2 size 27260
0/2216
load 'misc/pci_autoconfig' id 17 loaded @ 0xfffffffff7873000/0xfffffffffbe580ba 
size 39960/328
installing pci_autoconfig, module id 17.
installing acpica, module id 18.
ACPI: RSDP fda20 00024 (v2    Xen)
ACPI: XSDT fc009fd0 00054 (v1    Xen      HVM 00000000 HVML 00000000)
ACPI: FACP fc009900 000F4 (v4    Xen      HVM 00000000 HVML 00000000)
ACPI: DSDT fc0012b0 085CD (v2    Xen      HVM 00000000 INTL 20100528)
ACPI: FACS fc001270 00040
ACPI: APIC fc009a00 00460 (v2    Xen      HVM 00000000 HVML 00000000)
ACPI: HPET fc009ee0 00038 (v1    Xen      HVM 00000000 HVML 00000000)
ACPI: WAET fc009f20 00028 (v1    Xen      HVM 00000000 HVML 00000000)
ACPI: SSDT fc009f50 00031 (v2    Xen      HVM 00000000 INTL 20100528)
ACPI: SSDT fc009f90 00031 (v2    Xen      HVM 00000000 INTL 20100528)
installing pcie, module id 19.
installing busra, module id 20.
installing iovcfg, module id 21.      
load 'misc/acpidev' id 22 loaded @ 0xfffffffff7926000/0xfffffffffbe5c6a2 size 73
448/2720
installing acpidev, module id 22.
load 'drv/isa' id 23 loaded @ 0xfffffffff7938000/0xfffffffffbe5d172 size 16280/1
336
installing isa, module id 23.
Using default device instance data
SMBIOS v2.4 loaded (353 bytes)
load 'mach/uppc' id 24 loaded @ 0xfffffffff793c000/0xfffffffffbe5d6aa size 13352
/488
installing uppc, module id 24.
Skipping psm: xpv_psm
load 'mach/apix' id 26 loaded @ 0xfffffffff7942000/0xfffffffffbe5ea62 size 84344
/1856
installing apix, module id 26.
load 'mach/pcplusmp' id 27 loaded @ 0xfffffffff795a000/0xfffffffffbe62253 size 6
8784/1776
installing pcplusmp, module id 27.
load 'drv/rootnex' id 28 loaded @ 0xfffffffff796e000/0xfffffffffbe66bf4 size 190
56/720
installing rootnex, module id 28.
root nexus = i86pc
load 'drv/options' id 29 loaded @ 0xfffffffff7814d30/0xfffffffffbe66ecc size 592
/192
installing options, module id 29.
load 'drv/pseudo' id 30 loaded @ 0xfffffffff784e4f8/0xfffffffffbe66f8c size 2688
/568
installing pseudo, module id 30.
pseudo0 at root
pseudo0 is /pseudo
load 'drv/clone' id 31 loaded @ 0xfffffffff7959a98/0xfffffffffbe671c4 size 1312/
568
installing clone, module id 31.
load 'misc/scsi' id 33 loaded @ 0xfffffffff7986000/0xfffffffffbe67624 size 14344
0/16016
load 'drv/scsi_vhci' id 32 loaded @ 0xfffffffff7973000/0xfffffffffbe673fc size 7
4064/552
installing scsi_vhci, module id 32.
installing scsi, module id 33.
load 'misc/scsi_vhci/scsi_vhci_f_asym_sun' id 34 loaded @ 0xfffffffff7985150/0xf
ffffffffbe6b61a size 3712/208
installing scsi_vhci_f_asym_sun, module id 34.
load 'misc/scsi_vhci/scsi_vhci_f_asym_lsi' id 35 loaded @ 0xfffffffff79ad000/0xf
ffffffffbe6b6ea size 7152/640
installing scsi_vhci_f_asym_lsi, module id 35.
load 'misc/scsi_vhci/scsi_vhci_f_asym_emc' id 36 loaded @ 0xfffffffff79af000/0xf
ffffffffbe6b96a size 4248/232
installing scsi_vhci_f_asym_emc, module id 36.
load 'misc/scsi_vhci/scsi_vhci_f_sym_emc' id 37 loaded @ 0xfffffffff786ec68/0xff
fffffffbe6ba52 size 864/208
installing scsi_vhci_f_sym_emc, module id 37.
load 'misc/scsi_vhci/scsi_vhci_f_sym_hds' id 38 loaded @ 0xfffffffff78018a0/0xff
fffffffbe6bb22 size 1856/200
installing scsi_vhci_f_sym_hds, module id 38.
load 'misc/scsi_vhci/scsi_vhci_f_sym' id 39 loaded @ 0xfffffffff7956978/0xffffff
fffbe6bbea size 1504/336
installing scsi_vhci_f_sym, module id 39.
load 'misc/scsi_vhci/scsi_vhci_f_tpgs' id 40 loaded @ 0xfffffffffbbff350/0xfffff
ffffbe6bd3a size 3072/192
installing scsi_vhci_f_tpgs, module id 40.
scsi_vhci0 at root
scsi_vhci0 is /scsi_vhci
uninstalled apix
unloading apix, module id 26, loadcnt 1.
load 'misc/iommu' id 42 loaded @ 0xfffffffff794aed0/0xfffffffffbe5edb2 size 2268
0/584
load 'drv/intel_iommu' id 41 loaded @ 0xfffffffff7942000/0xfffffffffbe5ea62 size
 36560/848
installing intel_iommu, module id 41. 
installing iommu, module id 42.
No DMAR ACPI table. No Intel IOMMU present

unloading intel_iommu, module id 41, loadcnt 1.
load 'drv/amd_iommu' id 43 loaded @ 0xfffffffff7942000/0xfffffffffbe5ea62 size 3
6080/520
installing amd_iommu, module id 43.
unloading amd_iommu, module id 43, loadcnt 1.
load 'drv/npe' id 44 loaded @ 0xfffffffff7942000/0xfffffffffbe5f032 size 32672/3
136
installing npe, module id 44.
npe0 at root: space 0 offset 0
npe0 is /pci@0,0
trap: Unknown trap type 8 in user mode

panic[cpu0]/thread=fffffffffbc36de0: 
BAD TRAP: type=d (#gp General protection) rp=fffffffffbc48660 addr=f000ff53f000f
f00


#gp General protection
addr=0xf000ff53f000ff00
pid=0, pc=0xfffffffffb865f1d, sp=0xfffffffffbc48758, eflags=0x10286
cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 6b8<xmme,fxsr,pge,pae,pse,de>
cr2: 0
cr3: f8e6000
cr8: 0

        rdi:                0 rsi:                1 rdx:               40
        rcx:                2  r8: fffffffffbc48870  r9:                0
        rax: fffffffffbc36de0 rbx:                0 rbp: fffffffffbc487b0
        r10: fffffffffb85b7d8 r11: f000ff53f000ff00 r12:                0
        r13: f000ff53f000ff00 r14:                1 r15: f000ff53f000ff00
        fsb:        200000000 gsb: fffffffffbc3ebc0  ds:                0
         es:                0  fs:                0  gs:                0
        trp:                d err:                0 rip: fffffffffb865f1d
         cs:               30 rfl:            10286 rsp: fffffffffbc48758
         ss:               38

Warning - stack not written to the dump buffer
fffffffffbc48580 unix:die+131 ()
fffffffffbc48650 unix:trap+3b2 ()
fffffffffbc48660 unix:cmntrap+e6 ()
fffffffffbc487b0 unix:mutex_owner_running+d ()
fffffffffbc48840 genunix:dump_one_core+6b ()
fffffffffbc488e0 genunix:core+419 ()  
fffffffffbc48a10 unix:kern_gpfault+188 ()
fffffffffbc48ae0 unix:trap+393 ()
fffffffffbc48af0 unix:cmntrap+e6 ()

[0]> ::status
debugging live kernel (64-bit) on (not set)
operating system: 5.11 11.0 (i86pc)
image uuid: (not set)
DTrace state: inactive
stopped on: debugger entry trap
[0]> $c
kmdb_enter+0xb()
debug_enter+0x3f(fffffffffb959d60)
panicsys+0x5bd(fffffffffb957418, fffffffffbc484d0, fffffffffbc87bb0, 1)
vpanic+0x15c()
panic+0x94()
die+0x131(d, fffffffffbc48660, f000ff53f000ff00, 0)
trap+0x3b2(fffffffffbc48660, f000ff53f000ff00, 0)
0xfffffffffb8001d6()
mutex_owner_running+0xd()
dump_one_core+0x6b(b, ffffffff, 1, 0, fffffffffbc48870)
core+0x419(b, 0)
kern_gpfault+0x188(fffffffffbc48af0)
trap+0x393(fffffffffbc48af0, fffffffffbc7f6d8, 0)
0xfffffffffb8001d6()
[0]> 


[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Thu, Aug 2, 2012 at 10:38 AM, David Erickson <halcyon1981@gmail.com> wrote:
> On Wed, Aug 1, 2012 at 10:52 AM, David Erickson <halcyon1981@gmail.com> wrote:
>> On Wed, Aug 1, 2012 at 4:13 AM, Stefano Stabellini
>> <stefano.stabellini@eu.citrix.com> wrote:
>>> On Tue, 31 Jul 2012, David Erickson wrote:
>>>> On Tue, Jul 31, 2012 at 4:39 AM, Stefano Stabellini
>>>> <stefano.stabellini@eu.citrix.com> wrote:
>>>> > On Tue, 31 Jul 2012, 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.  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.
>>>> >
>>>> > "unsupported delivery mode 3" means that the Linux guest is trying to
>>>> > remap the MSI onto an event channel but Xen is still trying to deliver
>>>> > the MSI using the emulated code path anyway.
>>>> >
>>>> > Adding
>>>> >
>>>> > #define XEN_PT_LOGGING_ENABLED 1
>>>> >
>>>> > at the top of hw/xen_pt.h and posting the additional QEMU logs could
>>>> > be helpful.
>>>> >
>>>> > The full Xen logs might also be useful. I would add some more tracing to
>>>> > the hypervisor too:
>>>> >
>>>> > diff --git a/xen/drivers/passthrough/io.c b/xen/drivers/passthrough/io.c
>>>> > index b5975d1..08f4ab7 100644
>>>> > --- a/xen/drivers/passthrough/io.c
>>>> > +++ b/xen/drivers/passthrough/io.c
>>>> > @@ -474,6 +474,11 @@ static void hvm_pci_msi_assert(
>>>> >  {
>>>> >      struct pirq *pirq = dpci_pirq(pirq_dpci);
>>>> >
>>>> > +    printk("DEBUG %s pirq=%d hvm_domain_use_pirq=%d emuirq=%d\n", __func__,
>>>> > +            pirq->pirq,
>>>> > +            hvm_domain_use_pirq(d, pirq),
>>>> > +            pirq->arch.hvm.emuirq);
>>>> > +
>>>> >      if ( hvm_domain_use_pirq(d, pirq) )
>>>> >          send_guest_pirq(d, pirq);
>>>> >      else
>>>>
>>>> Hi Stefano-
>>>> I made the modifications (it looks like that DEFINE hasn't been used
>>>> in awhile, caused a few compilation issues, I had to prefix most of
>>>> the logged variables with s->hostaddr.), and am attaching the
>>>> qemu-dm-ubuntu.log and dmesg from xl.  You referred to full Xen logs,
>>>> where do I find those at?
>>>
>>> Thanks for the logs!
>>> You can get the full Xen logs from the serial console but you can also
>>> grab the last few lines with "xl dmesg", like you did and it seems to be
>>> enough in this case.
>>>
>>>
>>> The initial MSI remapping has been done:
>>>
>>> [00:05.0] msi_msix_setup: requested pirq 4 for MSI-X (vec: 0, entry: 0)
>>> [00:05.0] msi_msix_update: Updating MSI-X with pirq 4 gvec 0 gflags 0x3037 (entry: 0)
>>>
>>> But the guest is not issuing the EVTCHNOP_bind_pirq hypercall that is
>>> necessary to be able to receive event notifications (emuirq=-1 in the
>>> Xen logs).
>>>
>>> Now we need to figure out why: we still need more logs, this time on the
>>> guest side.
>>> What is the kernel version that you are using in the guest?
>>> Could you please add "debug loglevel=9" to the guest kernel command line
>>> and then post the guest dmesg again?
>>> It would be great if you could use the emulated serial to get the logs
>>> rather than a picture. You can do that by adding serial='pty' to the VM
>>> config file and console=ttyS0 to the guest command line.
>>> This additional Xen change could also tell us if the EVTCHNOP_bind_pirq
>>> has been done:
>>>
>>>
>>> diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
>>> index 53777f8..d65a97a 100644
>>> --- a/xen/common/event_channel.c
>>> +++ b/xen/common/event_channel.c
>>> @@ -405,6 +405,8 @@ static long evtchn_bind_pirq(evtchn_bind_pirq_t *bind)
>>>  #ifdef CONFIG_X86
>>>      if ( is_hvm_domain(d) && domain_pirq_to_irq(d, pirq) > 0 )
>>>          map_domain_emuirq_pirq(d, pirq, IRQ_PT);
>>> +    printk("DEBUG %s %d pirq=%d irq=%d emuirq=%d\n", __func__, __LINE__,
>>> +            pirq, domain_pirq_to_irq(d, pirq), domain_pirq_to_emuirq(d, pirq));
>>>  #endif
>>>
>>>   out:
>>
>> The guest is an Ubuntu 11.10 livecd, kernel version 3.0.0-12-generic.
>> I've also attached all the logs, thanks for the tip on the serial
>> console, very useful.
>>
>> Additionally I've attached logs for booting a solaris livecd (my
>> ultimate goal is to use this HBA card in Solaris), with the serial
>> console tip I was able to capture its kernel boot as well.
>
> I'm attaching another log from Solaris' kernel debugger, I'm not sure
> how helpful it is but I found it interesting that it didn't detect an
> Intel IOMMU/ACPI table and unloaded it, then tried AMD - and I'm new
> to Solaris but comparing this log to one without PCI Passthrough, the
> npe module never gets loaded without PCI passthrough, so I assume it
> failed while setting up the AMD IOMMU module then loaded the npe
> module to report the error.

Just following up, is there anything I can do to further help debug
and figure out what is causing the problem here?  I'm assuming since
it isn't working properly in PV or HVM guests there may be multiple
bugs.  Is there an easy way to run Ubuntu as HVM only (more friendly
than Solaris) to try and isolate if that is a separate bug from what
is being seen with the PV Ubuntu VM?

Thanks,
David

Re: LSI SAS2008 Option Rom Failure

[Stefano Stabellini]

On Fri, 3 Aug 2012, David Erickson wrote:
> On Thu, Aug 2, 2012 at 10:38 AM, David Erickson <halcyon1981@gmail.com> wrote:
> > On Wed, Aug 1, 2012 at 10:52 AM, David Erickson <halcyon1981@gmail.com> wrote:
> >> On Wed, Aug 1, 2012 at 4:13 AM, Stefano Stabellini
> >> <stefano.stabellini@eu.citrix.com> wrote:
> >>> On Tue, 31 Jul 2012, David Erickson wrote:
> >>>> On Tue, Jul 31, 2012 at 4:39 AM, Stefano Stabellini
> >>>> <stefano.stabellini@eu.citrix.com> wrote:
> >>>> > On Tue, 31 Jul 2012, 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.  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.
> >>>> >
> >>>> > "unsupported delivery mode 3" means that the Linux guest is trying to
> >>>> > remap the MSI onto an event channel but Xen is still trying to deliver
> >>>> > the MSI using the emulated code path anyway.
> >>>> >
> >>>> > Adding
> >>>> >
> >>>> > #define XEN_PT_LOGGING_ENABLED 1
> >>>> >
> >>>> > at the top of hw/xen_pt.h and posting the additional QEMU logs could
> >>>> > be helpful.
> >>>> >
> >>>> > The full Xen logs might also be useful. I would add some more tracing to
> >>>> > the hypervisor too:
> >>>> >
> >>>> > diff --git a/xen/drivers/passthrough/io.c b/xen/drivers/passthrough/io.c
> >>>> > index b5975d1..08f4ab7 100644
> >>>> > --- a/xen/drivers/passthrough/io.c
> >>>> > +++ b/xen/drivers/passthrough/io.c
> >>>> > @@ -474,6 +474,11 @@ static void hvm_pci_msi_assert(
> >>>> >  {
> >>>> >      struct pirq *pirq = dpci_pirq(pirq_dpci);
> >>>> >
> >>>> > +    printk("DEBUG %s pirq=%d hvm_domain_use_pirq=%d emuirq=%d\n", __func__,
> >>>> > +            pirq->pirq,
> >>>> > +            hvm_domain_use_pirq(d, pirq),
> >>>> > +            pirq->arch.hvm.emuirq);
> >>>> > +
> >>>> >      if ( hvm_domain_use_pirq(d, pirq) )
> >>>> >          send_guest_pirq(d, pirq);
> >>>> >      else
> >>>>
> >>>> Hi Stefano-
> >>>> I made the modifications (it looks like that DEFINE hasn't been used
> >>>> in awhile, caused a few compilation issues, I had to prefix most of
> >>>> the logged variables with s->hostaddr.), and am attaching the
> >>>> qemu-dm-ubuntu.log and dmesg from xl.  You referred to full Xen logs,
> >>>> where do I find those at?
> >>>
> >>> Thanks for the logs!
> >>> You can get the full Xen logs from the serial console but you can also
> >>> grab the last few lines with "xl dmesg", like you did and it seems to be
> >>> enough in this case.
> >>>
> >>>
> >>> The initial MSI remapping has been done:
> >>>
> >>> [00:05.0] msi_msix_setup: requested pirq 4 for MSI-X (vec: 0, entry: 0)
> >>> [00:05.0] msi_msix_update: Updating MSI-X with pirq 4 gvec 0 gflags 0x3037 (entry: 0)
> >>>
> >>> But the guest is not issuing the EVTCHNOP_bind_pirq hypercall that is
> >>> necessary to be able to receive event notifications (emuirq=-1 in the
> >>> Xen logs).
> >>>
> >>> Now we need to figure out why: we still need more logs, this time on the
> >>> guest side.
> >>> What is the kernel version that you are using in the guest?
> >>> Could you please add "debug loglevel=9" to the guest kernel command line
> >>> and then post the guest dmesg again?
> >>> It would be great if you could use the emulated serial to get the logs
> >>> rather than a picture. You can do that by adding serial='pty' to the VM
> >>> config file and console=ttyS0 to the guest command line.
> >>> This additional Xen change could also tell us if the EVTCHNOP_bind_pirq
> >>> has been done:
> >>>
> >>>
> >>> diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
> >>> index 53777f8..d65a97a 100644
> >>> --- a/xen/common/event_channel.c
> >>> +++ b/xen/common/event_channel.c
> >>> @@ -405,6 +405,8 @@ static long evtchn_bind_pirq(evtchn_bind_pirq_t *bind)
> >>>  #ifdef CONFIG_X86
> >>>      if ( is_hvm_domain(d) && domain_pirq_to_irq(d, pirq) > 0 )
> >>>          map_domain_emuirq_pirq(d, pirq, IRQ_PT);
> >>> +    printk("DEBUG %s %d pirq=%d irq=%d emuirq=%d\n", __func__, __LINE__,
> >>> +            pirq, domain_pirq_to_irq(d, pirq), domain_pirq_to_emuirq(d, pirq));
> >>>  #endif
> >>>
> >>>   out:
> >>
> >> The guest is an Ubuntu 11.10 livecd, kernel version 3.0.0-12-generic.
> >> I've also attached all the logs, thanks for the tip on the serial
> >> console, very useful.
> >>
> >> Additionally I've attached logs for booting a solaris livecd (my
> >> ultimate goal is to use this HBA card in Solaris), with the serial
> >> console tip I was able to capture its kernel boot as well.
> >
> > I'm attaching another log from Solaris' kernel debugger, I'm not sure
> > how helpful it is but I found it interesting that it didn't detect an
> > Intel IOMMU/ACPI table and unloaded it, then tried AMD - and I'm new
> > to Solaris but comparing this log to one without PCI Passthrough, the
> > npe module never gets loaded without PCI passthrough, so I assume it
> > failed while setting up the AMD IOMMU module then loaded the npe
> > module to report the error.

unfortunately I don't know much about solaris so it doesn't help me very
much


> Just following up, is there anything I can do to further help debug
> and figure out what is causing the problem here?  I'm assuming since
> it isn't working properly in PV or HVM guests there may be multiple
> bugs.  Is there an easy way to run Ubuntu as HVM only (more friendly
> than Solaris) to try and isolate if that is a separate bug from what
> is being seen with the PV Ubuntu VM?

I didn't get any specific output on the PV MSI setup, probably because
it is only printed when CONFIG_DEBUG is setup.
Would you be able to rebuild your Ubuntu kernel with the appended patch?


diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c
index 6e96e65..039f29c 100644
--- a/arch/x86/pci/xen.c
+++ b/arch/x86/pci/xen.c
@@ -90,6 +90,7 @@ static int xen_hvm_setup_msi_irqs(struct pci_dev *dev, int nvec, int type)
 	struct msi_desc *msidesc;
 	struct msi_msg msg;
 
+	printk("DEBUG %s %d   %s %s nvec=%d\n",__func__,__LINE__,dev_driver_string(&dev->dev), dev_name(&dev->dev),nvec);
 	list_for_each_entry(msidesc, &dev->msi_list, list) {
 		__read_msi_msg(msidesc, &msg);
 		pirq = MSI_ADDR_EXT_DEST_ID(msg.address_hi) |
@@ -102,7 +103,9 @@ static int xen_hvm_setup_msi_irqs(struct pci_dev *dev, int nvec, int type)
 			xen_msi_compose_msg(dev, pirq, &msg);
 			__write_msi_msg(msidesc, &msg);
 			dev_dbg(&dev->dev, "xen: msi bound to pirq=%d\n", pirq);
+			printk("DEBUG %s %d   %s %s pirq=%d\n",__func__,__LINE__,dev_driver_string(&dev->dev), dev_name(&dev->dev),pirq);
 		} else {
+			printk("DEBUG %s %d   %s %s pirq=%d already bound\n",__func__,__LINE__,dev_driver_string(&dev->dev), dev_name(&dev->dev),pirq);
 			dev_dbg(&dev->dev,
 				"xen: msi already bound to pirq=%d\n", pirq);
 		}
@@ -115,9 +118,11 @@ static int xen_hvm_setup_msi_irqs(struct pci_dev *dev, int nvec, int type)
 		dev_dbg(&dev->dev,
 			"xen: msi --> pirq=%d --> irq=%d\n", pirq, irq);
 	}
+	printk("DEBUG %s %d   %s %s pirq=%d irq=%d\n",__func__,__LINE__,dev_driver_string(&dev->dev), dev_name(&dev->dev),pirq,irq);
 	return 0;
 
 error:
+	printk("DEBUG %s %d   %s %s error\n",__func__,__LINE__,dev_driver_string(&dev->dev), dev_name(&dev->dev));
 	dev_err(&dev->dev,
 		"Xen PCI frontend has not registered MSI/MSI-X support!\n");
 	return -ENODEV;

Re: LSI SAS2008 Option Rom Failure

[ivo]

[-- Attachment #1.1: Type: text/plain, Size: 2498 bytes --]

On Thu, Jul 19, 2012 at 1:52 AM, David Erickson <halcyon1981@gmail.com>wrote:

> Hi Ivo-
> Can you mention how you built it?  I checked out xen-unstable, tried
> modifying the Config.mk to change the QEMU_UPSTREAM_URL variable,
> however when I built with this new url it complained when it tried to
> checkout the qemu traditional because the revision doesn't exist at
> that url.  So instead I built normally, then went into
> tools/qemu-xen-dir and added the git remote for qemu unstable, checked
> out the master branch, ran ./configure, then backed up to the main
> xen-unstable.hg folder and did sudo make dist and sudo make install.
> When I then started the VM with the config containing device model
> qemu-xen nothing changed.  I then added the line:
>
>
> device_model_override="/home/derickso/xen-unstable.hg/tools/qemu-xen-dir/i386-softmmu/qemu-system-i386"
>
> And started the VM, but got a bunch of errors:
>
> derickso@xen:~/xen-unstable.hg/tools/qemu-xen-dir/i386-softmmu$ sudo
> xl -v create /etc/xen/ubuntu.conf -V
> Parsing config from /etc/xen/ubuntu.conf
> xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9dcc8
> xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19dcc8
> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>   Loader:        0000000000100000->000000000019dcc8
>   TOTAL:         0000000000000000->000000007f800000
>   ENTRY ADDRESS: 0000000000100000
> xc: info: PHYSICAL MEMORY ALLOCATION:
>   4KB PAGES: 0x0000000000000200
>   2MB PAGES: 0x00000000000003fb
>   1GB PAGES: 0x0000000000000000
> xc: detail: elf_load_binary: phdr 0 at 0x0x7f77f2409000 -> 0x0x7f77f249db4d
> libxl: error: libxl_dm.c:1096:device_model_spawn_outcome: domain 2
> device model: spawn failed (rc=-3)
> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:
> No such file or directory
> libxl: error: libxl_exec.c:227:libxl__wait_for_offspring: Device Model not
> ready
> vncviewer: ConnectToTcpAddr: connect: Connection refused
> Unable to connect to VNC server
>
> Any suggestions?
>
> Thanks,
> David
>

I have just followed the wiki, using xen-unstable rev. 25567:165eb54e57c0
Create a file in the root of xen-unstable named  .config and add this:


QEMU_UPSTREAM_URL = git://git.qemu.org/qemu.git
QEMU_UPSTREAM_REVISION = master

Next, just ./configure and make as always.  Check the output messages
(tools directory) to be sure qemu git is used.

Later add this to your xl config file:
device_model_version = 'qemu-xen'

It worked flawlessy in my Ubuntu-12.04.

[-- Attachment #1.2: Type: text/html, Size: 3861 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

LSI SAS2008 Option Rom Failure

[David Erickson]

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

Hi-
I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an
HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device
model.  On boot I see the following error:

MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h)

A list search yielded
(http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172),
however there was no solution for an HVM VM.  I've attached the log
file for booting.  The expansion/option ROM gets installed at
0xf7a00000 and is first accessed and mapped with the line:

pt_iomem_map: e_phys=f3000001 maddr=f7a00000 type=8 len=524288 index=6
first_map=1

However the following log line seems to immediately map the same
address space to a strange e_phys location:

pt_iomem_map: e_phys=ffffffff maddr=f7a00000 type=8 len=524288 index=6
first_map=0

Any help or suggestions would be appreciated.  I have tested the same
card using PCI pass-through on ESXi and it functioned properly there.

Thanks!
David

[-- Attachment #2: qemu-dm-solaris.log --]
[-- Type: application/octet-stream, Size: 3589 bytes --]

domid: 21
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
Strip off blktap sub-type prefix to /mnt/solarisdisk (drv 'aio')
Using file /mnt/solarisdisk in read-write mode
Strip off blktap sub-type prefix to /home/derickso/sol-11-1111-live-x86.iso (drv 'aio')
Using file /home/derickso/sol-11-1111-live-x86.iso in read-only mode
Watching /local/domain/0/device-model/21/logdirty/cmd
Watching /local/domain/0/device-model/21/command
Watching /local/domain/21/cpu
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = f56665e9-bb6f-4492-9f5c-bb82328a7dbb
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 = Invalid argument): Internal error
xen be: qdisk-768: xen be: qdisk-768: xc_gnttab_set_max_grants failed: Invalid argument
xc_gnttab_set_max_grants failed: Invalid argument
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 = Invalid argument): Internal error
xen be: qdisk-5632: xen be: qdisk-5632: xc_gnttab_set_max_grants failed: Invalid argument
xc_gnttab_set_max_grants failed: Invalid argument
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/21/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/f56665e9-bb6f-4492-9f5c-bb82328a7dbb/vncpasswd.
medium change watch on `hdc' (index: 1): aio:/home/derickso/sol-11-1111-live-x86.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
vcpu-set: watch node error.
xs_read(/local/domain/21/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/21/log-throttling'
medium change watch on `/local/domain/21/log-throttling' - unknown device, ignored
dm-command: hot insert pass-through pci dev 
register_real_device: Assigning real physical device 02:00.0 ...
register_real_device: Enable MSI translation via per device option
register_real_device: Enable power management
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x2:0x0.0x0
pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000d001)
pt_register_regions: IO region registered (size=0x00004000 base_addr=0xf7ac0004)
pt_register_regions: IO region registered (size=0x00040000 base_addr=0xf7a80004)
pt_register_regions: Expansion ROM registered (size=0x00080000 base_addr=0xf7a00000)
pt_msix_init: get MSI-X table bar base f7ac0000
pt_msix_init: table_off = 2000, total_entries = 15
pt_msix_init: mapping physical MSI-X table to 7f6ec18ed000
pt_msi_setup: msi mapped with pirq 37
pci_intx: intx=1
register_real_device: Real physical device 02:00.0 registered successfuly!
IRQ type = MSI-INTx
cirrus vga map change while on lfb mode
pt_iomem_map: e_phys=f3080000 maddr=f7a80000 type=0 len=262144 index=3 first_map=1
pt_iomem_map: e_phys=f30c0000 maddr=f7ac0000 type=0 len=16384 index=1 first_map=1
pt_ioport_map: e_phys=c200 pio_base=d000 len=256 index=0 first_map=1
pt_iomem_map: e_phys=f3000001 maddr=f7a00000 type=8 len=524288 index=6 first_map=1
pt_iomem_map: e_phys=ffffffff maddr=f7a00000 type=8 len=524288 index=6 first_map=0
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[Ian Campbell]

On Wed, 2012-07-18 at 10:47 +0100, David Erickson wrote:
> Hi-
> I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an
> HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device
> model.  On boot I see the following error:
> 
> MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h)
> 
> A list search yielded
> (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172),
> however there was no solution for an HVM VM.  I've attached the log
> file for booting.  The expansion/option ROM gets installed at
> 0xf7a00000 and is first accessed and mapped with the line:
> 
> pt_iomem_map: e_phys=f3000001 maddr=f7a00000 type=8 len=524288 index=6
> first_map=1
> 
> However the following log line seems to immediately map the same
> address space to a strange e_phys location:
> 
> pt_iomem_map: e_phys=ffffffff maddr=f7a00000 type=8 len=524288 index=6
> first_map=0
> 
> Any help or suggestions would be appreciated.

SeaBIOS (used by qemu-xen) should be a lot better than ROMBIOS (used
with qemu-xen-traditional) at supporting Option ROMS, so it would be
worth trying that.

Ian.

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

[-- Attachment #1: Type: text/plain, Size: 2387 bytes --]

On Wed, Jul 18, 2012 at 2:59 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Wed, 2012-07-18 at 10:47 +0100, David Erickson wrote:
>> Hi-
>> I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an
>> HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device
>> model.  On boot I see the following error:
>>
>> MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h)
>>
>> A list search yielded
>> (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172),
>> however there was no solution for an HVM VM.  I've attached the log
>> file for booting.  The expansion/option ROM gets installed at
>> 0xf7a00000 and is first accessed and mapped with the line:
>>
>> pt_iomem_map: e_phys=f3000001 maddr=f7a00000 type=8 len=524288 index=6
>> first_map=1
>>
>> However the following log line seems to immediately map the same
>> address space to a strange e_phys location:
>>
>> pt_iomem_map: e_phys=ffffffff maddr=f7a00000 type=8 len=524288 index=6
>> first_map=0
>>
>> Any help or suggestions would be appreciated.
>
> SeaBIOS (used by qemu-xen) should be a lot better than ROMBIOS (used
> with qemu-xen-traditional) at supporting Option ROMS, so it would be
> worth trying that.

Ya I gave this a shot and it seems like with this device model and
bios it doesn't really pass the card through at all, in that there is
no message about the expansion/option rom at boot, and once I'm into
Solaris and run scanpci, nothing shows up at all (it is at least
enumerable under traditional).  There isn't a lot of logging to
indicate a problem either, here is the qemu-dm-solaris.log:

xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed
(22 = Invalid argument): Internal error
xen be: qdisk-768: xc_gnttab_set_max_grants failed: Invalid argument
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
xen be: qdisk-768: error: unknown operation (3)

xen-hotplug.log prints a couple of the following lines, but it also
prints them for traditional:
RTNETLINK answers: Operation not supported

xl pci-list thinks it has attached it:
derickso@xen:/var/log/xen$ sudo xl pci-list solaris
Vdev Device
00.0 0000:02:00.0

I've also attached the xl dmesg from both a rombios and seabios boot
if that is helpful.

Thanks,
David

[-- Attachment #2: seabios-dmesg.log --]
[-- Type: application/octet-stream, Size: 4730 bytes --]

(XEN) HVM5: HVM Loader
(XEN) HVM5: Detected Xen v4.2-unstable
(XEN) HVM5: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM5: System requested SeaBIOS
(XEN) HVM5: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom5 PCI link 0 changed 0 -> 5
(XEN) HVM5: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom5 PCI link 1 changed 0 -> 10
(XEN) HVM5: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom5 PCI link 2 changed 0 -> 11
(XEN) HVM5: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom5 PCI link 3 changed 0 -> 5
(XEN) HVM5: PCI-ISA link 3 routed to IRQ5
(XEN) HVM5: pci dev 01:3 INTA->IRQ10
(XEN) HVM5: pci dev 03:0 INTA->IRQ5
(XEN) HVM5: pci dev 04:0 INTA->IRQ5
(XEN) HVM5: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM5: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM5: pci dev 02:0 bar 30 size 00010000: f3000000
(XEN) HVM5: pci dev 04:0 bar 30 size 00010000: f3010000
(XEN) HVM5: pci dev 02:0 bar 14 size 00001000: f3020000
(XEN) HVM5: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM5: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM5: pci dev 04:0 bar 14 size 00000100: f3021000
(XEN) HVM5: pci dev 01:1 bar 20 size 00000010: 0000c201
(XEN) HVM5: Multiprocessor initialisation:
(XEN) HVM5:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM5: Testing HVM environment:
(XEN) HVM5:  - REP INSB across page boundaries ... passed
(XEN) HVM5:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM5: Passed 2 of 2 tests
(XEN) HVM5: Writing SMBIOS tables ...
(XEN) HVM5: Loading SeaBIOS ...
(XEN) HVM5: Creating MP tables ...
(XEN) HVM5: Loading ACPI ...
(XEN) HVM5: vm86 TSS at fc00a080
(XEN) HVM5: BIOS map:
(XEN) HVM5:  10000-100d3: Scratch space
(XEN) HVM5:  e0000-fffff: Main BIOS
(XEN) HVM5: E820 table:
(XEN) HVM5:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM5:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM5:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM5:  [02]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM5:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM5:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM5: Invoking SeaBIOS ...
(XEN) stdvga.c:147:d5 entering stdvga and caching modes
(XEN) stdvga.c:151:d5 leaving stdvga
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (4) to (5) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (5) to (6) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (6) to (7) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (7) to (8) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (8) to (9) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (9) to (10) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (10) to (11) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (11) to (12) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (12) to (13) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (13) to (14) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (14) to (15) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (15) to (16) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (16) to (17) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (17) to (18) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (18) to (19) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (19) to (20) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (20) to (21) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (21) to (22) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (22) to (23) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (23) to (24) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (24) to (25) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (25) to (26) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (26) to (27) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (27) to (28) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (28) to (29) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (29) to (30) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (30) to (31) frames.
(XEN) grant_table.c:1204:d5 Expanding dom (5) grant table from (31) to (32) frames.
(XEN) irq.c:375: Dom5 callback via changed to GSI 28


[-- Attachment #3: rombios-dmesg.log --]
[-- Type: application/octet-stream, Size: 7406 bytes --]

(XEN) HVM6: HVM Loader
(XEN) HVM6: Detected Xen v4.2-unstable
(XEN) HVM6: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM6: System requested ROMBIOS
(XEN) HVM6: CPU speed is 3293 MHz
(XEN) irq.c:270: Dom6 PCI link 0 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom6 PCI link 1 changed 0 -> 10
(XEN) HVM6: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom6 PCI link 2 changed 0 -> 11
(XEN) HVM6: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom6 PCI link 3 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 3 routed to IRQ5
(XEN) HVM6: pci dev 01:3 INTA->IRQ10
(XEN) HVM6: pci dev 03:0 INTA->IRQ5
(XEN) HVM6: pci dev 04:0 INTA->IRQ5
(XEN) HVM6: pci dev 05:0 INTA->IRQ10
(XEN) HVM6: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM6: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM6: pci dev 05:0 bar 30 size 00080000: f3000000
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) HVM6: pci dev 05:0 bar 1c size 00040000: f3080004
(XEN) memory_map:add: dom6 gfn=f30c0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30c3 mfn=f7ac3 nr=1
(XEN) HVM6: pci dev 05:0 bar 14 size 00004000: f30c0004
(XEN) HVM6: pci dev 02:0 bar 14 size 00001000: f30c4000
(XEN) HVM6: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM6: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM6: pci dev 04:0 bar 14 size 00000100: f30c5000
(XEN) HVM6: pci dev 05:0 bar 10 size 00000100: 0000c201
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) HVM6: pci dev 01:1 bar 20 size 00000010: 0000c301
(XEN) HVM6: Multiprocessor initialisation:
(XEN) HVM6:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: Testing HVM environment:
(XEN) HVM6:  - REP INSB across page boundaries ... passed
(XEN) HVM6:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM6: Passed 2 of 2 tests
(XEN) HVM6: Writing SMBIOS tables ...
(XEN) HVM6: Loading ROMBIOS ...
(XEN) HVM6: 12636 bytes of ROMBIOS high-memory extensions:
(XEN) HVM6:   Relocating to 0xfc001000-0xfc00415c ... done
(XEN) HVM6: Creating MP tables ...
(XEN) HVM6: Loading Cirrus VGABIOS ...
(XEN) HVM6: Loading PCI Option ROM ...
(XEN) HVM6:  - Manufacturer: http://ipxe.org
(XEN) HVM6:  - Product name: iPXE
(XEN) memory_map:add: dom6 gfn=f3000 mfn=f7a00 nr=80
(XEN) HVM6: Loading PCI Option ROM ...
(XEN) HVM6:  - Manufacturer: LSI Corporation
(XEN) HVM6:  - Product name: LSI MPI Boot Support
(XEN) memory_map:remove: dom6 gfn=f3000 mfn=f7a00 nr=80
(XEN) HVM6: Option ROMs:
(XEN) HVM6:  c0000-c8fff: VGA BIOS
(XEN) HVM6:  c9000-d8fff: Etherboot ROM
(XEN) HVM6:  d9000-e5fff: PCI Option ROMs
(XEN) HVM6: Loading ACPI ...
(XEN) HVM6: vm86 TSS at fc010280
(XEN) HVM6: BIOS map:
(XEN) HVM6:  f0000-fffff: Main BIOS
(XEN) HVM6: E820 table:
(XEN) HVM6:  [00]: 00000000:00000000 - 00000000:0009e000: RAM
(XEN) HVM6:  [01]: 00000000:0009e000 - 00000000:000a0000: RESERVED
(XEN) HVM6:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM6:  [02]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM6:  [03]: 00000000:00100000 - 00000000:7f800000: RAM
(XEN) HVM6:  HOLE: 00000000:7f800000 - 00000000:fc000000
(XEN) HVM6:  [04]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM6: Invoking ROMBIOS ...
(XEN) HVM6: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) stdvga.c:147:d6 entering stdvga and caching modes
(XEN) HVM6: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $
(XEN) HVM6: Bochs BIOS - build: 06/23/99
(XEN) HVM6: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) HVM6: Options: apmbios pcibios eltorito PMM 
(XEN) HVM6: 
(XEN) HVM6: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) HVM6: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (16384 MBytes)
(XEN) HVM6: IDE time out
(XEN) HVM6: ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) HVM6: IDE time out
(XEN) HVM6: 
(XEN) HVM6: PCI device 1000:0070 not found at index 0
(XEN) HVM6: PCI device 1000:0072 not found at index 1
(XEN) HVM6: PCI device 1000:0074 not found at index 0
(XEN) HVM6: PCI device 1000:0076 not found at index 0
(XEN) HVM6: PCI device 1000:0077 not found at index 0
(XEN) HVM6: PCI device 1000:0064 not found at index 0
(XEN) HVM6: PCI device 1000:0065 not found at index 0
(XEN) HVM6: PCI device 1000:0080 not found at index 0
(XEN) HVM6: PCI device 1000:0081 not found at index 0
(XEN) HVM6: PCI device 1000:0082 not found at index 0
(XEN) HVM6: PCI device 1000:0083 not found at index 0
(XEN) HVM6: PCI device 1000:0084 not found at index 0
(XEN) HVM6: PCI device 1000:0085 not found at index 0
(XEN) HVM6: PCI device 1000:0086 not found at index 0
(XEN) HVM6: PCI device 1000:0087 not found at index 0
(XEN) HVM6: PCI device 1000:006e not found at index 0
(XEN) HVM6: 
(XEN) HVM6: 
(XEN) HVM6: Press F12 for boot menu.
(XEN) HVM6: 
(XEN) HVM6: Booting from Hard Disk...
(XEN) HVM6: Booting from 0000:7c00
(XEN) HVM6: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM6: int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) HVM6: *** int 15h function AX=00c0, BX=0000 not yet supported!
(XEN) stdvga.c:151:d6 leaving stdvga
(XEN) HVM6: int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) HVM6: int13_harddisk: function 08, unmapped device for ELDL=82
(XEN) HVM6: int13_harddisk: function 08, unmapped device for ELDL=83
(XEN) HVM6: int13_harddisk: function 08, unmapped device for ELDL=84
(XEN) HVM6: int13_harddisk: function 08, unmapped device for ELDL=85
(XEN) HVM6: int13_harddisk: function 08, unmapped device for ELDL=86
(XEN) HVM6: int13_harddisk: function 08, unmapped device for ELDL=87
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f30c0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30c3 mfn=f7ac3 nr=1
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f30c0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30c3 mfn=f7ac3 nr=1
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f30c0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30c3 mfn=f7ac3 nr=1
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f30c0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30c3 mfn=f7ac3 nr=1
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f30c0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30c3 mfn=f7ac3 nr=1
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f30c0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30c3 mfn=f7ac3 nr=1
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) ioport_map:remove: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:remove: dom6 gfn=f30c0 mfn=f7ac0 nr=2
(XEN) memory_map:remove: dom6 gfn=f30c3 mfn=f7ac3 nr=1
(XEN) memory_map:remove: dom6 gfn=f3080 mfn=f7a80 nr=40
(XEN) ioport_map:add: dom6 gport=c200 mport=d000 nr=100
(XEN) memory_map:add: dom6 gfn=f30c0 mfn=f7ac0 nr=2
(XEN) memory_map:add: dom6 gfn=f30c3 mfn=f7ac3 nr=1
(XEN) memory_map:add: dom6 gfn=f3080 mfn=f7a80 nr=40


[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

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

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

On Wed, Jul 18, 2012 at 10:55 AM, David Erickson <halcyon1981@gmail.com> wrote:
> On Wed, Jul 18, 2012 at 2:59 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> On Wed, 2012-07-18 at 10:47 +0100, David Erickson wrote:
>>> Hi-
>>> I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an
>>> HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device
>>> model.  On boot I see the following error:
>>>
>>> MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h)
>>>
>>> A list search yielded
>>> (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172),
>>> however there was no solution for an HVM VM.  I've attached the log
>>> file for booting.  The expansion/option ROM gets installed at
>>> 0xf7a00000 and is first accessed and mapped with the line:
>>>
>>> pt_iomem_map: e_phys=f3000001 maddr=f7a00000 type=8 len=524288 index=6
>>> first_map=1
>>>
>>> However the following log line seems to immediately map the same
>>> address space to a strange e_phys location:
>>>
>>> pt_iomem_map: e_phys=ffffffff maddr=f7a00000 type=8 len=524288 index=6
>>> first_map=0
>>>
>>> Any help or suggestions would be appreciated.
>>
>> SeaBIOS (used by qemu-xen) should be a lot better than ROMBIOS (used
>> with qemu-xen-traditional) at supporting Option ROMS, so it would be
>> worth trying that.
>
> Ya I gave this a shot and it seems like with this device model and
> bios it doesn't really pass the card through at all, in that there is
> no message about the expansion/option rom at boot, and once I'm into
> Solaris and run scanpci, nothing shows up at all (it is at least
> enumerable under traditional).  There isn't a lot of logging to
> indicate a problem either, here is the qemu-dm-solaris.log:
>
> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed
> (22 = Invalid argument): Internal error
> xen be: qdisk-768: xc_gnttab_set_max_grants failed: Invalid argument
> 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
> xen be: qdisk-768: error: unknown operation (3)
>
> xen-hotplug.log prints a couple of the following lines, but it also
> prints them for traditional:
> RTNETLINK answers: Operation not supported
>
> xl pci-list thinks it has attached it:
> derickso@xen:/var/log/xen$ sudo xl pci-list solaris
> Vdev Device
> 00.0 0000:02:00.0
>
> I've also attached the xl dmesg from both a rombios and seabios boot
> if that is helpful.

I should also mention I've seen the following messages that probably
aren't good when using the xen-qemu device model and pass-thru.  On
startup:

libxl: error: libxl_qmp.c:288:qmp_handle_error_response: received an
error message from QMP server: Parameter 'driver' expects a driver
name

On destroy:

libxl: error: libxl_qmp.c:288:qmp_handle_error_response: received an
error message from QMP server: Device 'pci-pt-02_00.0' not found

-David

Re: LSI SAS2008 Option Rom Failure

[David Erickson]

> I should also mention I've seen the following messages that probably
> aren't good when using the xen-qemu device model and pass-thru.  On
> startup:
>
> libxl: error: libxl_qmp.c:288:qmp_handle_error_response: received an
> error message from QMP server: Parameter 'driver' expects a driver
> name

I did a tiny bit more debugging and that driver it is looking for is
named "xen-pci-passthrough", and it is failing to locate it in the
tools/qemu-xen-dir/hw/qdev.c qdev_find_info method.

Re: LSI SAS2008 Option Rom Failure

[James Regan]

[-- Attachment #1.1: Type: text/plain, Size: 1001 bytes --]

David, I can confirm that I have seen the same error messages on using pass through with the qemu-xen device model.


From: David Erickson <halcyon1981@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com> 
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org> 
Sent: Wednesday, July 18, 2012 12:14 PM
Subject: Re: [Xen-devel] LSI SAS2008 Option Rom Failure

> I should also mention I've seen the following messages that probably
> aren't good when using the xen-qemu device model and pass-thru.  On
> startup:
>
> libxl: error: libxl_qmp.c:288:qmp_handle_error_response: received an
> error message from QMP server: Parameter 'driver' expects a driver
> name

I did a tiny bit more debugging and that driver it is looking for is
named "xen-pci-passthrough", and it is failing to locate it in the
tools/qemu-xen-dir/hw/qdev.c qdev_find_info method.

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

[-- Attachment #1.2: Type: text/html, Size: 2269 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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