Re: [qubes-project] Hosting for OpenQA instance

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2018-01-26 09:37, Marek Marczykowski-Górecki wrote:
> Hi,
>
> Manual testing of installation is a time consuming job, so I was looking
> for some tool to automate it. And found one:
>
> http://open.qa/
>
> This works by launching the system under test in KVM and then interact
> with it as user would do (mouse clicks, keyboard etc). Then compare
> screenshots (or parts of it).
> The nice thing is when using new new enough KVM, qemu and hardware with
> VT-x + EPT, Qubes installation works there! In theory KVM supports even
> nested virtualization, so HVM should works inside such setup, but in
> practice Xen and/or qemu crashes badly... But PV works fine, which is
> enough for installation testing.
>
> I've uploaded some basic tests here:
> https://github.com/marmarek/openqa-tests-qubesos
>
> The problem is we don't have a place to host it in long run. While I can
> launch it from time to time on one of my testing laptops, it doesn't
> scale well. And access to it is restricted, which limit who can work on
> this (and on issues found by tests).
>
> Does anyone have some place/recommendation where to look? Hardware we
> need:
> - CPU with VT-x + EPT, so KVM will work with reasonable performance (
> means a physical machine, not virtual one)
> - 6-8 GB RAM (4GB for KVM + something for OpenQA itself)
> - 50 GB of disk (preferably more)
>
> Does anyone have a spare machine running somewhere, and willing to
> share?
>
> Alternatively, it looks like we can get one for ~70 EUR/month. Andrew,
> Michael, could we use opencollective money for this?
>

The OpenCollective money is supposed to be used to pay developers to
work on the open-source version of Qubes. While this would not be a
direct payment to a developer, I can see how it would qualify, since
it's directly saving you and other devs time and work that would
otherwise have to be spent on testing. I think it would adhere to the
spirit of the rule, which is that the money should be spent on
improving the open-source version of Qubes. (Arguably, it would be
even more efficient than paying a developer directly, since Qubes
would probably benefit a lot more from the testing bought by that ~70
EUR/month than it would from the tiny amount of developer time ~70
EUR/month would pay for.)

However, I'd be surprised if there were no one in the Qubes community
willing to share a suitable machine for this purpose. My guess is that
there aren't as many readers on qubes-project as there are on
qubes-devel and qubes-users, so I'm CCing those other lists.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpr1ioACgkQ203TvDlQ
MDBZaA/9HZWo8gZh5UsrKEAWIC4c4b4hnL2U0NZvqi508qbr65DmqW67y/QGXA0q
EI3VNHpNrhL99jpWGlsGnN3K1Dss+NKKEk82AVsqw6in9P1LA+9CyMjf3TQB1yLn
QkWyFc0E/+wN4ExpMgUuX7kqTv9TgjPrFki+KajpsIvQpXDOqMxM6vNdYitI8fer
B1cpIn0gS17ANcvlXJU2OhLKEradX6msZJdAYWlrZPpy7XEIPtnJTugsN5fm6kr/
ChsQtGH7OTHIJkd0pEr9YODhyr/Tpp6OYDwsQL1uWW4W8K03Mhmh5q+MuKg/scvG
nv8vINL0wo010GdiqsU/bvqB7pYkOFcdsghgM3gy1jBK8E7aR4KgNrafKn22D7eu
fC0Y2LlJmGZ6s+l//sfI6YIMi/iCj+6zUHXLdcGrLI9v+iYu23/9Lz6oyKl1Vedv
+6zh0PasElJXxAgdBGN7Se16ApC8/cTLeEcHhAQ1No/Tye3TaYE1U4ouj+9d6o1l
f7LLiSs1wxmBZcRdK09yK7zqcqi92NsgwBzmKwoz6fQFljo+G3/giar0xZ+8HPXN
HTnQ0von8o22yoK7x5H9jc+Fmq32zUvmYy2R3dAkY8PVmOgVEyf5z2OY3q0HEiEK
25kYJw9tdC7ZS6kI22l4tLGaAm6ntoM/ZbFUG0wrpESunWVrZOE=
=EIwB
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Jan 28, 2018 at 06:23:02PM +0000, BePe wrote:
> Hi All,
>
> FYI, and it in case that it can help, I have succesfully installed Qubes 4.0
> rc3 in KVM with nested virtualization and iommu enabled.
> I had to hack a little bit the qemu intel_iommu.c, but now I have fully
> fonctional Qubes 4  (with all the VM in hvm mode).
> The VM are not flying but they do work.

I've tried that too, but gave up after few iterations. Can you send
exact modifications to intel_iommu.c? Anything more than this:
http://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg05901.html

?

Also, exact qemu cmdline would help.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpuMSEACgkQ24/THMrX
1yyRQAf/V0/yeHFrgdrAeF5X/jSAvcFi1QXDKOIG+lM9lebY6VpTuoMEMmPETLnf
Ky/jTXgCICCedAC2KSIFTG6A7dz+gEEVgIof4XjlVbfEow+H41zYOt878gd9QS9+
BfDAPPbNjdirA2fhtC4swCjsFQzdARP1mfPHr7Q4TR+Crfa41qYqYNd4F682bNAF
A2sxQlg+eiEil1NrxvPyC4p/TY+XjociYpZLeZK7oYw/N1HTk75hmccu9mLi1sIa
3r/9yLcwsDaRu9Fyvp+rF3tsGJKVp1xr4iKp/yfLA6IcZTi9BVXbRqiQG1JWBh1d
NR1XRijdC3zJ7RTdclGp1whWPwNiyA==
=xS71
-----END PGP SIGNATURE-----

[BePe]

I was not aware of the patch in the URL you have indic ated, but I have done something like that to be able to have the QUEBES 4 VM to run.
After that I had to configure the VM using some hints available here : https://www.berrange.com/posts/2017/02/16/setting-up-a-nested-kvm-guest-for-developing-testing-pci-device-assignment-with-numa
Please find attached the XML file of the VM that is working.
I am using qemu 2.11.
Hope that it will help.

P.S.: Don't take into account the number of network interfaces configured, I needed it to test assignment of PCI devices (it works also).

-

BePe - From Bamako