** Changed in: qemu
Status: Incomplete => 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/1926246
Title:
chrome based apps can not be run under qemu user mode
Status in QEMU:
New
Bug d
Here is the command line to start chromium, --no-zygote is needed to
avoid the gpu releated crash:
qemu-aarch64 /usr/lib/chromium/chrome --no-sandbox --no-zygote
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.
Yes. It fixes the execve issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1926246
Title:
chrome based apps can not be run under qemu user mode
Status in QEMU:
New
Bug description:
chrome
Just found there's already a patch for this:
https://lists.sr.ht/~philmd/qemu/patches/8196
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1926246
Title:
chrome based apps can not be run under qemu u
qemu patch:
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 95d79ddc43..227d9b1b0e 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -8537,7 +8537,7 @@ static abi_long do_syscall1(void *cpu_env, int num,
abi_long arg1,
* before the execve completes and
I found out the reason for "qemu: unknown option 'type=utility'", created a
sample code to demo it and a small wrokaround patch to chromium. Found more
info in:
https://bugs.launchpad.net/qemu/+bug/1926246
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
Public bug reported:
chrome uses /proc/self/exe to fork render process.
Here a simple code to reproduce the issue. It's output parent then child but
failed with qemu: unknown option 'type=renderer'.
Maybe we can modify exec syscall to replace /proc/self/exe to the real
path.
//gcc -o self self.
