Since wget/curl use the openssl library - which (unless a specific engine is specified) uses the lowest common denominator - it will work even when z/Arch VX is present.. However, "golang" may be using a different technique (and may not be using openssl at all) - or invoke openssl with a specific engine if it detects z/Arch VX...
However, I have the workaround (vx=off), but I'd love to see if there is something amiss with z/Arch VX (for purely educational purpose). -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1847232 Title: qemu TCG in s390x mode issue with calculating HASH Status in QEMU: New Bug description: When using go on s390x on Debian x64 (buster) (host) and debian s390x (sid) (guest) I run into the following problem : The following occurs while trying to build a custom project : go: github.com/FactomProject/basen@v0.0.0-20150613233007-fe3947df716e: Get https://proxy.golang.org/github.com/%21factom%21project/basen/@v/v0.0.0-20150613233007-fe3947df716e.mod: local error: tls: bad record MAC Doing a git bisect I find that this problem only occurs on and after commit 08ef92d556c584c7faf594ff3af46df456276e1b Before that commit, all works fine. Past this commit, build always fails. Without any proof, It looks like a hash calculation bug related to using z/Arch vector facilities... To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1847232/+subscriptions
