(wrong bug, sorry!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
To manage notifications about this bug go to:
Hello, this seems to be still an issue
W: Failure while unpacking required packages. This will be attempted up to
five times.
W: See //debootstrap/debootstrap.log for details (possibly the package
/var/cache/apt/archives/bash_4.4.18-1ubuntu1_arm64.deb is at fault)
dpkg -l |grep qemu
ii
This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu1
---
qemu (1:2.11+dfsg-1ubuntu1) bionic; urgency=medium
* Merge with Debian testing, among other fixes this includes
- fix fatal error on negative maxcpus (LP: #1722495)
- fix segfault on dump-guest-memory on
per former comments, in context qemu 2.11 is in proposed
** Changed in: qemu (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
** Tags added: qemu-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
To manage notifications about this bug go to:
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
To manage notifications about this bug go
We think we've fixed our linux-user threading issues, so if there are
still problems as of qemu-2.11 or later, please raise a fresh bug report
with repro instructions.
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member
We're now building armhf/arm64 packages on real arm64 hardware in
Launchpad, so, while this problem may well still exist in qemu, it no
longer applies to Launchpad builds.
** Changed in: launchpad-buildd
Status: Triaged => Won't Fix
--
You received this bug notification because you are a
We're now building armhf/arm64 packages on real arm64 hardware in
Launchpad, so, while this problem may well still exist in qemu, it no
longer applies to Launchpad builds.
** Changed in: launchpad-buildd
Status: Triaged => Won't Fix
--
You received this bug notification because you are a
Well. This is definitely wrong. It is a valid bug, but it needs quite
serious work to fix, which requires major refactoring of the tcg code.
Upstream is working on it, see http://wiki.qemu.org/Features/tcg-
multithread
** Changed in: qemu
Status: Invalid => Confirmed
--
You received
Well. This is definitely wrong. It is a valid bug, but it needs quite
serious work to fix, which requires major refactoring of the tcg code.
Upstream is working on it, see http://wiki.qemu.org/Features/tcg-
multithread
** Changed in: qemu
Status: Invalid => Confirmed
--
You received
Ah, thanks for setting me straight.
** Changed in: qemu (Ubuntu)
Status: Invalid => 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/1350435
Title:
tcg.c:1693: tcg
Ah, thanks for setting me straight.
** Changed in: qemu (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
To
This patch is still not applied upstream.
As there has been no discussion in over a year, I assume it is no longer
a problem and I'm going to mark it invalid. Please rep;ly if that is
not the case.
If it *is* still a problem, then we should go discuss on oftc#qemu.
** Changed in: qemu
This patch is still not applied upstream.
As there has been no discussion in over a year, I assume it is no longer
a problem and I'm going to mark it invalid. Please rep;ly if that is
not the case.
If it *is* still a problem, then we should go discuss on oftc#qemu.
** Changed in: qemu
Hi Serge, sorry for the delay,
the problem is that if I run pbuilder-dist utopic armhf create
pbuilder-dist utopic armhf build boinc_whatever.dsc the build never fails also
with the trusty qemu, so I cannot test your package with the patch.
(I'm already on trusty, should I really install a server
Perhaps i don't understand what you are doing.
My understanding was that a package is being built (in the buildds)
under qemu. Qemu is failing due to tcg failure. We want to tes
twhether a qemu patch fixes it.
That's why I suggest installing the new qemu package on your host, using
it to run a
I didn't install a VM because:
-I'm on ubuntu 14.04 on my laptop
-I use pbuilder-dist (from ubuntu-dev-tools) armhf that uses qemu as underlying
virtualization system.
the fact is:
why on my machine it doesn't show this error?
possible solution:
-because qemu+pbuilder-dist is not multithreaded?
Hi Serge, sorry for the delay,
the problem is that if I run pbuilder-dist utopic armhf create
pbuilder-dist utopic armhf build boinc_whatever.dsc the build never fails also
with the trusty qemu, so I cannot test your package with the patch.
(I'm already on trusty, should I really install a server
Perhaps i don't understand what you are doing.
My understanding was that a package is being built (in the buildds)
under qemu. Qemu is failing due to tcg failure. We want to tes
twhether a qemu patch fixes it.
That's why I suggest installing the new qemu package on your host, using
it to run a
I didn't install a VM because:
-I'm on ubuntu 14.04 on my laptop
-I use pbuilder-dist (from ubuntu-dev-tools) armhf that uses qemu as underlying
virtualization system.
the fact is:
why on my machine it doesn't show this error?
possible solution:
-because qemu+pbuilder-dist is not multithreaded?
Are these new failures using the qem upackage in ppa:serge-hallyn/qemu-
user-thread, or using the stock trusty qemu 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/1350435
How can I use your one? I have no possibility to tweak the host system,
I'm not an lp admin, do you think I can try to add your ppa as
dependency and it will work?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
No, that won't work as it's the emulator in which the build is running.
You should however be able to install the ppa's qemu on a local host,
install a standard ubuntu server vm, apt-get install ubuntu-dev-tools,
copy the package sources over to the vm, and build the packages inside
the vm.
--
Are these new failures using the qem upackage in ppa:serge-hallyn/qemu-
user-thread, or using the stock trusty qemu package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693:
How can I use your one? I have no possibility to tweak the host system,
I'm not an lp admin, do you think I can try to add your ppa as
dependency and it will work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, that won't work as it's the emulator in which the build is running.
You should however be able to install the ppa's qemu on a local host,
install a standard ubuntu server vm, apt-get install ubuntu-dev-tools,
copy the package sources over to the vm, and build the packages inside
the vm.
--
Interesting enough the utopic build was successful!
--
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/1350435
Title:
tcg.c:1693: tcg fatal error
To manage notifications about this bug
I got this morning a new FTBFS in a package that have been always built
successfully in the past, just FYI
https://launchpadlibrarian.net/181879742/buildlog_ubuntu-trusty-armhf.boinc_7.4.0~nightly1~~git20140809%2Br21874~r184~ubuntu14.04.1_FAILEDTOBUILD.txt.gz
--
You received this bug
And when I retried the failed build it succeeded but a segmentation fault (core
dumped) is in the logs
https://code.launchpad.net/~costamagnagianfranco/+archive/ubuntu/firefox/+build/6254532
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
I got this morning a new FTBFS in a package that have been always built
successfully in the past, just FYI
https://launchpadlibrarian.net/181879742/buildlog_ubuntu-trusty-armhf.boinc_7.4.0~nightly1~~git20140809%2Br21874~r184~ubuntu14.04.1_FAILEDTOBUILD.txt.gz
--
You received this bug
Interesting enough the utopic build was successful!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
To manage notifications about this bug go to:
And when I retried the failed build it succeeded but a segmentation fault (core
dumped) is in the logs
https://code.launchpad.net/~costamagnagianfranco/+archive/ubuntu/firefox/+build/6254532
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
https://launchpad.net/~serge-hallyn/+archive/ubuntu/qemu-user-thread
contains a package with this patch applied (built for trusty). Please
let us know how much it helps.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://launchpad.net/~serge-hallyn/+archive/ubuntu/qemu-user-thread
contains a package with this patch applied (built for trusty). Please
let us know how much it helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Peter: While this is true, is it actually likely to happen? I thought
in our conversations in the past (when I previously attempted to
escalate this class of problems via Linaro) it had been fairly clear
that this was a very difficult task that isn't likely to be scheduled
for the foreseeable
I think it's likely to happen eventually; it depends rather on the
balance between this and other work priorities (at least if it's going
to be Linaro doing the work). Regardless, I'm not taking hacky
workarounds like this into mainline (hacks are hard to get out once you
let them in, and they
Right, I can absolutely understand that. The question would I suppose
be whether you think this is a completely unreasonable thing to put in a
distro patch; I think SUSE are doing so for basically the same reason we
would be, that is, a setup such as PPAs where virtualisation isn't
available
Well, it won't make anything any worse, so it's your call based on how
much it actually improves your failure rate I guess.
--
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/1350435
Title:
Peter: While this is true, is it actually likely to happen? I thought
in our conversations in the past (when I previously attempted to
escalate this class of problems via Linaro) it had been fairly clear
that this was a very difficult task that isn't likely to be scheduled
for the foreseeable
I think it's likely to happen eventually; it depends rather on the
balance between this and other work priorities (at least if it's going
to be Linaro doing the work). Regardless, I'm not taking hacky
workarounds like this into mainline (hacks are hard to get out once you
let them in, and they
Well, it won't make anything any worse, so it's your call based on how
much it actually improves your failure rate I guess.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693:
Right, I can absolutely understand that. The question would I suppose
be whether you think this is a completely unreasonable thing to put in a
distro patch; I think SUSE are doing so for basically the same reason we
would be, that is, a setup such as PPAs where virtualisation isn't
available
No, I did not test the patch, I don't think that I can push that patch
in lp infrastructure, and I don't have my own one.
Anyway Peter is right, we don't need to hide bugs, but to fix them ;)
** Changed in: qemu (Ubuntu)
Status: Incomplete = New
** Tags removed: patch
--
You received
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
** Changed in: qemu (Ubuntu)
Importance: High = Wishlist
--
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/1350435
Title:
No, I did not test the patch, I don't think that I can push that patch
in lp infrastructure, and I don't have my own one.
Anyway Peter is right, we don't need to hide bugs, but to fix them ;)
** Changed in: qemu (Ubuntu)
Status: Incomplete = New
** Tags removed: patch
--
You received
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
** Changed in: qemu (Ubuntu)
Importance: High = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg
** Also affects: launchpad-buildd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: launchpad-buildd (Ubuntu)
** Also affects: launchpad-buildd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server
** 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/1350435
Title:
tcg.c:1693: tcg fatal error
To manage notifications
Hi,
have already tested with that patch to verify that it fixes the
issue? If I put qemu + that patch into a ppa, will your infrastructure
allow you to test that way?
I'm a bit concerned about this patch, as it appears to be one which has
been in the Suse tree for quite some time, begging the
That patch is not in mainline because it's an appalling hack. If we care
about multi-threaded guests we need to fix them properly, not paper over
the issues by constraining multiple threads to one CPU in the hopes the
race conditions don't bite us so often.
--
You received this bug notification
** Also affects: launchpad-buildd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: launchpad-buildd (Ubuntu)
** Also affects: launchpad-buildd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
To manage notifications about this bug go
Hi,
have already tested with that patch to verify that it fixes the
issue? If I put qemu + that patch into a ppa, will your infrastructure
allow you to test that way?
I'm a bit concerned about this patch, as it appears to be one which has
been in the Suse tree for quite some time, begging the
That patch is not in mainline because it's an appalling hack. If we care
about multi-threaded guests we need to fix them properly, not paper over
the issues by constraining multiple threads to one CPU in the hopes the
race conditions don't bite us so often.
--
You received this bug notification
55 matches
Mail list logo
