KVM-49 crash on XP(SP2) install

KVM-49 crash on XP(SP2) install

[Tim Dempsey]

Avi,

I have subscribed to the mailing list, so hopefully my responses will
be threaded.

The patch you sent appeared to work initially. But when I repeated the install
I received the same symptom. A blank qemu/kvm window with stopped in the title
bar.

Host - 32 bit Linux
Linux version 2.6.23-gentoo (root@jart) (gcc version 4.1.2 (Gentoo 4.1.2)) #1
SMP PREEMPT Sun Oct 28 13:40:52 EDT 2007

qemu cmd line:
/usr/local/kvm/bin/qemu-system-x86_64 test.img -cdrom Microsoft\ Windows\ XP\
Professional\ \(SP2\).iso -boot d

cpu info:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 14
model name      : Genuine Intel(R) CPU           T2600  @ 2.16GHz
stepping        : 8
cpu MHz         : 2167.000
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc arch_perfmon
bts pni monitor vmx est tm2 xtpr
bogomips        : 4326.21
clflush size    : 64

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 14
model name      : Genuine Intel(R) CPU           T2600  @ 2.16GHz
stepping        : 8
cpu MHz         : 2167.000
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc arch_perfmon
bts pni monitor vmx est tm2 xtpr
bogomips        : 4322.47
clflush size    : 64

