Vagrant in Fedora

Alex Drahon adrahon at redhat.com
Thu Oct 17 12:36:46 UTC 2013


On 16/10/13 23:54, Nathanael D. Noblet wrote:
> On 10/15/2013 01:06 PM, Alex Drahon wrote:
>
>> Hope some of you can test it.
>
> After doing a vagrant up --provider=kvm I get prompted via polkit and 
> then the terminal output is as follows:
>
>
> [gnat at iridium kvm]$ vagrant up --provider=kvm
> Bringing machine 'default' up with 'kvm' provider...
> [default] Importing base box 'precise32'...
> WARNING: Nokogiri was built against LibXML version 2.9.0, but has 
> dynamically loaded 2.9.1
> qemu-img: 
> /home/gnat/.vagrant.d/tmp/storage-pool/box-disk1-1381964017.img: error 
> while converting raw: Permission denied
>
> /usr/share/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/driver/driver.rb:145:in 
> `lookup_volume_by_name': Call to virStorageVolLookupByName failed: 
> Storage volume not found: no storage vol with matching name 
> 'box-disk1-1381964017.img' (Libvirt::RetrieveError)
>     from 
> /usr/share/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/driver/driver.rb:145:in 
> `import_ovf'
>     from 
> /usr/share/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/import.rb:27:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/warden.rb:34:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/check_box.rb:31:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/warden.rb:34:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/runner.rb:61:in 
> `block in run'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/util/busy.rb:19:in `busy'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/runner.rb:61:in 
> `run'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/builtin/call.rb:51:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/warden.rb:34:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/init_storage_pool.rb:14:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/warden.rb:34:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/builtin/config_validate.rb:25:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/warden.rb:34:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/set_name.rb:25:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/warden.rb:34:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-kvm-0.1.4/lib/vagrant-kvm/action/check_kvm.rb:18:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/warden.rb:34:in 
> `call'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/builder.rb:116:in `call' 
>
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/runner.rb:61:in 
> `block in run'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/util/busy.rb:19:in `busy'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/action/runner.rb:61:in 
> `run'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/machine.rb:147:in `action'
>     from 
> /usr/share/gems/gems/vagrant-1.3.3/lib/vagrant/batch_action.rb:63:in 
> `block (2 levels) in run'
>
>
OK, what it means is that you got the polkit prompt, which gave you 
access to libvirtd, but then the storage pool in 
/home/gnat/.vagrant.d/tmp/storage-pool/ was created by libvirt with root 
as the owner so when vagrant calls qemu-img (without root privileges) it 
fails. Bad testing on my side again...


More information about the cloud mailing list