xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Jim Fehlig <jfehlig@suse.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
	osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [ovmf test] 87014: regressions - FAIL
Date: Thu, 24 Mar 2016 14:12:40 +0000	[thread overview]
Message-ID: <20160324141240.GB11369@citrix.com> (raw)
In-Reply-To: <56F33326.4080500@suse.com>

On Wed, Mar 23, 2016 at 06:21:58PM -0600, Jim Fehlig wrote:
> On 03/23/2016 09:27 AM, osstest service owner wrote:
> > flight 87014 ovmf real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/87014/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
> >  test-amd64-i386-xl-qemuu-ovmf-amd64  9 debian-hvm-install fail REGR. vs. 65543
> I've been testing Anthony's series to 'Load BIOS via toolstack instead of been
> embedded in hvmloader' [0] in an attempt to use the distro ovmf instead of
> "ovmf-xen". openSUSE Factory's ovmf package [1] is updated regularly with an
> upstream git snapshot and I noticed VMs did not boot when using it. I bisected
> and found ovmf commit 7b0a1ead the culprit
> commit 7b0a1ead7d2efa7f9eae4c2b254ff154d9c5f74f
> Author: Ruiyu Ni <ruiyu.ni@intel.com>
> Date:   Wed Feb 17 18:06:36 2016 +0800
>     MdeModuelPkg/PciBus: Return AddrTranslationOffset in GetBarAttributes
>     Some platform doesn't use CPU(HOST)/Device 1:1 mapping for PCI Bus.
>     But PCI IO doesn't have interface to tell caller (device driver)
>     whether the address returned by GetBarAttributes() is HOST address
>     or device address.
>     UEFI Spec 2.6 addresses this issue by clarifying the address returned
>     is HOST address and caller can use AddrTranslationOffset to calculate
>     the device address.
> I'm sure it's biting this test too.

Yes, and OSSTest already fingered that commit. According to Anthony OVMF
is even more broken now because more bugs crept in.

Anthony is working on fixing OVMF.

> BTW, any pointers on getting debug info from
> hvmloader+ovmf+qemu+other-components-involved? With the broken ovmf, I got
> nothing on the VM serial port, an empty, black vfb, nothing beyond "Invoking
> OVMF..." in xl dmesg, and no errors in the qemu log file. Beyond bisecting, I
> wasn't sure how to debug :-). I tried adding
> device_model_args=[ "-debugcon file:debug.log", "-global isa-debugcon.iobase=0x402"]

Can you try

  device_model_args = ["-debugcon", "file:debug.log", "-global", "isa-debugcon.iobase=0x402"]



> to the VM config, but qemu failed to start with "-debugcon file:debug.log:
> invalid option"
> Regards,
> Jim
> [0] http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg01626.html
> [1] https://build.opensuse.org/package/show/Virtualization/ovmf

Xen-devel mailing list

  reply	other threads:[~2016-03-24 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 15:27 [ovmf test] 87014: regressions - FAIL osstest service owner
2016-03-24  0:21 ` Jim Fehlig
2016-03-24 14:12   ` Wei Liu [this message]
2016-03-24 16:38     ` Jim Fehlig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160324141240.GB11369@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=jfehlig@suse.com \
    --cc=osstest-admin@xenproject.org \
    --cc=xen-devel@lists.xensource.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).