[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
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 bo
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscrib
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
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 receiv
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 wi
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:
On 09/23/15 17:13, PeteVine wrote:
> 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-
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-20
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.
** 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/sy
10 matches
Mail list logo
