Guilherme G. Piccoli writes: > Can you capture the serial console in a pastebin? Maybe add something > like "earlyprintk=ttySX", where ttySX is your known-to-work serial > console output. This helps to determine if it's a shutdown issue or an > early boot problem. The regular xen cosole should work for this shouldn't it? So earlyprintk=hvc0 I guess? I also threw in console=hvc0 and loglevel=7: [ 184.734810] systemd-shutdown[1]: Syncing filesystems and block devices. [ 185.772511] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 185.896957] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 185.901111] systemd-shutdown[1]: Unmounting file systems. [ 185.902180] [1035]: Remounting '/' read-only in with options 'errors=remount-ro'. [ 185.990634] EXT4-fs (xvda1): re-mounted. Opts: errors=remount-ro [ 186.002373] systemd-shutdown[1]: All filesystems unmounted. [ 186.002411] systemd-shutdown[1]: Deactivating swaps. [ 186.002502] systemd-shutdown[1]: All swaps deactivated. [ 186.002529] systemd-shutdown[1]: Detaching loop devices. [ 186.002699] systemd-shutdown[1]: All loop devices detached. [ 186.002727] systemd-shutdown[1]: Stopping MD devices. [ 186.002814] systemd-shutdown[1]: All MD devices stopped. [ 186.002840] systemd-shutdown[1]: Detaching DM devices. [ 186.002974] systemd-shutdown[1]: All DM devices detached. [ 186.003017] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached. [ 186.168475] systemd-shutdown[1]: Syncing filesystems and block devices. [ 186.169150] systemd-shutdown[1]: Rebooting with kexec. [ 186.418653] xenbus_probe_frontend: xenbus_frontend_dev_shutdown: device/vbd/5632: Initialising != Connected, skipping [ 186.427377] kexec_core: Starting new kernel _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
