similar to: Reg: shutdown/restart from within the container(system LXC)

Hi, What is the difference between chroot & pivot_root. They don't seem obvious based on the man pages apart from the below mentioned caveats. 1) Inherited Open file descriptors, have to be explicitly closed. 2) Does not change CWD of the process, which can be overcome by doing a chdir before & after chroot call. Any information on this would be useful. Thanks,

Hi All, I am facing the following issue, while using Libvirt version 0.8.4. (1) Libvirt API does not return, since the qemu-kvm process is hung up. Based on the information available on mail thread *https://bugzilla.redhat.com/show_bug.cgi?id=676205* (comment 26 - scenario 1), this has been fixed in later version of Libvirt, specifically in RHEL 6.2(libvirt 0.9.4). I have checked the

Hi , Is there anyway to get uuid info inside a lxc container which is created by libvirt_lxc? For kvm, we can use dmidecode or lshw to get this info inside vm. Is there any tools to do this thing for libvirt lxc? Thanks for any help~ -- ------------ Jackie Best Regards

于 2014年07月08日 12:06, Eric Blake 写道: > On 07/07/2014 10:02 PM, Qiang Guan wrote: >> Hi , >> >> Is there anyway to get uuid info inside a lxc container which is created >> by libvirt_lxc? >> >> For kvm, we can use dmidecode or lshw to get this info inside vm. Is >> there any tools >> to do this thing for libvirt lxc? > Per the docs: >

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

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 :)

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>

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>

Hi Team I'm trying to launch LXC VM with libvirt 1.2.12 having commit *22cff52a2b8e06c913b1f97767e5d3**90fb17fc3b *with below XML configuration.. <domain type="lxc"> <uuid>64c48da2-e318-4085-8b88-c980aab4de34</uuid> <name>test</name> <memory>524288</memory> <vcpu>1</vcpu> <os> <type

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>

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

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

Thanks Cole. I need to use network type="ethernet" with LXC instead of Qemu. I have reopened my bug. On Mon, Apr 11, 2016 at 8:25 PM, Cole Robinson <crobinso@redhat.com> wrote: > On 04/11/2016 09:24 AM, abhishek jain wrote: > > Hi Team > > > > I'm trying to launch LXC VM with libvirt 1.2.12 having commit > >

At Tue, 08 Jul 2014 12:19:40 +0800, Qiang Guan wrote: > > > 于 2014年07月08日 12:06, Eric Blake 写道: > > On 07/07/2014 10:02 PM, Qiang Guan wrote: > >> Hi , > >> > >> Is there anyway to get uuid info inside a lxc container which is created > >> by libvirt_lxc? > >> > >> For kvm, we can use dmidecode or lshw to get this info inside

On 07/07/2014 10:02 PM, Qiang Guan wrote: > Hi , > > Is there anyway to get uuid info inside a lxc container which is created > by libvirt_lxc? > > For kvm, we can use dmidecode or lshw to get this info inside vm. Is > there any tools > to do this thing for libvirt lxc? Per the docs: http://libvirt.org/drvlxc.html#envvars pid 1 inside lxc inherits $container_uuid into

> > NB user namespaces are a fairly new piece of functionality that > is still somewhat rough around the edges. You usuaully want to > have the most recent kernel.org stable kernel available when > using this. > Yes, I confirm it is a little bit touchy for me. gabx@hortensia ➤➤ ~ % uname -a Linux hortensia 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64

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 Mon, Mar 03, 2014 at 03:52:01PM +0100, Dariusz Michaluk wrote: > Hi. > > Another week, another experiment ;) I was trying to run systemd user > session for non-root user, for example darek (uid=1000), operation > failed with error: > > systemd[26]: pam_unix(systemd-user:session): session opened for user > darek by (uid=0) > systemd[1]: Started Login Service. >

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

Hi All, I am trying to start a lxc container using libvirt and I am facing an issue due to pivot_root. The return code from the system call ?pivot_root? is EINVAL (Invalid arguments). I isolated the issue to this specific condition check within the system call. This is an code snippet from fs/namespace.c::pivot_root * error = -EINVAL; if (root.mnt->mnt_root != root.dentry)