** Changed in: lxc (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf container on an
I've been creating several armhf containers on raring with no problems.
Can we call this fix released in raring?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu
** Tags removed: apport-bug rls-q-incoming
** Tags added: aport-bug rls-q-notfixing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf
qemu-user-static was installed on the system when I have been able to
reproduce this error (installed on 2012-06-06 from apt log files)
I tried again this morning, and it works correctly. The main difference
is that qemu-user-static has been upgraded from 1.0.50-2012.03-0ubuntu3
to
** Changed in: qemu-linaro (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf
Ok - I'm able to reproduce this when qemu-user-static is not installed.
When qemu-user-static is installed, container creation succeeds.
Looking at the lxc-ubuntu template, I'm not sure what we want to do in
the failing case. I would guess we want to announce that qemu-armhf-
static is not
@jibel,
to be clear, you should NOT get this if you have qemu-user-static
installed. If you do, please shout to have the priority raised.
The question for now is what we should do about this. Should we detect
foreign arch and insist qemu-user-static be installed?
In the meantime, since there
(my guess fwiw is that calling qemu-arm in a chroot fails because the
libraries it links against are not available; hence the need for qemu-
arm-static)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf container on an amd64 host
To manage notifications
The problem persists on Quantal with all updates applied:
$ sudo lxc-create -n quantal-armhf -t ubuntu -- -r quantal -a armhf
[...]
Fetched 22.1 MB in 60s (365 kB/s)
I can't currently reproduce this as it seems the armhf archives are out
of sync
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf
ping - is this still happening for you? Can we mark it fix released?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf container on
I cannot tell for the moment, it is not possible to install an armhf
container on an amd64 host due to gcc 4.7.1-7ubuntu1 failing to build on
armhf.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I get it systematically on my system with latest updates applied. Do you
have any advice how to troubleshoot it ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu
Quoting Jean-Baptiste Lallement (jean-bapti...@ubuntu.com):
I get it systematically on my system with latest updates applied. Do you
By systematically do you mean every time, or every N times?
have any advice how to troubleshoot it ?
A few things may help,
1. install the qemu-user-static-dbg
Hm, I can't reproduce this exactly, rather I got:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following
(actually it just occurred to me that machine was not quite pristine,
re-trying elsewhere)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an
This is bug 1017862
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf container on an amd64 host
To manage notifications about this
Right, with quantal-proposed enable you shouldn't be getting that bug
anymore (1017862), I'll SRU it next week.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu
Could you re-try this on a clean machine? I can create a precise
container on quantal with no problems. I'm having trouble with a
quantal container, but it seems to be a problem in lxc (which should be
fixed) or transient archive problem. I see no qemu crashes here.
** Changed in: lxc (Ubuntu)
Makes sense, thanks. Will re-try one more time with -proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf container on an amd64
couldn't reproduce.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1017847
Title:
qemu segfaults when creating an armhf container on an amd64 host
To manage notifications about this
Thanks for submitting this bug. The qemu used by lxc is actually qemu-
arm-static which comes from the qemu-linaro package, so I will re-target
the bug. I'll also mark it as affecting lxc.
** Package changed: qemu-kvm (Ubuntu) = qemu-linaro (Ubuntu)
** Also affects: lxc (Ubuntu)
Importance:
This looks like a regression in qemu from Precise to Quantal. I just
rebuilt my test containers here on Precise and both precise and quantal
armhf containers built successfully.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
24 matches
Mail list logo
