Tried applying the -cpu parameter into Qemu 4.1.1 but I got:
qemu-system-riscv64: unable to find CPU model 'qemu'
My command is:
qemu-system-riscv64 \
-machine virt \
-cpu qemu,vx=off \
-nographic \
-smp 4 \
-m 4G \
-bios fw_payload.bin \
-device virtio-blk-device,drive=hd0 \
-object rng-random,filename=/dev/urandom,id=rng0 \
-device virtio-rng-device,rng=rng0 \
-drive file=riscv64-debianrootfs-qemu.qcow2,format=qcow2,id=hd0 \
-device virtio-net-device,netdev=usernet \
-netdev user,id=usernet,hostfwd=tcp::22222-:22"
--
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:
Fix Released
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
