Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 11 23:17
    chrisroberts commented #1310
  • Jun 11 23:11
    chrisroberts opened #1310
  • Jun 11 21:37

    electrofelix on 0.5.3

    (compare)

  • Jun 11 21:32

    electrofelix on master

    Use qemu-img json output and co… Merge pull request #1309 from y… (compare)

  • Jun 11 21:32
    electrofelix closed #1309
  • Jun 11 14:50
    yamatoRT synchronize #1309
  • Jun 11 08:06
    yamatoRT synchronize #1309
  • Jun 10 20:11
    yamatoRT opened #1309
  • Jun 10 20:10
    yamatoRT edited #1308
  • Jun 09 20:29
    electrofelix commented #1308
  • Jun 09 19:22
    yamatoRT edited #1308
  • Jun 09 18:25
    electrofelix commented #85
  • Jun 09 17:42
    yamatoRT opened #1308
  • Jun 09 10:43
    mgedmin commented #85
  • Jun 07 18:58
    electrofelix synchronize #1307
  • Jun 07 18:58

    electrofelix on add-packaging-unit-tests

    Ensure open3 required and qemu-… Merge branch 'master' into add-… (compare)

  • Jun 07 16:57
    electrofelix synchronize #1307
  • Jun 07 16:57

    electrofelix on add-packaging-unit-tests

    Basic packaging tests and restr… (compare)

  • Jun 07 16:57
    electrofelix edited #1307
  • Jun 07 16:56
    electrofelix commented #1254
sidisgood
@sidisgood
hello all, how I can compile vagrant 1.9.1 from source? is there any guide?
sidisgood
@sidisgood
Gerben Meijer
@infernix
@electrofelix ping :)
Brad Searle
@bobthebutcher
Hello team, I am wondering if there is an option to configure the vcpu_quota
sorry if this is not the best place to ask this type of question
Gerben Meijer
@infernix
@bobthebutcher i don't think we support that, no
Brad Searle
@bobthebutcher
the equivalent command with virsh is similar tovirsh schedinfo vsrx-test_fw2 --set vcpu_quota=33000
oh ok cool, thanks for clarifying
rayascott
@rayascott

I’m using Fedora 27 and Vagrant 2.0.1. I see the QA versions are a bit behind that, so I’m wondering if I need to drop back a few versions, or assume the docs are out of date.

I’m busy learning Vagrant by following a bit of an outdated book, and trying to substitute vagrant-libvirt for the usual VBox default.

The problem I’m seeing is that (I’m using the fedora/27-cloud-base box) if I make a change to a file in my host directory (the one I ran “vagrant up” in), those changes aren’t automatically reflected in the guest’s “/vagrant” directory.

Is this normal behaviour for the plugin? I was thinking perhaps it’s a permissions issue, but no vagrant docs seem to mention this.

Any Ideas? Is there a debug flag that might help when running vagrant up?

Gerben Meijer
@infernix
Use nfs in vagrantfile
rayascott
@rayascott
Is 9p a bad idea?
Gerben Meijer
@infernix
It's not great
You can try it but you're quickly going to run into permissions problems
rayascott
@rayascott
Are there other issues with 9p beyond permissions?
Gerben Meijer
@infernix
shouldnt be
but 9p is linux only
nfs works on osx too
rayascott
@rayascott
ah ok, thanks for the info.
one last question, do Vagrant plugins have to be written in Ruby?
Gerben Meijer
@infernix
pretty sure that's a yes
rayascott
@rayascott
ok thanks.
Gerben Meijer
@infernix
@pronix @electrofelix any objections to pushing a new release?
Dmitry Vasilets
@pronix
i use edge, no opinion :)
Gerben Meijer
@infernix
edge?
Dmitry Vasilets
@pronix
git latest version
gotoole
@bashrc666
Hi all,
need some help on something ;)
I'm not able to not activate the private network from the Vagrantfile
here is my vagrantfile
```
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.define :grafana do |grafana|
    grafana.vm.box = "generic/debian9"
    grafana.vm.hostname = "grafana"
    grafana.vm.network :public_network,
      :dev => "vmbr10",
      :mode => "bridge",
      :type => "bridge"
    grafana.ssh.insert_key = false
  end

  config.vm.provider :libvirt do |libvirt|
    libvirt.management_network_name = "vmbr10"
    libvirt.driver = "kvm"
    libvirt.host = "*******"
    libvirt.connect_via_ssh = true
    libvirt.username = "*****"
    libvirt.storage_pool_name = "vms"
    libvirt.default_prefix = ''
  end

  config.vm.provision "ansible" do |ansible|
    ansible.limit = "all"
    ansible.playbook = "tests/playbook.yml"
  end
end
I only wanna keep vmbr10
And also i'ts a great plugin ;)
Gerben Meijer
@infernix
@pronix @electrofelix either of you guys at FOSDEM this year?
Dmitry Vasilets
@pronix
hi. i'm not. i am again repeating mistake - participate in startup.
Gerben Meijer
@infernix
hehe
it's called taking chances :D
Darragh Bailey
@electrofelix
@infernix I'm not, but I'm heading to cfgmgmtcamp for the Mon-Wed afterwards in Ghent just an hour from Brussels. Don't suppose you are heading there as well?
Gerben Meijer
@infernix
@electrofelix i wasn't :)
on a more serious note
i just tested the fog-libvirt changes
on centos 6:
/root/.vagrant.d/gems/2.4.3/gems/fog-libvirt-0.4.2/lib/fog/libvirt/models/compute/server.rb:329:in `local_ip_command': undefined local variable or method `ip_command' for #<Fog::Compute::Libvirt::Server:0x0000000002475048> (NameError)
    from /root/.vagrant.d/gems/2.4.3/gems/fog-libvirt-0.4.2/lib/fog/libvirt/models/compute/server.rb:367:in `addresses_ip_command'
    from /root/.vagrant.d/gems/2.4.3/gems/fog-libvirt-0.4.2/lib/fog/libvirt/models/compute/server.rb:290:in `addresses'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:43:in `block (3 levels) in call'
    from /root/.vagrant.d/gems/2.4.3/gems/fog-core-1.43.0/lib/fog/core/model.rb:72:in `instance_eval'
    from /root/.vagrant.d/gems/2.4.3/gems/fog-core-1.43.0/lib/fog/core/model.rb:72:in `block in wait_for'
    from /root/.vagrant.d/gems/2.4.3/gems/fog-core-1.43.0/lib/fog/core/wait_for.rb:7:in `block in wait_for'
    from /root/.vagrant.d/gems/2.4.3/gems/fog-core-1.43.0/lib/fog/core/wait_for.rb:6:in `loop'
    from /root/.vagrant.d/gems/2.4.3/gems/fog-core-1.43.0/lib/fog/core/wait_for.rb:6:in `wait_for'
    from /root/.vagrant.d/gems/2.4.3/gems/fog-core-1.43.0/lib/fog/core/model.rb:69:in `wait_for'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:42:in `block (2 levels) in call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/util/retryable.rb:17:in `retryable'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:37:in `block in call'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/util/timer.rb:9:in `time'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:34:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/start_domain.rb:302:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_boot_order.rb:78:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_network_interfaces.rb:182:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_networks.rb:84:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/share_folders.rb:20:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:18:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
    from /root/.vagrant.d/gems/2.4.3/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call'
    from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vag
i think you have a typo there?
Ingmars Melkis
@zingmars
Hello. Is there a way to configure spice's opengl functionality (specify render device) using vagrant-libvirt?
Ingmars Melkis
@zingmars
An example of the configuration option can be seen in https://libvirt.org/formatdomain.html#elementsGraphics under the SPICE section (<gl enable="yes"(...))
Brad Searle
@bobthebutcher
gday everyone. I am trying to set the cpu model of a host to core2duo but I can seem to get the right options.
       domain.cpu_mode = "custom"
      domain.cpu_model = "core2duo"
I am using these options, but it does not look like they make it to the xml file
not sure if I am going about it in the correct way