Giter VIP home page Giter VIP logo

Comments (5)

p0deje avatar p0deje commented on June 21, 2024

Are you sure you have config.vm.network :private_network, ip: "192.168.192.10" in your Vagrantfile? Looks like you don't.

from vagrant-kvm.

eddyxu avatar eddyxu commented on June 21, 2024

Em, Yes, my bad. But even after I have config.vm.network :private_network, ip: "192.168.192.10" in Vagrantfile,

The following errors have been report as well:

~/work/vagrant-boxes/devbox (master) $ vagrant up  --provider=kvm
Bringing machine 'default' up with 'kvm' provider...
[default] Importing base box 'raring'...
    (100.00/100%)
[default] Matching MAC address for NAT networking...
[default] Preparing network interfaces based on configuration...
[default] Creating shared folders metadata...
[default] Booting VM...
[default] Destroying VM and associated drives...
/home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/driver/driver.rb:238:in `create': Call to virDomainCreateWithFlags failed: unsupported configuration: spicevmc not supported in this QEMU binary (Libvirt::Error)
    from /home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/driver/driver.rb:238:in `start'
    from /home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/action/boot.rb:14:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/set_hostname.rb:16:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/action/share_folders.rb:20:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/action/prepare_nfs_settings.rb:11:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/nfs.rb:28:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/action/prune_nfs_exports.rb:15:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/provision.rb:45:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/action/network.rb:54:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/action/check_kvm.rb:18:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/call.rb:57:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/action/init_storage_pool.rb:14:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/eddyxu/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/lib/vagrant-kvm/action/check_kvm.rb:18:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/machine.rb:147:in `action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'

I've installed qemu-kvm-spice, but there is no difference

$ dpkg -l | grep kvm
ii  kvm-ipxe                                  1.0.0+git-3.55f6c88-0ubuntu5              all          PXE ROM's for KVM
ii  qemu-kvm                                  1.2.0+noroms-0ubuntu2.12.10.3             amd64        Full virtualization on supported hardware
ii  qemu-kvm-spice                            1.2.0-2012.09-0ubuntu1                    amd64        Full virtualization on amd64 hardware

from vagrant-kvm.

adrahon avatar adrahon commented on June 21, 2024

You are hitting this issue #8

You could try removing mentions of spice in the domain template file https://github.com/adrahon/vagrant-kvm/blob/master/templates/libvirt_domain.erb It should be in ~/.vagrant.d/gems/gems/vagrant-kvm-0.1.1/templates

Try removing

<channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>

and

 <graphics type='spice' autoport='yes'/>

If it works we commit it, we don't need spice for Vagrant.

from vagrant-kvm.

eddyxu avatar eddyxu commented on June 21, 2024

After removing those spice related parts, the VM starts correctly.

But it would be better if it does not require NFS to mount /vagrant. My Vagrantfile is on a NFS mounted /home already, which makes it report:

[default] Exporting NFS shared folders...
Preparing to edit /etc/exports. Administrator privileges will be required...

  • Stopping NFS kernel daemon [ OK ]
  • Unexporting directories for NFS kernel daemon... [ OK ]
  • Exporting directories for NFS kernel daemon...
    exportfs: '/home/eddyxu/work/vagrant-boxes/devbox' does not support NFS export
  • Starting NFS kernel daemon [ OK ]
    [default] Mounting NFS shared folders...
    Guest-specific operations were attempted on a machine that is not
    ready for guest communication. This should not happen and a bug
    should be reported.

But it might be another issue though.

from vagrant-kvm.

adrahon avatar adrahon commented on June 21, 2024

I'm going to close this issue as the spice problem is fixed by 544c919

Please open a new issue for NFS, it's going to be a long discussion though ;)

from vagrant-kvm.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.