> Eric W. Biederman wrote:>> Zachary Amsden <zach@vmware.com> writes:>> Huh? Rebooting through the BIOS and kexec are pretty much mutually exclusive.>> Looking at the patch I can't see what you are talking about either.>>>> Let me rephrase - kexec doesn't define calls for machine_shutdown and others> that are in arch/i386/kernel/reboot.c. So kexec requires BIOS reboot code to be> compiled in, even though the usage of the two is mutually exclusive.

Partially true. Basically it has never been optional to compile in theBIOS reboot code and kexec did not change that situation. Although itdid provide a similar mechanism.

>> Does kexec successfully work under VMWare?>>>> It should work just fine. But it could expose bugs on either end. I've been> monitoring our kexec testing, and I'll be able to help you with any issues that> we might find on the Linux side. :)

Ok.

>> machine_halt does not want to stop the processor. It is very much>> about killing the kernel and user space but having the software still>> linger a little.>>>> I was afraid of that. I can back that change out. The problem I had was that> the shutdown code I was running in userspace would not make the syscalls to> actually call machine_power_off, but machine_halt instead. Will fix.

/sbin/halt -p will call machine_power_off if pm_power_off is defined.otherwise it will call machine_halt.