Skip to content

Instantly share code, notes, and snippets.

@simonsd
Created December 3, 2011 22:39
Show Gist options
  • Select an option

  • Save simonsd/1428377 to your computer and use it in GitHub Desktop.

Select an option

Save simonsd/1428377 to your computer and use it in GitHub Desktop.
veewee kvm vnc error
[root@shinku veewee]# veewee kvm build arch -f
WARNING: gnome-keyring:: no socket to connect to
Building Box arch with Definition arch:
- postinstall_include : []
- postinstall_exclude : []
- force : true
The isofile archlinux-2011.08.19-netinstall-x86_64.iso already exists.
Waiting 5 seconds for the machine to boot
Received port hint - 7122
Found port 7122 available
Sending keystrokes to VNC port :-5901 - TCP port: -1
/home/crasher/tmp/veewee/lib/net/vnc/vnc.rb:108:in `initialize': Connection refused - connect(2) (Errno::ECONNREFUSED)
from /home/crasher/tmp/veewee/lib/net/vnc/vnc.rb:108:in `open'
from /home/crasher/tmp/veewee/lib/net/vnc/vnc.rb:108:in `connect'
from /home/crasher/tmp/veewee/lib/net/vnc/vnc.rb:85:in `initialize'
from /home/crasher/tmp/veewee/lib/net/vnc/vnc.rb:91:in `new'
from /home/crasher/tmp/veewee/lib/net/vnc/vnc.rb:91:in `open'
from /home/crasher/tmp/veewee/lib/veewee/provider/core/box/vnc.rb:15:in `vnc_type'
from /home/crasher/tmp/veewee/lib/veewee/provider/kvm/box.rb:36:in `console_type'
from /home/crasher/tmp/veewee/lib/veewee/provider/core/box/build.rb:63:in `build'
from /home/crasher/tmp/veewee/lib/veewee/command/kvm.rb:16:in `build'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/gems/thor-0.14.6/lib/thor/invocation.rb:109:in `invoke'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/gems/thor-0.14.6/lib/thor.rb:205:in `block in subcommand'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/gems/thor-0.14.6/lib/thor/base.rb:389:in `start'
from /home/crasher/tmp/veewee/bin/veewee:18:in `<top (required)>'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/bin/veewee:19:in `load'
from /home/crasher/tmp/veewee/ruby-libvirt/ruby/1.9.1/bin/veewee:19:in `<main>'
@karel1980
Copy link

Did you ever find what's causing this error? (Seeing the same thing)

@simonsd
Copy link
Author

simonsd commented Feb 6, 2012

sorry, can't remember it actually.
First things that come to mind would be checking the kvm kmods.
Tried looking for an issue where I might have attached the gist, but no such luck.

@simonsd
Copy link
Author

simonsd commented Feb 6, 2012

Can you give me some more info about your setup?

  • vagrant version
  • veewee version
  • kvm version
  • cpu model
  • distro
  • architecture

Might be able to help us forward a bit.

@karel1980
Copy link

Hey sorry, I don't know what was wrong either. I rebooted to double check virtualisation was turned on in my bios (it was), and after the reboot it just started working again.
In case you still want to do something with the info:
veewee from trunk (just updated an hour ago).
qemu-kvm=0.14.1+noroms-0ubuntu6.2
cpu model name (from /proc/cpuinfo) = Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
distro=ubuntu oneiric on 64bit arch (dell M4600 precision)

@simonsd
Copy link
Author

simonsd commented Feb 6, 2012

Hmm I suppose it could indeed have been the kmods.
If you just installed kvm and didn't reboot before trying, the kmods might not have been loaded automatically.
On ubuntu they probably autoload the kmods for kvm, so by rebooting the kmods were inserted and everything starts working.

Perhaps if someone else runs into this issue they can comment.
Or you could try manually unloading the kmods once and see if the problem surfaces again.

@karel1980
Copy link

karel1980 commented Feb 9, 2012 via email

@flomotlik
Copy link

Any idea what the problem may be? I got basically the same specs as karel above.

I uninstalled virtualbox and restarted to be sure it is gone and the modules are loaded correctly.

@karel1980
Copy link

karel1980 commented Feb 12, 2012 via email

@flomotlik
Copy link

INFO: /dev/kvm exists
KVM acceleration can be used

just tried creating a new VM via virt-manager and I get the same error. Seems to be something with my KVM setup. Will investigate further and see if I can find the problem.

@simonsd
Copy link
Author

simonsd commented Feb 13, 2012

@flomotik: iirc you can't use kvm and virtualbox at the same time.
try unloading the vbox kernel mods if you have those set up.
Otherwise, check the kvm wiki for archlinux, pretty well written though the pkg names will probably be different for your distro.
https://wiki.archlinux.org/index.php/KVM

@flomotlik
Copy link

Got it working now for KVM and Ubuntu 11.10.

The file needs to begin with "Veewee::Definition.declare({" instead of "Veewee::Session.declare({"

I will create a pull request for the definition.rb changes I did to get it working.

Do you know is there a way to take a snapshot before postinstall scripts are run and when creating the virtual machine the next time use the snapshot?

I am rebuilding the machine quite often and it would be nice to automatically prepare a basemachine that i can use to run the postinstall scripts in. Of course I could simply copy the image to somewhere else and run the scripts via ssh, but it would be nice to have all of that done via veewee.

Vagrant isn't really an option as I want it to work with KVM for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment