similar to: Communicating between libvirt contains on separate hosts

On 04/01/2016 07:04 PM, Peter Steele wrote: > On 04/01/2016 02:07 PM, Laine Stump wrote: >> On 03/31/2016 06:43 PM, Peter Steele wrote: >>> I've created an EC2 AMI for AWS that essentially represents a CentOS >>> 7 "hypervisor" image. I deploy instances of these in AWS and create >>> an number of libvirt based lxc containers on each of these

On 04/01/2016 02:07 PM, Laine Stump wrote: > On 03/31/2016 06:43 PM, Peter Steele wrote: >> I've created an EC2 AMI for AWS that essentially represents a CentOS >> 7 "hypervisor" image. I deploy instances of these in AWS and create >> an number of libvirt based lxc containers on each of these instances. >> The containers run fine within a single host and

I've created an EC2 AMI for AWS that essentially represents a CentOS 7 "hypervisor" image. I deploy instances of these in AWS and create an number of libvirt based lxc containers on each of these instances. The containers run fine within a single host and have no problem communicating with themselves as well as with their host, and vice versa. However, containers hosted in one

On 03/31/2016 06:43 PM, Peter Steele wrote: > I've created an EC2 AMI for AWS that essentially represents a CentOS 7 > "hypervisor" image. I deploy instances of these in AWS and create an > number of libvirt based lxc containers on each of these instances. The > containers run fine within a single host and have no problem > communicating with themselves as well as

I'm using libvirt_lxc and that has an XML based configuration. Based on what I've read, I think I need to add this to the ctdb container's config: <features> <capabilities policy='default'> <sys_nice state='on'/> </capabilities> </features> That didn't do the trick though. I need to figure out how to turn on all caps to

I have hit a problem running libvirt based containers in a CentOS 7 based host, with the extra wrinkle that my host is an EC2 instance in AWS. Ultimately everything works as advertised, and I can launch instances that host multiple libvirt lxc containers without problems, with one caveat: About one time in ten when the containers are started, the instance loses all network connectivity. This

Hi, I am trying to run containers on rhel 6.2 using libvirt-lxc. I want to migrate my containers from sf.net lxc to libvirt-lxc. So, I am using the same root file system for libvirt-lxc, which I used for sf.netlxc. After starting the container, and getting console for it, I can see the boot log for the container, it shows all the services started successfully. I get ping reply from the IP assigned

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. > > ostara ~ # tail /var/log/libvirt/lxc/dwj-hfax-dev.log > 2013-09-10

Now reporduced with 100% 1) create contrainer with memory limit 1Gb 2) run inside simple memory test allocator: #include <malloc.h> #include <unistd.h> #include <memory.h> #define MB 1024 * 1024 int main() { int total = 0; while (1) { void *p = malloc( 100*MB ); memset(p,0, 100*MB ); total = total + 100; printf("Alloc %d Mb\n",total); sleep(1);

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

[Dropping libvirt-announce list] On 05.08.2014 11:47, Himanshu Sharma wrote: > Dear Team, > Greetings!! > > I'm testing libvirt with VMware ESXi. I'm able to connect to VMware ESXi with libvirt driver but not able to connect it through "Virtual Machine manager" GUI also not able to run virt-clone command inturn to clone ESXi VM. Can you please guide me how to do so?

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

On 2015-08-04 at 19:27 +0200, Ralph Böhme wrote: > Hi Peter, > > On Tue, Aug 04, 2015 at 10:11:56AM -0700, Peter Steele wrote: > > We're transitioning from a VM based environment to one that uses LXC based > > containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. > > The same packages running under LXC however seem to have issues: > > >

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.

Hi Peter, On Tue, Aug 04, 2015 at 10:11:56AM -0700, Peter Steele wrote: > We're transitioning from a VM based environment to one that uses LXC based > containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. > The same packages running under LXC however seem to have issues: > > # systemctl start ctdb.service > Job for ctdb.service failed. See 'systemctl

We're transitioning from a VM based environment to one that uses LXC based containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. The same packages running under LXC however seem to have issues: # systemctl start ctdb.service Job for ctdb.service failed. See 'systemctl status ctdb.service' and 'journalctl -xn' for details. # systemctl status ctdb.service

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

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

On Mon, Aug 10, 2015 at 09:50:04PM +0100, Mark Clarkson wrote: > Hi, > I noticed that libvirt-lxc will be deprecated for RedHat: > > "Future development on the Linux containers framework is now based on the > docker command-line interface. libvirt-lxc tooling may be removed in a > future release of Red Hat Enterprise Linux (including Red Hat Enterprise > Linux 7) and

On Mon, Aug 10, 2015 at 09:50:04PM +0100, Mark Clarkson wrote: >Hi, >I noticed that libvirt-lxc will be deprecated for RedHat: > >"Future development on the Linux containers framework is now based on >the docker command-line interface. libvirt-lxc tooling may be removed >in a future release of Red Hat Enterprise Linux (including Red Hat >Enterprise Linux 7) and should not