similar to: Libvirt with containers

Displaying 20 results from an estimated 4000 matches similar to: "Libvirt with containers"

2017 Oct 18
2
Can we disable write to /sys/fs/cgroup tree inside container ?
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
2012 Nov 08
3
Failed to access console after launching LXC through libvirt
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
2013 Jul 12
0
Re: libvrtd-1.1.0 crashes when attempting to start some (but not all) LXC containers
The debug log ends with this: 2013-07-12 16:43:31.740+0000: 21365: debug : virCgroupMakeGroup:708 : Make group /machine/dwj-hfax-dev.libvirt-lxc 2013-07-12 16:43:31.740+0000: 21365: debug : virCgroupMakeGroup:729 : Make controller /sys/fs/cgroup/cpu/machine/dwj-hfax-dev.libvirt-lxc/ 2013-07-12 16:43:31.740+0000: 21365: debug : virCgroupMakeGroup:729 : Make controller
2013 Jul 12
2
Re: libvrtd-1.1.0 crashes when attempting to start some (but not all) LXC containers
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 that to my domain. In any event, libvirtd should probably not crash due to the
2017 Sep 21
1
How automatically set group.devices.allow for libvirt-lxc container after start ?
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
2016 Nov 08
0
Re: Sharing network namespace between containers
On Tue, Nov 08, 2016 at 09:01:34AM +0530, Harish Vishwanath wrote: >Hello > >Based on the lxc driver documentation, I am trying to create an xml to >share an existing network namespace with another container. I am running >libvirt 1.2.15. > >Here is the xml: > ><domain type='lxc' xmlns:lxc='http://libvirt.org/schemas/domain/lxc/1.0'> > >
2011 Aug 23
1
Strange libvirt exit status 1 (LXC containers)
Hello, I've encountered the following error, trying to start a domain: error: internal error Child process (PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LIBVIRT_DEBUG=2 LIBVIRT_LOG_OUTPUTS=2:syslog:libvirtd /usr/libexec/libvirt_lxc --name vm_14 --console 18 --handshake 21 --background --veth veth1) status unexpected: exit status 1 I see nothing relevant
2016 Nov 08
1
Re: Sharing network namespace between containers
Thank you. It looks like after I 'ignore', nothing is persisted in xml for the app. Any idea what is the minimum version of libvirt required for this feature? Regards, Harish On Tue, Nov 8, 2016 at 1:36 PM, Martin Kletzander <mkletzan@redhat.com> wrote: > On Tue, Nov 08, 2016 at 09:01:34AM +0530, Harish Vishwanath wrote: > >> Hello >> >> Based on the lxc
2013 Nov 20
1
Failed to access the console after starting the lxc container
Hello, I am starting the system container without "/" directory So that it can share the host /bin /sbin /lib and /lib64 and i have sepeartely mounted /var, /etc and /usr directory for the container Below is xml file <domain type='lxc'> <name>test6</name> <memory>102400</memory> <os> <type>exe</type>
2016 Nov 08
3
Sharing network namespace between containers
Hello Based on the lxc driver documentation, I am trying to create an xml to share an existing network namespace with another container. I am running libvirt 1.2.15. Here is the xml: <domain type='lxc' xmlns:lxc='http://libvirt.org/schemas/domain/lxc/1.0'> <name>nt</name> <uuid>43c00192-e114-4e29-8ce7-4b5487f60a75</uuid> <memory
2013 Sep 10
3
libvirt-1.2.2-r1 (Gentoo) fails to start LXC containers
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
2013 Jul 31
2
start lxc container on fedora 19
hello, i am new to lxc, i have created a lxc container on fedora 19 i created a container rootfs of fedora 19 by using yum --installroot=/containers/test1 --releasever=19 install openssh test1.xml file for container test1 <domain type="lxc"> <name>test1</name> <vcpu placement="static">1</vcpu> <cputune>
2013 Jul 12
2
libvrtd-1.1.0 crashes when attempting to start some (but not all) LXC containers
Hello all, I have two issues: 1) I am unable to start a seemingly correct LXC domain (I cloned it from a working domain). 2) I am able to crash "libvirtd" by attempting to start the cloned domain, but starting the original works just fine. I humbly submit that item #2 is a bug - the "libvirtd" daemon should never crash due to anything the "libvirt" client
2013 Apr 18
1
libvirt 1.0.3 Vs 1.0.4 / cgroup devices
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
2014 Apr 17
1
Re: LXC + USB passthrough = Operation not permitted
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
2012 Mar 06
1
Correctly using libvirt to mount /dev/pts and /dev in an lxc application container
We would like to mount /dev and /dev/pts correctly using the libvirt xml config file instead of doing a bind mount in a container init script we use. Currently the container config is: <domain type='lxc'> <name>CentOS_57</name> <uuid>ff5d3c04-49e6-a3cc-0a14-ff13625eca3c</uuid> <memory>262144</memory>
2014 Sep 15
0
Re: cgroups inside LXC containers losts memory limits after some time
HI all >After unpredictable time passed (1-5 day ?), cgroups inside LXC >magicaly removed. virsh dumpxml config look like this: <domain type='lxc' id='3566'> <name>puppet</name> <uuid>6d49b280-5686-4e3c-b048-1b5d362fb137</uuid> <memory unit='KiB'>8388608</memory> <currentMemory
2015 Apr 11
0
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
2011 Aug 24
0
Bug#639112: xen: DomU access to dual-ported RAM area on PCI card fails
Package: xen-hypervisor-4.0-i386 Version: 4.0.1-2 Severity: normal File: xen -- System Information: Debian Release: 6.0.2 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set
2017 Apr 20
0
Re: understanding --idmap for containers (v2.5.0)
On Thu, Apr 20, 2017 at 08:26:11AM +0000, mailing lists wrote: > Hello, > I'm testing containers on a host machine without selinux so I'm trying use the idmap feature, but I must be missing something because all that I get is a readonly container for the root user. > > # virsh version --daemon > Compiled against library: libvirt 2.5.0 > Using library: libvirt 2.5.0 >