** Changed in: maas (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh nodeinfo doesn't report CPU frequency on s390x
To manage notifications
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh nodeinfo doesn't report CPU frequency on s390x
To
** Tags removed: severity-medium
** Tags added: severity-high
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh nodeinfo doesn't report CPU frequency on s390x
To manage
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Tags removed: severity-high
** Tags added: severity-medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh nodeinfo doesn't report CPU frequency on s390x
To
It is fixed:
ubuntu@s1lp5:~$ virsh nodeinfo
CPU model: s390x
CPU(s): 12
CPU frequency: 5000 MHz
CPU socket(s): 2
Core(s) per socket: 6
Thread(s) per core: 1
NUMA cell(s):1
Memory size: 10080436 KiB
Still personally don't find the information
** Tags added: reverse-proxy-bugzilla
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh nodeinfo doesn't report CPU frequency on s390x
To manage notifications about this bug go
--- Comment From heinz-werner_se...@de.ibm.com 2018-01-24 05:33 EDT---
Updated target distro to Ubuntu 18.04.
Libvirt v4.0.0 has been released on January 19th, 2018.
** Tags removed: targetmilestone-inin1604
** Tags added: targetmilestone-inin1804
--
You received this bug notification
Hi Boris, I already saw that and prepped the 4.0 upload that way -
thanks for the ping still, it is not always that clear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh
** Changed in: libvirt (Ubuntu)
Status: New => Fix Committed
** Changed in: libvirt (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh nodeinfo doesn't report CPU frequency on s390x
To manage
** Tags added: libvirt-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh nodeinfo doesn't report CPU frequency on s390x
To manage notifications about this bug go to:
My honest opinion, this sounds like the worst feature ever.
Due to that being affected by cpu freq scaling this is rather close to "if
$RANDOM > 50% then do".
I expect/guess/hope there is much more detail behind it that makes this more
meaningful as it sounds.
--
You received this bug
answer from MAAS team:
'MAAS has an option were it allows you to create machines from pods
using the frequency. I created a work around for the issue. I really
have no strong feelings on having it, but for consistency, it is
probably required.'
--
You received this bug notification because you
I can understand both views:
1) the fact that the cpu frequency data is probably not very useful
2) in case a component is ported to Z, the features shouldn't be reduced until
it fits
But I'll ask the MAAS team for a comment here ...
** Also affects: maas (Ubuntu)
Importance: Undecided
Nice: comment #1 + comment #3 = Christians are in sync :-)
Frank I think you should actually open a bug task against MAAS on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
It's used in MAAS - a workaround can be added for sure - but also thought
it's not to bad to close that little gap (on low prio ...)
Frank Heimes | Tech. Lead Ubuntu Server on Z | Canonical Ltd.
mail: frank.hei...@canonical.com
irc: jfh
www.canonical.com | www.ubuntu.com |
Hi Frank,
I see you already mirrored which is right as it just isn't implmented on s390
afaik.
But IMHO frequency these days is just as good as /dev/urandom - so I'd not be
offended if somebody says "Won't fix"
A patch to drop it from all architectures would be nice thou ...
@Frank - did you
** Tags added: architecture-s39064 bugnameltc-161610 severity-high
targetmilestone-inin1604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733688
Title:
virsh nodeinfo doesn't report CPU frequency
19 matches
Mail list logo
