{"action":"created","issue":{"url":"https://api.github.com/repos/hashicorp/vagrant/issues/9180","repository_url":"https://api.github.com/repos/hashicorp/vagrant","labels_url":"https://api.github.com/repos/hashicorp/vagrant/issues/9180/labels{/name}","comments_url":"https://api.github.com/repos/hashicorp/vagrant/issues/9180/comments","events_url":"https://api.github.com/repos/hashicorp/vagrant/issues/9180/events","html_url":"https://github.com/hashicorp/vagrant/issues/9180","id":273470802,"number":9180,"title":"vagrant ssh stuck","user":{"login":"houami","id":2004915,"avatar_url":"https://avatars2.githubusercontent.com/u/2004915?v=4","gravatar_id":"","url":"https://api.github.com/users/houami","html_url":"https://github.com/houami","followers_url":"https://api.github.com/users/houami/followers","following_url":"https://api.github.com/users/houami/following{/other_user}","gists_url":"https://api.github.com/users/houami/gists{/gist_id}","starred_url":"https://api.github.com/users/houami/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/houami/subscriptions","organizations_url":"https://api.github.com/users/houami/orgs","repos_url":"https://api.github.com/users/houami/repos","events_url":"https://api.github.com/users/houami/events{/privacy}","received_events_url":"https://api.github.com/users/houami/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-11-13T15:31:15Z","updated_at":"2017-11-29T06:38:48Z","closed_at":"2017-11-13T17:27:52Z","author_association":"NONE","body":"Please note that the Vagrant issue tracker is reserved for bug reports and\r\nenhancements. For general usage questions, please use the Vagrant mailing list:\r\nhttps://groups.google.com/forum/#!forum/vagrant-up. Thank you!\r\n\r\n### Vagrant version\r\nRun `vagrant -v` to show the version. If you are not running the latest version\r\nof Vagrant, please upgrade before submitting an issue.\r\n$ vagrant --version\r\nVagrant 2.0.1\r\n\r\n\r\n### Host operating system\r\nThis is the operating system that you run locally.\r\nWindows 8 \r\n\r\n### Guest operating system\r\nThis is the operating system you run in the virtual machine.\r\ncentos7\r\n\r\n### Vagrantfile\r\n```ruby\r\n# Copy-paste your Vagrantfile here\r\n# -*- mode: ruby -*-\r\n# vi: set ft=ruby :\r\n\r\n# All Vagrant configuration is done below. The \"2\" in Vagrant.configure\r\n# configures the configuration version (we support older styles for\r\n# backwards compatibility). Please don't change it unless you know what\r\n# you're doing.\r\nVagrant.configure(\"2\") do |config|\r\n  # The most common configuration options are documented and commented below.\r\n  # For a complete reference, please see the online documentation at\r\n  # https://docs.vagrantup.com.\r\n\r\n  # Every Vagrant development environment requires a box. You can search for\r\n  # boxes at https://vagrantcloud.com/search.\r\n  config.vm.box = \"bento/centos-7.2\"\r\n\r\n  # Disable automatic box update checking. If you disable this, then\r\n  # boxes will only be checked for updates when the user runs\r\n  # `vagrant box outdated`. This is not recommended.\r\n  # config.vm.box_check_update = false\r\n\r\n  # Create a forwarded port mapping which allows access to a specific port\r\n  # within the machine from a port on the host machine. In the example below,\r\n  # accessing \"localhost:8080\" will access port 80 on the guest machine.\r\n  # NOTE: This will enable public access to the opened port\r\n  # config.vm.network \"forwarded_port\", guest: 80, host: 8080\r\n\r\n  # Create a forwarded port mapping which allows access to a specific port\r\n  # within the machine from a port on the host machine and only allow access\r\n  # via 127.0.0.1 to disable public access\r\n  # config.vm.network \"forwarded_port\", guest: 80, host: 8080, host_ip: \"127.0.0.1\"\r\n\r\n  # Create a private network, which allows host-only access to the machine\r\n  # using a specific IP.\r\n  # config.vm.network \"private_network\", ip: \"192.168.33.10\"\r\n\r\n  # Create a public network, which generally matched to bridged network.\r\n  # Bridged networks make the machine appear as another physical device on\r\n  # your network.\r\n  # config.vm.network \"public_network\"\r\n\r\n  # Share an additional folder to the guest VM. The first argument is\r\n  # the path on the host to the actual folder. The second argument is\r\n  # the path on the guest to mount the folder. And the optional third\r\n  # argument is a set of non-required options.\r\n  # config.vm.synced_folder \"../data\", \"/vagrant_data\"\r\n\r\n  # Provider-specific configuration so you can fine-tune various\r\n  # backing providers for Vagrant. These expose provider-specific options.\r\n  # Example for VirtualBox:\r\n  #\r\n  # config.vm.provider \"virtualbox\" do |vb|\r\n  #   # Display the VirtualBox GUI when booting the machine\r\n  #   vb.gui = true\r\n  #\r\n  #   # Customize the amount of memory on the VM:\r\n  #   vb.memory = \"1024\"\r\n  # end\r\n  #\r\n  # View the documentation for the provider you are using for more\r\n  # information on available options.\r\n\r\n  # Enable provisioning with a shell script. Additional provisioners such as\r\n  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the\r\n  # documentation for more information about their specific syntax and use.\r\n  # config.vm.provision \"shell\", inline: <<-SHELL\r\n  #   apt-get update\r\n  #   apt-get install -y apache2\r\n  # SHELL\r\nend\r\n\r\n```\r\n\r\nPlease note, if you are using Homestead or a different Vagrantfile format, we\r\nmay be unable to assist with your issue. Try to reproduce the issue using a\r\nvanilla Vagrantfile first.\r\n\r\n### Debug output\r\nProvide a link to a GitHub Gist containing the complete debug output:\r\nhttps://www.vagrantup.com/docs/other/debugging.html. The debug output should\r\nbe very long. Do NOT paste the debug output in the issue, just paste the\r\nlink to the Gist.\r\n```\r\n$vagrant up;vagrant ssh\r\nBringing machine 'default' up with 'virtualbox' provider...\r\n==> default: Checking if box 'bento/centos-7.2' is up to date...\r\n==> default: Clearing any previously set forwarded ports...\r\n==> default: Clearing any previously set network interfaces...\r\n==> default: Preparing network interfaces based on configuration...\r\n    default: Adapter 1: nat\r\n==> default: Forwarding ports...\r\n    default: 22 (guest) => 2222 (host) (adapter 1)\r\n==> default: Booting VM...\r\n==> default: Waiting for machine to boot. This may take a few minutes...\r\n    default: SSH address: 127.0.0.1:2222\r\n    default: SSH username: vagrant\r\n    default: SSH auth method: private key\r\n==> default: Machine booted and ready!\r\n[default] No installation found.\r\nLoaded plugins: fastestmirror\r\nLoading mirror speeds from cached hostfile\r\n * base: ftp.iitm.ac.in\r\n * extras: ftp.iitm.ac.in\r\n * updates: ftp.iitm.ac.in\r\nNo package kernel-devel-3.10.0-327.el7.x86_64 available.\r\nPackage gcc-4.8.5-16.el7.x86_64 already installed and latest version\r\nPackage binutils-2.25.1-32.base.el7_4.1.x86_64 already installed and latest version\r\nPackage 1:make-3.82-23.el7.x86_64 already installed and latest version\r\nPackage 4:perl-5.16.3-292.el7.x86_64 already installed and latest version\r\nPackage bzip2-1.0.6-13.el7.x86_64 already installed and latest version\r\nNothing to do\r\nCopy iso file C:\\Program Files\\Oracle\\VirtualBox\\VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso\r\nMounting Virtualbox Guest Additions ISO to: /mnt\r\nmount: /dev/loop0 is write-protected, mounting read-only\r\nInstalling Virtualbox Guest Additions 5.1.30 - guest version is unknown\r\nVerifying archive integrity... All good.\r\nUncompressing VirtualBox 5.1.30 Guest Additions for Linux...........\r\nVirtualBox Guest Additions installer\r\nRemoving installed version 5.1.30 of VirtualBox Guest Additions...\r\nCopying additional installer modules ...\r\nInstalling additional modules ...\r\nvboxadd.sh: Starting the VirtualBox Guest Additions.\r\nFailed to set up service vboxadd, please check the log file\r\n/var/log/VBoxGuestAdditions.log for details.\r\nAn error occurred during installation of VirtualBox Guest Additions 5.1.30. Some functionality may not work as intended.\r\nIn most cases it is OK that the \"Window System drivers\" installation failed.\r\nRedirecting to /bin/systemctl start  vboxadd.service\r\nJob for vboxadd.service failed because the control process exited with error code. See \"systemctl status vboxadd.service\" and \"journalctl -xe\" for details.\r\nUnmounting Virtualbox Guest Additions ISO from: /mnt\r\n==> default: Checking for guest additions in VM...\r\n    default: No guest additions were detected on the base box for this VM! Guest\r\n    default: additions are required for forwarded ports, shared folders, host only\r\n    default: networking, and more. If SSH fails on this machine, please install\r\n    default: the guest additions and repackage the box to continue.\r\n    default:\r\n    default: This is not an error message; everything may continue to work properly,\r\n    default: in which case you may ignore this message.\r\n==> default: Mounting shared folders...\r\n    default: /vagrant => D:/vagrantboxes/bento_centos7.2\r\nVagrant was unable to mount VirtualBox shared folders. This is usually\r\nbecause the filesystem \"vboxsf\" is not available. This filesystem is\r\nmade available via the VirtualBox Guest Additions and kernel module.\r\nPlease verify that these guest additions are properly installed in the\r\nguest. This is not a bug in Vagrant and is usually caused by a faulty\r\nVagrant box. For context, the command attempted was:\r\n\r\nmount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant\r\n\r\nThe error output from the command was:\r\n\r\n/sbin/mount.vboxsf: mounting failed with the error: No such device\r\n```\r\n\r\n`$ vagrant ssh\r\n\r\n`\r\n^ does nothing\r\n\r\n\r\n### Expected behavior\r\nWhat should have happened?\r\nto ssh\r\n### Actual behavior\r\nWhat actually happened?\r\n\r\n### Steps to reproduce\r\n1.$ vboxmanage --version\r\n5.1.30r118389\r\n\r\n2.\r\n3.\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/hashicorp/vagrant/issues/comments/347767433","html_url":"https://github.com/hashicorp/vagrant/issues/9180#issuecomment-347767433","issue_url":"https://api.github.com/repos/hashicorp/vagrant/issues/9180","id":347767433,"user":{"login":"Artistan","id":801349,"avatar_url":"https://avatars3.githubusercontent.com/u/801349?v=4","gravatar_id":"","url":"https://api.github.com/users/Artistan","html_url":"https://github.com/Artistan","followers_url":"https://api.github.com/users/Artistan/followers","following_url":"https://api.github.com/users/Artistan/following{/other_user}","gists_url":"https://api.github.com/users/Artistan/gists{/gist_id}","starred_url":"https://api.github.com/users/Artistan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Artistan/subscriptions","organizations_url":"https://api.github.com/users/Artistan/orgs","repos_url":"https://api.github.com/users/Artistan/repos","events_url":"https://api.github.com/users/Artistan/events{/privacy}","received_events_url":"https://api.github.com/users/Artistan/received_events","type":"User","site_admin":false},"created_at":"2017-11-29T06:38:48Z","updated_at":"2017-11-29T06:38:48Z","author_association":"NONE","body":"the other post is relative to vagrant ssh, this one is due to not even finishing the installation.\r\n`/sbin/mount.vboxsf: mounting failed with the error: No such device`\r\n\r\nI had the same issue as this post\r\nhttps://gist.github.com/Artistan/199c8b6c988ad9c20fbeda5dc8218b24\r\n\r\nThis solution worked for me https://github.com/Artistan/homestead-builder\r\n\r\nbasically, build a homestead virtualbox.box with your local settings all up to date. It ended up being a virtual box guest additions issue with bindfs on my mac.\r\n\r\nMore details on the errors I found ... all the way down to the bento box https://github.com/chef/bento/issues/944"}}
{"actor":{"display_login":"Artistan"}}