Hi Don, Hi all,
The key reason why I think that kexec/kdump does makes sense for xen, at
least to some extent, is for the case where the hypervisor goes into a
bad state, and you actually want to get rid of it and kdump into
something else for forensics. There is also the advantage that by
kexecing xen, you get access to the entire physical machine, either for
crash-dump analysis, or because *gasp* you want to get out of xen for
some other crazy reason :) And, on hardware that takes forever and a day
to reboot, I believe that doing a kexec will be quite useful for
hypervisor development.
I would also like to note, that while my patch does involve moving parts
of kexec/kdump into the hypervisor, and more similar parts need to be
added in order to support other architectures, it is by no means all of
kexec/kdump.
--
Horms
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|