Public bug reported:
libvirt version 0.9.2-4ubuntu8 failed to build on armel
Link to failed build:
https://launchpad.net/ubuntu/+source/libvirt/0.9.2-4ubuntu8/+build/2673838
Direct link to the build log:
https://launchpad.net/ubuntu/+source/libvirt/0.9.2-4ubuntu8/+build/2673838/+files
Repo out of sync?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/823711
Title:
libvirt version 0.9.2-4ubuntu8 failed to build on armel
To manage notifications about this bug go
** Changed in: u-boot-linaro (Ubuntu)
Assignee: (unassigned) = John Rigby (jcrigby)
** Changed in: u-boot-linaro (Ubuntu)
Status: New = Confirmed
** Changed in: u-boot-linaro (Ubuntu)
Importance: Undecided = Medium
** Also affects: u-boot-linaro
Importance: Undecided
Can you later post your patch or link to this bug? Then I can help
testing it with rootstock.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/604872
Title:
qemu-system-arm
On Fri, Jan 7, 2011 at 7:53 AM, Jani Monoses j...@ubuntu.com wrote:
should the fixes be applied to qemu-kvm if we plan on packaging qemu-
meego for ARM support anyway?
It depends on the size of the fix, if it's something simple we can for
sure also update the qemu-kvm package. But as Loic
This also happens with Maverick, as we're using 0.12.5+noroms-
0ubuntu7.1. Would be good to have it fixed in order to create natty
rootfs with rootstock.
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
I'm now implementing the support for creating a rootstock rootfs without
requiring root, and I also got stuck at a segmentation fault, just after
executing the debootstrap' second stage.
I'm running the qemu-system-arm from qemu-kvm-extras 0.12.4+noroms-
0ubuntu4, at maverick.
My qemu command
Public bug reported:
Binary package hint: qemu-kvm
As I'm now implementing the support for creating a rootstock rootfs
without requiring root, I need to run the deboostrap' second stage
inside a VM, to correctly install the packages into the rootfs.
qemu-system-arm fails right after debootstrap
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/51803593/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/51803594/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51803595/Dependencies.txt
**
Maverick:
I: Base system installed successfully.
I: Starting basic services in VM
Program received signal SIGSEGV, Segmentation fault.
0xceeef54c in ?? ()
(gdb) bt full
#0 0xceeef54c in ?? ()
No symbol table info available.
#1 0x7fffdfa0 in ?? ()
No symbol table info
I'm also able to reproduce with upstream Qemu, hash
aa5fb7b3bf388d643bd9c6e6fee9ace5db2e590f
I: Base system installed successfully.
I: Starting basic services in VM
Program received signal SIGSEGV, Segmentation fault.
0x8be2208b in ?? ()
(gdb) bt full
#0 0x8be2208b in ?? ()
No
If you're at Lucid or Maverick, you can also create the rootfs img by
running the attached rootstock script.
Please install all rootstock dependencies by installing the official version
provided by the distro:
sudo apt-get install rootstock
Using the attached script:
sudo bash ./rootstock
For the seg fault bug I've created the bug 604872.
Meanwhile I'll try to reproduce the hang problem with Maverick and
upstream Qemu.
--
apt/dpkg in qemu-system-arm hangs if a big task is installed
https://bugs.launchpad.net/bugs/532733
You received this bug notification because you are a member
Here is where it's getting stuck now:
Selecting previously deselected package libimobiledevice0.
Unpacking libimobiledevice0 (from
.../libimobiledevice0_0.9.7-1ubuntu1_armel.deb) ...
Selecting previously deselected package libtalloc2.
Unpacking libtalloc2 (from
Tested with Maverick's vmlinuz-2.6.35-10-versatile and I'm still able to
reproduce the problem (qemu cdcf9153e5e17dde340135fee5dcc7c299f2d4f5
this time).
--
qemu-system-arm segfaults emulating versatile machine after running debootstrap
--second-stage inside vm
Public bug reported:
Binary package hint: qemu-kvm
At lucid the pselect patch was added to qemu, in a way to remove the
annoying qemu: Unsupported syscall: 335 messages that you get when
running apt-get with qemu arm user emulation, but now this message is
back in Maverick.
Original bug for
The thread explaining why the pselect patch was dropped:
http://www.mail-archive.com/qemu-de...@nongnu.org/msg28238.html
--
qemu shows qemu: Unsupported syscall: 335 for pselect in Maverick
https://bugs.launchpad.net/bugs/610742
You received this bug notification because you are a member of
What fails is qemu-arm-static, as rootstock uses it internally to
install the packages.
--
apt/dpkg in qemu-system-arm hangs if a big task is installed
https://bugs.launchpad.net/bugs/532733
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1429938
Title:
systemd changes behavior of apt-get
** Changed in: snappy/15.04
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1450642
Title:
seccomp missing many new syscalls
To
** Also affects: snappy/15.04
Importance: Undecided
Status: New
** Changed in: snappy/15.04
Milestone: None = 15.04.1
** Changed in: snappy/15.04
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
** Changed in: snappy/15.04
Status: New = Fix Committed
** Changed
21 matches
Mail list logo
