Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upinfo disconnect between xentop and Qubes VM Manager #1120
Comments
marmarek
added
bug
C: qubes-manager
labels
Aug 25, 2015
marmarek
added this to the Release 3.0 milestone
Aug 25, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 25, 2015
Member
Yup, dom0 CPU stats are not implemented there... Maybe we should just hide that bar (for dom0) for now?
|
Yup, dom0 CPU stats are not implemented there... Maybe we should just hide that bar (for dom0) for now? |
marmarek
modified the milestones:
Release 3.1,
Release 3.0
Sep 2, 2015
mfc
referenced this issue
Oct 16, 2015
Closed
Qubes manager always reports dom0 CPU usage as 0% #1302
marmarek
referenced this issue
Nov 5, 2015
Closed
Consider removing dom0 from a VM list in Qubes Manager #1382
marmarek
modified the milestones:
Release 3.1,
Release 3.1 updates
Feb 8, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Jan 27, 2017
Member
yes this should be hidden by default, and replaced with the NetVM info column.
|
yes this should be hidden by default, and replaced with the NetVM info column. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jpouellet
Jan 30, 2017
Contributor
OTOH, this is useful to diagnose "why are my fans running?" when some VM has gone rogue and is hanging at 100% CPU
@mfc how do you recommend people know which VM to kill without the cpu column?
|
OTOH, this is useful to diagnose "why are my fans running?" when some VM has gone rogue and is hanging at 100% CPU @mfc how do you recommend people know which VM to kill without the cpu column? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Jan 30, 2017
Member
so are you proposing having "n/a" for dom0 listing in CPU instead? how do we communicate to users to trust some of the information provided in the CPU column but not all of it?
anyway it is still available to users, just not visible by default. I think this is the appropriate choice for the time being.
obviously we are interested in an accurate display CPU usage for all VMs, I am deferring to Marek re: time & prioritization of this functionality (which I feel is low). this ticket will follow such implementation.
|
so are you proposing having "n/a" for dom0 listing in CPU instead? how do we communicate to users to trust some of the information provided in the CPU column but not all of it? anyway it is still available to users, just not visible by default. I think this is the appropriate choice for the time being. obviously we are interested in an accurate display CPU usage for all VMs, I am deferring to Marek re: time & prioritization of this functionality (which I feel is low). this ticket will follow such implementation. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@andrewdavidwong Confirmed this issue still arises in 3.2 milestone |
mfc commentedAug 14, 2015
Running xentop in dom0 one can see that dom0 uses a bunch of CPU sometimes.
This is not reflected in the Qubes VM Manager at all (CPU stays at 0).
Expected behavior: xentop info should be accurately reflected on in Qubes VM Manager.
Reported at CCCamp!
Qubes 3.0RC2, both installed and live USB.