From: Phillip Susi <phill@thesusis.net>
To: "Guilherme G. Piccoli" <guilherme.piccoli@canonical.com>
Cc: xen-devel@lists.xenproject.org,
kexec mailing list <kexec@lists.infradead.org>
Subject: Re: kexec not working in xen domU?
Date: Mon, 14 Dec 2020 15:08:57 -0500 [thread overview]
Message-ID: <87czzcdtir.fsf@vps.thesusis.net> (raw)
In-Reply-To: <CAHD1Q_zcruQ6KVHApvhb=0+mG0m80T+tmg1UzjQBki8j+aR51A@mail.gmail.com>
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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2020-12-14 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 19:09 kexec not working in xen domU? Phillip Susi
2020-12-14 18:52 ` Guilherme G. Piccoli
2020-12-14 20:08 ` Phillip Susi [this message]
2020-12-17 17:34 ` Guilherme G. Piccoli
2020-12-17 21:25 ` Phillip Susi
2020-12-18 20:59 ` Phillip Susi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czzcdtir.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=guilherme.piccoli@canonical.com \
--cc=kexec@lists.infradead.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox