Vagrant in Fedora

[Nathanael Noblet]

Sorry for the cross + top post however I figured perhaps -devel folks 
may have some ideas as to what is going on belowl

On 10/17/2013 06:36 AM, Alex Drahon wrote:
> 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)
>>
> 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...

So a couple days ago I started trying to get this working again. 
Something else must be going on. The first problem I had was that 
kvm/libvirt couldn't read .vmdk vagrant images. I converted them to 
qcow2, and then ran vagrant as root. This skips the whole polkit step 
however I get a similar error message as root.

[root at mba Vagrant]# vagrant up --provider=kvm
Bringing machine 'default' up with 'kvm' provider...
[default] Importing base box 'f19'...
qemu-img: /root/.vagrant.d/tmp/storage-pool/box-disk1-1385699731.img: 
error while converting raw: No such file or directory

/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-1385699731.img' (Libvirt::RetrieveError)

So I don't think this is a polkit/libvirt error persay as much as it is 
something isn't creating whatever img its looking for. Anyone have any 
ideas as to what could be causing this issue?

-- 
Nathanael