On Thu, Nov 19, PGNet Dev wrote: > On 11/19/2015 01:35 AM, Olaf Hering wrote: > >eno1 does not exist as interface name. > Hm. It certainly _used_ to prior to the upgrade ...
It might be caused by the fact that Leap uses SLE12 as a base for systemd, which forces net.ifnames=0. Try to boot with net.ifnames=1 on kernel cmdline. > > Again, it worked absolutely fine prior to the upgrade; the script executed, > and the knobs' values were verified to be set. Likely by ifup scripts instead of wicked. > That preceding "(null):" is a problem, but iirc is due to the lack of > properly init'd xenstored wicked and xenstored are unrelated. > >At least xen works on my Leap installation. Not sure why EFI would make > >any difference. > >Are there stale xen related .service files or sysv > >scripts which prevent xenstored.service/xenstored.socked from starting? > >Our xencommons.service is supposed to start everything. > > I made a little progress. > > I read this > > > http://lists.xenproject.org/archives/html/xen-devel/2015-10/msg01262.html > > exec'd these > > systemctl enable xenstored.service > systemctl enable xenconsoled.service > systemctl enable xen-init-dom0.service > systemctl enable xen-qemu-dom0-disk-backend.service > systemctl enable xendomains.service > > So now, > > systemctl list-unit-files | grep -i xen > proc-xen.mount static > var-lib-xenstored.mount static > xen-dom0-modules.service disabled > xen-init-dom0.service enabled > xen-qemu-dom0-disk-backend.service enabled > xen-watchdog.service disabled > xencommons.service enabled > xenconsoled.service enabled > xendomains.service enabled > xenstored.service enabled > xenstored.socket enabled > xenstored_ro.socket enabled Which one was missing? xencommons.service is supposed to start them all. > Also found & removed these from the /etc/default/grub > > - GRUB_CMDLINE_LINUX_XEN_REPLACE=" (.*) rdloaddriver=xennet > rdloaddriver=xenblk" > + GRUB_CMDLINE_LINUX_XEN_REPLACE=" (.*) " This is unrelated I think. > Nov 18 19:15:56 xensvr systemd-udevd[812]: Network interface NamePolicy= > disabled on kernel commandline, ignoring. > > I've no idea what it's referring to, as Likely because its forced to be off in the sources. Olaf -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
