Re: [ Re: unhandled vm exit: 0x80000021 vcpu_id 0]

2008-10-12 Thread Sheng Yang
Hi Pier

The only thing I can tell that is, seems guest completely messed up...
It ran into some non-code segment.

> unhandled vm exit: 0x8021 vcpu_id 0
> rax 0007 rbx 1490 rcx  rdx
> 19a0 rsi  rdi  rsp
> 0080 rbp 96bf r8   r9
>  r10  r11  r12
>  r13  r14  r15
>  rip 002a rflags 00023202
> cs 14a2 (/ p 0 dpl 0 db 0 s 0 type 9 l 0 g 0 avl 0)
> ds 19a0 (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
> es 1a31 (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
> ss 1a29 (/ p 0 dpl 0 db 0 s 0 type 1 l 0 g 0 avl 0)
Segments maybe messed up...

> fs  (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
> gs  (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
> tr 0058 (00201ffa/ p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
> ldt  (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
> gdt 20/1dd8
> idt 201df0/188
> cr0 8019 cr2 0 cr3 144 cr4 0 cr8 0 efer 0

CR0.PE set(sorry for wrong decode before...), CR0.PG set. Guest in
protected mode. But CR4 is wrong, at least CR4.PAE and CR4.VMXE should
be set.

> code: 00 f0 53 ff 00 f0 53 ff 00 f0 a5 fe 00 f0 87 e9 00 f0 53 ff --> 00 f0
> 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 57 ef 00 f0 53 ff 00 f0 3a 83 00 c0 4d
> f8 00 f0

Seems like meaningless code...

Well, still don't know what the "checkpoint" done caused this... At
least it seems more than a emulation bug.

Anybody else have idea?...

--
regards
Yang, Sheng
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [ Re: unhandled vm exit: 0x80000021 vcpu_id 0]

2008-10-10 Thread [EMAIL PROTECTED]


>Messaggio originale
>Da: [EMAIL PROTECTED]
>Data: 09/10/2008 16.58
>A: "[EMAIL PROTECTED]"<[EMAIL PROTECTED]>
>Cc: "kvm"
>Ogg: Re: [ Re: unhandled vm exit: 0x8021 vcpu_id 0]
>
>On Wed, Oct 8, 2008 at 7:16 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]
it> wrote:
>> Hi Yang,
>> I often hibernate my Linux, so may be that the loadmodule message 
is
>> missing in the dmesg because it is too old.
>>
>> I have rebooted the system and I attach a "clean" dmesg.
>
>Yeah, now I can see the load info of kvm-76.
>
>>
>> What means  "Windows always trig a apic write error before Jan's 
patch
>> make them slience"? which Windows?
>
>At least Windows XP like to do this, now for upstream, Jan's patch 
clean it.
>>
>> However, when I try ro run qemu/kvm using the winxp image, no error
>> happens in the dmesg.  I can see the error as output of the 
qemu/kvm
>> command.
>
>It's indeed hard to debug with so limit info... I still suggest you 
to
>fill a bug first.

Ok, I will try to do it.

>
>And if you have time, please try the attached patch and update info

I have compiled kvm-76 with your patch. In the attachment the result

Have a nice week end, Pier Luigi.
>
>--
>regards
>Yang, Sheng
>>
>> Reagrds,
>>  Pier Luigi
>>
>>
>>  Original Message 
>> Subject:Re: unhandled vm exit: 0x8021 vcpu_id 0
>> Date:   Fri, 3 Oct 2008 08:57:31 +0800
>> From:   Sheng Yang <[EMAIL PROTECTED]>
>> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>> CC: [EMAIL PROTECTED], kvm@vger.kernel.org
>> References: <[EMAIL PROTECTED]>
>>
>>
>>
>> On Fri, Oct 03, 2008 at 12:16:20AM +0200, [EMAIL PROTECTED] wrote:
>>>
>>> Hi,
>>> I understand the "particularity" (checkpoint) of this case.
>>
>> Hi Pier
>>
>> Thanks for your understanding. :)
>>>
>>> Any way, in the attachment the dmesg log and the output of the
>> dmesg
>>> command.
>>
>> But it's strange that I almost can't see anything correlated with 
kvm
>> in the
>> log. If you built kvm as a modules(I suppose you did it because you
>> tried
>> many versions), at least something like "load kvm module xxx" 
should
>> appear(and Windows always trig a apic write error before Jan's 
patch
>> make
>> them slience).
>>
>> Is this the dmesg when the error was happening?
>>
>> --
>> regards
>> Yang, Sheng
>>
>>>
>>> thanks for your helpfulness.
>>>
>>> Regards.
>>>
>>> Sheng Yang wrote:
>>> > On Mon, Sep 29, 2008 at 6:18 PM, [EMAIL PROTECTED] > [EMAIL PROTECTED]
>>> it> wrote:
>>> >
>>> >> Hi,
>>> >> I have successfully installed windows XP SP2 on kvm. After the
>>> >> installation I have launched the setup of  "Checkpoint -
>> Pointsec"
>>> for
>>> >> the entire disk encryption.
>>> >>
>>> >
>>> > Hi Pier
>>> >
>>> > Can you issue a bug for this? But sadly "Checkpoint" is a
>> commercial
>>> > software, we may not deal with it directly and immediately.
>>> >
>>> >
>>> >> The first step of installation was run successfully, but when 
the
>>> >> system reboots and "Pointsec" loads the initial code, the
>> following
>>> >> error happens:
>>> >>
>>>
>> 
==
>>> >> unhandled vm exit: 0x8021 vcpu_id 0
>>> >> rax 0007 rbx 1490 rcx 
>> rdx
>>> >> 19a0
>>> >> rsi  rdi  rsp 0080
>> rbp
>>> >> 96bf
>>> >> r8   r9   r10 
>> r11
>>> >> 
>>> >> r12  r13  r14 
>> r15
>>> >> 
>>> >> rip 002a rflags 00023202
>>> >> cs 14a2 (/ p 0 dpl 0 db 0 s 0 type 9 l 0 g 0 
avl
>> 0)
>>> >> ds 19a0 (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 
avl
>> 0)
>>> >> es 1a31 (/ p 0 dpl 0 db 0 s 0 t

Re: [ Re: unhandled vm exit: 0x80000021 vcpu_id 0]

2008-10-09 Thread Sheng Yang
On Wed, Oct 8, 2008 at 7:16 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi Yang,
> I often hibernate my Linux, so may be that the loadmodule message is
> missing in the dmesg because it is too old.
>
> I have rebooted the system and I attach a "clean" dmesg.

Yeah, now I can see the load info of kvm-76.

>
> What means  "Windows always trig a apic write error before Jan's patch
> make them slience"? which Windows?

At least Windows XP like to do this, now for upstream, Jan's patch clean it.
>
> However, when I try ro run qemu/kvm using the winxp image, no error
> happens in the dmesg.  I can see the error as output of the qemu/kvm
> command.

It's indeed hard to debug with so limit info... I still suggest you to
fill a bug first.

And if you have time, please try the attached patch and update info.

--
regards
Yang, Sheng
>
> Reagrds,
>  Pier Luigi
>
>
>  Original Message 
> Subject:Re: unhandled vm exit: 0x8021 vcpu_id 0
> Date:   Fri, 3 Oct 2008 08:57:31 +0800
> From:   Sheng Yang <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], kvm@vger.kernel.org
> References: <[EMAIL PROTECTED]>
>
>
>
> On Fri, Oct 03, 2008 at 12:16:20AM +0200, [EMAIL PROTECTED] wrote:
>>
>> Hi,
>> I understand the "particularity" (checkpoint) of this case.
>
> Hi Pier
>
> Thanks for your understanding. :)
>>
>> Any way, in the attachment the dmesg log and the output of the
> dmesg
>> command.
>
> But it's strange that I almost can't see anything correlated with kvm
> in the
> log. If you built kvm as a modules(I suppose you did it because you
> tried
> many versions), at least something like "load kvm module xxx" should
> appear(and Windows always trig a apic write error before Jan's patch
> make
> them slience).
>
> Is this the dmesg when the error was happening?
>
> --
> regards
> Yang, Sheng
>
>>
>> thanks for your helpfulness.
>>
>> Regards.
>>
>> Sheng Yang wrote:
>> > On Mon, Sep 29, 2008 at 6:18 PM, [EMAIL PROTECTED]  [EMAIL PROTECTED]
>> it> wrote:
>> >
>> >> Hi,
>> >> I have successfully installed windows XP SP2 on kvm. After the
>> >> installation I have launched the setup of  "Checkpoint -
> Pointsec"
>> for
>> >> the entire disk encryption.
>> >>
>> >
>> > Hi Pier
>> >
>> > Can you issue a bug for this? But sadly "Checkpoint" is a
> commercial
>> > software, we may not deal with it directly and immediately.
>> >
>> >
>> >> The first step of installation was run successfully, but when the
>> >> system reboots and "Pointsec" loads the initial code, the
> following
>> >> error happens:
>> >>
>>
> ==
>> >> unhandled vm exit: 0x8021 vcpu_id 0
>> >> rax 0007 rbx 1490 rcx 
> rdx
>> >> 19a0
>> >> rsi  rdi  rsp 0080
> rbp
>> >> 96bf
>> >> r8   r9   r10 
> r11
>> >> 
>> >> r12  r13  r14 
> r15
>> >> 
>> >> rip 002a rflags 00023202
>> >> cs 14a2 (/ p 0 dpl 0 db 0 s 0 type 9 l 0 g 0 avl
> 0)
>> >> ds 19a0 (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl
> 0)
>> >> es 1a31 (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl
> 0)
>> >> ss 1a29 (/ p 0 dpl 0 db 0 s 0 type 1 l 0 g 0 avl
> 0)
>> >> fs  (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl
> 0)
>> >> gs  (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl
> 0)
>> >> tr 0058 (00201ffa/ p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl
> 0)
>> >> ldt  (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0
> avl
>> 0)
>> >> gdt 20/1dd8
>> >> idt 201df0/188
>> >> cr0 8019 cr2 0 cr3 144 cr4 0 cr8 0 efer 0
>> >>
>> >
>> > What's this... CR0.PE clear, CR0.PG set... And segment register
> also
>> > strange. May be some real emulation wrong...
>> >
>> >
>> >> Aborted
>> >>
>>
> ==
>> >> I am able to boot this system (image) using qemu (with kqemu
>> enabled
>> >> for user code), but not using kvm.
>> >> I have also tried with the options: -no-kvm-irqchip -no-kvm-pit -
>> no-
>> >> acpi without success. Only the -no-kvm option works.
>> >> I have tried these kvm releases: from 65 to 76; and these kernel
>> >> (vanilla) releases: from 2.6.23.1 to 2.6.26.5.
>> >>
>> >
>> > Thanks for your patient...
>> >
>> >> My computer is a Dell D630 equipped with Intel(R) Core(TM)2 Duo
> CPU
>> >> T7300  @ 2.00GHz
>> >> The HOST Linux distributions used are: Fedora 8/9 for i386, and
>> Fedora
>> >> 9 for x86_64.
>> >>
>> >
>> > Can you show dmesg as well? That's also helps.
>> >
>> >
>>
>>
>>
>>
>>
>>
>>
>> ___
>>
>> Con Tiscali Adsl 8 Mega navighi SENZA LIMITI e GRATIS PE