Bug #16370

isobuilders can't start Vagrant VMs => all ISO builds fail

Added by intrigeri 2019-01-18 06:26:48 . Updated 2019-05-06 18:15:43 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Continuous Integration
Target version:
Tails_3.13.2
Start date:
2019-01-18
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

See e.g. /var/log/libvirt/qemu/tails-builder-amd64-stretch-20190114-e426707444_default.log on isobuilder1.lizard.

I’ve verified that /sys/module/kvm_intel/parameters/nested says Y on lizard.

Subtasks

History

#1 Updated by groente 2019-01-18 15:59:09

  • Status changed from Confirmed to In Progress
  • Priority changed from High to Elevated

it’s definately kernel-related.

rolled back to an older one and nested kvm works again.

#2 Updated by anonym 2019-01-30 11:59:39

  • Target version changed from Tails_3.12 to Tails_3.13

#3 Updated by intrigeri 2019-02-18 15:33:43

In /var/log/libvirt/qemu/tails-builder-amd64-stretch-20190125-e43d76a8c7_default.log on isobuilder1 I see “KVM: entry failed, hardware error 0x7”; this looks a bit like https://lkml.org/lkml/2019/1/22/682 and https://patchwork.kernel.org/patch/10763351/. Older instances of this error seem to be fixable by using a less extreme vcpu configuration; I’ve tried CPU mode host-model (for the Vagrant box) and it did not help.

#4 Updated by CyrilBrulebois 2019-03-20 14:34:11

  • Target version changed from Tails_3.13 to Tails_3.14

#5 Updated by intrigeri 2019-04-29 16:19:04

  • Status changed from In Progress to Resolved
  • Assignee deleted (groente)

It seems that @bertagaz rebooted on 4.19.0-0.bpo.4-amd64 i.e. 4.19.28-2~bpo9+1 and Jenkins builds started since the reboot managed to start Vagrant. Calling this done then! :)

#6 Updated by bertagaz 2019-04-29 18:59:16

intrigeri wrote:
> It seems that @bertagaz rebooted on 4.19.0-0.bpo.4-amd64 i.e. 4.19.28-2~bpo9+1 and Jenkins builds started since the reboot managed to start Vagrant. Calling this done then! :)

Yes, I was willing to wait a bit before reporting on this ticket.

#7 Updated by intrigeri 2019-05-05 08:24:03

  • Target version changed from Tails_3.14 to Tails_3.13.2

#8 Updated by anonym 2019-05-06 15:03:18

  • Target version changed from Tails_3.13.2 to Tails_3.14

#9 Updated by intrigeri 2019-05-06 18:15:43

  • Target version changed from Tails_3.14 to Tails_3.13.2