Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Exception on premounted cgroup #17

Open
ghost opened this issue Jun 23, 2013 · 10 comments
Open

Exception on premounted cgroup #17

ghost opened this issue Jun 23, 2013 · 10 comments
Assignees
@miurahr
Labels
bug enhancement

Comments

@ghost
Copy link

ghost commented Jun 23, 2013

I had this in mount before running vagrant up

cgroup on /cgroup type cgroup (rw,relatime,hugetlb,net_prio,perf_event,blkio,freezer,devices,memory,cpuacct,cpu,cpuset)

and I got this:

    Bringing machine 'default' up with 'kvm' provider...
[default] Importing base box 'raring64'...
    (100.00/100%)
[default] Matching MAC address for NAT networking...
[default] Preparing network interfaces based on configuration...
[default] Creating shared folders metadata...
[default] Booting VM...
[default] Destroying VM and associated drives...
/home/user1/.vagrant.d/gems/gems/vagrant-kvm-0.1.3/lib/vagrant-kvm/driver/driver.rb:240:in `create': Call to virDomainCreateWithFlags failed: Unable to initialize /machine cgroup: Invalid argument (Libvirt::Error)
    from /home/user1/.vagrant.d/gems/gems/vagrant-kvm-0.1.3/lib/vagrant-kvm/driver/driver.rb:240:in `start'
    from /home/user1/.vagrant.d/gems/gems/vagrant-kvm-0.1.3/lib/vagrant-kvm/action/boot.rb:14:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/v
@miurahr
Copy link
Collaborator

miurahr commented Jul 16, 2013

Libvirt is made cgroups container when system support cgroups. In historical reason, /machine is default for it.
It may help us to understand it.
https://www.berrange.com/posts/2013/05/13/a-new-configurable-cgroups-layout-for-libvirt-with-qemu-kvm-lxc/
http://libvirt.org/cgroups.html

Vagrant-kvm should detect cgroups existence and configure box.xml around cgroups required.
such as

/machine/production

and make directory

@adrahon
Copy link
Owner

adrahon commented Jul 16, 2013

Would be great to have a pull request for this.

@ghost ghost assigned miurahr Nov 13, 2013
@miurahr
Copy link
Collaborator

miurahr commented Nov 16, 2013

I've just reproduced it.
Using ubuntu 12.04(LTS) and cgroup-bin package.

@y-p you can escape it with uninstall cgroup-bin and install cgroup-lite instead.

@miurahr
Copy link
Collaborator

miurahr commented Nov 16, 2013

In my environment,
cgroups on /sys/fs/cgroup type tmpfs (rw,uid=0,gid=0,mode=0755)

@miurahr
Copy link
Collaborator

miurahr commented Nov 16, 2013 

$ vagrant up
 INFO global: Vagrant version: 1.3.5
 INFO manager: Registered plugin: resume command
 INFO manager: Registered plugin: suspend command
 INFO manager: Registered plugin: ssh-config command
 INFO manager: Registered plugin: package command
 INFO manager: Registered plugin: up command
 INFO manager: Registered plugin: plugin command
 INFO manager: Registered plugin: ssh command
 INFO manager: Registered plugin: destroy command
 INFO manager: Registered plugin: reload command
 INFO manager: Registered plugin: halt command
 INFO manager: Registered plugin: provision command
 INFO manager: Registered plugin: box command
 INFO manager: Registered plugin: status command
 INFO manager: Registered plugin: help command
 INFO manager: Registered plugin: init command
 INFO manager: Registered plugin: kernel
 INFO manager: Registered plugin: shell
 INFO manager: Registered plugin: file
 INFO manager: Registered plugin: CFEngine Provisioner
 INFO manager: Registered plugin: salt
 INFO manager: Registered plugin: ansible
 INFO manager: Registered plugin: chef
 INFO manager: Registered plugin: puppet
 INFO manager: Registered plugin: kernel
 INFO manager: Registered plugin: RedHat guest
 INFO manager: Registered plugin: Solaris 11 guest.
 INFO manager: Registered plugin: OmniOS guest.
 INFO manager: Registered plugin: Gentoo guest
 INFO manager: Registered plugin: Linux guest.
 INFO manager: Registered plugin: PLD Linux guest
 INFO manager: Registered plugin: Ubuntu guest
 INFO manager: Registered plugin: CoreOS guest
 INFO manager: Registered plugin: Arch guest
 INFO manager: Registered plugin: Debian guest
 INFO manager: Registered plugin: Solaris guest.
 INFO manager: Registered plugin: Fedora guest
 INFO manager: Registered plugin: ESXi guest.
 INFO manager: Registered plugin: OpenBSD guest
 INFO manager: Registered plugin: FreeBSD guest
 INFO manager: Registered plugin: Darwin guest
 INFO manager: Registered plugin: SUSE guest
 INFO manager: Registered plugin: ssh communicator
 INFO manager: Registered plugin: Red Hat host
 INFO manager: Registered plugin: BSD host
 INFO manager: Registered plugin: Gentoo host
 INFO manager: Registered plugin: Linux host
 INFO manager: Registered plugin: Arch host
 INFO manager: Registered plugin: Windows host
 INFO manager: Registered plugin: Slackware host
 INFO manager: Registered plugin: OpenSUSE host
 INFO manager: Registered plugin: FreeBSD host
 INFO manager: Registered plugin: VirtualBox provider
 INFO vagrant: `vagrant` invoked: ["up"]
 INFO environment: Environment initialized (#<Vagrant::Environment:0x000000012e4cc0>)
 INFO environment:   - cwd: /opt/vagrant/users/miurahr/work/precise64
 INFO environment: Home path: /home/miurahr/.vagrant.d
 INFO environment: Local data path: /opt/vagrant/users/miurahr/work/precise64/.vagrant
 INFO environment: Loading plugin from JSON: vagrant-kvm
 INFO manager: Registered plugin: KVM provider
 INFO environment: Loading plugin from JSON: vagrant-libvirt
 INFO manager: Registered plugin: libvirt
 INFO environment: Loading plugin from JSON: vagrant-lxc
 INFO manager: Registered plugin: vagrant-lxc
 INFO environment: Running hook: environment_load
 INFO environment: Initializing config...
 INFO loader: Set :default = "/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/config/default.rb"
 INFO loader: Set :root = #<Pathname:/opt/vagrant/users/miurahr/work/precise64/Vagrantfile>
 INFO loader: Loading configuration in order: [:default, :home, :root]
 INFO hosts: Host class: VagrantPlugins::HostLinux::Host
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000001e42f40>
 INFO cli: CLI: [] "up" []
 INFO environment: Getting machine: default (kvm)
 INFO environment: Uncached load of machine.
 INFO loader: Set :vm_default = []
 INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
 INFO box_collection: Searching for box: precise64 (kvm) in /home/miurahr/.vagrant.d/boxes/precise64/kvm/metadata.json
 INFO box_collection: Box found: precise64 (kvm)
 INFO environment: Box exists with Vagrantfile. Reloading machine config.
 INFO loader: Set :box_precise64_kvm = #<Pathname:/home/miurahr/.vagrant.d/boxes/precise64/kvm/Vagrantfile>
 INFO loader: Loading configuration in order: [:default, :box_precise64_kvm, :home, :root, :vm_default]
 INFO machine: Initializing machine: default
 INFO machine:   - Provider: VagrantPlugins::ProviderKvm::Provider
 INFO machine:   - Box: #<Vagrant::Box:0x000000017e12a0>
 INFO machine:   - Data dir: /opt/vagrant/users/miurahr/work/precise64/.vagrant/machines/default/kvm
 INFO driver: Check KVM kernel modules
 INFO driver: Init storage pool vagrant
 INFO command: With machine: default (QEMU/KVM (new VM))
 INFO interface: info: Bringing machine 'default' up with 'kvm' provider...
Bringing machine 'default' up with 'kvm' provider...
 INFO batch_action: Enabling parallelization by default.
 INFO batch_action: Disabling parallelization because provider doesn't support it: kvm
 INFO batch_action: Batch action will parallelize: false
 INFO batch_action: Starting action: #<Vagrant::Machine:0x00000001a183c0> up {:destroy_on_error=>true, :parallel=>true, :provision_ignore_sentinel=>false, :provision_types=>nil}
 INFO machine: Calling action: up on provider QEMU/KVM (new VM)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000001f5bc88>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::CheckKvm:0x00000001933540>
 INFO driver: Check KVM kernel modules
 INFO driver: Init storage pool vagrant
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::SetName:0x000000019334a0>
 INFO setname: Setting the name of the VM: precise64_1384595020
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000001bea130>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::InitStoragePool:0x00000001bea0b8>
 INFO driver: Check KVM kernel modules
 INFO driver: Init storage pool vagrant
 INFO driver: Init storage pool vagrant
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000001bea090>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000000020d2af8>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::Created:0x000000020d13b0>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::Created:0x000000020d13b0>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x00000001fe5b68>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::CheckBox:0x00000001fe5a50>
 INFO box_collection: Searching for box: precise64 (kvm) in /home/miurahr/.vagrant.d/boxes/precise64/kvm/metadata.json
 INFO box_collection: Box found: precise64 (kvm)
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::Import:0x00000001fe5a00>
 INFO interface: info: Importing base box 'precise64'...
[default] Importing base box 'precise64'...
 INFO driver: Importing VM
 INFO driver: Creating volume precise64-1384595021.img backed by precise64.img
Formatting '/home/miurahr/.vagrant.d/tmp/storage-pool/precise64-1384595021.img', fmt=qcow2 size=10632560640 backing_file='/home/miurahr/.vagrant.d/boxes/precise64/kvm/precise64.img' encryption=off cluster_size=65536 lazy_refcounts=off 
 INFO driver: Creating new VM
 INFO machine: New machine ID: "16c38208-5046-8737-2ea1-816567e3600a"
 INFO driver: Check KVM kernel modules
 INFO driver: Init storage pool vagrant
 INFO driver: Check if VM 16c38208-5046-8737-2ea1-816567e3600a exists
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::MatchMACAddress:0x00000001fe59d8>
 INFO interface: info: Matching MAC address for NAT networking...
[default] Matching MAC address for NAT networking...
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::MatchMACAddress:0x00000001fe59d8>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::Import:0x00000001fe5a00>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::CheckBox:0x00000001fe5a50>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::CheckKvm:0x00000001be9fc8>
 INFO driver: Check KVM kernel modules
 INFO driver: Init storage pool vagrant
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000001be9f78>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000001be9f50>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007fc3bc27a150>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::IsRunning:0x007fc3bc278b48>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::IsRunning:0x007fc3bc278b48>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x007fc3bc0e1078>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x007fc3bc0e1000>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007fc3bc40f330>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::IsSaved:0x007fc3bc103808>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::IsSaved:0x007fc3bc103808>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x007fc3bc2314a0>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x007fc3bc231428>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007fc3bc01e960>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::IsPaused:0x007fc3bc024540>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::IsPaused:0x007fc3bc024540>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x007fc3bc357898>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::PrepareGui:0x007fc3bc358360>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::Network:0x007fc3bc358388>
 INFO interface: info: Preparing network interfaces based on configuration...
[default] Preparing network interfaces based on configuration...
 INFO driver: Creating network vagrant
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Provision:0x000000015acd68>
 INFO provision: Checking provisioner sentinel if we should run...
 INFO provision: Sentinel not found.
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::PruneNFSExports:0x0000000198e788>
 INFO linux: Pruning invalid NFS entries...
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::NFS:0x0000000198e760>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::PrepareNFSSettings:0x00000001b442d0>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SetHostname:0x00000001bc4700>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::Boot:0x00000001bc46d8>
 INFO interface: info: Booting VM...
[default] Booting VM...
ERROR warden: Error occurred: Call to virDomainCreateWithFlags failed: Unable to create cgroup for precise64_1384595020: No such file or directory
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: Call to virDomainCreateWithFlags failed: Unable to create cgroup for precise64_1384595020: No such file or directory
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x007fc3bc231428>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
ERROR warden: Error occurred: Call to virDomainCreateWithFlags failed: Unable to create cgroup for precise64_1384595020: No such file or directory
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x007fc3bc0e1000>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
ERROR warden: Error occurred: Call to virDomainCreateWithFlags failed: Unable to create cgroup for precise64_1384595020: No such file or directory
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000001be9f50>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000001bea090>
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<VagrantPlugins::ProviderKvm::Action::Import:0x00000001fe5a00>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007fc3bc05c4e0>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::CheckKvm:0x007fc3bc05ade8>
 INFO driver: Check KVM kernel modules
 INFO driver: Init storage pool vagrant
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x007fc3bc05adc0>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007fc3bc6655a8>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::Created:0x007fc3bc66c0d8>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::Created:0x007fc3bc66c0d8>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x007fc3bc6597a8>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x007fc3bc659730>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007fc3bc0023f0>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::DestroyConfirm:0x007fc3bc034fa8>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::DestroyConfirm:0x007fc3bc034fa8>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x000000015e0438>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x000000015e03c0>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::EnvSet:0x000000015e0398>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::CheckKvm:0x000000015e02d0>
 INFO driver: Check KVM kernel modules
 INFO driver: Init storage pool vagrant
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x000000015e02a8>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000001cf6c18>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::Created:0x00000001cf35e0>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::Created:0x00000001cf35e0>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x00000001fec828>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000001fec760>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007fc3bc1e0de8>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::IsPaused:0x007fc3bc1df628>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::IsPaused:0x007fc3bc1df628>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x007fc3bc383600>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000001fec710>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007fc3bc4d2ee8>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::GracefulHalt:0x007fc3bc4d9838>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::GracefulHalt:0x007fc3bc4d9838>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x007fc3bc2c6320>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::ForcedHalt:0x007fc3bc2c62a8>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::ForcedHalt:0x007fc3bc2c62a8>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00000001fec710>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00000001fec760>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::PruneNFSExports:0x000000015e0230>
 INFO linux: Pruning invalid NFS entries...
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderKvm::Action::Destroy:0x000000015e0140>
 INFO interface: info: Destroying VM and associated drives...
[default] Destroying VM and associated drives...
 INFO machine: New machine ID: nil
 INFO driver: Check KVM kernel modules
 INFO driver: Init storage pool vagrant
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::Destroy:0x000000015e0140>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::PruneNFSExports:0x000000015e0230>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x000000015e02a8>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::CheckKvm:0x000000015e02d0>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::EnvSet:0x000000015e0398>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::ConfigValidate:0x000000015e03c0>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x007fc3bc659730>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x007fc3bc05adc0>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderKvm::Action::CheckKvm:0x007fc3bc05ade8>
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO environment: Running hook: environment_unload
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007fc3bc06a1a8>
/home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/driver/driver.rb:348:in `create': Call to virDomainCreateWithFlags failed: Unable to create cgroup for precise64_1384595020: No such file or directory (Libvirt::Error)
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/driver/driver.rb:348:in `start'
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/boot.rb:14:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/set_hostname.rb:16:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/prepare_nfs_settings.rb:11:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/nfs.rb:30:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/prune_nfs_exports.rb:15:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/provision.rb:54:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/network.rb:54:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/prepare_gui.rb:13:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/check_kvm.rb:18:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:57:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/init_storage_pool.rb:14:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/set_name.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /home/miurahr/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/check_kvm.rb:18:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/machine.rb:147:in `action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'

@miurahr
Copy link
Collaborator

miurahr commented Nov 16, 2013

After just install cgroup-bin and run vagrant up cause this. But rebooting after install, it has gone.
The resolution is reboot. It make everything is done in order to recognize cgroup setup.

No need to fix.

@miurahr miurahr closed this as completed Nov 16, 2013
@miurahr miurahr reopened this Nov 16, 2013
@miurahr
Copy link
Collaborator

miurahr commented Nov 16, 2013

Original problem: on cgroup on /cgroup type cgroup where location is differ.
@y-p could you provide more information? cgroup-bin or similar package version, kernel version and distro version.

@ghost
Copy link
Author

ghost commented Nov 17, 2013

I'm on debian testing, there's no cgroup-lite package available (though ubuntu's may work).
Am using other tools now, so can't offer more info on this.

@miurahr
Copy link
Collaborator

miurahr commented Nov 19, 2013

In debian, document consult user should mount cgroups as follows:

cgroup  /sys/fs/cgroup  cgroup  defaults  0   0

Could you check your fstab?

*) https://wiki.debian.org/LXC

@miurahr
Copy link
Collaborator

miurahr commented Dec 12, 2013

I think we need faq document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@miurahr miurahr

Labels
bug enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@miurahr @adrahon