Bug #6356

Fix Vagrant basebox building using veewee and KVM

Added by anonym 2013-10-10 04:57:55 . Updated 2016-02-21 21:33:24 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Build system
Target version:
Start date:
2013-10-10
Due date:
% Done:

100%

Feature Branch:
feature/6354-vagrant-libvirt
Type of work:
Code
Blueprint:

https://tails.boum.org/blueprint/vagrant-libvirt/

Starter:
0
Affected tool:
Deliverable for:

Description

See the blueprint. We have to wait until there’s a new release of veewee, and then there’s some coding to be done.

Subtasks

Related issues

Blocks Tails - Feature #6354: Migrate to vagrant-libvirt Resolved 2014-10-13

History

#1 Updated by BitingBird 2014-06-21 21:36:25

There was a veewee release the 31th october 2013, and none since. Does that release work ?

#2 Updated by BitingBird 2015-01-08 04:28:38

A lot of veewee releases happened since.

#3 Updated by anonym 2015-08-26 09:24:23

An alternative is to use vagrant-mutate to convert the virtualbox basebox to a libvirt one. The easiest would probably be for us to do the conversion and then host the libvirt one too, as opposed to letting the client download the basebox and (automatically) converting it when using libvirt.

#4 Updated by intrigeri 2016-02-21 21:33:24

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • Feature Branch changed from feature/vagrant-libvirt to feature/6354-vagrant-libvirt