similar to: configuring a lxc guest to run 32bits from a 64bits host under libvirt-lxc

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>

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 >

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

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 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 ?

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

On 26.02.2014 17:59, Stephan Sachse wrote: >> # chown -R foo:foo /var/lib/libvirt/filesystems/mycontainer > > you must "shift" the uids for the container 0 -> 666, 1 -> 667, 2 -> > 668. there is a tool for this: uidmapshift I prepared two containers, the first I used chown, in the second uidmapshift, here is the results. ./uidmapshift -r

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

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

Hi! I am trying to run tap networking with libvirtd. My test system is Fedora18/ppc64, libvirt 1.0.4 (compiled from git and installed). On another system with Fedora17/ppc64 with the same settings, dnsmasq is running. All configs in /etc/libvirt/ are default and not changed, the only exception is /etc/libvirt/qemu/networks/default.xml which I copied from Fedora17/ppc64 setup. What does

Hi there I’ve just moved to libvirt-1.2.3 from 1.2.1; we use it for dealing with lxc containers I just wanted to report that everything went well for us with this new release, except for one little glitch At some point the lxc drivers seems to check that the kernel indeed has the netns feature built in Well in our environment this checks miserably fails; I haven’t been able to tell exactly why,

On Thu, Feb 27, 2014 at 3:07 PM, Dariusz Michaluk <d.michaluk@samsung.com> wrote: > On 26.02.2014 17:59, Stephan Sachse wrote: >>> >>> # chown -R foo:foo /var/lib/libvirt/filesystems/mycontainer >> >> you must "shift" the uids for the container 0 -> 666, 1 -> 667, 2 -> >> 668. there is a tool for this: uidmapshift > > I

Hi, >> > # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home >> > prop-1.img prop-expand.img >> > command line: virt-resize -d --expand /dev/sda1 --LV-expand >> > /dev/mapper/prop-home prop-1.img prop-expand.img >> > Examining prop-1.img ... >> > libguestfs: trace: add_drive "prop-1.img" "readonly:true"

Apologies as this is is not a specific libvirt question. Is qemu-img convert compatible with thin-provisioned LVs as targets ? I wanted to convert a file-based image to a LV image where the file-based image has a capacity much larger than the actual data it contains, so it has a small footprint on disk (either a qcow2 or a raw, but sparse, image). If I use qemu-img convert -O raw ... with a

Hello I am trying to create interfaces within an LXC container with specific name. I am using the following XML: <interface type='network' name='blah'> <source network='dpbr_n_0'/> </interface> This doesn't seem to work; it always ends up creating interface with name as "eth0". I found some examples here:

On Thu, Apr 02, 2015 at 10:25:23AM +0200, Thierry Parmentelat wrote: >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:///

hi guys With lxc container under libvirt control - how can guest create device nodes? I'm specifically looking for FUSE device. Is it possible somehow to get it to the guest(passthrough?) or allow the guest to create dev node? many thanks, L.

Dear Fil, I am not sure if my answer can help you. I had ever asked a similar question to Daniel and I was using a thirty-party card. As a container uses a shared kernel with the host, so hostdev mode='subsystem' doesn't make sense. Maybe you can try to use hostdev mode='capabilities'. Please see http://libvirt.org/formatdomain.html#elementsHostDevCaps Hope this helps Cheng

Thanks Martin. What I would like to achieve is govern the interface name created within the container, so that my application can take different actions on different interfaces (such as eth0, eth1 etc.,). Libvirt's lxc driver seems to create interfaces as eth0, eth1 and so on, when there are multiple <interface /> entries in the domain xml. How can I request for a particular interface

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