On Mon, Oct 27, 2008 at 09:09:37AM -0400, Vivek Goyal wrote:
> On Mon, Oct 27, 2008 at 10:54:01AM +0200, Avi Kivity wrote:
<snip>
> >
> > The hang was likely caused by vmx blocking INIT.  Sigh.
> 
> Avi,
> 
> We boot kdump kernel with maxcpus=1. IIUC, in that code path we will not
> be using INIT. So did you try booting kdump kernel with maxcpus=1 and did
> it work for you? If not than problem could be something else.

Just checked it here: I am passing maxcpus=1 to the kdump kernel. My
full kexec commandline is this:

/sbin/kexec --console-serial -p '--command-line=ro root=/dev/vg0/rawhide rhgb  
console=ttyS0,115200 ignore_loglevel irqpoll maxcpus=1 reset_devices 
earlyprintk=ttyS0,115200' --initrd=/boot/initrd-2.6.28-rc2kdump.img 
/boot/vmlinuz-2.6.28-rc2

Additional info: I don't get the "I'm in purgatory" message on serial
console, when the system hangs. I do get the message if I trigger the
crash dump after unloading the kvm-intel module, so the serial console
is working.

-- 
Eduardo

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

Reply via email to