| 2020-06-04 18:12:02 |
Hajin Jang |
bug |
|
|
added bug |
| 2020-06-04 18:12:02 |
Hajin Jang |
attachment added |
|
MSBuild crash logs https://bugs.launchpad.net/bugs/1882123/+attachment/5380400/+files/QEMU-4.2.0-NET-SEHException.txt |
|
| 2020-06-04 18:16:59 |
Hajin Jang |
description |
[*] Summary
Latest QEMU has an ARM CPU emulation regression.
Regression is reproducible by building any C# project with .NET Core SDK 3.1.300 on Debian 10 armhf.
Affected releases: QEMU 4.2.0, 5.0.0
Not affected releases: QEMU 4.1.0, QEMU 4.1.1
[*] Detail
qemu-system-arm fails to run .NET Core SDK 3.1 on Debian 10 armhf.
I occasionally test my C# projects on the virtual armhf/arm64 system emulated by QEMU.
MSBuild, a build engine of the .NET Core SDK, crashes on QEMU 4.2.0 or later.
The crash only happens when MSBuild tries to do any JIT compiling (dotnet build / dotnet test).
I attached MSBuild crash logs. MSBuild always crashes with SEHException, which means it tried to call C binary from .NET binary.
The issue affects QEMU 4.2.0 and 5.0.0.
QEMU 4.1.0, 4.1.1, and real Raspberry Pi 2 machine is not affected by this issue, and .NET Core SDK works completely fine.
Thus, I think an ARM CPU regression happened between QEMU 4.1.1 ~ QEMU 4.2.0.
[*] Environment
[Host OS]
Distribution: Linux Mint 19.3 amd64
CPU: AMD Ryzen 5 3600
Kernel: Ubuntu 5.3.0-51-generic
[QEMU Arguments]
qemu-system-arm \
-smp 3 -M virt -m 4096 \
-kernel vmlinuz-4.19.0-9-armmp-lpae \
-initrd initrd.img-4.19.0-9-armmp-lpae \
-append "root=/dev/vda2" \
-drive if=none,file=debian_arm.qcow2,format=qcow2,id=hd \
-device virtio-blk-device,drive=hd \
-netdev user,id=mynet,hostfwd=tcp::<PORT>-:22 \
-device virtio-net-device,netdev=mynet \
-device virtio-rng-device\
[QEMU Guest OS]
Distribution: Debian 10 Buster armhf
Kernel: Debian 4.19.0-9-armmp-lpae
.NET Core SDK: 3.1.300
[Raspberry Pi 2]
Distribution: Raspberry Pi OS Buster armhf (20200527)
[Tested C# Projects]
This is a list of C# projects I have tested on QEMU and RPI2.
- https://github.com/ied206/Joveler.DynLoader
- https://github.com/ied206/Joveler.Compression
- https://github.com/ied206/ManagedWimLib |
[*] Summary
Latest QEMU has an ARM CPU emulation regression.
Regression is reproducible by building any C# project with .NET Core SDK 3.1.300 on Debian 10 armhf.
Releases affected: QEMU 4.2.0, 5.0.0
Releases not affected: QEMU 4.1.0, QEMU 4.1.1
[*] Detail
.NET Core SDK 3.1 fails to run on Debian 10 emulated by qemu-system-arm.
I occasionally test my C# projects on the virtual armhf/arm64 system emulated by QEMU. MSBuild, a build engine of the .NET Core SDK, crashes on QEMU 4.2.0 or later. The crash only happens when MSBuild tries to do any JIT compiling (dotnet build / dotnet test).
I attached the MSBuild crash logs. MSBuild always crashes with SEHException, which means it tried to call C binary from .NET binary.
I think an ARM CPU regression happened between QEMU 4.1.1 ~ QEMU 4.2.0. The issue affects QEMU 4.2.0 and 5.0.0. QEMU 4.1.0, 4.1.1, and real Raspberry Pi 2 are not affected by this issue, and .NET Core SDK works completely fine.
[*] Environment
[Host OS]
Distribution: Linux Mint 19.3 amd64
CPU: AMD Ryzen 5 3600
Kernel: Ubuntu 5.3.0-51-generic
[QEMU Guest OS]
Distribution: Debian 10 Buster armhf
Kernel: Debian 4.19.0-9-armmp-lpae
.NET Core SDK: 3.1.300
[Raspberry Pi 2]
Distribution: Raspberry Pi OS Buster armhf
Kernel: 4.19.118-v7+
[Tested C# Projects]
This is a list of C# projects I have tested on QEMU and RPI2.
- https://github.com/ied206/Joveler.DynLoader
- https://github.com/ied206/Joveler.Compression
- https://github.com/ied206/ManagedWimLib
[QEMU Launch Arguments]
qemu-system-arm \
-smp 3 -M virt -m 4096 \
-kernel vmlinuz-4.19.0-9-armmp-lpae \
-initrd initrd.img-4.19.0-9-armmp-lpae \
-append "root=/dev/vda2" \
-drive if=none,file=debian_arm.qcow2,format=qcow2,id=hd \
-device virtio-blk-device,drive=hd \
-netdev user,id=mynet,hostfwd=tcp::<PORT>-:22 \
-device virtio-net-device,netdev=mynet \
-device virtio-rng-device
[QEMU Configure Arguments]
./configure --enable-spice --enable-gtk --enable-vnc-jpeg --enable-vnc-png --enable-avx2 --enable-libusb --enable-opengl --enable-virglrenderer --enable-kvm --enable-system --enable-modules --audio-drv-list=pa |
|
| 2020-06-04 18:17:52 |
Hajin Jang |
description |
[*] Summary
Latest QEMU has an ARM CPU emulation regression.
Regression is reproducible by building any C# project with .NET Core SDK 3.1.300 on Debian 10 armhf.
Releases affected: QEMU 4.2.0, 5.0.0
Releases not affected: QEMU 4.1.0, QEMU 4.1.1
[*] Detail
.NET Core SDK 3.1 fails to run on Debian 10 emulated by qemu-system-arm.
I occasionally test my C# projects on the virtual armhf/arm64 system emulated by QEMU. MSBuild, a build engine of the .NET Core SDK, crashes on QEMU 4.2.0 or later. The crash only happens when MSBuild tries to do any JIT compiling (dotnet build / dotnet test).
I attached the MSBuild crash logs. MSBuild always crashes with SEHException, which means it tried to call C binary from .NET binary.
I think an ARM CPU regression happened between QEMU 4.1.1 ~ QEMU 4.2.0. The issue affects QEMU 4.2.0 and 5.0.0. QEMU 4.1.0, 4.1.1, and real Raspberry Pi 2 are not affected by this issue, and .NET Core SDK works completely fine.
[*] Environment
[Host OS]
Distribution: Linux Mint 19.3 amd64
CPU: AMD Ryzen 5 3600
Kernel: Ubuntu 5.3.0-51-generic
[QEMU Guest OS]
Distribution: Debian 10 Buster armhf
Kernel: Debian 4.19.0-9-armmp-lpae
.NET Core SDK: 3.1.300
[Raspberry Pi 2]
Distribution: Raspberry Pi OS Buster armhf
Kernel: 4.19.118-v7+
[Tested C# Projects]
This is a list of C# projects I have tested on QEMU and RPI2.
- https://github.com/ied206/Joveler.DynLoader
- https://github.com/ied206/Joveler.Compression
- https://github.com/ied206/ManagedWimLib
[QEMU Launch Arguments]
qemu-system-arm \
-smp 3 -M virt -m 4096 \
-kernel vmlinuz-4.19.0-9-armmp-lpae \
-initrd initrd.img-4.19.0-9-armmp-lpae \
-append "root=/dev/vda2" \
-drive if=none,file=debian_arm.qcow2,format=qcow2,id=hd \
-device virtio-blk-device,drive=hd \
-netdev user,id=mynet,hostfwd=tcp::<PORT>-:22 \
-device virtio-net-device,netdev=mynet \
-device virtio-rng-device
[QEMU Configure Arguments]
./configure --enable-spice --enable-gtk --enable-vnc-jpeg --enable-vnc-png --enable-avx2 --enable-libusb --enable-opengl --enable-virglrenderer --enable-kvm --enable-system --enable-modules --audio-drv-list=pa |
[*] Summary
Latest QEMU has an ARM CPU emulation regression.
Regression is reproducible by building any C# project with .NET Core SDK 3.1.300 on Debian 10 armhf guest OS.
Releases affected: QEMU 4.2.0, 5.0.0
Releases not affected: QEMU 4.1.0, QEMU 4.1.1
[*] Detail
.NET Core SDK 3.1 fails to run on Debian 10 emulated by qemu-system-arm.
I occasionally test my C# projects on the virtual armhf/arm64 system emulated by QEMU. MSBuild, a build engine of the .NET Core SDK, crashes on QEMU 4.2.0 or later. The crash only happens when MSBuild tries to do any JIT compiling (dotnet build / dotnet test).
I attached the MSBuild crash logs. MSBuild always crashes with SEHException, which means it tried to call C binary from .NET binary.
I think an ARM CPU regression happened between QEMU 4.1.1 ~ QEMU 4.2.0. The issue affects QEMU 4.2.0 and 5.0.0. QEMU 4.1.0, 4.1.1, and real Raspberry Pi 2 are not affected by this issue, and .NET Core SDK works completely fine.
[*] Environment
[Host OS]
Distribution: Linux Mint 19.3 amd64
CPU: AMD Ryzen 5 3600
Kernel: Ubuntu 5.3.0-51-generic
[QEMU Guest OS]
Distribution: Debian 10 Buster armhf
Kernel: Debian 4.19.0-9-armmp-lpae
.NET Core SDK: 3.1.300
[Raspberry Pi 2]
Distribution: Raspberry Pi OS Buster armhf
Kernel: 4.19.118-v7+
[Tested C# Projects]
This is a list of C# projects I have tested on QEMU and RPI2.
- https://github.com/ied206/Joveler.DynLoader
- https://github.com/ied206/Joveler.Compression
- https://github.com/ied206/ManagedWimLib
[QEMU Launch Arguments]
qemu-system-arm \
-smp 3 -M virt -m 4096 \
-kernel vmlinuz-4.19.0-9-armmp-lpae \
-initrd initrd.img-4.19.0-9-armmp-lpae \
-append "root=/dev/vda2" \
-drive if=none,file=debian_arm.qcow2,format=qcow2,id=hd \
-device virtio-blk-device,drive=hd \
-netdev user,id=mynet,hostfwd=tcp::<PORT>-:22 \
-device virtio-net-device,netdev=mynet \
-device virtio-rng-device
[QEMU Configure Arguments]
./configure --enable-spice --enable-gtk --enable-vnc-jpeg --enable-vnc-png --enable-avx2 --enable-libusb --enable-opengl --enable-virglrenderer --enable-kvm --enable-system --enable-modules --audio-drv-list=pa |
|
| 2020-06-04 18:18:54 |
Hajin Jang |
description |
[*] Summary
Latest QEMU has an ARM CPU emulation regression.
Regression is reproducible by building any C# project with .NET Core SDK 3.1.300 on Debian 10 armhf guest OS.
Releases affected: QEMU 4.2.0, 5.0.0
Releases not affected: QEMU 4.1.0, QEMU 4.1.1
[*] Detail
.NET Core SDK 3.1 fails to run on Debian 10 emulated by qemu-system-arm.
I occasionally test my C# projects on the virtual armhf/arm64 system emulated by QEMU. MSBuild, a build engine of the .NET Core SDK, crashes on QEMU 4.2.0 or later. The crash only happens when MSBuild tries to do any JIT compiling (dotnet build / dotnet test).
I attached the MSBuild crash logs. MSBuild always crashes with SEHException, which means it tried to call C binary from .NET binary.
I think an ARM CPU regression happened between QEMU 4.1.1 ~ QEMU 4.2.0. The issue affects QEMU 4.2.0 and 5.0.0. QEMU 4.1.0, 4.1.1, and real Raspberry Pi 2 are not affected by this issue, and .NET Core SDK works completely fine.
[*] Environment
[Host OS]
Distribution: Linux Mint 19.3 amd64
CPU: AMD Ryzen 5 3600
Kernel: Ubuntu 5.3.0-51-generic
[QEMU Guest OS]
Distribution: Debian 10 Buster armhf
Kernel: Debian 4.19.0-9-armmp-lpae
.NET Core SDK: 3.1.300
[Raspberry Pi 2]
Distribution: Raspberry Pi OS Buster armhf
Kernel: 4.19.118-v7+
[Tested C# Projects]
This is a list of C# projects I have tested on QEMU and RPI2.
- https://github.com/ied206/Joveler.DynLoader
- https://github.com/ied206/Joveler.Compression
- https://github.com/ied206/ManagedWimLib
[QEMU Launch Arguments]
qemu-system-arm \
-smp 3 -M virt -m 4096 \
-kernel vmlinuz-4.19.0-9-armmp-lpae \
-initrd initrd.img-4.19.0-9-armmp-lpae \
-append "root=/dev/vda2" \
-drive if=none,file=debian_arm.qcow2,format=qcow2,id=hd \
-device virtio-blk-device,drive=hd \
-netdev user,id=mynet,hostfwd=tcp::<PORT>-:22 \
-device virtio-net-device,netdev=mynet \
-device virtio-rng-device
[QEMU Configure Arguments]
./configure --enable-spice --enable-gtk --enable-vnc-jpeg --enable-vnc-png --enable-avx2 --enable-libusb --enable-opengl --enable-virglrenderer --enable-kvm --enable-system --enable-modules --audio-drv-list=pa |
[*] Summary
Latest QEMU has an ARM CPU emulation regression.
Regression is reproducible by building any C# project with .NET Core SDK 3.1.300 on Debian 10 armhf guest OS.
Releases affected: QEMU 4.2.0, 5.0.0
Releases not affected: QEMU 4.1.0, QEMU 4.1.1
[*] Detail
.NET Core SDK 3.1 fails to run on Debian 10 emulated by qemu-system-arm.
I occasionally test my C# projects on the virtual armhf/arm64 system emulated by QEMU. MSBuild, a build engine of the .NET Core SDK, crashes on QEMU 4.2.0 or later. The crash only happens when MSBuild tries to do any JIT compiling (dotnet build / dotnet test).
I attached the MSBuild crash logs. MSBuild always crashes with SEHException, which means it tried to call C binary from .NET binary.
I think the ARM CPU emulation regression happened between QEMU 4.1.1 ~ 4.2.0. The issue affects QEMU 4.2.0 and 5.0.0. QEMU 4.1.0, 4.1.1, and real Raspberry Pi 2 are not affected by this issue, and .NET Core SDK works completely fine.
[*] Environment
[Host OS]
Distribution: Linux Mint 19.3 amd64
CPU: AMD Ryzen 5 3600
Kernel: Ubuntu 5.3.0-51-generic
[QEMU Guest OS]
Distribution: Debian 10 Buster armhf
Kernel: Debian 4.19.0-9-armmp-lpae
.NET Core SDK: 3.1.300
[Raspberry Pi 2]
Distribution: Raspberry Pi OS Buster armhf
Kernel: 4.19.118-v7+
[Tested C# Projects]
This is a list of C# projects I have tested on QEMU and RPI2.
- https://github.com/ied206/Joveler.DynLoader
- https://github.com/ied206/Joveler.Compression
- https://github.com/ied206/ManagedWimLib
[QEMU Launch Arguments]
qemu-system-arm \
-smp 3 -M virt -m 4096 \
-kernel vmlinuz-4.19.0-9-armmp-lpae \
-initrd initrd.img-4.19.0-9-armmp-lpae \
-append "root=/dev/vda2" \
-drive if=none,file=debian_arm.qcow2,format=qcow2,id=hd \
-device virtio-blk-device,drive=hd \
-netdev user,id=mynet,hostfwd=tcp::<PORT>-:22 \
-device virtio-net-device,netdev=mynet \
-device virtio-rng-device
[QEMU Configure Arguments]
./configure --enable-spice --enable-gtk --enable-vnc-jpeg --enable-vnc-png --enable-avx2 --enable-libusb --enable-opengl --enable-virglrenderer --enable-kvm --enable-system --enable-modules --audio-drv-list=pa |
|
| 2020-06-29 07:28:09 |
Philippe Mathieu-Daudé |
bug |
|
|
added subscriber Richard Henderson |
| 2020-11-05 10:55:49 |
Peter Maydell |
qemu: status |
New |
Confirmed |
|
| 2021-05-11 05:38:32 |
Thomas Huth |
qemu: status |
Confirmed |
Expired |
|
| 2021-05-11 05:38:33 |
Thomas Huth |
bug watch added |
|
https://gitlab.com/qemu-project/qemu/-/issues/271 |
|
| 2023-01-30 11:57:09 |
Qiang Liu |
bug watch added |
|
https://gitlab.com/qemu-project/qemu/-/issues/119 |
|
| 2023-01-30 11:57:09 |
Qiang Liu |
bug watch added |
|
https://gitlab.com/qemu-project/qemu/-/issues/303 |
|
