[Bug 1709877] Comment bridged from LTC Bugzilla

2019-02-14 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2019-02-15 01:12 EDT--- Closing as previous comment. Regards, -Satheesh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709877 Title: CPU hotplug fails

[Bug 1709877] Comment bridged from LTC Bugzilla

2019-01-22 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2019-01-23 01:49 EDT--- (In reply to comment #38) > Thanks for the discussion and suggestion Frank. > I agree that the 16.04 release notes are much more appropriate and easier to > change in that regard. > > @Satheera - would that work and be ok for

[Bug 1709877] Comment bridged from LTC Bugzilla

2019-01-21 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2019-01-21 04:57 EDT--- (In reply to comment #35) > I agree to your summary. > I was considering this being "open" so long without being a major issue for > anyone combined with the required work getting bigger to implement/fix it > for real. So of the

[Bug 1709877] Comment bridged from LTC Bugzilla

2019-01-09 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2019-01-10 00:15 EDT--- (In reply to comment #33) > This is just the libvirt as in Xenial plus the requested patches. > I don't see anything obvious to be wrong except if the requested changes > were incomplete. > > Could it be that the use case you are

[Bug 1709877] Comment bridged from LTC Bugzilla

2019-01-09 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2019-01-09 04:58 EDT--- (In reply to comment #31) > A proper documentation of a limitation is just as much effort as a fix since > it is known in this case. And I like to fix things, I just wanted to make > sure that the case is real. > > You will have

[Bug 1709877] Comment bridged from LTC Bugzilla

2019-01-07 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2019-01-08 01:08 EDT--- (In reply to comment #28) > Well, if it is a real issue and not just existing in the Lab with a very > special machine (it seems hard to get one for you as well) then I can > re-port the fix to the current version of Xenials

[Bug 1709877] Comment bridged from LTC Bugzilla

2019-01-04 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2019-01-04 06:51 EDT--- Finally I managed to get the hardware with config I had raised this issue, and still able to reproduce the failure with latest pieces of software. Host env: #uname -a Linux abc 4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5

[Bug 1709877] Comment bridged from LTC Bugzilla

2018-08-31 Thread bugproxy
--- Comment From s...@us.ibm.com 2018-08-31 15:29 EDT--- :ast update was 7 months ago, perhaps because it probably should have been moved to NEEDINFO. Satheesh? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1709877] Comment bridged from LTC Bugzilla

2018-01-02 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2018-01-02 05:07 EDT--- (In reply to comment #22) > Hi Satheera, > since this was waiting for verification so long the version number used in > the ppa was consumed by another (unrelated) update. I think there is no > reason to drive all of the rebuild

[Bug 1709877] Comment bridged from LTC Bugzilla

2017-12-22 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2017-12-22 12:47 EDT--- (In reply to comment #17) > Hi, > There is a test build of a backport available at [1]. > > This did work through some basic checks, but a full regression test will > take some more time. > > Please could you check if that fixes

[Bug 1709877] Comment bridged from LTC Bugzilla

2017-09-12 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2017-09-13 00:51 EDT--- (In reply to comment #12) > There is some noise when applying this to Xenial. > Nothing too big, but I think at least > commit dc0d7fe0267e2ff6e5a9625164f2896f9cc5 (HEAD) > Author: Peter Krempa > Date: