[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
Indeed, I had no problem booting the images this time around: https://asciinema.org/a/d2m42g5c0n3z2pnbskhirdv5j -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: Fix Committed Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 1529226] Re: qemu-i386-user on 32-bit Linux: uncaught target signal 11
A simpler way to reproduce would probably be to wrap the regular, installed rustc that way and try running some compilations using cargo. That should be enough to elicit the same 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/1529226 Title: qemu-i386-user on 32-bit Linux: uncaught target signal 11 Status in QEMU: New Bug description: Even though the command I'm trying to run (a wrapper script for qemu-i386-user running rustc, the rust compiler) produces the expected compiled output, the build process is interrupted: qemu: uncaught target signal 11 (Segmentation fault) - core dumped i686-unknown-linux-gnu/stage0/bin/rustc: line 1: 7474 Segmentation fault /usr/local/bin/qemu-i386 -cpu qemu32 /home/petevine/stage0/rustc.bin -C target-cpu=pentium2 -L /home/petevine/unpacked/rust-master/i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/ "$@" make: *** [i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/stamp.rustc_back] Error 139 The stamp file is not being created so this could be about forking bash after finishing the wrapper script. Qemu was compiled from the latest git source. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1529226/+subscriptions
[Qemu-devel] [Bug 1529226] Re: qemu-i386-user on 32-bit Linux: uncaught target signal 11
My recollection is fuzzy but it would probably amount to something like this on any platform currently: - download rust-1.10 beta source https://static.rust-lang.org/dist /rustc-beta-src.tar.gz - download this stage0 snapshot https://www.dropbox.com/s/01ywl9mwwo6xojw/rust-stage0-2016-04-18-b324fa7 -linux-armv7.tar.xz?dl=0 - unpack the stage0 rustc binary to ~/somewhere/bin, renaming it to rustc.bin, and create a wrapper script named rustc in that directory containing: `/usr/bin/qemu-arm ~/somewhere/rustc.bin "$@"` In the rustc source directory, start the rust bootstrap process (with LLVM 3.7 or higher installed) issuing the following command: `./configure --enable-optimize --enable-local-rust --local-rust-root=~/somewhere --llvm-root=/usr` Followed by `make`. At the time of the original report, QEMU wasn't able to complete all crates' build commands naturally. (the stamp file had to be created manually to continue) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1529226 Title: qemu-i386-user on 32-bit Linux: uncaught target signal 11 Status in QEMU: New Bug description: Even though the command I'm trying to run (a wrapper script for qemu-i386-user running rustc, the rust compiler) produces the expected compiled output, the build process is interrupted: qemu: uncaught target signal 11 (Segmentation fault) - core dumped i686-unknown-linux-gnu/stage0/bin/rustc: line 1: 7474 Segmentation fault /usr/local/bin/qemu-i386 -cpu qemu32 /home/petevine/stage0/rustc.bin -C target-cpu=pentium2 -L /home/petevine/unpacked/rust-master/i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/ "$@" make: *** [i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/stamp.rustc_back] Error 139 The stamp file is not being created so this could be about forking bash after finishing the wrapper script. Qemu was compiled from the latest git source. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1529226/+subscriptions
[Qemu-devel] [Bug 1568107] [NEW] setup_rt_frame: not implemented
Public bug reported: Trying to run this binary (https://github.com/ethcore/parity/releases/download/v1.0.1/parity_linux_1.0.1-0_amd64.deb) under qemu-x86_64 on ARM, ends like this: $ qemu-x86_64 parity --pruning fast setup_rt_frame: not implemented qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault ** 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/1568107 Title: setup_rt_frame: not implemented Status in QEMU: New Bug description: Trying to run this binary (https://github.com/ethcore/parity/releases/download/v1.0.1/parity_linux_1.0.1-0_amd64.deb) under qemu-x86_64 on ARM, ends like this: $ qemu-x86_64 parity --pruning fast setup_rt_frame: not implemented qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1568107/+subscriptions
[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
FWIW: Program received signal SIGINT, Interrupt. 0xb644f73c in seqlock_read_retry (sl=0xb6b2acc8 , start=0) at /tmp/qemu/include/qemu/seqlock.h:69 69 return unlikely(atomic_read(&sl->sequence) != start); (gdb) bt #0 0xb644f73c in seqlock_read_retry (sl=0xb6b2acc8 , start=0) at /tmp/qemu/include/qemu/seqlock.h:69 #1 0xb644fa3c in cpu_get_icount () at /tmp/qemu/cpus.c:182 #2 0xb644f518 in cpu_get_host_ticks () at /tmp/qemu/include/qemu/timer.h:1006 #3 0xb644fcc4 in cpu_enable_ticks () at /tmp/qemu/cpus.c:252 #4 0xb658a9ec in vm_start () at vl.c:764 #5 0xb6597200 in main (argc=5, argv=0xbecfa6b4, envp=0xbecfa6cc) at vl.c:4651 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: Confirmed Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
Unfortunately that doesn't seem to work. Qemu immediately goes into infinite loop and has to be killed -9. Building anything besides qemu-system-i386 leads to link errors: LINK x86_64-linux-user/qemu-x86_64 /usr/bin/ld.gold.real: error: ../libqemustub.a(cpu-get-icount.o): multiple definition of 'use_icount' /usr/bin/ld.gold.real: exec.o: previous definition here -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: Confirmed Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 1556044] Re: Redox GUI hangs with 100% CPU on ARM
** Summary changed: - Redox GUI hangs with 100% CPU + Redox GUI hangs with 100% CPU on ARM -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1556044 Title: Redox GUI hangs with 100% CPU on ARM Status in QEMU: New Bug description: Booting into Redox OS cli on ARM with qemu-system-i386 works fine. However, starting the Redox GUI (orbital) brings up the graphical interface and then starts using 100% CPU. I'd guess it's related to mouse detection and handling. The OS image is fully usable on x86. https://www.dropbox.com/s/u6v2k9wzcuiycfo/redox-disk.img.xz?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1556044/+subscriptions
[Qemu-devel] [Bug 1556044] [NEW] Redox GUI hangs with 100% CPU
Public bug reported: Booting into Redox OS cli on ARM with qemu-system-i386 works fine. However, starting the Redox GUI (orbital) brings up the graphical interface and then starts using 100% CPU. I'd guess it's related to mouse detection and handling. The OS image is fully usable on x86. https://www.dropbox.com/s/u6v2k9wzcuiycfo/redox-disk.img.xz?dl=0 ** Affects: qemu Importance: Undecided Status: New ** Tags: arm -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1556044 Title: Redox GUI hangs with 100% CPU Status in QEMU: New Bug description: Booting into Redox OS cli on ARM with qemu-system-i386 works fine. However, starting the Redox GUI (orbital) brings up the graphical interface and then starts using 100% CPU. I'd guess it's related to mouse detection and handling. The OS image is fully usable on x86. https://www.dropbox.com/s/u6v2k9wzcuiycfo/redox-disk.img.xz?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1556044/+subscriptions
[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
Another OS that works: https://static.redox-os.org/redox-installer.iso -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: Confirmed Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 1529226] [NEW] qemu-i386-user on 32-bit Linux: uncaught target signal 11
Public bug reported: Even though the command I'm trying to run (a wrapper script for qemu-i386-user running rustc, the rust compiler) produces the expected compiled output, the build process is interrupted: qemu: uncaught target signal 11 (Segmentation fault) - core dumped i686-unknown-linux-gnu/stage0/bin/rustc: line 1: 7474 Segmentation fault /usr/local/bin/qemu-i386 -cpu qemu32 /home/petevine/stage0/rustc.bin -C target-cpu=pentium2 -L /home/petevine/unpacked/rust-master/i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/ "$@" make: *** [i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/stamp.rustc_back] Error 139 The stamp file is not being created so this could be about forking bash after finishing the wrapper script. Qemu was compiled from the latest git source. ** 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/1529226 Title: qemu-i386-user on 32-bit Linux: uncaught target signal 11 Status in QEMU: New Bug description: Even though the command I'm trying to run (a wrapper script for qemu-i386-user running rustc, the rust compiler) produces the expected compiled output, the build process is interrupted: qemu: uncaught target signal 11 (Segmentation fault) - core dumped i686-unknown-linux-gnu/stage0/bin/rustc: line 1: 7474 Segmentation fault /usr/local/bin/qemu-i386 -cpu qemu32 /home/petevine/stage0/rustc.bin -C target-cpu=pentium2 -L /home/petevine/unpacked/rust-master/i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/ "$@" make: *** [i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/stamp.rustc_back] Error 139 The stamp file is not being created so this could be about forking bash after finishing the wrapper script. Qemu was compiled from the latest git source. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1529226/+subscriptions
[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
Still present in 2.5. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: New Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 1519037] Re: qemu-i386 32-bit segfault
It seems this crash only happens in xterm (and not normal console). Having compared the respective environment vars the culprit turned out to be: TERM=xterm-color You're welcome. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1519037 Title: qemu-i386 32-bit segfault Status in QEMU: New Bug description: I'm getting segfaults on 32-bit linux trying to run binaries using qemu-i386 from git. These segfaults go away when run in gdb or strace - could it be about the environment somehow? In contrast qemu-x86_64 works fine. How can I pinpoint the cause of this? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1519037/+subscriptions
[Qemu-devel] [Bug 1519037] [NEW] qemu-i386 32-bit segfault
Public bug reported: I'm getting segfaults on 32-bit linux trying to run binaries using qemu-i386 from git. These segfaults go away when run in gdb or strace - could it be about the environment somehow? In contrast qemu-x86_64 works fine. How can I pinpoint the cause of this? Thanks! ** 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/1519037 Title: qemu-i386 32-bit segfault Status in QEMU: New Bug description: I'm getting segfaults on 32-bit linux trying to run binaries using qemu-i386 from git. These segfaults go away when run in gdb or strace - could it be about the environment somehow? In contrast qemu-x86_64 works fine. How can I pinpoint the cause of this? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1519037/+subscriptions
[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
I tried installing openbsd yesterday from an official image to another raw image disk - no problem and the installed system works flawlessly. Hurd also boots fine (via grub) along with a few toy x86 kernels. It almost begins to look as if the raw images are ok whereas the qcow2 format is the problem somehow. Had I tried those other images first I'd be convinced running x86 on arm hosts poses no problem at all - how is it even possible? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: New Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
BTW, it seems the more expensive (but vastly less popular) odroids like the xu4 are built around kvm enabled processors which is why this bug doesn't affect them. The most popular C1/C1+'s processor doesn't support kvm though so any update would be appreciated. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: New Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM
In case anyone's interested I've just discovered booting in recovery mode (root already logged in) doesn't exhibit the problem with non- working keyboard. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1498144 Title: Failure booting hurd with qemu-system-i386 on ARM Status in QEMU: New Bug description: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( fmt=0x1 , assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", line=91, line@entry=3069931692, function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:92 #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from 2015-09-15, armv7 Odroid C1) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1498144/+subscriptions
[Qemu-devel] [Bug 1469342] Re: qemu-i386 pentium3/athlon incorrect instruction set
I think I may have found the culprit - athlon is defined as 'PPRO_FEATURES + some additional features'. If PPRO_FEATURES is what I think it is (pentium pro) why does it have SSE and SSE2 defined? It should end with MMX. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1469342 Title: qemu-i386 pentium3/athlon incorrect instruction set Status in QEMU: Won't Fix Bug description: Running a binary containing a movsd instruction (SSE2) in 32-bit qemu-i386 from 20150609 using the -cpu pentium3 switch results in flawless execution whereas it should crash with SIGILL as P3 only had SSE and not SSE2. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469342/+subscriptions
[Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM
Even though not related to the original issue (was also happening on i386 a few days ago), after getting to the login prompt inside hurd the keyboard doesn't work and the only clue from the kernel at boot time might be this: 'Unexpected ACK from keyboard' or this: '/bin/console: could not receive return value from the daemon process: Connection timed out' I haven't got any more info so I'm not going to open a new bug myself. Thx. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1498144 Title: Failure booting hurd with qemu-system-i386 on ARM Status in QEMU: New Bug description: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( fmt=0x1 , assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", line=91, line@entry=3069931692, function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:92 #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from 2015-09-15, armv7 Odroid C1) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1498144/+subscriptions
[Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM
Lastly, the machine 'power down' button doesn't work and a new message appeared inside hurd: 'kdb: queue full' -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1498144 Title: Failure booting hurd with qemu-system-i386 on ARM Status in QEMU: New Bug description: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( fmt=0x1 , assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", line=91, line@entry=3069931692, function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:92 #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from 2015-09-15, armv7 Odroid C1) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1498144/+subscriptions
[Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM
I've just tried again with the latest commits - hurd boots, hooray! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1498144 Title: Failure booting hurd with qemu-system-i386 on ARM Status in QEMU: New Bug description: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( fmt=0x1 , assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", line=91, line@entry=3069931692, function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:92 #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from 2015-09-15, armv7 Odroid C1) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1498144/+subscriptions
[Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM
I can't get any more useful info - either the script is expecting some outdated version of python or there's simply nothing else to see cause qemu failed to start. For example: (gdb) source qemu-gdb.py (gdb) run Starting program: /usr/bin/qemu-system-i386 -m 512 -hda /media/odroid/debian-hurd-20150320.img and so on (gdb) qemu mtree Python Exception No symbol "address_space_memory" in current context.: Error occurred in Python command: No symbol "address_space_memory" in current context. As for using: qemu coroutine, I'm not sure where the pointer value should come from but feeding it a bogus one ends exactly as above. Any suggestions? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1498144 Title: Failure booting hurd with qemu-system-i386 on ARM Status in QEMU: New Bug description: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( fmt=0x1 , assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", line=91, line@entry=3069931692, function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:92 #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from 2015-09-15, armv7 Odroid C1) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1498144/+subscriptions
[Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM
All right, I'll rebuild and try qemu-gdb.py if still necessary. Do any fancy CFLAGS make a difference in performance or should they be avoided altogether on ARM? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1498144 Title: Failure booting hurd with qemu-system-i386 on ARM Status in QEMU: New Bug description: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( fmt=0x1 , assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", line=91, line@entry=3069931692, function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:92 #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from 2015-09-15, armv7 Odroid C1) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1498144/+subscriptions
[Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM
** Description changed: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () - at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 + at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () - at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 + at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) - at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 + at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( - fmt=0x1 , - assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, - file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", - line=91, line@entry=3069931692, - function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") - at assert.c:92 - #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", - line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") - at assert.c:101 + fmt=0x1 , + assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, + file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", + line=91, line@entry=3069931692, + function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") + at assert.c:92 + #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", + line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") + at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from - 2015-09-15) + 2015-09-15, armv7 Odroid C1) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1498144 Title: Failure booting hurd with qemu-system-i386 on ARM Status in QEMU: New Bug description: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( fmt=0x1 , assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", line=91, line@entry=3069931692, function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:92 #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from 2015-09-15, armv7 Odroid C1) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1498144/+subscriptions
[Qemu-devel] [Bug 1498144] [NEW] Failure booting hurd with qemu-system-i386 on ARM
Public bug reported: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( fmt=0x1 , assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", line=91, line@entry=3069931692, function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:92 #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from 2015-09-15) ** 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/1498144 Title: Failure booting hurd with qemu-system-i386 on ARM Status in QEMU: New Bug description: Trying to boot debian-hurd-20150320.img ends with: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xb6ef8f0e in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb6efb766 in __GI_abort () at abort.c:89 #3 0xb6ef4150 in __assert_fail_base ( fmt=0x1 , assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb566 "\001", line=91, line@entry=3069931692, function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:92 #4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb566 "\001", line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all") at assert.c:101 #5 0x7f59a6b4 in ?? () I was using the same setup as in Bug 893208 (i.e git checkout from 2015-09-15) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1498144/+subscriptions
[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
What a funny coincidence, just before getting all of that bug email (telepathy?), I decided to also try a debian hurd image, but it immediately aborts: qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all: Assertion `qemu_in_coroutine()' failed. Aborted Is this known and/or deserving a separate 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/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: New Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 1469342] Re: qemu-i386 pentium3/athlon incorrect instruction set
After looking at target-i386/cpu.c, it's clear to me CPUID_SSE and CPUID_SSE2 are defined seperately and neither pentium3 nor athlon have those defines set. This could mean it's a bug not in the instruction set but possibly in the build process somewhere. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1469342 Title: qemu-i386 pentium3/athlon incorrect instruction set Status in QEMU: Won't Fix Bug description: Running a binary containing a movsd instruction (SSE2) in 32-bit qemu-i386 from 20150609 using the -cpu pentium3 switch results in flawless execution whereas it should crash with SIGILL as P3 only had SSE and not SSE2. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469342/+subscriptions
[Qemu-devel] [Bug 1469342] Re: qemu-i386 pentium3/athlon incorrect instruction set
In the case it's really unfixable and both pentium3 and athlon are nothing more than aliases for 'QEMU Virtual CPU version 2.4.50' they should be removed from the list the user gets after: qemu-i386 -cpu help so as not to mislead. Thanks! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1469342 Title: qemu-i386 pentium3/athlon incorrect instruction set Status in QEMU: Won't Fix Bug description: Running a binary containing a movsd instruction (SSE2) in 32-bit qemu-i386 from 20150609 using the -cpu pentium3 switch results in flawless execution whereas it should crash with SIGILL as P3 only had SSE and not SSE2. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469342/+subscriptions
[Qemu-devel] [Bug 1469342] Re: qemu-i386 pentium3/athlon incorrect instruction set
I'm pretty sure you're right regarding entire instruction sets - but surely simply disabling SSE2 is possible even now? (after all pentium2 and below doesn't have it) That could solve this problem with a simple hack like, eg. : pentium3 = $pentium3 - SSE2 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1469342 Title: qemu-i386 pentium3/athlon incorrect instruction set Status in QEMU: Won't Fix Bug description: Running a binary containing a movsd instruction (SSE2) in 32-bit qemu-i386 from 20150609 using the -cpu pentium3 switch results in flawless execution whereas it should crash with SIGILL as P3 only had SSE and not SSE2. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469342/+subscriptions
[Qemu-devel] [Bug 1469342] Re: qemu-i386 pentium3 incorrect instruction set
Still there in the latest master. To clarify, running the binary with the -cpu athlon switch (same instruction set as P3) also exhibits the problem whereas a real athlon SIGILL's correctly. ** Description changed: Running a binary containing a movsd instruction (SSE2) in 32-bit - qemu-i386 -cpu pentium3 from 20150609 results in flawless execution - whereas it should crash with SIGILL as P3 only had SSE. + qemu-i386 from 20150609 using the -cpu pentium3 switch results in + flawless execution whereas it should crash with SIGILL as P3 only had + SSE and not SSE2. ** Summary changed: - qemu-i386 pentium3 incorrect instruction set + qemu-i386 pentium3/athlon incorrect instruction set -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1469342 Title: qemu-i386 pentium3/athlon incorrect instruction set Status in QEMU: New Bug description: Running a binary containing a movsd instruction (SSE2) in 32-bit qemu-i386 from 20150609 using the -cpu pentium3 switch results in flawless execution whereas it should crash with SIGILL as P3 only had SSE and not SSE2. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469342/+subscriptions
[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
Just for laughs I 've tested my qemu build with this guy's x86 kernel and it's working as expected: https://github.com/mopp/Axel the difference being it was using -cdrom switch to boot from an .iso image -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: New Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 893208] Re: qemu on ARM hosts can't boot i386 image
I was about to file a bug with the exact symptoms. I can't boot a (possibly the very one) debian wheezy standard qcow2 image on my Odroid C1 (works fine on x86-32 with the same command line) using qemu-system-i386 that I built yesterday from git source. Is there a workaround or has nobody needed this for the last 4 years? Please advise on how to provide more relevant details. Thanks -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/893208 Title: qemu on ARM hosts can't boot i386 image Status in QEMU: New Status in Linaro QEMU: New Bug description: If you apply some workarounds for bug 870990, bug 883133 and bug 883136 QEMU still cannot boot the i386 debian_squeeze_i386_standard.qcow2 image from http://people.debian.org/~aurel32/qemu/i386/ -- grub starts to boot but something causes the system to reset just before display of the blue-background grub menu, so we go round in a loop forever. This image boots OK on i386 hosted qemu so this indicates some kind of ARM- host specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/893208/+subscriptions
[Qemu-devel] [Bug 1469342] [NEW] qemu-i386 pentium3 incorrect instruction set
Public bug reported: Running a binary containing a movsd instruction (SSE2) in 32-bit qemu-i386 -cpu pentium3 from 20150609 results in flawless execution whereas it should crash with SIGILL as P3 only had SSE. ** 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/1469342 Title: qemu-i386 pentium3 incorrect instruction set Status in QEMU: New Bug description: Running a binary containing a movsd instruction (SSE2) in 32-bit qemu-i386 -cpu pentium3 from 20150609 results in flawless execution whereas it should crash with SIGILL as P3 only had SSE. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469342/+subscriptions
