* [Bug 1861341] [NEW] ARM QEMU: Unknown syscall 397
@ 2020-01-29 21:18 rinigus
2020-03-06 11:52 ` [Bug 1861341] " Laurent Vivier
2020-08-20 15:39 ` Thomas Huth
0 siblings, 2 replies; 3+ messages in thread
From: rinigus @ 2020-01-29 21:18 UTC (permalink / raw
To: qemu-devel
Public bug reported:
QEMU is reporting
```
Unknown syscall 397
```
(statx if I read tables right) when used via flatpak for ARM images on
x86_64. This has been reproduced on Fedora and Gentoo.
To reproduce:
- get flatpak KDE 5.12 for arm:
flatpak install --user org.kde.Sdk/arm/5.12 org.kde.Platform/arm/5.12
- run qmake inside Sdk:
QEMU_STRACE=1 flatpak run --filesystem=host --command=qmake
org.kde.Sdk/arm/5.12 .
You will get a host of messages with unknown syscall. In practice, qmake will fail to find .pro files if you have them in that folder and libraries in the system.
As far as I understand, Flatpak images are built on AARCH64 hardware.
My config on Gentoo:
kernel: 4.19.86-gentoo x86_64
app-emulation/qemu: ~4.2.0-r1 , same with 4.0.0
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1861341
Title:
ARM QEMU: Unknown syscall 397
Status in QEMU:
New
Bug description:
QEMU is reporting
```
Unknown syscall 397
```
(statx if I read tables right) when used via flatpak for ARM images on
x86_64. This has been reproduced on Fedora and Gentoo.
To reproduce:
- get flatpak KDE 5.12 for arm:
flatpak install --user org.kde.Sdk/arm/5.12 org.kde.Platform/arm/5.12
- run qmake inside Sdk:
QEMU_STRACE=1 flatpak run --filesystem=host --command=qmake
org.kde.Sdk/arm/5.12 .
You will get a host of messages with unknown syscall. In practice, qmake will fail to find .pro files if you have them in that folder and libraries in the system.
As far as I understand, Flatpak images are built on AARCH64 hardware.
My config on Gentoo:
kernel: 4.19.86-gentoo x86_64
app-emulation/qemu: ~4.2.0-r1 , same with 4.0.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1861341/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 1861341] Re: ARM QEMU: Unknown syscall 397
2020-01-29 21:18 [Bug 1861341] [NEW] ARM QEMU: Unknown syscall 397 rinigus
@ 2020-03-06 11:52 ` Laurent Vivier
2020-08-20 15:39 ` Thomas Huth
1 sibling, 0 replies; 3+ messages in thread
From: Laurent Vivier @ 2020-03-06 11:52 UTC (permalink / raw
To: qemu-devel
New syscall definitions for ARM have been added lately by:
73209e1f15c6 ("linux-user: arm: Update syscall numbers to kernel 5.5
level")
It will available in QEMU 5.0
** Changed in: qemu
Assignee: (unassigned) => Laurent Vivier (laurent-vivier)
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1861341
Title:
ARM QEMU: Unknown syscall 397
Status in QEMU:
Fix Committed
Bug description:
QEMU is reporting
```
Unknown syscall 397
```
(statx if I read tables right) when used via flatpak for ARM images on
x86_64. This has been reproduced on Fedora and Gentoo.
To reproduce:
- get flatpak KDE 5.12 for arm:
flatpak install --user org.kde.Sdk/arm/5.12 org.kde.Platform/arm/5.12
- run qmake inside Sdk:
QEMU_STRACE=1 flatpak run --filesystem=host --command=qmake
org.kde.Sdk/arm/5.12 .
You will get a host of messages with unknown syscall. In practice, qmake will fail to find .pro files if you have them in that folder and libraries in the system.
As far as I understand, Flatpak images are built on AARCH64 hardware.
My config on Gentoo:
kernel: 4.19.86-gentoo x86_64
app-emulation/qemu: ~4.2.0-r1 , same with 4.0.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1861341/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 1861341] Re: ARM QEMU: Unknown syscall 397
2020-01-29 21:18 [Bug 1861341] [NEW] ARM QEMU: Unknown syscall 397 rinigus
2020-03-06 11:52 ` [Bug 1861341] " Laurent Vivier
@ 2020-08-20 15:39 ` Thomas Huth
1 sibling, 0 replies; 3+ messages in thread
From: Thomas Huth @ 2020-08-20 15:39 UTC (permalink / raw
To: qemu-devel
** 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/bugs/1861341
Title:
ARM QEMU: Unknown syscall 397
Status in QEMU:
Fix Released
Bug description:
QEMU is reporting
```
Unknown syscall 397
```
(statx if I read tables right) when used via flatpak for ARM images on
x86_64. This has been reproduced on Fedora and Gentoo.
To reproduce:
- get flatpak KDE 5.12 for arm:
flatpak install --user org.kde.Sdk/arm/5.12 org.kde.Platform/arm/5.12
- run qmake inside Sdk:
QEMU_STRACE=1 flatpak run --filesystem=host --command=qmake
org.kde.Sdk/arm/5.12 .
You will get a host of messages with unknown syscall. In practice, qmake will fail to find .pro files if you have them in that folder and libraries in the system.
As far as I understand, Flatpak images are built on AARCH64 hardware.
My config on Gentoo:
kernel: 4.19.86-gentoo x86_64
app-emulation/qemu: ~4.2.0-r1 , same with 4.0.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1861341/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-08-20 15:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-01-29 21:18 [Bug 1861341] [NEW] ARM QEMU: Unknown syscall 397 rinigus
2020-03-06 11:52 ` [Bug 1861341] " Laurent Vivier
2020-08-20 15:39 ` Thomas Huth
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.