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

Wei Liu wrote:
> 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.

Cool. Thanks Anthony!

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

Yes, that worked. Thanks.

Regards,
Jim

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

      reply	other threads:[~2016-03-24 16:38 UTC|newest]

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

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=56F417F2.1080307@suse.com \
    --to=jfehlig@suse.com \
    --cc=anthony.perard@citrix.com \
    --cc=osstest-admin@xenproject.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --subject='Re: [ovmf test] 87014: regressions - FAIL' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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