![](https://seccdn.libravatar.org/avatar/89b0014651e56cef4b5e2023c73e3877.jpg?s=120&d=mm&r=g)
Hi Tony - Thanks for the reply! On Wed, Jan 8, 2020 at 9:24 AM Tony Su <tonysu@su-networking.com> wrote:
Was thinking along the same lines as the last resort... If you can pin down the problem as a HostOS problem, Shouldn't your Xen Guests(with docker containers within) be easily migratable to a newly built HostOS? Don't know what else is running on your system, but typically it's a recommended best practice to keep the HostOS in a multi-apartment system as simple and uncomplex as possible.
Yes but I must have explained it backwards. At this point, I think it's a problem inside the guest, not the host. I have 9 hosts, and about 16 guests, and the problem follows this particular guest. All hosts are solid. All the other guests are solid. It's only this one guest (or copies of it) that fails, no matter which host I run it on. So I am going to fresh-load the guest, and just reconnect services, and yes, it won't be that complex, it just "a pain" and I was hoping to avoid it.
And a general observation, If this machine was originally installed as a 13.1 and survived every upgrade for each openSUSE version from then to now, IMO that's quite an accomplishment.
This made me smile. At this point, all of my hosts are freshly-loaded 15.1. But this guest - yes, it's last fresh load was back on 13.1, and we've just "zypper dup"'ped it at each new release, all the way up until now. But it's clearly time to bite the bullet and reload the guest fresh. THANK YOU again for your support and responses as I've tried to figure this out! Glen -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org