On 24.04.2013 23:26, Alex wrote:
> Hi Qubes team
> Thank you for a fantastic project - I like the principle and the system is
> already very usable.
> Attaching a HCL report from my Dell E6320 laptop with 4GB of RAM on which
> Qubes works quite decently performance-wise.
> Some observations follow - your guidance would be appreciated:
> 1. [Bug?] In Qubes VM Manager going to About -> Qubes OS returns "Qubes OS
> Release 1.0" even though this is V2 R2
Ah, indeed, thanks!
> 2. [Fedora issue?] When asking the laptop to power off (via KDE's shutdown
> GUI, we sometimes get stuck in the following console state:
> Powering off.
> [nnnnn.nnnnnn] Power down.
> The power is not actually cut, one has to press the physical power button
> for the laptop to power off.
Strange... Is it deterministic problem, or happens only sometimes? Perhaps
kernel upgrade will fix this issue. I'm still not sure which kernel will be in
R2 beta3 (and final R2) release.
> 3. How is it possible to install non-rpm applications like TrueCrypt? A
> universal and a domain-specific way would be useful.
Yes, same as in other linux distributions. If you want install such software
in dom0 (which is bad idea in most cases), you need to copy file there in the
> 4. Memory usage: Straight after boot, my Firewallvm domain consumes approx.
> 730MB of RAM. Why is so much memory necessary?
Memory is assigned to VMs proportionally to requirements. Just after system
boot there are very low memory needs, so free RAM is distributed among all VMs
(which have dynamic memory management enabled - netvm hasn't).
> 5. [bug?] In Qubes VM Manager asking it to backup VMs fails with:
> [Dom0] Houston, we have a problem...
> Whoops. A critical error has occured (<- btw this should be "occurred").
> This is most likely a bug in Qubes Manager.
I know, this is already fixed in git repo, but still we haven't released new
> 6. [bug?] Sometimes VMs fail to start. The message is "[Dom0 Qrexec daemon
> - Kdialog: Timeout while trying connecting to qrexec agent (Xen domain
> ID:5). Do you want to wait next 60 seconds?"
> Invariably waiting for those next 60 seconds does not result in a
> successful launch, but rather in a message in the "Notifications" panel of
> KDE saying "Error while starting the 'untrusted' VM: ERROR: Cannot execute
Check /var/log/xen/console/guest-unstrusted.log. This file should be available
in Qubes Manager (right click on VM). Also check "xl list" output before you
click anything in the message window - is the "untrusted" VM present there?
What is its state and time used?
Best Regards / Pozdrawiam,
Invisible Things Lab