Hi, Le 23/11/2012 02:56, Andrew Cooper a écrit : > For within-guest kexec/kdump functionality, I agree that it is barking > mad. However, we do see cloud operators interested in the idea so VM > administrators can look after their crashes themselves. It's not "barking mad" when your dayjob is to investigate and fix other people's kernel problems. Right now, it's impossible to get a kernel image of a failing EC2 instance, so every time someone shows up with a "my kernel crashes in my instance", we're lest with mostly unusable backtraces and oops messages. When I'm able to reproduce someone's kernel panic, I'm quite happy to be able to use virtualization to run a kernel dump analysis on a locally reproduced context. It's also quite useful when packaging things like makedumpfile, kdump-tools to be able to avoid having to rely on bare metal to test new releases. So yes, in theory it may look barking mad, but real life is somewhat different. Kind regards, ...Louis -- Louis Bouchard Backline Support Analyst Canonical Ltd Ubuntu support: http://landscape.canonical.com _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
