similar to: Question about libvirt / LXC

Hi there, Do you know if there is a way to modify how libvirt interacts with the cgroup? Because, I successfully add the /dev/net/tun support in my LXC container by doing: echo c 10:200 rwm >> /cgroup/libvirt/lxc/instance-00000005/devices.allow But when I restart the instance/LXC container, this option has gone. How can I make this persistant? Is there a configuration file? Thanks

Hi. I need to use /dev/ppp inside the lxc container, for very ancient software. Problem solved this way: 1) virsh edit container name and add section: <features> <capabilities policy='default'> <mknod state='on'/> </capabilities> </features> 2) start container 3) attach or ssh container, be root: #mknod /dev/ppp c 108 0 4) inside

Hi, I'm trying to manage LXC instances through OpenStack, which use libvirt as a virtualization driver layer. After launching LXC instance, I simply could not attach to the console. virsh # list Id Name State ---------------------------------- 14366 instance-00000078 running virsh # console 14366 Connected to domain instance-00000078 Escape character is ^] And it keeps

Hi all Each lxc container on node have mounted tmpfs for cgroups tree: [root-inside-lxc@tst1 ~]# mount | grep cgroups cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on

On Sat, Jul 06, 2013 at 09:59:39PM +0200, Thomas Karcher wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi lxc folks, > > the symptom my libvirt LXC container suffers from is: > > root@depot:/dev/net# ls -la > total 0 > drwxr-xr-x 2 root root 40 Jun 29 16:26 . > drwxr-xr-x 5 root root 480 Jun 29 16:26 .. > > root@depot:/dev/net# mknod tun c

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi lxc folks, the symptom my libvirt LXC container suffers from is: root@depot:/dev/net# ls -la total 0 drwxr-xr-x 2 root root 40 Jun 29 16:26 . drwxr-xr-x 5 root root 480 Jun 29 16:26 .. root@depot:/dev/net# mknod tun c 10 200 mknod: `tun': Operation not permitted The host is an up-to-date AMD64 Ubuntu raring on 3.8.0-25-generic that was

Hi there, I am using libvirt with lxc to create fedora 16 & 18 containers on fedora 18 host. first I did the setup with libvirt 1.0.3 and everything worked fine, then after upgrading to libvirt 1.0.4, I could not create character device on the guests : Test on the guest1 : # ls -l /dev total 0 lrwxrwxrwx. 1 root root 10 Apr 17 21:18 console -> /dev/pts/0 lrwxrwxrwx. 1 root root 11

Hello, I created lxc container on F19 with virt-manager and it starts OK. The only problem is that sshd does not run complaining "/dev/null is not a character device". # ls -l /dev/null -rw-r--r-- 1 root root 0 2014-02-25 22:39 /dev/null /sys/fs/cgroup/devices/machine/VM_NAME.libvirt-lxc/devices.list has "c 1:3 rwm" line, but I cannot create /dev/null: # mknod /dev/nulll c 1

On Tue, Feb 25, 2014 at 08:58:43PM +0000, Nerijus Baliunas wrote: > Hello, > > I created lxc container on F19 with virt-manager and it starts OK. The only > problem is that sshd does not run complaining "/dev/null is not a character > device". > # ls -l /dev/null > -rw-r--r-- 1 root root 0 2014-02-25 22:39 /dev/null > >

Hi, all, I used lxc-tools to create a linux container. I am trying to transfrom LXC container configuration into a domain XML fragment using the following command: *$ virsh -c lxc:/// domxml-from-native lxc /var/lib/lxc/my_conatiner/config* However, I get the error message, error: this function is not supported by the connection driver: virConnectDomainXMLFromNative It seems that

Hello. tl;dr = v1.0.0 can boot my LXC containers, v.1.0.1 and v.1.0.2 fails. Paraphrased error message: "lxcContainerMountProcFuse:616 : Failed to mount ..../meminfo" I'd like to know if my host is misconfigured, or my domains, or ... why 1.0.2 and 1.0.1 are not working for me. I've been using libvirt for a while to manage QEMU instances. I have experimented with lxc.

Hello. Centos 7.6 with libvirt build from base "virt" repository: libvirt-daemon-driver-lxc-5.0.0-1.el7.x86_64 libvirt-client-5.0.0-1.el7.x86_64 libvirt-daemon-5.0.0-1.el7.x86_64 libvirt-daemon-driver-network-5.0.0-1.el7.x86_64 libvirt-libs-5.0.0-1.el7.x86_64 + systemd-219-62.el7_6.2.x86_64 Now lxc containers with type='direct' can be started, but can't be stopped :)

I have a container rootfs that I use to keep all work-related stuff. This container was originally created by lxd (which creates all containers for use with user namespacing), but now I decided to start using libvirt for container management since I already use it for virtual machines, which will spare me from dealing with multiple hypervisor technologies. I managed to create a working domain xml

Hi, I am trying to define a container using libvirt, and I need to allow access of the device /dev/uio0 on the host on the container as well. That is, I have the following line in the container config file: lxc.mount.entry = /dev/uio0 dev/uio0 none bind,create=file lxc.cgroup.devices.allow = c 249:1 rwm And I want to add it in the libvirt XML file for the container. I tried something like:

Me again! Think we've found it. By diving into the LXC logs for the specific container, we found this: 2014-04-17 21:07:06.066+0000: 2861: debug : virCgroupSetValueStr:678 : Set value '/sys/fs/cgroup/devices/machine/oshi32134.libvirt-lxc/devices.allow' to 'c 189:130 rw' Looks like libvirt the permission to 'rw', not 'rmw' [1], so no surprise that when it

Howdy, I am playing around with asterisk within an LXC container on Ubuntu 11.04. I have asterisk (1.4.42) running fine, but want access to dahdi_dummy for timing (meetme). I have dahdi installed on the "host", and dahdi_dummy is loaded: root at astnorth:/# ls -ltr /dev/dahdi total 0 crw-rw---- 1 root root 196, 250 2011-06-08 13:59 transcode crw-rw---- 1 root root 196, 253

Hi, I'm running OpenStack on CentOS 6.3 to manage lxc instances. And running into series of problem relating libvirt and lxc interaction. For example, libvirt_lxc segfault ( https://bugzilla.redhat.com/show_bug.cgi?id=874549) which has an upstream fix. And another bugs such as fail to start when SELinux disabled. Finally, I decides to adopt libvirt 0.10.2, self compiled from

On 03.03.2014 16:26, Daniel P. Berrange wrote: > That looks really bizarre. The same two directory names nested over > and over again. I can't reproduce this kind of thing on my own host. > Libvirt only ever creates the first two levels as expected > > /sys/fs/cgroup/systemd/machine.slice > /sys/fs/cgroup/systemd/machine.slice/machine-lxc\x2dmycontainer.scope > > The

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

I'm trying to permanently change memory allocation for a libvirt-lxc domain. So far I tried changing memory in memory.limit_in_bytes under /cgroup/memory/libvirt/lxc/<container>/.  This didn't help. It appears that libvirt is not reading changes in cgroup. My requirements are 1) Be able to dynamically change memory of a LXC domain without reboot 2) The memory change must survive