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.

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

NoMethodError during 'vagrant up' #161

Closed
roman-holovin opened this issue Feb 27, 2014 · 22 comments

Comments

Projects
None yet
3 participants
@roman-holovin
Copy link

commented Feb 27, 2014

Bringing machine 'default' up with 'kvm' provider...
/home/dantix/.vagrant.d/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/driver/driver.rb:270:in `init_storage_directory': undefined method `active?' for #<Libvirt::StoragePool:0x00000003073660> (NoMethodError)

Well, I looked up in documentation - there is such method. So I wrote simple script

require "libvirt"

conn = Libvirt::open("qemu:///system")
pool = conn.lookup_storage_pool_by_name("vagrant")

puts pool.active?

I've run it with my system ruby and it printed "true" as it should. My pool configuration looks like this:

virsh pool-list
 Name                 State      Autostart 
-------------------------------------------
 vagrant              active     no        

Any suggestions how to make it work?

@roman-holovin

This comment has been minimized.

Copy link
Author

commented Feb 28, 2014

Resolved by adding some missing defines in ruby-libvirtd and rebuilding it

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 1, 2014

@Dantix -

Can you please share your solution with us? I ran into the same problem in Arch Linux.

Thanks!

@roman-holovin

This comment has been minimized.

Copy link
Author

commented Mar 1, 2014

@tatsuya6502, I have patched vagrant's copy of ruby-libvirt, but now I know that there is no real need in it. You can install "ruby-libvirt" package from AUR and replace vagrant's ruby-libvirt with it.

yaourt -S ruby-libvirt

pacman -Ql ruby-libvirt

Vagrant's copy can be found here - ~/.vagrant.d/gems/gems

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 1, 2014

You can install "ruby-libvirt" package from AUR and replace vagrant's ruby-libvirt with it.

@Dantix, thanks a lot! It solved the problem. It seems AUR is just a plain ruby-libvirt 0.5.2 (PKGBUILD), so I think we will need ruby-libvirt 0.5.2 on any Linux distributions to run vagrant-kvm against the latest libvirtd (1.2.1).

/home/tatsuya% uname -srv  
Linux 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014
/home/tatsuya% libvirtd --version
libvirtd (libvirt) 1.2.1
/home/tatsuya% ls -ld ~/.vagrant.d/gems/gems/ruby-libvirt-*     
drwxr-xr-x 5 tatsuya users 4096 Mar  1 21:53 /home/tatsuya/.vagrant.d/gems/gems/ruby-libvirt-0.5.2
@miurahr

This comment has been minimized.

Copy link
Collaborator

commented Mar 2, 2014

We are planed to keep ruby-libvirt 0.4.0 in release 0.1.5, and update it to 0.5.2 in vagrant-kvm 0.1.6 and after.
Is it better to update it now?