dmesg output:
general protection fault: 0000 [#1]
PREEMPT SMP
Modules linked in: kvm_intel kvm ipx p8022 psnap llc p8023 arc4 ecb blkcipher
cryptomgr crypto_algapi ieee80211_crypt_wep ipw3945 snd_hda_intel snd_pcm
snd_timer snd snd_page_alloc fglrx(P) yenta_socket rsrc_nonstatic pcmcia_core
dm_bbr dm_snapshot e1000 xfs jfs dm_mirror scsi_wait_scan
CPU:    0
EIP:    0060:[<f8f99222>]    Tainted: P        VLI
EFLAGS: 00210202   (2.6.23-gentoo #1)
EIP is at vmx_save_host_state+0x132/0x190 [kvm_intel]
eax: 0036c68f   ebx: 00000000   ecx: c0000080   edx: 00000000
esi: f5df0000   edi: 0036c68e   ebp: 00000000   esp: f5d09d34
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process qemu-system-x86 (pid: 7852, ti=f5d08000 task=f5d03a40 task.ti=f5d08000)
Stack: 0a657571 00000000 f5df0000 00000000 f58b1000 f5df0000 f984e8a8 b72ce067
       00000001 10002800 00000000 f984f030 f5fad840 00000000 f984fb80 dfe2ad48
       c018aa96 00000000 d662d853 dfe2ad50 000f41a8 f5d09dc4 f5d4e434 f5d03a40
Call Trace:
 [<f984e8a8>] kvm_vcpu_ioctl_run+0xa8/0x4c0 [kvm]
 [<f984f030>] kvm_vcpu_ioctl+0x0/0xbb0 [kvm]
 [<f984fb80>] kvm_vcpu_ioctl+0xb50/0xbb0 [kvm]
 [<c018aa96>] __d_lookup+0xb6/0x150
 [<c0123f8f>] enqueue_entity+0xbf/0x230
 [<c0122c65>] kunmap_atomic+0x35/0x70
 [<c0155eb3>] file_read_actor+0xf3/0x100
 [<c0156865>] do_generic_mapping_read+0x3c5/0x490
 [<c0122c65>] kunmap_atomic+0x35/0x70
 [<c015abd3>] get_page_from_freelist+0x2c3/0x3c0
 [<c044ed0e>] _read_unlock_irq+0xe/0x30
 [<c015613e>] find_lock_page+0x8e/0xb0
 [<c0158685>] filemap_fault+0x215/0x4b0
 [<c0160a97>] __inc_zone_state+0x17/0x70
 [<c01620a3>] __do_fault+0x173/0x380
 [<c0164340>] handle_mm_fault+0x190/0x700
 [<c01449e6>] getnstimeofday+0x36/0xd0
 [<c01430f2>] ktime_get_ts+0x22/0x60
 [<f984f030>] kvm_vcpu_ioctl+0x0/0xbb0 [kvm]
 [<c0184c1b>] do_ioctl+0x2b/0x90
 [<c0184cdc>] vfs_ioctl+0x5c/0x290
 [<c0184f4d>] sys_ioctl+0x3d/0x70
 [<c010537e>] sysenter_past_esp+0x5f/0x85
 =======================
Code: 31 d9 31 f8 09 c1 74 2b 8b 0c 24 b8 01 00 00 00 31 db 89 86 74 0d 00 00 89
ea 89 f8 09 da 81 e1 01 08 00 00 09 c8 b9 80 00 00 c0 <0f> 30 ff 86 b0 00 00 00
8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b
EIP: [<f8f99222>] vmx_save_host_state+0x132/0x190 [kvm_intel] SS:ESP
0068:f5d09d34
note: qemu-system-x86[7852] exited with preempt_count 1
general protection fault: 0000 [#2]
PREEMPT SMP
Modules linked in: kvm_intel kvm ipx p8022 psnap llc p8023 arc4 ecb blkcipher
cryptomgr crypto_algapi ieee80211_crypt_wep ipw3945 snd_hda_intel snd_pcm
snd_timer snd snd_page_alloc fglrx(P) yenta_socket rsrc_nonstatic pcmcia_core
dm_bbr dm_snapshot e1000 xfs jfs dm_mirror scsi_wait_scan
CPU:    0
EIP:    0060:[<f8f97018>]    Tainted: P      D VLI
EFLAGS: 00210046   (2.6.23-gentoo #1)
EIP is at load_msrs+0x18/0x30 [kvm_intel]
eax: 0a657571   ebx: f5816ff8   ecx: 65707954   edx: 00000000
esi: 00000000   edi: 00000001   ebp: f5df0000   esp: f5d09c2c
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process qemu-system-x86 (pid: 7852, ti=f5d08000 task=f5d03a40 task.ti=f5d08000)
Stack: 00000000 00000001 00000000 f8f98e3a 00ff003b c2816000 f5df0004 00000000
       00000010 f5d03500 f984c59c f985adf9 dfefd340 f5d03a40 f985aae2 00000010
       f5d03a40 f5d03500 f5d09c88 dfefd340 f5d08000 00000001 f5d08000 c044c6b0
Call Trace:
 [<f8f98e3a>] vmx_vcpu_put+0xfa/0x130 [kvm_intel]
 [<f984c59c>] kvm_sched_out+0xc/0x10 [kvm]
 [<f985adf9>] preempt_notifier_trigger+0x79/0x90 [kvm]
 [<f985aae2>] pn_int1_handler+0x12/0x30 [kvm]
 [<c044c6b0>] schedule+0x0/0x700
 [<c012f3c6>] do_exit+0x576/0x7b0
 [<c0106acd>] die+0x26d/0x280
 [<c044f630>] do_general_protection+0x0/0x2b0
 [<c044eeaa>] error_code+0x72/0x78
 [<f985007b>] kvm_emulate_pio_string+0x1b/0x320 [kvm]
 [<f8f99222>] vmx_save_host_state+0x132/0x190 [kvm_intel]
 [<f984e8a8>] kvm_vcpu_ioctl_run+0xa8/0x4c0 [kvm]
 [<f984f030>] kvm_vcpu_ioctl+0x0/0xbb0 [kvm]
 [<f984fb80>] kvm_vcpu_ioctl+0xb50/0xbb0 [kvm]
 [<c018aa96>] __d_lookup+0xb6/0x150
 [<c0123f8f>] enqueue_entity+0xbf/0x230
 [<c0122c65>] kunmap_atomic+0x35/0x70
 [<c0155eb3>] file_read_actor+0xf3/0x100
 [<c0156865>] do_generic_mapping_read+0x3c5/0x490
 [<c0122c65>] kunmap_atomic+0x35/0x70
 [<c015abd3>] get_page_from_freelist+0x2c3/0x3c0
 [<c044ed0e>] _read_unlock_irq+0xe/0x30
 [<c015613e>] find_lock_page+0x8e/0xb0
 [<c0158685>] filemap_fault+0x215/0x4b0
 [<c0160a97>] __inc_zone_state+0x17/0x70
 [<c01620a3>] __do_fault+0x173/0x380
 [<c0164340>] handle_mm_fault+0x190/0x700
 [<c01449e6>] getnstimeofday+0x36/0xd0
 [<c01430f2>] ktime_get_ts+0x22/0x60
 [<f984f030>] kvm_vcpu_ioctl+0x0/0xbb0 [kvm]
 [<c0184c1b>] do_ioctl+0x2b/0x90
 [<c0184cdc>] vfs_ioctl+0x5c/0x290
 [<c0184f4d>] sys_ioctl+0x3d/0x70
 [<c010537e>] sysenter_past_esp+0x5f/0x85
 =======================
Code: <0f> 30 46 83 c3 10 39 f7 75 ee 5b 5e 5f c3 8d 76 00 8d bc 27 00 00
EIP: [<f8f97018>] load_msrs+0x18/0x30 [kvm_intel] SS:ESP 0068:f5d09c2c
Fixing recursive fault but reboot is needed!

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Re: KVM-49 crash on XP(SP2) install

[Avi Kivity]

Tim Dempsey wrote:
> Avi,
>
> I have subscribed to the mailing list, so hopefully my responses will
> be threaded.
>   

You don't actually need to subscribe for that.  Simply hitting 
reply-to-all every time should work.


> The patch you sent appeared to work initially. But when I repeated the install
> I received the same symptom. A blank qemu/kvm window with stopped in the title
> bar.
>
>   

Looks like you're hitting a different problem now.

> Code: 31 d9 31 f8 09 c1 74 2b 8b 0c 24 b8 01 00 00 00 31 db 89 86 74 0d 00 00 89
> ea 89 f8 09 da 81 e1 01 08 00 00 09 c8 b9 80 00 00 c0 <0f> 30 ff 86 b0 00 00 00
> 8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b
> EIP: [<f8f99222>] vmx_save_host_state+0x132/0x190 [kvm_intel] SS:ESP
>   

Hmm, the EFER-less T2600 strikes again.  I'll prepare a patch.

-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Re: KVM-49 crash on XP(SP2) install

[Avi Kivity]

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

Avi Kivity wrote:
>
>> Code: 31 d9 31 f8 09 c1 74 2b 8b 0c 24 b8 01 00 00 00 31 db 89 86 74 
>> 0d 00 00 89
>> ea 89 f8 09 da 81 e1 01 08 00 00 09 c8 b9 80 00 00 c0 <0f> 30 ff 86 
>> b0 00 00 00
>> 8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b
>> EIP: [<f8f99222>] vmx_save_host_state+0x132/0x190 [kvm_intel] SS:ESP
>>   
>
> Hmm, the EFER-less T2600 strikes again.  I'll prepare a patch.
>

Sorry, forgot about this, but a guilty conscience reminded me.  Does the 
attached patch help?


-- 
Any sufficiently difficult bug is indistinguishable from a feature.


[-- Attachment #2: no-efer-on-some-cpus.patch --]
[-- Type: text/x-patch, Size: 390 bytes --]

diff --git a/kernel/vmx.c b/kernel/vmx.c
index 42e7fad..f4cb3c1 100644
--- a/kernel/vmx.c
+++ b/kernel/vmx.c
@@ -370,6 +370,8 @@ static void load_transition_efer(struct vcpu_vmx *vmx)
 	u64 guest_efer = vmx->guest_msrs[efer_offset].data;
 	u64 ignore_bits;
 
+	if (efer_offset < 0)
+		return;
 	/*
 	 * NX is emulated; LMA and LME handled by hardware; SCE meaninless
 	 * outside long mode

[-- Attachment #3: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-49 crash on XP(SP2) install

[Tim Dempsey]

I applied the attached patch to KVM-50 and installed XP(SP2) several
times with the following cmd line:

/usr/local/kvm/bin/qemu-system-x86_64 test.img -cdrom Microsoft\
Windows\ XP\ Professional\ \(SP2\).iso -m 512 -no-acpi -boot d

The install freezes on the first reboot after copying files to the
hard drive. If I close the window and re execute the cmd without the
'-boot d' switch the install completes. The only thing in the log is
the following messages(a lot of them):

Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring

The above message doesn't seem to happen after the install completes.

I also did several installs without the '-no-acpi' switch. The vm
froze several times during the install, but restarting the vm each
time and the install finally completed. Along with the vectoring
faults the log contained the following msg several times.

apic write: bad size=1 fee00030
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 0

I continue to get the above msgs with the acpi enabled.

Having said all that, both installs seem to run well. Thank you for the patch.

Tim

On 11/5/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> Avi Kivity wrote:
> >
> >> Code: 31 d9 31 f8 09 c1 74 2b 8b 0c 24 b8 01 00 00 00 31 db 89 86 74
> >> 0d 00 00 89
> >> ea 89 f8 09 da 81 e1 01 08 00 00 09 c8 b9 80 00 00 c0 <0f> 30 ff 86
> >> b0 00 00 00
> >> 8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b
> >> EIP: [<f8f99222>] vmx_save_host_state+0x132/0x190 [kvm_intel] SS:ESP
> >>
> >
> > Hmm, the EFER-less T2600 strikes again.  I'll prepare a patch.
> >
>
> Sorry, forgot about this, but a guilty conscience reminded me.  Does the
> attached patch help?
>
>
> --
> Any sufficiently difficult bug is indistinguishable from a feature.
>
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Re: KVM-49 crash on XP(SP2) install

[Avi Kivity]

Tim Dempsey wrote:
> I applied the attached patch to KVM-50 and installed XP(SP2) several
> times with the following cmd line:
>
> /usr/local/kvm/bin/qemu-system-x86_64 test.img -cdrom Microsoft\
> Windows\ XP\ Professional\ \(SP2\).iso -m 512 -no-acpi -boot d
>
> The install freezes on the first reboot after copying files to the
> hard drive. If I close the window and re execute the cmd without the
> '-boot d' switch the install completes. The only thing in the log is
> the following messages(a lot of them):
>
> Fault when IDT_Vectoring
> Fault when IDT_Vectoring
> Fault when IDT_Vectoring
>
>   

It's benign in most cases, though we do need to supress it when that's 
the case.

> Having said all that, both installs seem to run well. Thank you for the patch.
>
>   

Thanks for testing, I'll apply the patch.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/