[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110804162053.723541930@aepfle.de>
Date: Thu, 04 Aug 2011 18:20:53 +0200
From: Olaf Hering <olaf@...fle.de>
To: linux-kernel@...r.kernel.org,
Jeremy Fitzhardinge <jeremy@...p.org>,
Konrad <konrad.wilk@...cle.com>
Cc: xen-devel@...ts.xensource.com
Subject: [PATCH 0/3] [v4] kexec and kdump for Xen PVonHVM guests
The following series implements kexec and kdump in a Xen PVonHVM guest.
It is (should be) available via git:
git://github.com/olafhering/linux.git xen-kexec-3.0
The kexec or kdump kernel has to take care of already allocated virqs,
PV devices in Closed or Connected state, and of registered watches in
the old kernel. With the three patches these conditions are checked
during boot of the new kernel rather than in the reboot/crash path.
A fixed kexec-tools-2.0.2 package is required:
http://lists.infradead.org/pipermail/kexec/2011-May/005026.html
http://lists.infradead.org/pipermail/kexec/2011-August/005339.html
Another fix is for xenstored, it has to accept the XS_INTRODUCE from a guest:
http://lists.xensource.com/archives/html/xen-devel/2011-08/msg00007.html
One open issue is the balloon driver. It removes pages from the guest
and gives them back to the hypervisor. The kexec kernel is not aware of
the fact that some pages are unavailable, and hangs or crashes.
The workaround for the time being is:
if test -f /sys/devices/system/xen_memory/xen_memory0/target -a \
-f /sys/devices/system/xen_memory/xen_memory0/target_kb
then
cat /sys/devices/system/xen_memory/xen_memory0/target > \
/sys/devices/system/xen_memory/xen_memory0/target_kb
fi
kexec -e
This has to be resolved with another series of changes.
Olaf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists