On Wed, 2018-05-30 at 11:09 -0700, PGNet Dev wrote: > Upgrading working OpenSUSE leap42.3 / Xen servers (5, atm) to > leap15.0, after upgrade > Well,
> But checking, > > xl list > Name ID Mem > VCPUs State Time(s) > (null) 0 4016 > 4 r----- 329.6 > Xenstore 1 31 > 1 -b---- 0.0 > > and > > [...] > > systemctl status -l xenstored.service > ● xenstored.service - The Xen xenstore > Loaded: loaded (/usr/lib/systemd/system/xenstored.service; > enabled; vendor preset: disabled) > Active: failed (Result: timeout) since Wed 2018-05-30 > 10:37:08 PDT; 10min ago > Main PID: 1391 (code=exited, status=0/SUCCESS) > > May 30 10:35:39 xserver launch-xenstore[1391]: Starting > /usr/lib/xen/boot/xenstore-stubdom.gz... > This 'failed' here is likely why you see '(null)' instead of 'Domain- 0'. It looks like, for some reason, xenstored is not actually starting. In fact, in your other email, where you report that things work, this succeeded. Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Software Engineer @ SUSE https://www.suse.com/
signature.asc
Description: This is a digitally signed message part
