My kernel fails with kexec

2007-10-02 Thread Jun Koi
Greetings,

I have a kernel (which is not Linux kernel), and want to have it
worked with kexec. That means I want to get kexec boot my kernel.
Fortunately, kexec crashes when booting it. (with kexec -e command)

My suspect is that my kernel is not written to "support" kexec. So
could anybody tell me what is the requirement of a kernel, so it works
with kexec?

"kexec -e" spits out the below message in QEMU when booting my kernel. Any
hint where the problem lies, and on how to debug the problem?

Thanks,
Jun


(qemu) qemu: fatal: triple fault
EAX=1500 EBX=001001f1 ECX= EDX=4081
ESI=002ae8c0 EDI=002ac8c0 EBP=e098 ESP=8ffe
EIP=0d05 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0018   00cf9300
CS =4020 00040200  008f9f00
SS =4000 0004  9300
DS =0018   00cf9300
FS =0018   00cf9300
GS =0018   00cf9300
LDT=   8000
TR =0080 c1fd7000 2073 c10089fd
GDT= 0040a938 0017
IDT= c000 
CR0=0010 CR2=b7ed6200 CR3= CR4=
CCS=8000 CCD=4000 CCO=SARL
FCW=037f FSW= [ST=0] FTW=00 MXCSR=1f80
FPR0=  FPR1= 
FPR2=  FPR3= 
FPR4=  FPR5= 
FPR6=f424 4012 FPR7= 
XMM00= XMM01=
XMM02= XMM03=
XMM04= XMM05=
XMM06= XMM07=
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


My kernel fails with kexec

2007-10-02 Thread Jun Koi
Greetings,

I have a kernel (which is not Linux kernel), and want to have it
worked with kexec. That means I want to get kexec boot my kernel.
Fortunately, kexec crashes when booting it. (with kexec -e command)

My suspect is that my kernel is not written to support kexec. So
could anybody tell me what is the requirement of a kernel, so it works
with kexec?

kexec -e spits out the below message in QEMU when booting my kernel. Any
hint where the problem lies, and on how to debug the problem?

Thanks,
Jun


(qemu) qemu: fatal: triple fault
EAX=1500 EBX=001001f1 ECX= EDX=4081
ESI=002ae8c0 EDI=002ac8c0 EBP=e098 ESP=8ffe
EIP=0d05 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0018   00cf9300
CS =4020 00040200  008f9f00
SS =4000 0004  9300
DS =0018   00cf9300
FS =0018   00cf9300
GS =0018   00cf9300
LDT=   8000
TR =0080 c1fd7000 2073 c10089fd
GDT= 0040a938 0017
IDT= c000 
CR0=0010 CR2=b7ed6200 CR3= CR4=
CCS=8000 CCD=4000 CCO=SARL
FCW=037f FSW= [ST=0] FTW=00 MXCSR=1f80
FPR0=  FPR1= 
FPR2=  FPR3= 
FPR4=  FPR5= 
FPR6=f424 4012 FPR7= 
XMM00= XMM01=
XMM02= XMM03=
XMM04= XMM05=
XMM06= XMM07=
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [kvm-devel] [GIT PULL][RESEND] KVM cpu hotplug fixes

2007-06-02 Thread Jun Koi

Hi Avi,

On 6/2/07, Avi Kivity <[EMAIL PROTECTED]> wrote:

Linus Torvalds wrote:
> Don't send me pull requests like this. And absolutely do NOT send them as
> resends. I just  get grumpy.
>
> If all the added code had been KVM-only, I might not care. But when the
> bulk of the code touches core files, you had better explain why this is so
> important that it cannot wait for the next merge window.

Ok.  This was really wanted by laptop-carrying users, but I guess
they'll have to wait for 2.6.23.



Could you explain a bit:

1) Why CPU hotplug is that important for virtualization?

2) Why this patch is wanted by laptop users?

I tried to answer myself those questions, but to no avail.

Thank you,
Jun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [kvm-devel] [GIT PULL][RESEND] KVM cpu hotplug fixes

2007-06-02 Thread Jun Koi

Hi Avi,

On 6/2/07, Avi Kivity [EMAIL PROTECTED] wrote:

Linus Torvalds wrote:
 Don't send me pull requests like this. And absolutely do NOT send them as
 resends. I just  get grumpy.

 If all the added code had been KVM-only, I might not care. But when the
 bulk of the code touches core files, you had better explain why this is so
 important that it cannot wait for the next merge window.

Ok.  This was really wanted by laptop-carrying users, but I guess
they'll have to wait for 2.6.23.



Could you explain a bit:

1) Why CPU hotplug is that important for virtualization?

2) Why this patch is wanted by laptop users?

I tried to answer myself those questions, but to no avail.

Thank you,
Jun
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/