Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 971
    • Issues 971
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #6354
Closed
Open
Issue created Oct 10, 2013 by anonym@anonymMaintainer4 of 4 checklist items completed4/4 checklist items

Migrate to vagrant-libvirt

Originally created by @anonym on #6354 (Redmine)

Since our test suite uses libvirt/KVM, and our current Vagrant-based build system uses Virtualbox, both cannot be run at the same time (modules have to be switched). We should migrate to using a libvirt/KVM provider via the vagrant-libvirt module.

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

Feature Branch: feature/6354-vagrant-libvirt

Attachments

  • ruby-libvirt-0.5.1.gemspec

Parent Task: #7526 (closed)

Subtasks

  • #8086 (closed)
  • #11153 (closed)
  • #11154 (closed)

Related issues

  • Related to #6212 (closed)
  • Related to #11171
  • Blocked by #6356 (closed)
Edited May 21, 2020 by anonym
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking