Mhm, weird. On my other machine it works.
There I used the AUR package qemu-user-static instead of qemu-arm-static.
However that seems not to be the problem since it doesnt even work after
switching to qemu-user-static.
With the working setup the log files are also created (which makes sense
There is no syslog and everything else is empty:
ls -ltrR /mnt/var/log/
/mnt/var/log/:
total 8
drwxr-xr-x 2 root root 4096 20. Aug 12:33 apt
-rw-r--r-- 1 root root0 20. Aug 12:47 faillog
-rw-r--r-- 1 root root0 20. Aug 12:47 dpkg.log
-rw-rw-r-- 1 root tor 0 20. Aug 12:47 lastlog
Is that of any help?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1895053
Title:
Cannot nspawn raspbian 10 [FAILED] Failed to start Journal Service.
Status in QEMU:
New
Bug description:
Hi,
I had the same idea but didnt know about the restart part :D
attached is the strace =)
Thx
** Attachment added: "strace2"
https://bugs.launchpad.net/qemu/+bug/1895053/+attachment/5411345/+files/strace2
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Nope:
qemu-system-arm -M raspi2 -m 1G -dtb bcm2709-rpi-2-b.dtb -kernel
kernel7.img -append "rw earlyprintk loglevel=8 console=ttyAMA0,115200
dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2 dwc_otg.fiq_fsm_enable=0" -sd
2016-05-27-raspbian-jessie.img -smp 4 -serial stdio -display none
raspberrypi login:
ah, well then its the same error:
qemu-system-arm: /build/qemu/src/qemu-5.1.0/hw/usb/hcd-dwc2.c:666:
dwc2_glbreg_read: Assertion `addr <= GINTSTS2' failed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I take back everything and claim the opposite... same error as bug
reporter
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1895053
Title:
Cannot nspawn raspbian 10 [FAILED] Failed to start Journal
for me the output is:
% qemu-system-arm -M raspi2 -m 1G -dtb bcm2709-rpi-2-b.dtb -kernel kernel7.img
-append "rw earlyprintk loglevel=8 console=ttyAMA0,115200 dwc_otg.lpm_enable=0
root=/dev/mmcblk0p2" -sd 2016-05-27-raspbian-jessie.img -smp 4 -serial stdio
-display none
WARNING: Image format
tldr: i dont have the same issue as described in your bug
see my post there:
https://bugs.launchpad.net/qemu/+bug/1892604/comments/6
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1895053
Title:
for file in /proc/sys/fs/binfmt_misc/* ; do echo "$file"; LANG=C cat $file; done
/proc/sys/fs/binfmt_misc/aarch64
enabled
interpreter /usr/bin/qemu-aarch64-static
flags: OCF
offset 0
magic 7f454c46020101000200b7
mask ff00fe
Mhm, that doesnt work for me. My output is unchanged...
file /mnt/usr/bin/qemu-arm-*
/mnt/usr/bin/qemu-arm-org:ELF 64-bit LSB pie executable, x86-64, version 1
(SYSV), dynamically linked, stripped
/mnt/usr/bin/qemu-arm-static: ELF 64-bit LSB executable, x86-64, version 1
(GNU/Linux),
Hi thanks i ran the above, but where is the strace stored? its neither
in the console output nor journalctl
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1895053
Title:
Cannot nspawn raspbian 10
mhm thats somehow unfortunate since I dont know in what direction I
would have to go to solve the issue :/
I tried 245.7 but without success.
Do you maybe have an idea on how to investigate further?
Is this some kind of distribution problem? What is the actual problem anyway?
--
You received
can you reproduce the bug locally or is this a client problem?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1895053
Title:
Cannot nspawn raspbian 10 [FAILED] Failed to start Journal Service.
Thanks for the quick response!
I tried the whole day to get the PKGBUILD working...
Your patch doesnt fix the issue though - see attached log
** Attachment added: "log.txt"
https://bugs.launchpad.net/qemu/+bug/1895053/+attachment/5409429/+files/log.txt
--
You received this bug notification
Public bug reported:
Hi, I'm using nspawn and asked the question @systemd-devel. They redirected me
to you, guessing that nspawn calls a syscall or ioctl qemu isnt aware of and
can't implement properly?
They were like: "Sorry, that's not my department." ^^
Maybe you can reproduce the issue or
16 matches
Mail list logo
