Displaying 20 results from an estimated 200000 matches similar to: "Does lxc support cputune/vcpusched option"
2013 Mar 25
1
Failed to boot lxc with libvirt 1.0.3:2013-03-25 06:54:17.620+0000: 1: error : lxcContainerMountBasicFS:563 : Failed to mount /selinux on /selinux type selinuxfs flags=e opts=(null): No such device
hi all, I am using lxc with libvirt. But I can't boot lxc container by libvirt 1.0.3(libvirt 0.9.8 works) . Below is my environment. Do I miss something?
lxc1.xml:<domain type='lxc'> <name>lxc1</name> <memory>1024000</memory> <cputune> <shares>100</shares> </cputune> <os> <type>exe</type>
2016 Mar 31
2
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 themselves as well as with their host, and vice
versa. However, containers hosted in one
2016 Apr 03
0
Re: Networking issues with lxc containers in AWS EC2
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
2016 Apr 01
2
Re: 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 these instances.
>> The containers run fine within a single host and
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>
2013 Jul 31
2
start lxc container on fedora 19
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>
2016 Apr 14
0
Re: 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 Amazon's infrastructure. If you see
> packets from the container's IP going out
2016 Apr 12
2
Re: 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 have a message in dmesg that looks like this:
>
> bridge:
2014 Jan 15
2
Does libvirt lxc driver support "cpuset" attribute?
Dear all
I allocate only one vcpu for the container by the following statement, that is, I want to pin the vcpu to physical core "2".
<vcpu placement='static' cpuset="2" >1</vcpu>
My host has 4 physical cores. Before test, all the 4 cores are idle. After I run 4 processes in the container, I found all the 4 cores in the host are 100% used. That is, the
2014 Jan 15
0
Re: Does libvirt lxc driver support "cpuset" attribute?
On Wed, Jan 15, 2014 at 05:49:23AM +0000, WANG Cheng D wrote:
> Dear all
>
> I allocate only one vcpu for the container by the following
> statement, that is, I want to pin the vcpu to physical core "2".
> <vcpu placement='static' cpuset="2" >1</vcpu>
> My host has 4 physical cores. Before test, all the 4 cores are
> idle. After I run 4
2016 Apr 01
0
Re: Networking issues with lxc containers in AWS EC2
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
2014 Aug 27
0
Cputune causing VM to show usage as hardware interrupts
Hey All,
What is the correct method for using cputune to use a percentage of a host
core? From testing I currently have period set to 10,000 and quota set to
3,500. This gets me 35% of a used core on the host (36 3.4 2:42.20
qemu-system-x86) however when running stress inside the VM I am showing
this usage in top;w
%Cpu(s): 0.0 us, 0.0 sy, 0.0 ni, 0.0 id, 0.0 wa, 35.2 hi, 0.0 si,
64.8
2013 Dec 03
0
cputune shares with multiple cpu and pinning
Hi,
I have found the cpu time partitioning based on cpu shares weights not
very intuitive.
On RHEL64, I deployed two qemu/kvm VMs
VM1 with 1 vcpu and 512 cpu shares
VM2 with 2 vcpus and 1024 cpu shares
I pinned their vcpus to specific host pcpus:
VM1 vcpu 0 to host pcpu1
VM2 vcpu 0 to host pcpu1, VM2 vcpu 1 to host pcpu2
I executed inside the VMs a simple process that consume all
2019 Sep 15
3
virsh -c lxc:/// setvcpus and <vcpu> configuration fails
Hi folks!
i created a server with this XML file:
<domain type='lxc'>
<name>lxctest1</name>
<uuid>227bd347-dd1d-4bfd-81e1-01052e91ffe2</uuid>
<metadata>
<libosinfo:libosinfo
xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
<libosinfo:os id="http://centos.org/centos/6.9"/>
2019 Sep 16
0
Re: virsh -c lxc:/// setvcpus and <vcpu> configuration fails
On Sun, Sep 15, 2019 at 12:21:08PM +0200, info@layer7.net wrote:
>Hi folks!
>
>i created a server with this XML file:
>
><domain type='lxc'>
> <name>lxctest1</name>
> <uuid>227bd347-dd1d-4bfd-81e1-01052e91ffe2</uuid>
> <metadata>
> <libosinfo:libosinfo
2015 Aug 04
1
Does CTDB run under LXC containers?
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
2016 Apr 11
0
Re: Networking issues with lxc containers in AWS EC2
On 04/07/2016 09:50 AM, Peter Steele wrote:
> 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 not, perhaps the
2015 Aug 04
3
Does CTDB run under LXC containers?
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
2011 Feb 12
2
LXC libvirt support
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
2015 Aug 04
3
Does CTDB run under LXC containers?
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:
> >
>