similar to: how to boot the lxc container with a default ip

Displaying 20 results from an estimated 10000 matches similar to: "how to boot the lxc container with a default ip"

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
2015 Jul 30
2
libvirt-1.2.17 I can't define lxc container
Hello! I'd like to set up my first lxc container using libvirt. I'd like to start using the simplest configuration and next add things I need. So I've got xml as below: <domain type='lxc'> <name>vm1</name> <memory>32768</memory> <os> <type>exe</type> <init>/init</init> </os>
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
2015 Jul 30
0
Re: libvirt-1.2.17 I can't define lxc container
On Thu, Jul 30, 2015 at 12:49:39PM +0200, Marcin Mirosław wrote: > Hello! > > I'd like to set up my first lxc container using libvirt. I'd like to > start using the simplest configuration and next add things I need. So > I've got xml as below: > <domain type='lxc'> > <name>vm1</name> > <memory>32768</memory> >
2013 Feb 08
1
libvirt v1.0.2 fails to boot LXC container, but v1.0.0 works
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.
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
2010 Mar 11
1
LXC: unable to configure networking for LXC
Hello, I would like to set up sshd under an LXC application container and to be able to connect into it from the host. I was able to achieve that with LXC tools CLI after setting up a bridge via brctl and creating a proper lxc.conf file for lxc-execute to use. However, I am unable to do so via libvirt. I am using libvirt version 0.7.1 installed on fedora 12. I first verified that the default
2013 Feb 27
0
questions of libvirt's lxc
Hi all, I am trying to init lxc by libvirt instead of using lxc tools. I have several questions as following: software platform: integrating libvirt-0.10.1 to yocto based on sdk1.3 hardwatre platform: p4080ds steps: root at p4080ds:~# cat > container.xml <<EOF <domain type='lxc'> <name>container</name>
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>
2013 May 14
1
Unable to start LXC on Gentoo w/ libvirt 1.0.4 or 1.0.5. 1.0.3 works
Hello. I use libvirtd on my Gentoo development system to manage both QEMU and LXC. When 1.0.3 came out, I updated to it from 1.0.3-r2, but 1.0.4 failed to start my LXC containers. I did not research the issue at the time, so I revert to 1.0.3-r2. Today I updated to 1.0.5 and my LXC containers still fail to start. I have not changed my domain XML at all. I am looking for suggestions on
2010 Oct 04
2
LXC
hi All, I'm new to this list and also not a professional libvirt user:) I'm trying to use it for running a container. This is my config: <domain type='lxc'> <name>test</name> <uuid>d3667da2-061a-7b20-a29c-3afc798a257e</uuid> <memory>500000</memory> <currentMemory>500000</currentMemory> <vcpu>1</vcpu> <os>
2013 Jul 31
0
Re: start lxc container on fedora 19
On Wed, Jul 31, 2013 at 12:46:58PM +0530, Aarti Sawant wrote: > 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>
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
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>
2012 Oct 24
0
Failed to query file context on : No data available
Hi:I downloaded a cirros-0.3.0-x86_64-rootfs.img and mount it to /tmp/bak then I edit a xml file ,here is the content: <domain type='lxc'> <name>vm1</name> <memory>500000</memory> <os> <type>exe</type> <init>/bin/sh</init> </os> <vcpu>1</vcpu> <clock offset='utc'/>
2012 Jul 04
1
Problem halting/restaring a lxc container from within
Hi, I've been making some tests with libvirt and LXC and found some problems when halting/restarting a LXC container from within. Basically, on a Ubuntu 12.04 system with libvirt installed as package (0.9.8), I've created a basic container image with: lxc-create -t ubuntu -n lxc And started it using the libvirt XML listed below and the following command: virsh -c lxc:// create
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
2014 Apr 15
0
Re: LXC + USB passthrough = Operation not permitted
On Fri, Apr 11, 2014 at 05:32:28PM -0700, Filip Maj wrote: > Hi! > > First post, kind of a noobie. I've been working with LXC and libvirt for a > few months now. Trying to do some interesting things with containers and > Android devices :D > Here's my entire domain definition: > > <domain type='lxc'> > <name>oshi32134</name> >
2014 Sep 16
2
1.2.7 and 1.2.8 fail to start container: libvirt_lxc[4904]: segfault at 0 ip ...error 4 in libc-2.17.so[
HI all Centos 7, 3.10.0-123.6.3.el7.x86_64 libvirt 1.27, libvirt 1.2.8 builded from source with ./configure --prefix=/usr make && make install LXC with direct network failed to start: Sep 16 19:19:38 node01 kernel: device br502 entered promiscuous mode Sep 16 19:19:39 node01 kernel: device br502 left promiscuous mode Sep 16 19:19:39 node01 avahi-daemon[1532]: Withdrawing workstation
2012 May 14
0
libvirt, lxc, "/dev/log" ENOENT
Hello. I am experimenting with LXC via libvirt on my Gentoo development system. I can start the LXC domain and connect to its console. However, I am unable to login as root. I've used "chroot" and "passwd" from the host system to explicitly set the root password. Still no luck. So I began debugging.... I ran "strace" on the container's