Hi Junjiro, Hello Florian,
Florian Klink: I also got this problem on a Kernel without CONFIG_USER_NS (3.10.9-1-zen), so it's _not_ user namespace related. As far as I know, aufs doesn't put itself readonly. Currently I guess someone else did. For example, - mount -o remount,ro /your/aufs - brsync(8) in aufs-util.git I think, it gets remounted read-only by the "read-only remount" that happens inside the container during shutdown (by the init system there). Seems the only possible reason for it, as I don't use brsync. I can also "mount -o remount,rw /my/aufs". Create the lxc container inside libvirt (easy to do with virt-manager) Start the container Power off the container Would you explain more specifically? I don't know much about zen, libvirt, virt-manager and lxc. If it is reproducible on Debian wheezy (v7), I will easily do that. Yes, my test environment is debian. But I can install other distro on my machine. It just takes a little bit longer time. What is your distro and packages? I use Arch Linux (amd64) using the "zen-kernel" (tree on zen-kernel.org, linus' kernel plus some nice additional features like UKSM and aufs3). The package is called "linux-zen" in Arch Linux. libvirt is a "virtualization API" which allows you to define and control virtual machines (called domains) using many different virtualization techniques (kvm/qemu, xen, lxc, openvz, virtualbox, ...) using the same api. (virt-manager and virsh are "front-end interfaces" that use libvirt internally. I hope the problem will automatically go away, when aufs supports user namespaces (as the remount will then happen only inside the namespace of the machine). I therefore mailed you a "git-compatible" patch of Bhushan Jain's changes a minute ago. Florian J. R. Okajima
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
