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,dri
Thank you so much! I've been hitting the same issue with s390x.
Maybe an endian issue with hardware vx?
** Bug watch added: github.com/moby/moby/issues #40240
https://github.com/moby/moby/issues/40240
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Also affects RISC-V apparently.
https://github.com/moby/moby/issues/40240
--
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
I assume David's fixes have been released with QEMU v4.2, so I'm closing
this ticket now.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bug
I will exercise this thoroughly ! The go application involved is itself
a blockchain signing/verification application, so I suspect it will be a
good exercise (codenotary.io)
Thanks for looking into this and fixing this !
--Ivan
--
You received this bug notification because you are a member of
On 23.10.19 11:37, Ivan Warren wrote:
> Looks fixed to me ! The issue no longer shows even without specifying
> vx=off
>
Nice, I suspect that there might be more issues when using golang (as it
really makes excessive use of vector registers to my surprise). So in
case you run into problems (and
Looks fixed to me ! The issue no longer shows even without specifying
vx=off
--
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
** Changed in: qemu
Assignee: (unassigned) => David Hildenbrand (davidhildenbrand)
** Changed in: qemu
Status: New => In Progress
--
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
Ti
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 e
I was looking for a simpler method (without using go), but curl/wget and
whatnot don't seem to have any problem.. There must be something go is
doing that is different.
My guess (but ONLY a guess) is that the "go" TLS code might be doing
some dynamic checking on the z/Arch facility list (STFLE ?)
** Tags added: s390x
--
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 s390
11 matches
Mail list logo
