similar to: LXC + passthrough mount and host filesystem-cache

Hello, I'm seeing syslog messages "bleed" from the host and other LXC into the messages, maillog, secure logs of other LXCs. I'm using libvirt 1.0.0 on a host with systemd and kernel 3.9.10. Each LXC is running an older non-systemd linux distribution Is this a known issue? Is there a work around? Thank you for you time, Jim -- James R. Leu | Director of Technology | INOC

On Wed, Mar 26, 2014 at 02:52:58PM -0500, James R. Leu wrote: > Hello, > > I'm using libvirt to build/run LXC instances. My LXC instances use > passthrough filesystem mounts. When I try to do large file systems > operations (ex tar or rsync) the file systems cache on the host > spikes and causes the OOM handler to run and kills processes > in the LXC. So it is

http://bugzilla.mindrot.org/show_bug.cgi?id=1215 Jesse Zbikowski <embeddedlinuxguy at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |embeddedlinuxguy at gmail.com --- Comment #7 from Jesse Zbikowski <embeddedlinuxguy at

Dear Fil, I am not sure if my answer can help you. I had ever asked a similar question to Daniel and I was using a thirty-party card. As a container uses a shared kernel with the host, so hostdev mode='subsystem' doesn't make sense. Maybe you can try to use hostdev mode='capabilities'. Please see http://libvirt.org/formatdomain.html#elementsHostDevCaps Hope this helps Cheng

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

I'd also like to point out that, when setting up a linux container with _just_ the lxc tools available in ubuntu, all that was needed to be done was whitelist the appropriate cgroups for the Android devices. The lxc tools seem to create the appropriate character devices when you detach/attach the Android device via USB, and the Android `adb` tool recognized the devices. So, a tangential

We would like to mount /dev and /dev/pts correctly using the libvirt xml config file instead of doing a bind mount in a container init script we use. Currently the container config is: <domain type='lxc'> <name>CentOS_57</name> <uuid>ff5d3c04-49e6-a3cc-0a14-ff13625eca3c</uuid> <memory>262144</memory>

Can you see the USB device in the lxc? My answering assumes you cannot see the USB device in the container. If you can see it, please ignore my answer. According to my understanding, “hostdev mode='subsystem' “ is used with KVM only. We use this if we want to passthrough a device to a KVM virtual machine. After doing that, the host machine will lose control of the device. If container is

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

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

I've implemented a patch to openssh which allows the PAM auth layer to detect if the PAM stack has changed the user name and then adjusts its internal data structures accordingly. (imagine a PAM stack that uses individual credentials to authenticate, but assigns the user to a role account). First, is the openssh community interested in this patch? Second, if there is interest in the patch,

Hi, i use an BN4S0 with misdn an asterisk on Linux 2.6.9. The hfcmulti module is loaded with option: type=0x04 protocol=0x2,0x2,0x22,0x2 layermask=0xf,0xf,0xf,0xf and the fourth port is connected to an ISDN PTMP (MSN) port. Call to #72 from S0 (BN port 4) are not accepted from asterisk but why ? Can anyone give me a hint ?? misdn debug messages follows: lib: NEW_CR Ind with l3id:80001

Hi everyone, I've some doubts regarding the usage/working of libvirt-lxc with openstack. I'm doing a project titled "Low density virtualization for Storage cloud" 1. Can i use libvirt for lxc with Openstack swift alone (excluding nova, glance and keystone)? If no what other openstack components should i use for virtualization? (Is it necessary to install openstack nova to do

On Wed, Jul 02, 2014 at 12:56:18AM +0200, Thierry Parmentelat wrote: > Hi again > > Answering my own e-mail on a few points: > > . first off, stupid me, http://libvirt.org/format.html indeed is empty and it seems to be by design, but the subtrees are not, like e.g. > http://libvirt.org/formatdomain.html > > . from this page it seems like using something like >

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

Hi folks I have a question about lxc-enter-namespace I am migrating lxc containers from a host running libvirt-1.2.5 on f20 to another one running libvirt-1.2.9 on f21 and now I can't seem to use lxc-enter-namespace for entering in a container any more I would do virsh -c lxc:/// lxc-enter-namespace --noseclabel container /bin/bash but when I try the same now I am getting this: # virsh

Hi experts, When I hotplug nic into lxc, the nic in lxc seemed to be down status as following: 1224: vnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether fa:16:3e:fc:e5:96 brd ff:ff:ff:ff:ff:ff It seems mechanism such as udev is needed here. But I found udev is not supported well in lxc. So how can I get a 'up' nic after hotplug into lxc ? Very

Dear all, I'm a happy lxc (lxd) user with a need to add a bunch of KVM images to the mix. More importantly I need to have some simple frontend to give users the ability to quickly run some VMs for testing. Researching the topic brought me to virt-manager and from there libvirt. I've had however a hard time to answer a few questions that I hope this list can help me with: 1) is the

Hello, I would like to set up sshd under an LXC application container and to be able to connect into it from the host. I was able to achieve that with LXC tools CLI after setting up a bridge via brctl and creating a proper lxc.conf file for lxc-execute to use. However, I am unable to do so via libvirt. I am using libvirt version 0.7.1 installed on fedora 12. I first verified that the default