On Fri, December 22, 2017 8:55 am, '[799]' via qubes-users wrote:
>
> This I also what I assumed as there must be a good reason why Qubes Team
> has switched to HVM instead of using PV VMs. Still I'd like to learn more
> about the vulnerabilities, so I can make a decision risk vs. runtime. And
>
Original-Nachricht
An 22. Dez. 2017, 06:49, MirrorWay schrieb:
>> Since watts is already energy/time,
>> this should just say 9.5W
Ok, thanks :-)
>> As I understand it, Xen PV code has bad
>> track record of vulnerabilities, hence the
>> change to HVM in Qubes 4.0.
>> Also why
Another partial workaround, you can change virt_mode from hvm back to pv for
trustworthy VMs, like vault, etc...
The bug: https://github.com/QubesOS/qubes-issues/issues/2849
For me it amounts to an overhead of 10% x cpu core per hvm, according to xentop.
--
You received this message because
On 12/13/2017 07:30 PM, '[799]' via qubes-users wrote:
Hello Chris,
Original-Nachricht
An 13. Dez. 2017, 19:15, Chris Laprise schrieb
> Increased CPU usage is a known issue.
> You can see it in the 'xentop' listing.
> This may be one of the core tradeoffs
> when moving to
On 12/13/2017 01:30 PM, [799] wrote:
Hello Chris,
Original-Nachricht
An 13. Dez. 2017, 19:15, Chris Laprise schrieb
> Increased CPU usage is a known issue.
> You can see it in the 'xentop' listing.
> This may be one of the core tradeoffs
> when moving to R4.0
Thanks for the
Hello Chris,
Original-Nachricht
An 13. Dez. 2017, 19:15, Chris Laprise schrieb
> Increased CPU usage is a known issue.
> You can see it in the 'xentop' listing.
> This may be one of the core tradeoffs
> when moving to R4.0
Thanks for the hint.
Honestly I can't believe that
