This bug was fixed in the package qemu - 1.7.0+dfsg-3ubuntu5
---
qemu (1.7.0+dfsg-3ubuntu5) trusty; urgency=medium
[ dann frazier ]
* Add patches from the susematz tree to avoid intermittent segfaults:
- ubuntu/signal-added-a-wrapper-for-sigprocmask-function.patch
- ubun
** Branch linked: lp:ubuntu/trusty-proposed/qemu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1285363
Title:
qemu-aarch64-static segfaults
To manage notifications about this bug go
Quoting Peter Maydell (peter.mayd...@linaro.org):
> Doing this only for aarch64 targets seems like a bad idea to me -- this
> isn't an aarch64 specific issue. QEMU needs SIGSEGV to go to its own
> handler (so we can unprotect pages we've marked as read-only in order to
> catch guest writes to them
Doing this only for aarch64 targets seems like a bad idea to me -- this
isn't an aarch64 specific issue. QEMU needs SIGSEGV to go to its own
handler (so we can unprotect pages we've marked as read-only in order to
catch guest writes to them so we can throw away invalidated translated
code), and tha
@Serge: I can confirm that this is fixed in 1.7.0+dfsg-3ubuntu5sig1 from
your ppa.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1285363
Title:
qemu-aarch64-static segfaults
To manag
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1285363
Title:
qemu-aarch64-static segfaults
To manage notifications a
On Thu, Feb 27, 2014 at 3:34 PM, Serge Hallyn
<1285...@bugs.launchpad.net> wrote:
> Dann,
>
> can you confirm that you can reproduce this with the upstream git head
> (or the qemu-2.0~git package)?
I just reverified with upstream git head @
9fbee91a131a05e443d7108d7fbdf3ca91020290.
Note that this
I'm building a candidate package with a modified version of the patchset
(to only change behavior for aarch64 targets) in ppa:serge-hallyn/virt.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1285363
Title:
Dann,
can you confirm that you can reproduce this with the upstream git head
(or the qemu-2.0~git package)?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1285363
Title:
qemu-aarch64-
I'm a little nervous about the do_sigprocmask in linux-user/signal.c for
all arches. With the comment
/* Force set state of SIGSEGV, may be best for some apps, maybe not so good
++ * This is not required for qemu to work
Doing this conditionally for arm64 would be more comforting...
I'll go
The attachment "qemu.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you a
12 matches
Mail list logo
