similar to: issue on fedora21 with libvirt-1.2.13 and 1.2.14 - containers won't start at all

Hi there I am using fedora21 for hosts and guests, using lxc containers, and was on vanilla 1.2.9 as exposed by the fedora yum repo The other day I was needing the ability to grant mknod capability to some guests, some chap on IRC kindly pointed me at the <capabilities> tag However I was told that needed 1.2.11 So I went and rebuilt from this download

Hi folks I use libvirt to programmatically spawn lxc containers I am facing an issue when migrating from fedora23 to fedora24 I use the stock kernel and libvirt version on both deployments, i.e.: f23: libvirt-1.2.18.3-2.fc23.x86_64 - kernel 4.5.7-202.fc23.x86_64 f24: libvirt-1.3.3.1-4.fc24.x86_64 - kernel 4.6.3-300.fc24.x86_64 First off, I need to outline that the host installation is done

Hello The latest attempts that I made on fedora21 all gave me the same result I have tried . vanilla rpm from f21 (1.2.9 IIRC) . 1.2.14 . 1.2.13 . 1.2.12 these three ones I rebuilt from the source rpm published by libvirt eventually I reworked my own tools to enter the container via ssh, so this is not an immediate concern to me any longer but it is definitely odd I currently use 1.2.12

Hi again Answering my own e-mail on a few points: . first off, stupid me, http://libvirt.org/format.html indeed is empty and it seems to be by design, but the subtrees are not, like e.g. http://libvirt.org/formatdomain.html . from this page it seems like using something like <os> <type arch='i686'>exe</type> <init>/sbin/init</init> </os>

Hi folks I have a question about lxc-enter-namespace I am migrating lxc containers from a host running libvirt-1.2.5 on f20 to another one running libvirt-1.2.9 on f21 and now I can't seem to use lxc-enter-namespace for entering in a container any more I would do virsh -c lxc:/// lxc-enter-namespace --noseclabel container /bin/bash but when I try the same now I am getting this: # virsh

Hi there I have a couple of newbie questions concerning running a 32bits guest in a 64bits host using libvirt - lxc; I’m running libvirt-1.2.5 on fedora18 and fedora20 (a) is this supported at all, and (b) if so how do I configure this for a given guest ? guessing from the mere existence of http://www.redhat.com/archives/libvir-list/2011-February/msg01040.html I would think the answer to (a) is

Hi there I’m not quite proficient with libvirt yet, and have been using it so far primarily to manage lxc containers I was hoping to find a means to configure the set of capabilities that guests should drop, but came across a few web pages suggesting these were set in stone in the code is this correct, or is there a means to tweak this set from the host via the xml config or a virsh command ?

Thanks for the feedback I take it from your answer that there is no current plan in the direction of adding this as a feature, right ? In this case, how would you welcome pull requests if we managed to add this on our side ? Many thanks — Thierry On 29 Jan 2014, at 14:27, Daniel P. Berrange <berrange@redhat.com> wrote: > On Wed, Jan 29, 2014 at 09:43:25AM +0100, Thierry Parmentelat

On Wed, Jul 02, 2014 at 12:56:18AM +0200, Thierry Parmentelat wrote: > Hi again > > Answering my own e-mail on a few points: > > . first off, stupid me, http://libvirt.org/format.html indeed is empty and it seems to be by design, but the subtrees are not, like e.g. > http://libvirt.org/formatdomain.html > > . from this page it seems like using something like >

On Tue, Sep 10, 2013 at 2:20 PM, Dennis Jenkins <dennis.jenkins.75@gmail.com > wrote: > On Tue, Sep 10, 2013 at 1:34 PM, Doug Goldstein <cardoe@gentoo.org>wrote: > >> A suggestion would be to make sure that you have all the necessary >> kernel options enabled. You can check with: ebuild >> /usr/portage/app-emulation/libvirt/libvirt-1.1.2-r1.ebuild setup clean

On Tue, Sep 10, 2013 at 09:09:44AM -0500, Dennis Jenkins wrote: > I recently upgraded "libvirt" on Gentoo to 1.2.2-r1 (latest available). I > have not used LXC containers for a few weeks, so I don't recall what > version of libvirt I was using when my container last booted successfully. > > ostara ~ # tail /var/log/libvirt/lxc/dwj-hfax-dev.log > 2013-09-10

On Wed, Jan 29, 2014 at 09:43:25AM +0100, Thierry Parmentelat wrote: > Hi there > > I’m not quite proficient with libvirt yet, and have been using it > so far primarily to manage lxc containers > I was hoping to find a means to configure the set of capabilities > that guests should drop, but came across a few web pages suggesting > these were set in stone in the code > is

Hi again Sorry for the late reaction on this.. So everything seems to work fine for me when using the setting below, except maybe for one little point I was kind of expecting that # virsh -c lxc:/// lxc-enter-namespace my_32bits_vm ... would run in a 32bits environment too, but from what I can see it is not the case I take it it can be argued, reading the documentation for lxc-enter-namespace

On Tue, Sep 10, 2013 at 1:34 PM, Doug Goldstein <cardoe@gentoo.org> wrote: > On Tue, Sep 10, 2013 at 9:09 AM, Dennis Jenkins > <dennis.jenkins.75@gmail.com> wrote: > > Yeah our security people got a bit over zealous. That's being rectified. > > :) > > > > TL;DR: My container is configured to use "br0" for its networking. "br0"

On 09/11/2013 04:44 PM, Daniel P. Berrange wrote: > On Tue, Sep 10, 2013 at 09:09:44AM -0500, Dennis Jenkins wrote: >> I recently upgraded "libvirt" on Gentoo to 1.2.2-r1 (latest available). I >> have not used LXC containers for a few weeks, so I don't recall what >> version of libvirt I was using when my container last booted successfully. >> >>

I recently upgraded "libvirt" on Gentoo to 1.2.2-r1 (latest available). I have not used LXC containers for a few weeks, so I don't recall what version of libvirt I was using when my container last booted successfully. Unfortunately, Gentoo's portage tree does not offer any previous versions of libvirt that I could downgrade to. TL;DR: My container is configured to use

On 12.07.2013 20:32, Dennis Jenkins wrote: > Update: I am able to edit the XML in "dwj-hfax-dev" such that libvirtd > no longer crashes, and edit the XML for "dwj-lnx-dev" such that it will > crash. > > The presents of "<seclabel type='none'/>" near the bottom causes > libvirtd to crash. > > I do not recall ever manually adding

On Mon, Jul 15, 2013 at 7:53 AM, Dennis Jenkins <dennis.jenkins.75@gmail.com > wrote: > > > > TL;DR: "vm->seclabels[i]->model" is NULL. > > > It probably would have been helpful had I posted everything in the struct: (gdb) print vm->seclabels[i] $6 = (virSecurityLabelDefPtr) 0x7fffd0009dc0 (gdb) print *(vm->seclabels[i]) $7 = {model = 0x0, label

On Mon, Jul 15, 2013 at 7:37 AM, Dennis Jenkins <dennis.jenkins.75@gmail.com > wrote: > Ah ha! I just learned about "gdb bt full". The existing core dump might > have what you need: Line #442. However, the line numbers for the source > code in the source tree that my Gentoo system is building from does not > match exactly what you listed. > > Line #442 for me

Ah ha! I just learned about "gdb bt full". The existing core dump might have what you need: Line #442. However, the line numbers for the source code in the source tree that my Gentoo system is building from does not match exactly what you listed. Line #442 for me is the one containing the "STREQ" macro: virObjectLock(mgr); for (i = 0; i < vm->nseclabels; i++)