Hi again Glen, On Mon, 2020-02-24 at 08:06 -0800, Glen wrote: > I've completed my client migration, and those guests are also > surviving nicely. So I"m tagging this [SOLVED] and tossing in a few > subject line keywords for the archives, to help other find this, and > I've now brought back one of my (no longer in use) hosts to credit2 > so > I can start crashing that guest and hopefully capturing debugging > information from it. > That is great to hear... looking forward for some more info and logs on the subject.
> I'll report that data directly to xen-devel > since that seems to not be an OpenSuse problem. > Yep, this is definitely an upstream issue, and we definitely should talk on upstream MLs. It would be useful, though, to have a bug opened for it for better tracking (see below). > Apart from OpenSuse possibly making "sched=credit" a Xen boot default > now, via an update or whatever, there is one other small item of > interest for this group. It has been suggested ( > https://lists.xenproject.org/archives/html/xen-users/2020-02/msg00052.html > ) that Xen 4.12.2 contains fixes to these and other problems. I do > not know how these things work within OpenSuse, but I wonder if > bringing in Xen 4.12.2 as an update to OpenSuse 15.1 might be a > useful > thing to do? I through that out there for all of you who know much > more about these things than I. > In general, fixes are applied (backported). Whatever the fix for this would be to really revert to "sched=credit" or some actual changes to Credit2 (or whatever else), I think you can expect for it to be backported to any supported distribution. > Anyway, I expect this to be my last message on this topic to this > group, but wanted to thank all of you who responded to me over the > past months again for your help and patience. > Actually, thank you again for reporting the problem and for you will to help us find the solution. As I mentioned above, would you be willing to open a bug, on https://bugzilla.opensuse.org/ about this? It is indeed something we'll deal with upstream, but I think it would still be useful. In the description of the problem, you can mention the fact that the problem is being investigated and link the threads on the xen-devel and xen-users mailing lists. Thanks and Regards -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)
signature.asc
Description: This is a digitally signed message part
