similar to: error: internal error lxc state driver is not active

Thanks for your response, I found that the server's kernel has been changed so I installed the official kernel by yum. but there still question: /usr/bin/virsh -c lxc:/// start instance-00000011 error: Failed to start domain instance-00000011 error: internal error Child process (PATH=/sbin:/usr/sbin:/bin:/usr/bin LIBVIRT_DEBUG=3 LIBVIRT_LOG_OUTPUTS=3:stderr /usr/libexec/libvirt_lxc --name

Hi, Has anyone used libvirt to start/stop/manage LXC (linux containers) ? Is it supported at all? Last I tried, had few issues and the reply was : /// Note that libvirt lxc driver is a different implementation from lxc tools and doesn't use lxc tools internally. You may not be able to do what you are doing with lxc tools. Especially, the driver doesn't take aware of files and settings

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

Hi, I'm running OpenStack to manage LXC instance through libvirt. The same setting runs perfectly well on Ubuntu 12.04, while on CentOS 6u3, libvirt dumped following message when starting lxc instance. virsh -c lxc:/// start instance-00000032 error: internal error The 'cpuacct', 'devices' & 'memory' cgroups controllers must be mounted Really appreciated if

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

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

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 I'm running ubuntu 13.10 with LXC 1.0.1 and tried both libvirt 1.1.1 and 1.2.2 (backported from ubuntu-trusty), but with either version of libvirt am getting issues as soon as I try to get access to USB devices inside

Yeah, AppArmor is enabled, but I put everything (that I could find) into complain mode: $ sudo apparmor_status apparmor module is loaded. 12 profiles are loaded. 3 profiles are in enforce mode. lxc-container-default lxc-container-default-with-mounting lxc-container-default-with-nesting 9 profiles are in complain mode. /sbin/dhclient /usr/bin/lxc-start

(oops accidentally sent to -owners) Hi, i'm trying to start a LXC guest on a F14 computer .. followed the examples in http://libvirt.org/drvlxc.html, but got stuck when starting it .. 03:07:23.706: debug : virCgroupNew:542 : New group / 03:07:23.707: debug : lxcControllerRun:563 : Setting up private /dev/pts 03:07:23.711: debug : lxcControllerRun:589 : Mouting 'devpts' on

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

Hallo everyone, in March 2010 there was a discussion[1] about live migration of LXC Containers using libvirt. I was just wondering if there are any updates to this? regards, Dan Luedtke [1] http://www.mail-archive.com/lxc-users at lists.sourceforge.net/msg00198.html -- https://www.danrl.de/ GPG Key ID: 0xF8504F3E

Further followups! We are correlating DEBUG-level output from libvirt with the libvirt 1.2.2 code to try to figure out what libvirt is doing under the hood. Even though we have the log level set to 1 (info) in our libvirtd.conf, we are not seeing the VIR_DEBUG() [1] statements being printed out. There are tons of other presumably-debug lines of output showing up in our log. We are sort of

libvirt-0.9.6-2.fc15.x86_64 virt-manager-0.9.0-7.fc15.noarch I'm trying to use virt-manager create a simple lxc app container just to see how it works. App is /bin/sh, 128 megs, 1 cpu. All seems to go well, but when I click "Finish" and the "Creating Virtual Machine" box comes up, "Creating Domain..." stays at 0B though the slider keeps going back and forth.

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

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

How can I run command in containers on the host? Just like the lxc command lxc-attach. I run : virsh -c lxc:/// lxc-enter-namespace fedora2 --noseclabel /bin/ls but get error: libvirt: error : Expected at least one file descriptor error: internal error: Child process (14930) unexpected exit status 125 Here is my libvirt.xml <domain type='lxc'> <name>fedora2</name>

Hi, I'm not able to create lxc domains anymore with libvirt 1.2.0-1. The current arch linux package is affected by this bug: https://bugs.archlinux.org/task/38007). vm.xml: <domain type="lxc"> <name>test</name> <memory unit="GiB">2</memory> <os> <type>exe</type> <init>/sbin/init</init> </os>

So I've followed this tutorial on a vanilla CentOS 6.5 (x64) hardware install ... http://wiki.centos.org/HowTos/LXC-on-CentOS6 (barring the name and location of the container) I'm getting the following error when trying to intialise the container ... # virt-install --connect lxc:/// --name dns --ram 512 --vcpu 1 --filesystem /srv/lxc/dns,/ --noautoconsole ERROR internal error lxc

Hey guys, When I destroy a lxc container, It reported an error with details as following: root@debian:~$ vir destroy 901eef81-06b2-4252-aeef-53b87c402585 error: Failed to destroy domain 901eef81-06b2-4252-aeef-53b87c402585 error: internal error Some container PIDs refused to die root@debian:~$ vir version Compiled against library: libvirt 1.1.0 Using library: libvirt 1.1.0 Using API: LXC

Hello! Okay i tried again with only staticly linked busybox: offlinehacker:~/ $ /home/offlinehacker/busybox/busybox BusyBox v1.17.1 (Debian 1:1.17.1-8) multi-call binary. Copyright (C) 1998-2009 Erik Andersen, Rob Landley, Denys Vlasenko and others. Licensed under GPLv2. See source distribution for full notice. .... Again my id: uid=499(offlinehacker) gid=100(users)