Hi Intrigeri,
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/>). Took me a while to figure out this is not possible with VirtualBox.
Anyway, I’m now trying to build Tails master branch to figure out if my setup works in general. I’m now running into the following two bummers:
1. Build of master branch fails with the following error
I’m executing as root:
rake build && rake vm:halt
Which aborts with the error:
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.
2. Where to put the additional kernel modules
I’ve seen the HACKING.mdwn - but I not really figured out where and how to apply the instructions of the macbook12-spi-driver <
https://github.com/cb22/macbook12-spi-driver> Can you give a short walk through where to put the changes? Just some bullet points should be enough to get me going.
Thank you very much for your help!!
Marco
> Am 02.06.2018 um 12:39 schrieb intrigeri <intrigeri@???>:
>
> Hi Marco,
> Marco Betschart:
>> Thanks for your feedback. I understand the situation and your
>> proposed steps are absolutely legitimate from a Tails angle.
>
> :)
>
>> What would be the best approach for provide you a patch? I’ve seen
>> https://tails.boum.org/contribute/how/code
>
> Yes, that's the best entry point we have. See also HACKING.mdwn at the
> root of our Git tree, which can also be useful.
>
>> But since I only own my MacBook 12“ I’m not quite sure if it is fast
>> enough to build the whole project
>
> I'm not concerned about that. Worst case it'll take an hour or so to
> build an ISO, which is still manageable (that's what it took me in
> the first couple years of Tails development :)
>
>> and how I would ensure everything is working correctly afterwards?
>
> Assuming your changes are restricted to building an additional dkms
> kernel module, there's little chance they break anything unrelated;
> testing on various computers should be good enough.
>
> But if you're curious you can take a look at our automated test suite:
> https://tails.boum.org/contribute/release_process/test/automated_tests/
>
> Cheers!
