osuosl / vagrant-ganeti

Vagrant files for a Ganeti tutorial and/or Ganeti testing environment
28 stars 13 forks source link

ganeti 2.11.3 incompatible kvm_path=/usr/bin/qemu-system-x86_64 #14

Open zeph opened 10 years ago

zeph commented 10 years ago

it seems that spawning machines on ganeti 2.11.3 within a virtualbox "node" is not possible, as somehow qemu/KVM is than having as mandatory the hw-acceleration

I created my own vagrant gentoo image, and with ganeti 2.11.3 it failed while I succeded merging ganeti 2.7.2 ... I need to investigate what's the change

 node1 ganeti # gnt-instance start instance1 
 Waiting for job 16 for instance1.v ... 
 Job 16 for instance1.v has failed: Failure: prerequisites not met for 
 this operation: 
 Could not start instance '%s': Hypervisor error: Failed to start 
 instance instance1.v: exited with exit code 1 (Could not access KVM 
 kernel module: No such file or directory 
 failed to initialize KVM: No such file or directory 
 ) 

initially discussed on ganeti's ML at https://groups.google.com/forum/#!topic/ganeti/pdBD8p18irk

candlerb commented 9 years ago

Virtualbox does not emulate VT-x, therefore you cannot run KVM within a Virtualbox VM.

If you are just demonstrating/testing Ganeti, then set:

gnt-cluster modify -H kvm:kvm_path=/usr/bin/qemu-system-x86_64

and you will get QEMU software emulation instead of KVM. It runs 10 to 20 times slower than normal emulation, so is useless for production, but may be good enough for test or demonstration use. You can live-migrate these slow VMs for example.

Alternatively, run your VM inside something other than Virtualbox - VMware for instance.