Based on my tests I can confirm the warning is the same between 4.0.4 and 4.1.0, it’s just a warning and one can continue the installation, which I find is the correct way to go (more adoption) !
Note that I still can’t install 4.1.0 cause of a luks problem, even if at some point I succeeded but with another (now solved) problem, unfortunately I don’t remember how … So for now I only test 4.0.4.
Now, no one for any of my questions ? ^^
All questions are still valid, but here are some updates (the numbering reflects the order in my previous post) :
-
- the note about
data/meminfo_free 2405480 [\n] control/feature-balloon 1is irrelevant, I checked the logs and it happens all the time. But the initial point is still valid: ishapneeded
- the note about
-
- I still don’t know what the
vmexiterrors mean, but I found a way to logxl dmesgin text files. In the Xen source code, thexl dmesgring buffer size is hardcoded to 16k. The solution is to setXENCONSOLED_TRACEin/etc/default/xen(that would be sysconfig in Qubes), as per this post, but I have yet to make it work, seems the SIGHUP is not enough.
- I still don’t know what the
The vmexit thing seems the most annoying for now. But Qubes domUs seem to work, even if I only have sys-net and sys-fw running.