From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bader Subject: Using kexec-crashdump with recent Xen and Linux HVM Date: Wed, 11 Mar 2015 18:16:47 +0100 Message-ID: <5500787F.8060709@canonical.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7193974317442125244==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============7193974317442125244== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3GhMi7B53296qwFROrBXm7HPHaSbF7o7i" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3GhMi7B53296qwFROrBXm7HPHaSbF7o7i Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable After being asked about this I started to play around with Xen-4.4.1/4.5 together with HVM Linux guest running 3.13/3.16/3.19. With mixed success.= Usually rather failing. =46rom a bit of research most activity to enable things were back in 2011= =2E There was a bit of a throwback around Linux 3.2[1] but it appears [2] restored = this in a backwards compatible way. Around 3.17 xen_nopv was introduced but I hav= e not figured out a helpful usage of this. The failure exhibits no visible messages in the guest after the crash sta= cktrace caused by sysreq-trigger while 1vcpu seems to be in a spinning loop. On t= he host side I noticed changing messages (TX queue drain or EVCHNOP errors). Command-line is a mix of nomodeset (to keep cirrusdrm away) and some defa= ults from the kdump-tools (maxcpus=3D1 irqpoll nousb). The closest thing to success I can get to is using xen_emul_unplug=3Dneve= r for the normal boot (which propagates into the kexec command). This of course sto= ps usage of the pv drivers. I also tried some variation of blacklisting the emulated drivers and using xen_emul_unplug=3Dunnecessary but that did not= seem to work for me. The crash-kexec boot without unplugging still fails to bring= up the NIC but at least finds the root disk to store the dump there. But not usi= ng the pv drivers is not a setup one would want to have running just in case. So I was wondering whether I still miss something. -Stefan [1] commit 12275dd4b747f5d87fa36229774d76bca8e63068 Revert "xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches= =2E.." [2] commit cb6b6df111e46b9d0f79eb971575fd50555f43f4 xen/pv-on-hvm kexec: add quirk for Xen 3.4 and shutdown watches. --3GhMi7B53296qwFROrBXm7HPHaSbF7o7i Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJVAHiGAAoJEOhnXe7L7s6j+1gQAN1iOEaUOuVKV8Ii/mWzCBD7 /yZc4RsxBBT8xjx11gkpAZua/SM3oY9DRc/2WSSu/iLrvfp6vPDfqxzDti2QuDhJ JOOlOqhee+NQ0XZiL8SNZw00ai85H16lH5RSce8aVROwPYYTMbd97HzP0U9pL4uh +0+qNIhn3vnp7Y/jlwGhRNeLCZjl1dpSWY8h8JDzABoTrxc2td8P9PlAqJp4SUK/ VU4nAkGg2fK+444PJYhiqb9JR0uK8IL6L0YbuzMgamsZO+gO7xYJognBNRDM8TyP LZEAVeRWXX1yOj2xZXl1yOUhG0RBFplS5hKGkJ3Ax93AVcBR9uGhDKhEI/gFS3Ye krvgXJA0M7/xo3stJINeYSZf0XPKnD/UaE5k3q8MZ+IRpeyMUNbLhYoEk0iiFF3M ZfmNouAprxzdHah5pH6xDMRthEQ3jILC4nCv4l2EAzstOZBQ1KnhB0jcOX5SApzI 4h+rC577iSDUFOWcjlavr5Dhly0AgkiHTfpQa0yQuG+29D5qmOmVIUgzGz1Doq8f NtDLx2t27u4hFnvdFy21bxFKpxvSvp3oS/VhjvktWccKKfsjntSmhyXbOUUvuhnt JW0w8Kkgq8kqNGGkf3FjmBClDsjnR8frK9WpCPG9RGTF66qBfIp5NCiqBuKFkANE soxC187KB3HRuHbtd7fi =zLKK -----END PGP SIGNATURE----- --3GhMi7B53296qwFROrBXm7HPHaSbF7o7i-- --===============7193974317442125244== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============7193974317442125244==--