Re: [libvirt-users] Does lxc support cputune/vcpusched option

I should add that I am running under CentOS 7.3 with kernel version 3.10.0-514.6.2. On 04/27/2017 01:40 PM, Peter Steele wrote: I need a container that supports real time threads. According to the documentation, I can do something like this: test1 e7446f55-3d59-4af0-90b2-d1498ac4370d

[libvirt-users] Does lxc support cputune/vcpusched option

I need a container that supports real time threads. According to the documentation, I can do something like this: test1 e7446f55-3d59-4af0-90b2-d1498ac4370d ... 2 ... The document describes the vcpusched element as follows: The optional |vcpusched| elements specifies the sch

Re: [libvirt-users] Real time threads don't work in libvirt containers under CentOS 7.3

On 02/06/2017 09:47 AM, Daniel P. Berrange wrote: On Mon, Feb 06, 2017 at 09:32:29AM -0800, Peter Steele wrote: We've been using libvirt based containers under CentOS 7 and everything has been working fine. One application we run in our containers is ctdb, which uses SCHED_FIFO (real

[libvirt-users] Real time threads don't work in libvirt containers under CentOS 7.3

We've been using libvirt based containers under CentOS 7 and everything has been working fine. One application we run in our containers is ctdb, which uses SCHED_FIFO (real time) threads. This has been working without problems until our recent upgrade to CentOS 7.3. For some reason, ctdb is no

[libvirt-users] Communicating between libvirt contains on separate hosts

I have a group of CentOS 7.2 servers running as VMs under VMware's ESXi 6.0. These all reside on the same subnet and we have no problem communicating between the different virtual servers. In addition, each of these servers run a number of libvirt-based LXC containers, also based on CentOS 7.2.

[libvirt-users] How do you set real time bandwidth for a container?

When I create a VM using libvirt, the VM comes up the path /sys/fs/cgroup/cpu/cpu.rt_runtime_us set to something like 100. When I create a container however, the path /sys/fs/cgroup/cpu/cpu.rt_runtime_us is 0. This prevents my containers from being able to run any real time applications. I

[libvirt-users] Sharing a host directory with a Windows guest

I'm running libvirt un a CentOS 7.2 host and have created a Windows 10 VM under that. I've been researching how to share a folder on my host with the Windows guest VM but can't figure out if it's possible. I've added the code function='0x0'/> to the xml d

Re: [libvirt-users] Host loses network connectivity when starting containers

. Without this entry, the bridge's mac address changes whenever a container is started to match that of the container just started. This can cause a flood of arps and that was causing issues for the AWS networking infrastructure. Peter On 06/03/2016 09:56 PM, Peter Steele wrote: I have

[libvirt-users] Host loses network connectivity when starting containers

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

Re: [libvirt-users] Networking issues with lxc containers in AWS EC2

On 04/14/2016 03:35 PM, Peter Steele wrote: On 04/12/2016 01:37 PM, Peter Steele wrote: On 04/11/2016 11:33 AM, Laine Stump wrote: I wouldn't be too quick to judgement. First take a look at tcpdump on the bridge interface that the containers are attached to, and on the ethernet device

Re: [libvirt-users] Mapping physical interface to a container

I on the right track with this? Peter On 04/21/2016 06:33 AM, Peter Steele wrote: In the "other" LXC project (linuxcontainers.org), you can map a host's physical ethernet interface to a container, e.g. lxc.network.type = phys lxc.network.flags = up lxc.network.link = eth1 lxc.net

[libvirt-users] Mapping physical interface to a container

In the "other" LXC project (linuxcontainers.org), you can map a host's physical ethernet interface to a container, e.g. lxc.network.type = phys lxc.network.flags = up lxc.network.link = eth1 lxc.network.name = eth1 Is there an equivalent option for doing this with libvirt lxc? Peter

Re: [libvirt-users] Networking issues with lxc containers in AWS EC2

On 04/12/2016 01:37 PM, Peter Steele wrote: On 04/11/2016 11:33 AM, Laine Stump wrote: I wouldn't be too quick to judgement. First take a look at tcpdump on the bridge interface that the containers are attached to, and on the ethernet device that connects the bridge to the rest of Ama

Re: [libvirt-users] Networking issues with lxc containers in AWS EC2

On 04/11/2016 11:33 AM, Laine Stump wrote: Interesting. That functionality was moved out of the kernel's bridge module into br_netfilter some time back, but that was done later than the kernel 3.10 that is used by CentOS 7. Are you running some later kernel version? If your kernel doesn't hav

Re: [libvirt-users] Networking issues with lxc containers in AWS EC2

On 04/02/2016 05:20 PM, Laine Stump wrote: You say they can talk among containers on the same host, and with their own host (I guess you mean the virtual machine that is hosting the containers), but not to containers on another host. Can the containers communicate outside of the host at all? If n

Re: [libvirt-users] Networking issues with lxc containers in AWS EC2

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

[libvirt-users] Networking issues with lxc containers in AWS EC2

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 them

Re: [libvirt-users] /proc/meminfo

