Comment 12 for bug 1811198

Revision history for this message
Bin Li (binli) wrote : Re: [Bug 1811198] Re: virt-manager fail to start on huawei arm server

Christian,

Now I am in Chinese Spring Festival holiday, will back on 15th Feb. Thanks.

On Thu, Jan 31, 2019, 23:41 Christian Ehrhardt  <<email address hidden>
wrote:

> FYI - the fix for this bug as an SRUs is ready and testable from a PPA for
> Cosmic [1] and Bionic [2].
>
> Since the verification of this bug requires special hardware, I'd
> appreciate if you could precheck these PPAs if they fix the issues. That
> would ensure that:
> a) the fix is most likely to work when pushed as SRU
> b) our plan to verify the actual by your testing SRU will work
>
> In addition I'll push these PPAs through the automated regression tests
> for qemu/libvirt.
>
> [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3620
> [2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3621
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811198
>
> Title:
> virt-manager fail to start on huawei arm server
>
> Status in libvirt package in Ubuntu:
> Fix Released
> Status in libvirt source package in Bionic:
> Triaged
> Status in libvirt source package in Cosmic:
> Triaged
>
> Bug description:
> [Impact]
>
> * Some arm systems can have unexpected high core_id's which breaks
> libvirts arbitrary assumption to limit it at 4k
>
> * Upstream fix drops this limit and makes use of libvirts ability to
> size
> the bitsets automatically as needed
>
> [Test Case]
>
> * This is the hard part, as it needs special HW to be affected, but
> also
> to verify the fix.
>
> * We can ask the reporter to verify on his platform, but not 100% rely
> on
> that in case he is unavailable.
>
> [Regression Potential]
>
> * The change is removing a limit which only hit very special HW. For
> this
> special HW it is a fix, for all others it should be no functional
> change.
> * The one regression I could think of is that this dynamic bitmask
> handling would have (not yet identified issues) that would affect
> other
> cases (the feature is almost three years old now since lbivirt 1.3.3).
>
> [Other Info]
>
> * n/a
>
> ---
>
> We met an issue when run virt-manager on huawei arm server with
> 18.04.1.
>
> Error polling connection 'qemu:///system': internal error: Socket 5418
> can't be handled (max socket is 4095)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1811198/+subscriptions
>