by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Chris Roberts
    @chrisroberts
    yeah, no worries. 2 weeks will be the fastest. we've got other things we're working on as well to get merged in before the next release so i'm sure it will be a little longer :)
    Arindam Mondal
    @Arindam-Mondal

    I am getting the below error
    Failed to mount folders in Linux guest. This is usually because
    the "vboxsf" file system is not available. Please verify that
    the guest additions are properly installed in the guest and
    can work properly. The command attempted was:

    mount -t cifs -o vers=2.0,credentials=/etc/smb_creds_vgt-18791af46561bf3104c65671dfdfc0f9-6ad5fdbcbf2eaa93bd62f92333a2e6e5,5,uid=1000,gid=1000 //10.13.62.142/vgt-18791af46561bf3104c65671dfdfc0f9-6ad5fdbcbf2eaa93bd62f92333a2e6e5 /vagrant

    The error output from the last command was:

    mount error(115): Operation now in progress
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
    Can Anyone please help..It was working fine..Suddenly it is not working anymore...I am using windows 10..Thanks

    Ben Johnson
    @cbj4074
    @Arindam-Mondal Have you tried rebooting the Windows host?
    Ben Johnson
    @cbj4074

    Not sure if this is the appropriate place to discuss Packer, but I'm wondering why it seems to ignore the switch_name environment variable when using the Hyper-V Builder. This used to work as expected for me, but now, even if I specify it like

    $env:switch_name = 'Default Switch'

    and then confirm that it's set correctly with

    > Get-ChildItem Env:switch_name
    
    Name                           Value
    ----                           -----
    switch_name                    Default Switch

    Packer still forges right on ahead with creating a new packer-hyperv-iso switch:

    > packer build -only=hyperv-iso .\ubuntu-18.04-amd64.json
    hyperv-iso output will be in this color.
    
    ==> hyperv-iso: Creating build directory...
    ==> hyperv-iso: Retrieving ISO
    ...
    ==> hyperv-iso: Creating switch 'packer-hyperv-iso' if required...
    ==> hyperv-iso:     switch 'packer-hyperv-iso' already exists. Will not delete on cleanup...

    Ahh, my bad. It looks like Bento is overriding that behavior for whatever reason. In digging-around my Bento configuration, I notice that it contains

    "hyperv_switch": "{{env `hyperv_switch`}}",

    and so setting $env:hyperv_switch = 'Default Switch' does the job.

    Ben Johnson
    @cbj4074
    Oddly, the VM freezes during the early statges of Ubuntu setup when I use the Default Switch, so I just created another External switch, told Packer to use that, and it works fine. Sigh. Always something with Hyper-V's networking stack...
    AnPham
    @phamduchongan93
    Hi everyone, I have this gem issue in vagrant while loading the libvirt. This seems to be popular problem. What is the real problem? ```
       from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builder.rb:116:in `call'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `block in run'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/util/busy.rb:19:in `busy'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `run'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:238:in `action_raw'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:209:in `block in action'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/environment.rb:613:in `lock'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:195:in `call'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:195:in `action'
            from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run'
    my pc spec
    anpham@anpham-Latitude-5490:~/vagrant/libvirt/centos$ lsb_release -a                                                         
    No LSB modules are available.                                                                                                
    Distributor ID: Ubuntu
    Description:    Ubuntu 18.04.3 LTS
    Release:        18.04
    Codename:       bionic
    anpham@anpham-Latitude-5490:~/vagrant/libvirt/centos$
    Chris Roberts
    @chrisroberts
    a gist of the full output from a run with the --debug flag enabled would be more helpful to identify the root cause
    AnPham
    @phamduchongan93
    @chrisroberts I see, it's my first time here.
    AnPham
    @phamduchongan93
    Ben Johnson
    @cbj4074
    An error occurred while executing a PowerShell script. This error
    is shown below. Please read the error message and see if this is
    a configuration error with your system. If it is not, then please
    report a bug.
    
    Script: check_hyperv_access.ps1
    Error:
    
    where : Exception calling "Translate" with "1" argument(s): "Some or all identity references could not be translated."
    At C:\HashiCorp\Vagrant\embedded\gems\2.2.5\gems\vagrant-2.2.5\plugins\providers\hyperv\scripts\utils\VagrantVM\VagrantVM.psm1:721 char:32
    +     $systemACL = $acl.Access | where {
    +                                ~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Where-Object], MethodInvocationException
        + FullyQualifiedErrorId : IdentityNotMappedException,Microsoft.PowerShell.Commands.WhereObjectCommand

    Apparently, this is a known issue:

    hashicorp/vagrant#11271

    Nobody knows how to work around this, let alone what causes it? :/

    rubenst2013
    @rubenst2013
    Hi all. :) @briancain or @chrisroberts is there any news on the vagrant 2.2.7 release? last time it was mentioned end of Oct. I specifically need the new linux graceful restart & continue provisioning feature. the reload plugin sadly does not work. Only option right now is to compile from source and get that custom version to my colleagues.
    AdamJacks
    @AdamJacks
    Hey chaps
    I'm using Vagrant for the first time
    Trying to use an Ubuntu image but not having much luck
    Synthetic SCSI Controller (Instance ID B1C1F70F-F2D1-46F1-8414-2A1C8F4EBCBC): Failed to Power on with Error 'A virtual disk support provider for the specified file was not found.' (0xC03A0014). (Virtual machine ID 34CE42A8-1366-43C9-8CF4-4C536228DC9E)
    Does anyone have any knowledge of this
    Ben Johnson
    @cbj4074

    @AdamJacks Strange... never seen that one.

    a.) Which box are you using?

    b.) What is the host OS?

    Also using HyperV
    AdamJacks
    @AdamJacks
    Awkwardly I've got it working but it's in French and has a password protected login
    ...
    Ben Johnson
    @cbj4074
    @AdamJacks I've had nothing but problems with the stock Ubuntu boxes. Networking is usually broken and it seems that no real care is put into those releases. I've had much better success with https://app.vagrantup.com/bento/boxes/ubuntu-18.04
    (the password on that box you're using is probably secret, password, or something similar)
    Oussama DELASSI
    @delassiops
    Hi,
    For Vagrant VMware Plugin
    As a tool for advancing humans of DevOps
    , is there any revision of the price at lower price ($79) for be accessible to DevOps Adopter & Enthusiast
    Joel Sallow (/u/ta11ow)
    @vexx32
    o/ hullo! Does anyone know what steps I'd need to take to store a Vagrant box in a Nexus repository?
    dgarstang
    @dgarstang
    Anyone use the GCP vagrant plugin at https://github.com/mitchellh/vagrant-google with host networking? Just doesn't seem to work. :(
    dgarstang
    @dgarstang
    Sounds like .... no one. :(
    Joel Sallow (/u/ta11ow)
    @vexx32
    tbh this channel seems fairly quiet. There's probably another channel we can go to somewhere... wonder if there's a subreddit with other community links or something
    Ben Johnson
    @cbj4074
    For as quiet as it is, historically, the Vagrant staff has responded to anything "legitimate". That said, I wonder if there is indeed a more highly-trafficked venue.
    clownkalai
    @clownkalai
    @clownkalai
    Dan Čermák
    @dcermak
    Hey folks, I've received an email from hashicorp that I'm apparently a Core Contributor and they'd like to send me a care package. Which looks pretty suspicious to me, given that I have made pretty small contributions to Vagrant at best. Anyone else got something like that?
    Ben Johnson
    @cbj4074
    @dcermak Haven't received anything like that, but I agree that it sounds very suspicious.
    Joel Sallow (/u/ta11ow)
    @vexx32
    I'd be checking the email sender etc, make sure where it really comes from
    Dan Čermák
    @dcermak
    It all looks pretty genuine and the email address even belongs to hashicorp
    (and whoever is behind it responded that the email was genuine)
    Ben Johnson
    @cbj4074
    Let's see the DKIM headers from the email :D
    Nico Sap
    @NicoJuicy
    What could go wrong? :p
    Dan Čermák
    @dcermak
    Well I got a T-Shirt and a voucher for HashiConf for replying, so even if it was a scam, I'd say it was pretty worth it for me so far ;-)
    Zburator
    @Zburator
    Hi guys, I have a layman's question:
    Can you start a vagrant with virtualbox provider on a centos 7 machine with no VT-X?
    I'm curios if I can somehow allocate one processor for that virtual machine
    Dan Čermák
    @dcermak
    Don't think that that will work, afaik virtualbox needs hardware virtualization support
    alexk345
    @alexk345
    My laravel homestead vm do not boot.
    00:00:03.412108 ** End of CPUID dump **
    00:00:03.412133 VMEmt: Halt method global1 (5)
    00:00:03.412299 VMEmt: HaltedGlobal1 config: cNsSpinBlockThresholdCfg=50000
    00:00:03.412364 Changing the VM state from 'CREATING' to 'CREATED'
    00:00:03.413548 SharedFolders host service: Adding host mapping
    00:00:03.413564 Host path '\?\C:\Dashboard\Workspace\vagrant\homestead', map name 'vagrant', writable, automount=false, automntpnt=, create_symlinks=true, missing=false
    00:00:03.414391 Changing the VM state from 'CREATED' to 'POWERING_ON'
    00:00:03.414535 AIOMgr: Endpoints without assigned bandwidth groups:
    00:00:03.414556 AIOMgr: C:\Users\ghost\VirtualBox VMs\homestead\ubuntu-20.04-amd64-disk001.vmdk
    00:00:03.414880 Changing the VM state from 'POWERING_ON' to 'RUNNING'
    00:00:03.414905 Console: Machine state changed to 'Running'
    00:00:03.420925 VMMDev: Guest Log: BIOS: VirtualBox 6.1.10
    00:00:03.421292 PCI: Setting up resources and interrupts
    00:00:03.442243 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
    00:00:03.453650 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
    00:00:03.465650 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
    00:00:03.498725 VMMDev: Guest Log: CPUID EDX: 0x178bfbff
    00:00:03.501896 AHCI#0: Reset the HBA
    00:00:03.501918 VD#0: Cancelling all active requests
    00:00:03.502328 AHCI#0: Port 0 reset
    00:00:03.502400 VD#0: Cancelling all active requests
    00:00:03.504496 VMMDev: Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 0x0000000040000000 sectors
    00:00:03.518031 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
    00:00:03.519347 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000006b50000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
    00:00:05.355824 NAT: Old socket recv size: 64KB
    00:00:05.355863 NAT: Old socket send size: 64KB
    00:00:05.999713 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
    00:00:06.015907 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
    00:00:06.016702 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0032
    00:00:06.018399 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
    00:00:06.176131 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=81
    00:00:06.179167 VMMDev: Guest Log: int13_harddisk: function 00, unmapped device for ELDL=81
    00:00:06.182116 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=81
    00:00:06.185177 VMMDev: Guest Log: int13_harddisk: function 00, unmapped device for ELDL=81
    00:00:06.188234 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=81
    00:00:06.191194 VMMDev: Guest Log: int13_harddisk: function 00, unmapped device for ELDL=81
    00:00:07.181246 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000006b50000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
    00:00:13.851770 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
    00:00:16.030195 GIM: KVM: VCPU 0: Enabled system-time struct. at 0x0000000010001000 - u32TscScale=0x804a6fdd i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x0 uVirtNanoTS=0x0
    00:00:16.030233 TM: Host/VM is not suitable for using TSC mode 'RealTscOffset', request to change TSC mode ignored
    00:00:16.166319 GIM: KVM: Enabled wall-clock struct. at 0x0000000010000000 - u32Sec=1594387259 u32Nano=115290300 uVersion=2
    00:00:16.249854 PIT: mode=2 count=0x12a5 (4773) - 249.98 Hz (ch=0)
    00:00:16.278282 MsrExit/0: 0010:ffffffffa44788e8/LM: RDMSR 00000140 -> 00000000 / VERR_CPUM_RAISE_GP_0
    STUCK HERE
    alexk345
    @alexk345
    tried another laravel...
    same issue

    λ vagrant up
    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Box 'sternpunkt/jimmybox' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
    ==> default: Loading metadata for box 'sternpunkt/jimmybox'
    default: URL: https://vagrantcloud.com/sternpunkt/jimmybox
    ==> default: Adding box 'sternpunkt/jimmybox' (v3.0.2) for provider: virtualbox
    default: Downloading: https://vagrantcloud.com/sternpunkt/boxes/jimmybox/versions/3.0.2/providers/virtualbox.box
    Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
    default:
    ==> default: Successfully added box 'sternpunkt/jimmybox' (v3.0.2) for 'virtualbox'!
    ==> default: Importing base box 'sternpunkt/jimmybox'...
    ==> default: Matching MAC address for NAT networking...
    ==> default: Checking if box 'sternpunkt/jimmybox' version '3.0.2' is up to date...
    ==> default: Setting the name of the VM: homestead_default_1594389351893_24926
    ==> default: Clearing any previously set network interfaces...
    ==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    ==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
    ==> default: Booting VM...
    ==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    Timed out while waiting for the machine to boot. This means that
    Vagrant was unable to communicate with the guest machine within
    the configured ("config.vm.boot_timeout" value) time period.

    If you look above, you should be able to see the error(s) that
    Vagrant had when attempting to connect to the machine. These errors
    are usually good hints as to what may be wrong.

    If you're using a custom box, make sure that networking is properly
    working and you're able to connect to the machine. It is a common
    problem that networking isn't setup properly in these boxes.
    Verify that authentication configurations are also setup properly,
    as well.

    If the box appears to be booting properly, you may want to increase
    the timeout ("config.vm.boot_timeout") value.