The other thing that should be considered here is how utterly
preposterous the notion of doing in-guest crash dumping is in a system
that contains a hypervisor. The reason for kdump is that on bare metal
there are no other options, but in a hypervisor system the right thing
should be for the hypervisor to do the dump (possibly spawning a clean
I/O domain if the I/O domain is necessary to access the media.)
There is absolutely no reason to have a crashkernel sitting around in
each guest, consuming memory, and possibly get corrupt.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
