Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 05:34
    hswong3i synchronize #1268
  • 02:38
    hswong3i synchronize #1267
  • May 08 23:36
    electrofelix assigned #841
  • May 08 23:34
    electrofelix closed #911
  • May 08 23:34
    electrofelix commented #911
  • May 08 23:30
    electrofelix closed #912
  • May 08 23:30
    electrofelix commented #912
  • May 08 23:29
    electrofelix closed #919
  • May 08 23:29
    electrofelix commented #919
  • May 08 23:27
    electrofelix assigned #948
  • May 08 23:26
    electrofelix closed #989
  • May 08 23:26
    electrofelix commented #989
  • May 08 23:23
    electrofelix commented #995
  • May 08 23:21
    electrofelix assigned #995
  • May 08 23:21
    electrofelix closed #1003
  • May 08 23:21
    electrofelix commented #1003
  • May 08 23:15
    electrofelix closed #1051
  • May 08 23:15
    electrofelix commented #1051
  • May 08 23:15
    electrofelix closed #1058
  • May 08 23:15
    electrofelix commented #1058
sahanaha1234
@sahanaha1234
Hi Folks, I am trying to install vagrant-libvirt plugin without having internet access. I tried the steps mentioned in https://alwaystinkering.wordpress.com/2016/07/08/manually-installing-plugins-in-vagrant . This needs ruby version >=2.3.0 for package nokogiri-1.10.5.gem to be installed. Is there any way I can install vagrant-libvirt offline with out having requirement for ruby version to be 2.3.0 ? I see that vagrant-libvirt is having dependency of nokogiri >=1.6.0, hence if you could help me on how we can replace nokogiri-1.6.0 instead of nokogiri-1.10.5 in the above mentioned method will be great!
AnPham
@phamduchongan93
/@infernix I'm too is having the same gme issue
you folks found out the problem yet?
Roberto Ciatti
@gekorob
Hi guys I'm trying to package a running centos 8.1 as box, but after package box when I try to us it in a vagrant file the vagrant up hangs on waiting for ssh
default: Waiting for SSH to become available...
Does anybody has some hints?
elreydetoda
@elreydetoda

Is this were people are talking about this issue? vagrant-libvirt/vagrant-libvirt#1069

I don't know how I can help, but I would love to!

Dan Čermák
@dcermak
@elreydetoda I guess so? This channel is unfortunately not very active though…
elreydetoda
@elreydetoda
is there an "official" communication method that the other people who are going to be maintainers will have? or just any other communication methods?
Dan Čermák
@dcermak
I'd try this channel and github issues
Darragh Bailey
@electrofelix
@dcermak mostly the problem is due to most of the past maintainers not actively using vagrant-libvirt as much so difficult to devote time to it as part of work. I'm trying to keep the ball rolling so to speak, but it's clear I'm not in a viable position to actively maintain
Dan Čermák
@dcermak
@electrofelix That is a pity, as I (and probably a bunch of others) are actively using vagrant-libvirt
unfortunately Ruby is like black magic to me, so I also don't see myself contributing a lot :-(
however, I could try to look a bit into creating tests and test cases and a CI to prevent regressions, as they'd eventually bite me as well (I'm the current vagrant & vagrant-libvirt maintainer in openSUSE)
unfortunately won't have time for that until June
Darragh Bailey
@electrofelix
@dcermak the good news is I'm getting a little bit more time and there looks like a few others are helping get some PRs in good shape, so a little bit from a number of people may be enough to get it all rolling forward again
Dan Čermák
@dcermak
anyone knows if it is possible to modify the cmdline of the existing kernel of an existing vagrant box?
Darragh Bailey
@electrofelix
@dcermak I think it's only possible if you are setting the kernel and initrd to be used from the host as otherwise qemu is just launching the default bootloader in the disk image passed to it. The alternative is to boot, use the provision steps to modify from within the guest and then use the reload plugin to trigger a reboot to use the new settings
Dan Čermák
@dcermak
@electrofelix Thanks for your reply, so it's as I thought
matrixbot
@matrixbot
@mattiasb:matrix.org Hi! I regularly create vagrant boxes for testing ansible roles. Sometimes there's a lot of data to download before the playbook is done. Recently I've been bitten by this issue a lot: vagrant-libvirt/vagrant-libvirt#1122
@mattiasb:matrix.org According to the Vagrant developers this is an issue with the vagrant-libvirt plugin: https://github.com/hashicorp/vagrant/issues/11692#issuecomment-642133380
@mattiasb:matrix.org I say "issue" but it might very well be intended behaviour.
@mattiasb:matrix.org The problem is that when I forget to add the --no-destroy-on-error flag I might very well lose 30 minutes having to reprovision the machine from the beginning again while trying to find the issue with my playbook.
@mattiasb:matrix.org Is it possible somehow (without resorting to wrapping vagrant in a shell script) to configure vagrant-libvirt to not destroy the domain on error?
Darragh Bailey
@electrofelix
@matrixbot I think this will require me asking questions of the vagrant developers, because it looks like the CLI option documentation and what they intended to occur by default don't match. In the past there were issues because vagrant-libvirt always destroyed and didn't match the expected behaviour with the CLI option. The only thing I could think of is to expose a config option in vagrant-libvirt that overrides the command behaviour with an explicit warning, usually you'd always take the requested behaviour from the CLI but in this case vagrant will default to always setting destroy_on_error
Darragh Bailey
@electrofelix
@matrixbot I've logged hashicorp/vagrant#12098 to try and get them to explain what the intention of that option is, if it's not to perform a destroy on error as is currently documented
matrixbot
@matrixbot
@mattiasb:matrix.org Thanks! :)
defolos
@defolos:matrix.org
[m]
Hey @electrofelix, I've seen that the newest release of vagrant-libvirt contains the contextual_proc gem
Could that please, please be removed?
I'm currently looking into updating vagrant-libvirt to 0.4.0 in openSUSE, but the contextual_proc gem is effectively unpackageable, because it contains no license at all (i.e. it is proprietary from a legal pov and cannot be included in most Linux distros)
also, that gem is effectively just a single class, maybe it would be possible to completely omit it?
Darragh Bailey
@electrofelix
@defolos:matrix.org yes it should be removed shortly, the original maintainers have added a license to their repo and I'll look to work with them to get a subsequent release, my apologies for missing that there was no license
1 reply
Darragh Bailey
@electrofelix
@defolos:matrix.org just pushed a 0.4.1 release there with the contextual_proc gem removed, along with 2 small bugfixes, I'll look to avoid landing anything other than bugfixes for another week
defolos
@defolos:matrix.org
[m]
Plus it was really simple to rip out even for a ruby noob like myself