Activity log for bug #251065

Date Who What changed Old value New value Message
2008-07-23 08:41:00 Richard Laager bug added bug
2008-07-23 08:41:09 Richard Laager bug added subscriber Wiktel
2008-07-23 19:15:52 Richard Laager description Imagine a host with 4 CPUs and 4 GB of RAM. Imagine a guest with one CPU and 512 MB of RAM. If it maxes out its resources, it'll show as using 25% CPU and 12.5% of RAM. This is relative to the host, but that's not really meaningful when you're looking at the guest. Instead, those numbers should be relative to the guest, so it'd be 100% and 100%. As a special case, when the minimum and maximum RAM are the same, it should just show the amount (512 MB) because a constant 100% isn't really useful. The numbers on the main virt-manager screen (as opposed to on the detail of a specific host) are harder to define. I could see why one might want those relative to the host. If there's no clear consensus, both sets of numbers should be shown there. The line for the host should definitely show the numbers relative to the host, like it does now. Imagine a host with 4 CPUs and 4 GB of RAM. Imagine a guest with one CPU and 512 MB of RAM. If it maxes out its resources, it'll show as using 25% CPU and 12.5% of RAM. This is relative to the host, but that's not really meaningful when you're looking at the guest. Instead, those numbers should be relative to the guest, so it'd be 100% and 100%. As a special case, when the startup and maximum RAM are the same, it should just show the amount (512 MB) because a constant 100% isn't really useful. The numbers on the main virt-manager screen (as opposed to on the detail of a specific host) are harder to define. I can make a case for both sets of numbers. I would argue that both should be available (in separate columns), but the relative-to-guest columns should be hidden by default.
2008-10-01 19:27:20 Dustin Kirkland  virt-manager: importance Undecided Wishlist
2008-10-01 19:27:20 Dustin Kirkland  virt-manager: statusexplanation
2008-10-03 20:38:01 Dustin Kirkland  bug assigned to virt-manager
2008-12-10 20:11:43 Dan Bass virt-manager: status New Unknown
2008-12-10 20:11:43 Dan Bass virt-manager: importance Undecided Unknown
2008-12-10 20:11:43 Dan Bass virt-manager: statusexplanation
2008-12-10 20:23:06 Bug Watch Updater virt-manager: status Unknown Confirmed
2010-03-24 22:54:26 Marc Deslauriers virt-manager (Ubuntu): status New Confirmed
2017-10-27 05:59:24 Bug Watch Updater virt-manager: status Confirmed Invalid
2017-10-27 05:59:24 Bug Watch Updater virt-manager: importance Unknown Medium