I've already used ruby-libvirt 0.5.2, and it works fine in my development tree(https://github.com/miurahr/vagrant-kvm/tree/next) for 0.1.6.
Unfortunately it is not good quality assurance for production test because I use qemu 1.7.x, libvirt 1.1.1 backported(https://launchpad.net/~miurahr/+archive/vagrant-devel) on Ubuntu Precise.

It may be necessary to prepare a test environment for ArchLinux.

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 3, 2014

We are planed to keep ruby-libvirt 0.4.0 in release 0.1.5, and
update it to 0.5.2 in vagrant-kvm 0.1.6 and after.
Is it better to update it now?
...
It may be necessary to prepare a test environment for ArchLinux.

Thanks, but I think we don't have to rush this. At this moment, this only seem to affect Arch Linux who has a newer version of libvirt. And this one is easy to fix at user side.

I would prefer to have vagrant-kvm 0.1.5 released very soon (without upgrading ruby-libvirt to 0.5.2), because 0.1.4 does not support latest Vagrant 1.4.x (#158). I think #158 has more impact to users than this.

@miurahr

This comment has been minimized.

Copy link
Collaborator

commented Mar 24, 2014

Now you can test with master HEAD, 0.1.6dev, that is using ruby-libvirt 0.5.2.

@miurahr miurahr modified the milestones: 0.2.0, 0.1.6 Mar 24, 2014

@miurahr

This comment has been minimized.

Copy link
Collaborator

commented Mar 24, 2014

Need some document for Arch user.
Anyone want to contribute it?

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 24, 2014

Now you can test with master HEAD, 0.1.6dev, that is using ruby-libvirt 0.5.2.

@miurahr - Thanks. I'm playing with Veewee now for creating an Arch box. Once I'm done with it, I can test 0.1.6-dev. Also, I'm thinking to contribute a Vagrantfile for the Arch box that acts as a vagrant-kvm host (like the ones for Ubuntu and Fedora under the spec directory) so that anyone can test it.

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 24, 2014

Need some document for Arch user.
Anyone want to contribute it?

I could work on that. What kind of docs do you need?

@miurahr

This comment has been minimized.

Copy link
Collaborator

commented Mar 24, 2014

so I think we will need ruby-libvirt 0.5.2 on any Linux distributions to run vagrant-kvm against the >latest libvirtd (1.2.1).

It is worth providing to users. Arch use it. Ubuntu Trusty(14.04) also bundle libvirt 1.2.1.
Those who want to use vagrant-kvm on such OSes, are recommended to try vagrant-kvm 0.1.6 and later.

or consult work around with vagrant-kvm 0.1.5.x. such as downloading source, edit gemspec, build gem and install using local build package.

@miurahr

This comment has been minimized.

Copy link
Collaborator

commented Mar 25, 2014

sorry ubuntu trusty use libvirt 1.2.2.

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 25, 2014

so I think we will need ruby-libvirt 0.5.2 on any Linux
distributions to run vagrant-kvm against the latest libvirtd (1.2.1).

It is worth providing to users. Arch use it. Ubuntu Trusty(14.04)
also bundle libvirt 1.2.1. Those who want to use vagrant-kvm on such
OSes, are recommended to try vagrant-kvm 0.1.6 and later.

or consult work around with vagrant-kvm 0.1.5.x. such as downloading
source, edit gemspec, build gem and install using local build
package.

OK. Got it.

A quick update -- I tried vagrant-kvm 0.1.6.dev on Arch Linux but the problem remains. So this should not be a ruby-libvirt version issue but would be an Arch specific installation issue. More on next comment.

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 26, 2014

I used Veewee to create an Arch base box with the latest packages and tested vagrant-kvm 0.1.6.dev on that virtual machine (nested KVM). Like Ubuntu 14.04 beta, libvirt version was 1.2.2 and I verified that vagrant-kvm installed ruby-libvirt 0.5.2 under $HOME/.vagrant.d/gems/gems.

But I was surprised because this does not solve the problem in the first comment. So this does not seem a ruby-libvirt version issue (0.4.0 vs 0.5.2) anymore. (Although we still need to check whether vagrant-kvm 0.1.5 with ruby-libvirt 0.4.0 works on Ubuntu 14.04 with libvirt 1.2.2 or not.)

Then I installed ruby-libvirt package from AUR (Arch User Repository) and compared its contents against the one installed by vagrant-kvm. I found that extconf.h files are different. As you can see, the earlier one does not define 'storage pool is active' API.

ruby-libvirt 0.5.2 installed by vagrant-kvm

[vagrant@default ~]$ grep ACTIVE ~/.vagrant.d/gems/gems/ruby-libvirt-0.5.2/ext/libvirt/extconf.h
#define HAVE_CONST_VIR_INTERFACE_XML_INACTIVE 1
#define HAVE_CONST_VIR_DOMAIN_SNAPSHOT_LIST_INACTIVE 1
#define HAVE_CONST_VIR_NETWORK_XML_INACTIVE 1
#define HAVE_CONST_VIR_STORAGE_XML_INACTIVE 1

ruby-libvirt 0.5.2 from AUR

[vagrant@default ~]$ grep ACTIVE /lib/ruby/gems/2.1.0/gems/ruby-libvirt-0.5.2/ext/libvirt/extconf.h
#define HAVE_VIRSTORAGEPOOLISACTIVE 1
#define HAVE_VIRNETWORKISACTIVE 1
#define HAVE_VIRINTERFACEISACTIVE 1
#define HAVE_VIRDOMAINISACTIVE 1
#define HAVE_CONST_VIR_INTERFACE_XML_INACTIVE 1
#define HAVE_CONST_VIR_DOMAIN_SNAPSHOT_LIST_INACTIVE 1
#define HAVE_CONST_VIR_NETWORK_XML_INACTIVE 1
#define HAVE_CONST_VIR_STORAGE_XML_INACTIVE 1

extconf.h seems auto-generated by this file at install time using the header files of libvirt library available in the system.

When I installed vagrant-kvm, I added CONFIGURE_ARGS for ruby-libvirt (otherwise installation will fail). This command is documented in this Arch Wiki article.

$ CONFIGURE_ARGS="with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib" \
  vagrant plugin install vagrant-kvm-0.1.6.dev.gem

I will look into this issue, and try to figure out the root cause and a solution.

Also if anybody could test the current release version vagrant-kvm 0.1.5 against Ubuntu 14.04 beta, that would be great.

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 27, 2014

extconf.h seems auto-generated by this file at install time using the header files of
libvirt library available in the system.

When I installed vagrant-kvm, I added CONFIGURE_ARGS for ruby-libvirt (otherwise
installation will fail). This command is documented in this Arch Wiki article.

$ CONFIGURE_ARGS="with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib" \
 vagrant plugin install vagrant-kvm-0.1.6.dev.gem

Have to take a closer look at this. It will explain how extconf.rb misses HAVE_VIRSTORAGEPOOLISACTIVE

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 27, 2014

Here is what is happening on Arch Linux.

libvirt (installed via pacman) is built against the system curl library, but vagrant is trying to use the embedded curl library in /opt/vagrant/embedded/lib/ to build ruby-libvirt. ld does not like this so it exits with 1.

If I try to install vagrant-kvm with this command,

$ vagrant plugin install vagrant-kvm-0.1.6.dev.gem

building ruby-libvirt will fail at pkg_config("libvirt") because of the following ld error:

$ less ~/.vagrant.d/gems/gems/ruby-libvirt-0.5.2/ext/libvirt/mkmf.log

"gcc -o conftest -I/opt/vagrant/embedded/include/ruby-2.0.0/x86_64-linux -I/opt/vagrant/embedded/include/ruby-2.0.0/ruby/backward -I/opt/vagrant/embedded/include/ruby-2.0.0 -I.  -I/vagrant-substrate/staging/embedded/include   -I/vagrant-substrate/staging/embedded/include -fPIC conftest.c  -L. -L/opt/vagrant/embedded/lib -Wl,-R/opt/vagrant/embedded/lib -L/vagrant-substrate/staging/embedded/lib -Wl,-R/vagrant-substrate/staging/embedded/lib -lvirt -ldl     '-Wl,-rpath,/../lib' -Wl,-R -Wl,/opt/vagrant/embedded/lib -L/opt/vagrant/embedded/lib -lruby  -lpthread -lrt -ldl -lcrypt -lm   -lc"
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.2/../../../../lib/libvirt.so: undefined reference to `curl_global_init@CURL_OPENSSL_4'
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.2/../../../../lib/libvirt.so: undefined reference to `curl_multi_cleanup@CURL_OPENSSL_4'
...

collect2: error: ld returned 1 exit status

If I try to install vagrant-kvm with this command,

$ CONFIGURE_ARGS="with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib" \
  vagrant plugin install vagrant-kvm-0.1.6.dev.gem

building ruby-libvirt will not fail but mkmf have_func() call will get a similar ld error and return false. So the auto-generated extconf.h is almost empty and the embedded ruby-libvirt is useless.

$ less ~/.vagrant.d/gems/gems/ruby-libvirt-0.5.2/ext/libvirt/mkmf.log

...
have_func: checking for virStoragePoolIsActive() in libvirt/libvirt.h... -------------------- no

"gcc -o conftest -I/opt/vagrant/embedded/include/ruby-2.0.0/x86_64-linux -I/opt/vagrant/embedded/include/ruby-2.0.0/ruby/backward -I/opt/vagrant/embedded/include/ruby-2.0.0 -I.  -I/vagrant-substrate/staging/embedded/include   -I/usr/include -I/vagrant-substrate/staging/embedded/include -fPIC conftest.c  -L/usr/lib -Wl,-R/usr/lib -L/vagrant-substrate/staging/embedded/lib -Wl,-R/vagrant-substrate/staging/embedded/lib -L. -L/vagrant-substrate/staging/embedded/lib  -fstack-protector -rdynamic -Wl,-export-dynamic -L/vagrant-substrate/staging/embedded/lib  -Wl,-R/vagrant-substrate/staging/embedded/lib      '-Wl,-rpath,/../lib' -Wl,-R -Wl,/opt/vagrant/embedded/lib -L/opt/vagrant/embedded/lib -lruby  -lpthread -lrt -ldl -lcrypt -lm   -lc"
/tmp/cclIhOVD.o: In function `t':
conftest.c:(.text+0x7): undefined reference to `virStoragePoolIsActive'
collect2: error: ld returned 1 exit status

I have not figured out how to make the embedded ruby-libvirt to refer to the system curl library. So for now, workarounds would be:

  • Install ruby-libvirt from AUR, and copy it to ~/.vagrant/gems/gems/. This workaround is explained in this comment.
  • Or, temporary rename the embedded curl library to something else. Install vagrant-kvm (with ruby-libvirt) and then rename the curl library back to its original name. This workaround is explained here.
@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 27, 2014

Also if anybody could test the current release version vagrant-kvm 0.1.5
against Ubuntu 14.04 beta, that would be great.

No volunteers?

@roman-holovin

This comment has been minimized.

Copy link
Author

commented Mar 27, 2014

Will do in few hours

UPD: Seems like "not today"

@tatsuya6502

This comment has been minimized.

Copy link

commented Mar 27, 2014

@Dantix - Thank you!

@tatsuya6502

This comment has been minimized.

Copy link

commented Apr 10, 2014

Also if anybody could test the current release version vagrant-kvm 0.1.5
against Ubuntu 14.04 beta, that would be great.

I tested Vagrant 1.5.2 + vagrant-kvm 0.1.6 against Ubuntu 14.04 beta 2, and verified it worked. So this is an Arch Linux specific issue and the workarounds on this comment should work.

@miurahr, @adrahon please close this issue. I will get the workarounds documented in the Wiki (not Arch Wiki but vagrant-kvm Wiki).

Tested Version:

  • Ubuntu 14.04 "Trusty Tahr" Beta 2 Desktop
  • Vagrant 1.5.2
  • vagrant-kvm 0.1.6
  • libvirt 1.2.2

Result:

  • Passed
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ uname -a
Linux vagkvm-u2 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)"
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ libvirtd -V
libvirtd (libvirt) 1.2.2
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ vagrant -v
Vagrant 1.5.2
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ vagrant plugin list
vagrant-kvm (0.1.6)
vagrant-login (1.0.1, system)
vagrant-share (1.0.1, system)
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ vagrant up --provider=kvm
Bringing machine 'default' up with 'kvm' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

VagrantPlugins::ProviderKvm::Config:
* The following settings shouldn't exist: memory


tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ vi Vagrantfile 
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ git diff
diff --git a/spec/fedora/Vagrantfile b/spec/fedora/Vagrantfile
index 19b7ccd..7c5dd5d 100644
--- a/spec/fedora/Vagrantfile
+++ b/spec/fedora/Vagrantfile
@@ -1,7 +1,7 @@
 Vagrant.configure('2') do |config|
   config.vm.provider :kvm do |kvm, override|
     kvm.gui = true
-    kvm.memory = '512MB'
+    # kvm.memory = '512MB'
     override.vm.box = 'fedora19'
     override.vm.box_url = 'https://vagrant-kvm-boxes.s3.amazonaws.com/fedora19-amd64-kvm.box'
   end
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ vagrant up --provider=kvm
Bringing machine 'default' up with 'kvm' provider...
==> default: Importing base box 'fedora19'...
/home/tatsuya/.vagrant.d/gems/gems/vagrant-kvm-0.1.6/lib/vagrant-kvm/driver/driver.rb:105:in `create_volume': undefined method `create_volume_xml' for nil:NilClass (NoMethodError)
    from /home/tatsuya/.vagrant.d/gems/gems/vagrant-kvm-0.1.6/lib/vagrant-kvm/action/import.rb:111:in `import_volume'
    from /home/tatsuya/.vagrant.d/gems/gems/vagrant-kvm-0.1.6/lib/vagrant-kvm/action/import.rb:57:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/tatsuya/.vagrant.d/gems/gems/vagrant-kvm-0.1.6/lib/vagrant-kvm/action/set_name.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/tatsuya/.vagrant.d/gems/gems/vagrant-kvm-0.1.6/lib/vagrant-kvm/action/init_storage_pool.rb:16:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/tatsuya/.vagrant.d/gems/gems/vagrant-kvm-0.1.6/lib/vagrant-kvm/action/set_name.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/tatsuya/.vagrant.d/gems/gems/vagrant-kvm-0.1.6/lib/vagrant-kvm/action/check_kvm.rb:18:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/action/runner.rb:69:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/machine.rb:157:in `action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/batch_action.rb:72:in `block (2 levels) in run'
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ vagrant up --provider=kvm
Bringing machine 'default' up with 'kvm' provider...
==> default: Importing base box 'fedora19'...
==> default: Matching MAC address for NAT networking...
==> default: Preparing network interfaces based on configuration...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 192.168.123.10:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    ...
    default: Warning: Host unreachable. Retrying...
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.
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ vagrant halt
==> default: Attempting graceful shutdown of VM...
    default: Guest communication could not be established! This is usually because
    default: SSH is not running, the authentication information was changed,
    default: or some other networking issue. Vagrant will force halt, if
    default: capable.
==> default: Forcing shutdown of VM...
[sudo] password for tatsuya: 
tatsuya@vagkvm-u2:~/vagrant-kvm/spec/fedora$ vagrant up
Bringing machine 'default' up with 'kvm' provider...
==> default: Preparing network interfaces based on configuration...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 192.168.123.10:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
    default: Warning: Host unreachable. Retrying...
==> default: Machine booted and ready!
==> default: Creating shared folders metadata...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
nfsd not running
 * Exporting directories for NFS kernel daemon...                                                                                  [ OK ] 
 * Starting NFS kernel daemon                                                                                                      [ OK ] 
==> default: Mounting NFS shared folders...
==> default: Running provisioner: shell...
    default: Running: inline script
++ sudo yum install -y libvirt-daemon-kvm.x86_64
@tatsuya6502

This comment has been minimized.

Copy link

commented Apr 15, 2014

@miurahr, @adrahon please review and close this issue because there is no outstanding tasks. I'm not the one who filed this issue so I can't close it. (there is no "close" button for me).

@miurahr

This comment has been minimized.

Copy link
Collaborator

commented Apr 16, 2014

Confirmed close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.