On 03/25/2016 03:17 AM, mxs kolo wrote: I found a download for this version and tried it out but we ran into a different set of problems when running our software in containers under this environment. What kind problem ? Network ? That's a good question and I don't have a good short answer. We

Re: [libvirt-users] /proc/meminfo

On 03/24/2016 05:48 AM, Peter Steele wrote: On 03/24/2016 02:26 AM, mxs kolo wrote: use libvirt 1.3.2, it's more stable and never show negative values for memory and swap inside container The latest version available for CentOS/RHEL is version 1.2.17. What site are you using to get th

Re: [libvirt-users] /proc/meminfo

On 03/24/2016 02:26 AM, mxs kolo wrote: use libvirt 1.3.2, it's more stable and never show negative values for memory and swap inside container The latest version available for CentOS/RHEL is version 1.2.17. What site are you using to get the rpm for version 1.3.2? Peter

Re: [libvirt-users] /proc/meminfo

On 03/23/2016 11:26 AM, Cole Robinson wrote: Even if you don't reproduce on RHEL/Fedora, it would be useful if you figure out exactly what steps it takes to reproduce: is it random, or after a set amount of time, or after machine suspends, or some manual way to tickle the issue. Thanks, Cole I

Re: [libvirt-users] /proc/meminfo

On 03/23/2016 09:19 AM, Cole Robinson wrote: On 03/23/2016 12:10 PM, Peter Steele wrote: Has anyone seen this issue? We're running containers under CentOS 7.2 and some of these containers are reporting incorrect memory allocation in /proc/meminfo. The output below comes from a system wit

[libvirt-users] /proc/meminfo

Has anyone seen this issue? We're running containers under CentOS 7.2 and some of these containers are reporting incorrect memory allocation in /proc/meminfo. The output below comes from a system with 32G of memory and 84GB of swap. The values reported are completely wrong. # cat /proc/meminfo

Re: [libvirt-users] Zombie processes being created when console buffer is full

On 03/10/2016 12:34 AM, Martin Kletzander wrote: I'm not able to reproduce your issue, but that might be because I'm not running systemd neither in the container nor in the host. If we can reproduce it without systemd, though, that would be very helpful for finding out the cause of all this. W

[libvirt-users] How to test if a console session is active?

I use libvirt to manage a container based environment. Is there an efficient method for testing if someone has a console session open for a given container? The approach I'm using at the moment is to use lsof and check if there is an entry for the container's console pts device. For example, I

Re: [libvirt-users] removing virbr0

I do something similar, generating a custom image that gets installed on multiple systems. I just have a startup script in my image that runs "virsh net-undefine default" during boot-up. If you are creating your own image, you should be able to insert something similar in your start-up process.

Re: [libvirt-users] Libvirt-lxc packages deprecation

I'd like to hear the latest on this as well. We're considering moving to the "other" LXC framework if libvirt LXC truly is being dropped in RHEL. On 02/23/2016 11:41 AM, syed muhammad wrote: Folks, I foundthis thread tha

[libvirt-users] Virtual ethernet delivers corrupt tcpip data

We came across this article recently. Does anyone know if libvirt-lxc under CentOS 7 is impacted by this bug? It mentions that a fix for this has been ported back as far as 3.14 kernels, but CentOS 7.1 is still only at 3.10. http://linux.slashdot.org/story/16/02/22/1715202/linux-virtual-ethern

Re: [libvirt-users] Both virsh console logging and pty usage

I wrote a piece of code recently that monitors the consoles of the VMs and while no one is attached to the console, it throws away the buffer as any text appears. If someone *is* attached, it leaves it alone. It wouldn't be hard to modify the code to save the console text to a file instead of t

Re: [libvirt-users] Zombie processes being created when console buffer is full

On 01/29/2016 05:08 AM, Peter Steele wrote: We have been researching stuck zombie processes in our libvirt lxc containers. What we found was: 1) Each zombie’s parent was pid 1. init which symlinks to systemd. 2) In some cases, the zombies were launched by systemd, in others the zombie was

[libvirt-users] Zombie processes being created when console buffer is full

We have been researching stuck zombie processes in our libvirt lxc containers. What we found was: 1) Each zombie’s parent was pid 1. init which symlinks to systemd. 2) In some cases, the zombies were launched by systemd, in others the zombie was inherited. 3) While the child is in the zombie

[libvirt-users] Zombie processes being created when console buffer is full

We have been researching stuck zombie processes in our libvirt lxc containers. What we found was: 1) Each zombie’s parent was pid 1. init which symlinks to systemd. 2) In some cases, the zombies were launched by systemd, in others the zombie was inherited. 3) While the child is in the zombie

Re: [libvirt-users] Enabling capabilities in a container

There's no out there who can comment on this? Surely there must be a way to solve this problem for libvirt lxc based containers. Peter On 08/04/2015 03:44 PM, Peter Steele wrote: I'm using libvirt_lxc to create and manage various containers. I need to enable certain capabil

[libvirt-users] Enabling capabilities in a container

I'm using libvirt_lxc to create and manage various containers. I need to enable certain capabilities in a container to support ctdb, and as a quick solution I decided to just enable them all. I *thought* this would do the trick, adding the following XML to my container config: After a