Hi Intrigeri,
I was able to fix that; VMWare does support passing VT-x to the guest. But now I’m stuck with this IP Address issue. For some reason, the vagrant machine is not capable in getting one. Any idea how to fix this? Below the full output I get - the build stucks while waiting for the IP address. Please note: this is the master branch of the repo, no changes made from my end.
$: rake build
Using HTTP proxy: http://vagrant-stretch:3142
Bringing machine 'default' up with 'libvirt' provider...
==> default: Creating image (snapshot of base box volume).
==> default: Creating domain with the following settings...
==> default: -- Name: tails-builder-amd64-stretch-20180301-2f443fafad_default
==> default: -- Domain type: kvm
==> default: -- Cpus: 1
==> default: -- Memory: 1024M
==> default: -- Management MAC:
==> default: -- Loader:
==> default: -- Base box: tails-builder-amd64-stretch-20180301-2f443fafad
==> default: -- Storage pool: default
==> default: -- Image: /var/lib/libvirt/images/tails-builder-amd64-stretch-20180301-2f443fafad_default.img (20G)
==> default: -- Volume Cache: default
==> default: -- Kernel:
==> default: -- Initrd:
==> default: -- Graphics Type: vnc
==> default: -- Graphics Port: 5900
==> default: -- Graphics IP: 127.0.0.1
==> default: -- Graphics Password: Not defined
==> default: -- Video Type: cirrus
==> default: -- Video VRAM: 9216
==> default: -- Keymap: en-us
==> default: -- TPM Path:
==> default: -- Disks: vdb(qcow2,15G)
==> default: -- Disk(vdb): /var/lib/libvirt/images/apt-cacher-ng-data.qcow2 (Remove only manually) Not created - using existed.
==> default: -- INPUT: type=mouse, bus=ps2
==> default: -- Command line :
==> default: ================
==> default: Machine id: 3a12845b-e5a6-44c9-9d2a-6833d15b5e0f
==> default: Should be mounting folders
==> default: /vagrant, opts: {:type=>:"9p", :readonly=>true, :guestpath=>"/vagrant", :hostpath=>"/home/osboxes/tails/vagrant", :disabled=>false, :__vagrantfile=>true, :target=>"/vagrant", :accessmode=>"passthrough", :mount=>true, :mount_tag=>"2c56346e7960721c6c3f8de5e712c67"}
==> default: ================
==> default: Machine id: 3a12845b-e5a6-44c9-9d2a-6833d15b5e0f
==> default: Should be mounting folders
==> default: /amnesia.git, opts: {:type=>:"9p", :readonly=>true, :guestpath=>"/amnesia.git", :hostpath=>"/home/osboxes/tails", :disabled=>false, :__vagrantfile=>true, :target=>"/amnesia.git", :accessmode=>"passthrough", :mount=>true, :mount_tag=>"87850e485a799696ca30413b1dff3e1"}
==> default: Creating shared folders metadata...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...
> Am 03.06.2018 um 09:57 schrieb intrigeri <intrigeri@???>:
>
> Hi,
>
> Marco Betschart:
>> Got a local VMWare Fusion setup with Debian 9.3 and VT-x enabled on my MacBook
>> (Downloaded from OS-Boxes <https://www.osboxes.org/debian/>).
>
>> There was an error in Libvirt. The error is shown below:
>> Call to virDomainCreateWithFlags failed: internal error: process excited while
>> connecting to monitor: Could not access KVM kernel module: Permission denied failed
>> to initialize KVM: permission denied.
>
> I suspect VMWare does not expose (nested) VT-x capabilities to the
> Debian guest VM which prevents that VM from itself running a VM (as
> part of our build process). So either fix the Vmware VM configuration
> (if that's possible at all) or adjust vagrant/Vagrantfile, e.g.
> this line:
>
> domain.driver = 'kvm'
>
> _______________________________________________
> Tails-dev mailing list
> Tails-dev@???
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to Tails-dev-unsubscribe@???.
