From: Thomas Huth <thuth@redhat.com>
To: Warner Losh <imp@bsdimp.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
"Roman Bolshakov" <r.bolshakov@yadro.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Stefan Weil" <sw@weilnetz.de>
Subject: Re: [PATCH v2] FreeBSD: Upgrade to 12.2 release
Date: Mon, 8 Mar 2021 16:41:05 +0100 [thread overview]
Message-ID: <f48b0f77-02e7-fcf7-a8bd-9d7990c8db33@redhat.com> (raw)
In-Reply-To: <CANCZdfq+ocyZnMt2td3ynx3gWqdPm1csddTjuhAEbxV-QL3Gow@mail.gmail.com>
On 08/03/2021 16.26, Warner Losh wrote:
>
>
> On Mon, Mar 8, 2021 at 6:30 AM Thomas Huth <thuth@redhat.com
> <mailto:thuth@redhat.com>> wrote:
>
> On 07/03/2021 16.56, Warner Losh wrote:
> > FreeBSD 12.1 has reached end of life. Use 12.2 instead so that FreeBSD's
> > project's packages will work. Update which timezone to pick. Work
> around a QEMU
> > bug that incorrectly raises an exception on a CRC32 instruction with
> the FPU
> > disabled. The qemu bug is described here:
> > https://www.mail-archive.com/qemu-devel@nongnu.org/msg784158.html
> <https://www.mail-archive.com/qemu-devel@nongnu.org/msg784158.html>
> >
> > Signed-off-by: Warner Losh <imp@bsdimp.com <mailto:imp@bsdimp.com>>
> >
> > ---
> > tests/vm/freebsd | 14 +++++++++-----
> > 1 file changed, 9 insertions(+), 5 deletions(-)
>
> I gave this a try, but it's currently failing in the unit tests:
>
> Running test test-crypto-tlscredsx509
>
> ** (tests/test-crypto-tlscredsx509:9999): CRITICAL **: 12:56:35.157: Failed
> to sign certificate ASN1 parser: Value is not valid.
> ERROR test-crypto-tlscredsx509 - Bail out! FATAL-CRITICAL: Failed to sign
> certificate ASN1 parser: Value is not valid.
> gmake: *** [Makefile.mtest:576: run-test-70] Error 1
> gmake: *** Waiting for unfinished jobs....
> Running test test-crypto-tlssession
>
> ** (tests/test-crypto-tlssession:10002): CRITICAL **: 12:56:35.288: Failed
> to sign certificate ASN1 parser: Value is not valid.
> ERROR test-crypto-tlssession - Bail out! FATAL-CRITICAL: Failed to sign
> certificate ASN1 parser: Value is not valid.
>
>
> That's totally unrelated to my change. Was it failing before? What
> environment was it failing in because it all seemed to work for me...
It's been a while since I last ran "make vm-build-freebsd", so I can't
really tell whether the problem was already there before ... when I now try
to run it without your patch, it fails for me, too, but rather due to
FreeBSD 12.1 being out of service instead.
> I guess it's the same problem as:
>
> https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg06750.html
> <https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg06750.html>
>
> ... so this would require a bug fix in the libtasn of FreeBSD first? See:
>
> https://gitlab.com/gnutls/libtasn1/-/merge_requests/71
> <https://gitlab.com/gnutls/libtasn1/-/merge_requests/71>
>
> Is this on the host that built qemu, or inside the VM or where exactly?
It's inside the VM ... I assume the libtasn there has the same bug as the
one on macOS?
Thomas
next prev parent reply other threads:[~2021-03-08 15:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 15:56 RESEND [PATCH v2] bsd-user: Add new maintainers Warner Losh
2021-03-07 15:56 ` [PATCH v2] FreeBSD: Upgrade to 12.2 release Warner Losh
2021-03-08 13:30 ` Thomas Huth
2021-03-08 15:26 ` Warner Losh
2021-03-08 15:31 ` Daniel P. Berrangé
2021-03-08 15:41 ` Thomas Huth [this message]
2021-03-08 15:46 ` Roman Bolshakov
2021-03-08 16:49 ` Stefan Weil
2021-03-08 19:51 ` Warner Losh
2021-03-08 19:57 ` Warner Losh
2021-03-09 5:08 ` Thomas Huth
2021-03-19 12:01 ` Thomas Huth
2021-03-08 10:09 ` RESEND [PATCH v2] bsd-user: Add new maintainers Thomas Huth
2021-03-08 10:24 ` Peter Maydell
2021-03-08 11:16 ` Philippe Mathieu-Daudé
2021-03-08 11:49 ` Peter Maydell
2021-03-08 11:55 ` Thomas Huth
2021-03-08 12:01 ` Peter Maydell
2021-03-08 12:14 ` Daniel P. Berrangé
2021-03-08 13:14 ` Philippe Mathieu-Daudé
2021-03-08 15:21 ` Warner Losh
2021-03-08 15:27 ` Daniel P. Berrangé
2021-03-08 19:59 ` Warner Losh
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=f48b0f77-02e7-fcf7-a8bd-9d7990c8db33@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=imp@bsdimp.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.com \
--cc=sw@weilnetz.de \
/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
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).