From: PGNet Dev <pgnet.dev@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
Date: Wed, 15 Jan 2020 09:43:40 -0800 [thread overview]
Message-ID: <000db7ac-bc56-f2a4-b7b2-a5c867be49a7@gmail.com> (raw)
In-Reply-To: <bdfd64dd-6fe7-ec75-5c39-9e8d6063eb85@citrix.com>
On 1/15/20 9:21 AM, Andrew Cooper wrote:
> That is the command line for dom0 which is a VM. You need the Xen
> hypervisor command line.
thx. done.
> You'll need to edit xen-4.13.0_04-lp151.688.cfg which will be somewhere
> on the ESP (wherever that is mounted in an openSUSE system).
verifying,
cat /boot/efi/EFI/opensuse/xen-4.13.0_04-lp151.688.cfg
[global]
[config.1]
options=dom0=pvh ... reboot=a
kernel=...
now, on restart,
...
[ OK ] Reached target Shutdown.
[ 137.682171] watchdog: watchdog0: watchdog did not stop!
[ 139.373683] watchdog: watchdog0: watchdog did not stop!
dracut Warning: Killing all remaining processes
mdadm: stopped /dev/md4
mdadm: stopped /dev/md3
mdadm: stopped /dev/md2
mdadm: stopped /dev/md1
mdadm: stopped /dev/md0
Rebooting.
[ 144.908520] reboot: Restarting system
(XEN) [2020-01-15 17:38:25] Hardware Dom0 shutdown: rebooting machine
(XEN) [2020-01-15 17:38:25] APIC error on CPU0: 40(00)
(XEN) [2020-01-15 17:38:25] Resetting with ACPI MEMORY or I/O RESET_REG.
and reboot proceeds ...
the error's still there, but without the trace/noise
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2020-01-15 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 16:52 [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok PGNet Dev
2020-01-15 17:10 ` Andrew Cooper
2020-01-15 17:19 ` PGNet Dev
2020-01-15 17:21 ` Andrew Cooper
2020-01-15 17:43 ` PGNet Dev [this message]
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=000db7ac-bc56-f2a4-b7b2-a5c867be49a7@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=andrew.cooper3@citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).