[ kvm-Bugs-1935481 ] unhandled vm exit: 0x80000021 vcpu_id 0
Bugs item #1935481, was opened at 2008-04-05 18:37 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1935481group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Balaji Rao (balajirrao) Assigned to: Nobody/Anonymous (nobody) Summary: unhandled vm exit: 0x8021 vcpu_id 0 Initial Comment: Win Vista Ultimate 32 bit does not work. It works fine with -no-kvm. No problems during installation. Problem surfaces only on first boot. bash-3.2# qemu-system-x86_64 -m 1536 -hda vista.img unhandled vm exit: 0x8021 vcpu_id 0 rax 0010 rbx 0080 rcx rdx 0080 rsi 0026b238 rdi 0008b238 rsp 0200 rbp 1f20 r8 r9 r10 r11 r12 r13 r14 r15 rip 009b rflags 00023002 cs b000 (002b/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ds 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) es 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ss 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) fs 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) gs 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) tr (fffbd000/2088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt (/ p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt 2b/27 idt 0/3ff cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 Aborted -- Comment By: Jes Sorensen (jessorensen) Date: 2010-06-18 17:44 Message: Vista Ultimate x32 installs and boots fine here using recent kvm and qemu-kvm, at least when I tried yesterday. If this problem reoccurs, please open a new bug in launchpad. Cheers, Jes -- Comment By: Adam Hough (nilaab) Date: 2008-06-12 19:18 Message: Logged In: YES user_id=2116547 Originator: NO Could this bug be similar to what I am seeing in Fedora 9 with a PAE enabled kernel? https://bugzilla.redhat.com/show_bug.cgi?id=451035 -- Comment By: Justin Keogh (jakeogh) Date: 2008-05-05 07:57 Message: Logged In: YES user_id=2079304 Originator: NO I got the same error with kvm-67 on: Linux xeonbox 2.6.25-gentoo-r1 #14 SMP Mon May 5 03:46:09 MST 2008 x86_64 Intel(R) Xeon(R) CPU X5482 @ 3.20GHz GenuineIntel GNU/Linux guest: windows vista ultimate 32bit... crash happens on first boot after install. -no-acapi didnt help. -no-kvm works. -- Comment By: Balaji Rao (balajirrao) Date: 2008-04-06 16:22 Message: Logged In: YES user_id=1958935 Originator: YES Thats weird. Let me try, I'm working to fix it, or atleast to understand the problem better. -- Comment By: Technologov (technologov) Date: 2008-04-06 16:04 Message: Logged In: YES user_id=1839746 Originator: NO Unreproducible. -Alexey Technologov. -- Comment By: Balaji Rao (balajirrao) Date: 2008-04-06 15:58 Message: Logged In: YES user_id=1958935 Originator: YES I'm not sure if its a regression. The first time ever I installed and tried booting vista, it wouldn't run. -- Comment By: Avi Kivity (avik) Date: 2008-04-06 15:34 Message: Logged In: YES user_id=539971 Originator: NO Is this a regression? If so, which kvm version worked last? I've successfully installed and booted Vista in the past. -- Comment By: Balaji Rao (balajirrao) Date: 2008-04-05 21:26 Message: Logged In: YES user_id=1958935 Originator: YES Some critical facts i missed.. Host : Intel I forgot to mention the version too! KVM : kvm-64-210-g78e0016 kvm-userspace : kvm-64-18-gd84f71a -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1935481group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: unhandled vm exit: 0x80000021 vcpu_id 0
Gabe Black wrote: Hello again. I'm making more progress getting KVM going in M5, and right now I'm trying to figure out why I'm getting an unhandled vm exit with exit code 0x8021. According to Intel's manual, something about the guest state isn't being set up correctly. I dumped the initial register state for the 0th virtual CPU and noticed that some things Intel claims are illegal show up there, for instance having paging and protected mode disabled. I'm assuming there's some cooking done to the state as presented to KVM to, for instance, substitute V8086 mode for real mode, etc. I've fixed a number of bugs in M5 that cleaned up some issues, but I'm hoping somebody with more knowledge can tell me what illegal state is still there that would make it through the kvms twiddling and cause VMX to abort. One thing that I know looks funny is that the limit on the IDT is zero, but I haven't been able to find any evidence in the manuals that that's considered wrong rather than just a bad idea. Any help here would be very appreciated! idt.limit = 0 should be fine. cs 0008 (/ p 1 dpl 0 db 0 s 1 type a l 1 g 1 avl 0) ds 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) es 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) ss 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) fs 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) gs 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) Try setting bit 1 (accessed) on the types here. tr 0018 (/ p 1 dpl 0 db 1 s 0 type b l 0 g 1 avl 0) ldt (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gdt 76000/17 idt 0/0 cr0 8011 cr2 0 cr3 7 cr4 20 cr8 0 efer 500 kvm-kmod.git contains a vmx-debug.c which does the same checks as the cpu. If you link it in and call vm_entry_test() just before guest entry, it will point out where the state is bad. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
unhandled vm exit: 0x80000021 vcpu_id 0
Hello again. I'm making more progress getting KVM going in M5, and right now I'm trying to figure out why I'm getting an unhandled vm exit with exit code 0x8021. According to Intel's manual, something about the guest state isn't being set up correctly. I dumped the initial register state for the 0th virtual CPU and noticed that some things Intel claims are illegal show up there, for instance having paging and protected mode disabled. I'm assuming there's some cooking done to the state as presented to KVM to, for instance, substitute V8086 mode for real mode, etc. I've fixed a number of bugs in M5 that cleaned up some issues, but I'm hoping somebody with more knowledge can tell me what illegal state is still there that would make it through the kvms twiddling and cause VMX to abort. One thing that I know looks funny is that the limit on the IDT is zero, but I haven't been able to find any evidence in the manuals that that's considered wrong rather than just a bad idea. Any help here would be very appreciated! Gabe rax rbx rcx rdx rsi 00090200 rdi rsp rbp r8 r9 r10 r11 r12 r13 r14 r15 rip 0020 rflags 0002 cs 0008 (/ p 1 dpl 0 db 0 s 1 type a l 1 g 1 avl 0) ds 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) es 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) ss 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) fs 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) gs 0010 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) tr 0018 (/ p 1 dpl 0 db 1 s 0 type b l 0 g 1 avl 0) ldt (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gdt 76000/17 idt 0/0 cr0 8011 cr2 0 cr3 7 cr4 20 cr8 0 efer 500 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [ Re: unhandled vm exit: 0x80000021 vcpu_id 0]
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]
Messaggio originale Da: [EMAIL PROTECTED] Data: 09/10/2008 16.58 A: [EMAIL PROTECTED][EMAIL PROTECTED] Cc: kvmkvm@vger.kernel.org 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] p. [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 PER I PRIMI TRE MESI. In seguito paghi
Re: [ Re: unhandled vm exit: 0x80000021 vcpu_id 0]
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] p. [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 PER I PRIMI TRE MESI. In seguito paghi solo ??? 19,95 al mese. Attivala subito, l? offerta è valida fino al 02/10/2008! http://abbonati.tiscali. it/promo/adsl8mega/ ___ Visita Tiscali Shopping e troverai tutto quello che cerchi ai prezzi migliori http://shopping.tiscali.it/ -- regards, Yang, Sheng Index: kvm-76
Re: unhandled vm exit: 0x80000021 vcpu_id 0
Hi, I understand the particularity (checkpoint) of this case. Any way, in the attachment the dmesg log and the output of the dmesg command. 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 PER I PRIMI TRE MESI. In seguito paghi solo € 19,95 al mese. Attivala subito, l?offerta è valida fino al 02/10/2008! http://abbonati.tiscali.it/promo/adsl8mega/ dmesg.tgz Description: GNU Zip compressed data
Re: unhandled vm exit: 0x80000021 vcpu_id 0
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 PER I PRIMI TRE MESI. In seguito paghi solo ??? 19,95 al mese. Attivala subito, l?offerta è valida fino al 02/10/2008! http://abbonati.tiscali.it/promo/adsl8mega/ -- 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
unhandled vm exit: 0x80000021 vcpu_id 0
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. 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 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. 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. Regards, Pier Luigi Con Tiscali Adsl 8 Mega navighi SENZA LIMITI e GRATIS PER I PRIMI TRE MESI. In seguito paghi solo € 19,95 al mese. Attivala ora, l?offerta è valida fino al 02/10/2008! http://abbonati.tiscali.it/promo/adsl8mega/ -- 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: unhandled vm exit: 0x80000021 vcpu_id 0
On Mon, Sep 29, 2008 at 6:18 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] 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. -- 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
[ kvm-Bugs-1935481 ] unhandled vm exit: 0x80000021 vcpu_id 0
Bugs item #1935481, was opened at 2008-04-05 11:37 Message generated for change (Comment added) made by nilaab You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1935481group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Balaji Rao R (balajirrao) Assigned to: Nobody/Anonymous (nobody) Summary: unhandled vm exit: 0x8021 vcpu_id 0 Initial Comment: Win Vista Ultimate 32 bit does not work. It works fine with -no-kvm. No problems during installation. Problem surfaces only on first boot. bash-3.2# qemu-system-x86_64 -m 1536 -hda vista.img unhandled vm exit: 0x8021 vcpu_id 0 rax 0010 rbx 0080 rcx rdx 0080 rsi 0026b238 rdi 0008b238 rsp 0200 rbp 1f20 r8 r9 r10 r11 r12 r13 r14 r15 rip 009b rflags 00023002 cs b000 (002b/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ds 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) es 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ss 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) fs 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) gs 0020 (0200/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) tr (fffbd000/2088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt (/ p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt 2b/27 idt 0/3ff cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 Aborted -- Comment By: Adam Hough (nilaab) Date: 2008-06-12 12:18 Message: Logged In: YES user_id=2116547 Originator: NO Could this bug be similar to what I am seeing in Fedora 9 with a PAE enabled kernel? https://bugzilla.redhat.com/show_bug.cgi?id=451035 -- Comment By: Justin Keogh (jakeogh) Date: 2008-05-05 00:57 Message: Logged In: YES user_id=2079304 Originator: NO I got the same error with kvm-67 on: Linux xeonbox 2.6.25-gentoo-r1 #14 SMP Mon May 5 03:46:09 MST 2008 x86_64 Intel(R) Xeon(R) CPU X5482 @ 3.20GHz GenuineIntel GNU/Linux guest: windows vista ultimate 32bit... crash happens on first boot after install. -no-acapi didnt help. -no-kvm works. -- Comment By: Balaji Rao R (balajirrao) Date: 2008-04-06 09:22 Message: Logged In: YES user_id=1958935 Originator: YES Thats weird. Let me try, I'm working to fix it, or atleast to understand the problem better. -- Comment By: Technologov (technologov) Date: 2008-04-06 09:04 Message: Logged In: YES user_id=1839746 Originator: NO Unreproducible. -Alexey Technologov. -- Comment By: Balaji Rao R (balajirrao) Date: 2008-04-06 08:58 Message: Logged In: YES user_id=1958935 Originator: YES I'm not sure if its a regression. The first time ever I installed and tried booting vista, it wouldn't run. -- Comment By: Avi Kivity (avik) Date: 2008-04-06 08:34 Message: Logged In: YES user_id=539971 Originator: NO Is this a regression? If so, which kvm version worked last? I've successfully installed and booted Vista in the past. -- Comment By: Balaji Rao R (balajirrao) Date: 2008-04-05 14:26 Message: Logged In: YES user_id=1958935 Originator: YES Some critical facts i missed.. Host : Intel I forgot to mention the version too! KVM : kvm-64-210-g78e0016 kvm-userspace : kvm-64-18-gd84f71a -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1935481group_id=180599 -- 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
