Skip to contentSkip to conversation

kvm-48 release

ANNOUNCE Avi Kivity 3 participants 6 messages Oct 18, 2007 – Oct 19, 2007 5 messages not in the archive KVM

lore
Share & tools
lore

Avi Kivity

author
#0 lore raw

kvm-47 had a host memory corruption bug when setting the guest pte dirty bit, so here's kvm-48 with a fix.

Note that guest time accounting, below, will only work with Linux 2.6.24+.

Changes from kvm-47:
- use precise cpu accounting on ppc and s390 (Christian Borntraeger)
- make guest time accounting actually work (Laurent Vivier)
- fix host memory corruption when setting the guest dirty bit
- allow swapping with older userspace (Anthony Liguori)
- allow custom memory setup using libkvm (Gerd Hoffmann)

Notes:
If you use the modules bundled with kvm-48, you can use any version
of Linux from 2.6.9 upwards.
If you use the modules bundled with Linux 2.6.20, you need to use
kvm-12.
If you use the modules bundled with Linux 2.6.21, you need to use
kvm-17.
Modules from Linux 2.6.22 and up will work with any kvm version from
kvm-22. Some features may only be available in newer releases.
For best performance, use Linux 2.6.23-rc2 or later as the host.

http://kvm.qumranet.com

-------------------------------------------------------------------------
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/

A message that is not in the archive (sent off-list or not yet received): 471790A3.5080704-atKUWr5tajBWk0Htik3J/[email protected]

#2 lore raw
Quoted 4 lines · Avi Kivity

kvm-47 had a host memory corruption bug when setting the guest pte dirty bit, so here's kvm-48 with a fix.

Note that guest time accounting, below, will only work with Linux 2.6.24+.

smp guests still not working with kvm-48:-( i can't image what others can do to make it work. guests hang at random stage during boot. i attached guests boot screenshot. setup:
------------------------------------------------
- host:
- Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
- Intel S3000AHV
- 8GB RAM
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-1:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 i386 32bit
- guest-2:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-3:
- Mandrake-9
- kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
- Windows XP Professional 32bit
------------------------------------------------
i try guest-1 and huest-2 with 4 vcpu others with 1 vcpu. on host the only thing i've got in dmesg:
------------------------------------------------

Call Trace:
 <IRQ>  [<ffffffff800b2c30>] softlockup_tick+0xdb/0xed
 [<ffffffff800933ec>] update_process_times+0x42/0x68
 [<ffffffff80073d61>] smp_local_timer_interrupt+0x23/0x47
 [<ffffffff80074423>] smp_apic_timer_interrupt+0x41/0x47
 [<ffffffff8005bcc2>] apic_timer_interrupt+0x66/0x6c
 <EOI>  [<ffffffff88205999>] :kvm:kvm_flush_remote_tlbs+0xfb/0x109
 [<ffffffff88205988>] :kvm:kvm_flush_remote_tlbs+0xea/0x109
 [<ffffffff88206314>] :kvm:gfn_to_page+0xa3/0xd5
 [<ffffffff88205573>] :kvm:mark_page_dirty+0x9/0x2a
 [<ffffffff8820b62c>] :kvm:kvm_mmu_pte_write+0x1fc/0x330
 [<ffffffff882065d9>] :kvm:emulator_write_emulated_onepage+0x6e/0xce
 [<ffffffff8820fcd0>] :kvm:x86_emulate_insn+0x2b98/0x4134
 [<ffffffff80008e1a>] __handle_mm_fault+0x832/0xdf2
 [<ffffffff8840a404>] :kvm_intel:vmcs_readl+0x17/0x1c
 [<ffffffff88206ac2>] :kvm:emulate_instruction+0x152/0x290
 [<ffffffff8840cb98>] :kvm_intel:handle_exception+0x170/0x250
 [<ffffffff882074f6>] :kvm:kvm_vcpu_ioctl+0x343/0xf43
 [<ffffffff80044d32>] try_to_wake_up+0x407/0x418
 [<ffffffff800850b5>] __wake_up_common+0x3e/0x68
 [<ffffffff8002dd9c>] __wake_up+0x38/0x4f
 [<ffffffff80021b8a>] __up_read+0x19/0x7f
 [<ffffffff8011735a>] avc_has_perm+0x43/0x55
 [<ffffffff80117e91>] inode_has_perm+0x56/0x63
 [<ffffffff80058bf1>] getnstimeofday+0x10/0x28
 [<ffffffff80086c37>] default_wake_function+0x0/0xe
 [<ffffffff80117f32>] file_has_perm+0x94/0xa3
 [<ffffffff8003fc5b>] do_ioctl+0x21/0x6b
 [<ffffffff8002fa61>] vfs_ioctl+0x248/0x261
 [<ffffffff8004a267>] sys_ioctl+0x59/0x78
 [<ffffffff8005b2c1>] tracesys+0xd1/0xdc
------------------------------------------------
Signature · 1 line
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
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/

_______________________________________________
kvm-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw
Quoted 55 lines · Farkas Levente
Quoted 4 lines · Avi Kivity

kvm-47 had a host memory corruption bug when setting the guest pte dirty bit, so here's kvm-48 with a fix.

Note that guest time accounting, below, will only work with Linux 2.6.24+.

smp guests still not working with kvm-48:-( i can't image what others can do to make it work. guests hang at random stage during boot. i attached guests boot screenshot. setup:
------------------------------------------------
- host:
- Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
- Intel S3000AHV
- 8GB RAM
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-1:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 i386 32bit
- guest-2:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-3:
- Mandrake-9
- kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
- Windows XP Professional 32bit
------------------------------------------------
i try guest-1 and huest-2 with 4 vcpu others with 1 vcpu. on host the only thing i've got in dmesg:
------------------------------------------------

Call Trace:
 <IRQ>  [<ffffffff800b2c30>] softlockup_tick+0xdb/0xed
 [<ffffffff800933ec>] update_process_times+0x42/0x68
 [<ffffffff80073d61>] smp_local_timer_interrupt+0x23/0x47
 [<ffffffff80074423>] smp_apic_timer_interrupt+0x41/0x47
 [<ffffffff8005bcc2>] apic_timer_interrupt+0x66/0x6c
 <EOI>  [<ffffffff88205999>] :kvm:kvm_flush_remote_tlbs+0xfb/0x109
 [<ffffffff88205988>] :kvm:kvm_flush_remote_tlbs+0xea/0x109
 [<ffffffff88206314>] :kvm:gfn_to_page+0xa3/0xd5
 [<ffffffff88205573>] :kvm:mark_page_dirty+0x9/0x2a
 [<ffffffff8820b62c>] :kvm:kvm_mmu_pte_write+0x1fc/0x330
 [<ffffffff882065d9>] :kvm:emulator_write_emulated_onepage+0x6e/0xce
 [<ffffffff8820fcd0>] :kvm:x86_emulate_insn+0x2b98/0x4134
 [<ffffffff80008e1a>] __handle_mm_fault+0x832/0xdf2
 [<ffffffff8840a404>] :kvm_intel:vmcs_readl+0x17/0x1c
 [<ffffffff88206ac2>] :kvm:emulate_instruction+0x152/0x290
 [<ffffffff8840cb98>] :kvm_intel:handle_exception+0x170/0x250
 [<ffffffff882074f6>] :kvm:kvm_vcpu_ioctl+0x343/0xf43
 [<ffffffff80044d32>] try_to_wake_up+0x407/0x418
 [<ffffffff800850b5>] __wake_up_common+0x3e/0x68
 [<ffffffff8002dd9c>] __wake_up+0x38/0x4f
 [<ffffffff80021b8a>] __up_read+0x19/0x7f
 [<ffffffff8011735a>] avc_has_perm+0x43/0x55
 [<ffffffff80117e91>] inode_has_perm+0x56/0x63
Quoted 8 lines
 [<ffffffff80058bf1>] getnstimeofday+0x10/0x28
 [<ffffffff80086c37>] default_wake_function+0x0/0xe
 [<ffffffff80117f32>] file_has_perm+0x94/0xa3
 [<ffffffff8003fc5b>] do_ioctl+0x21/0x6b
 [<ffffffff8002fa61>] vfs_ioctl+0x248/0x261
 [<ffffffff8004a267>] sys_ioctl+0x59/0x78
 [<ffffffff8005b2c1>] tracesys+0xd1/0xdc
------------------------------------------------

the situation is even worse, the guests are hang during boot even with single vcpu and even with kvm-46:-( i attached another screenshot. but after i kill the guest and start it again it works. it seems the problem occurs when i start more guest at the same time (eg. after reboot the host). and it seems there is some kind of acpi error since all of the guest hang screenshot contains some kind of acpi error.

Signature · 1 line
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
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/

_______________________________________________
kvm-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel

A message that is not in the archive (sent off-list or not yet received): [email protected]

#6 lore raw
Quoted 64 lines · Farkas Levente
Quoted 54 lines · Farkas Levente
Quoted 4 lines · Avi Kivity

kvm-47 had a host memory corruption bug when setting the guest pte dirty bit, so here's kvm-48 with a fix.

Note that guest time accounting, below, will only work with Linux 2.6.24+.

smp guests still not working with kvm-48:-( i can't image what others can do to make it work. guests hang at random stage during boot. i attached guests boot screenshot. setup:
------------------------------------------------
- host:
- Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
- Intel S3000AHV
- 8GB RAM
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-1:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 i386 32bit
- guest-2:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-3:
- Mandrake-9
- kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
- Windows XP Professional 32bit
------------------------------------------------
i try guest-1 and huest-2 with 4 vcpu others with 1 vcpu. on host the only thing i've got in dmesg:
------------------------------------------------

Call Trace:
 <IRQ>  [<ffffffff800b2c30>] softlockup_tick+0xdb/0xed
 [<ffffffff800933ec>] update_process_times+0x42/0x68
 [<ffffffff80073d61>] smp_local_timer_interrupt+0x23/0x47
 [<ffffffff80074423>] smp_apic_timer_interrupt+0x41/0x47
 [<ffffffff8005bcc2>] apic_timer_interrupt+0x66/0x6c
 <EOI>  [<ffffffff88205999>] :kvm:kvm_flush_remote_tlbs+0xfb/0x109
 [<ffffffff88205988>] :kvm:kvm_flush_remote_tlbs+0xea/0x109
 [<ffffffff88206314>] :kvm:gfn_to_page+0xa3/0xd5
 [<ffffffff88205573>] :kvm:mark_page_dirty+0x9/0x2a
 [<ffffffff8820b62c>] :kvm:kvm_mmu_pte_write+0x1fc/0x330
 [<ffffffff882065d9>] :kvm:emulator_write_emulated_onepage+0x6e/0xce
 [<ffffffff8820fcd0>] :kvm:x86_emulate_insn+0x2b98/0x4134
 [<ffffffff80008e1a>] __handle_mm_fault+0x832/0xdf2
 [<ffffffff8840a404>] :kvm_intel:vmcs_readl+0x17/0x1c
 [<ffffffff88206ac2>] :kvm:emulate_instruction+0x152/0x290
 [<ffffffff8840cb98>] :kvm_intel:handle_exception+0x170/0x250
 [<ffffffff882074f6>] :kvm:kvm_vcpu_ioctl+0x343/0xf43
 [<ffffffff80044d32>] try_to_wake_up+0x407/0x418
 [<ffffffff800850b5>] __wake_up_common+0x3e/0x68
 [<ffffffff8002dd9c>] __wake_up+0x38/0x4f
 [<ffffffff80021b8a>] __up_read+0x19/0x7f
 [<ffffffff8011735a>] avc_has_perm+0x43/0x55
 [<ffffffff80117e91>] inode_has_perm+0x56/0x63
Quoted 8 lines
 [<ffffffff80058bf1>] getnstimeofday+0x10/0x28
 [<ffffffff80086c37>] default_wake_function+0x0/0xe
 [<ffffffff80117f32>] file_has_perm+0x94/0xa3
 [<ffffffff8003fc5b>] do_ioctl+0x21/0x6b
 [<ffffffff8002fa61>] vfs_ioctl+0x248/0x261
 [<ffffffff8004a267>] sys_ioctl+0x59/0x78
 [<ffffffff8005b2c1>] tracesys+0xd1/0xdc
------------------------------------------------
Quoted 6 lines

the situation is even worse, the guests are hang during boot even with single vcpu and even with kvm-46:-( i attached another screenshot. but after i kill the guest and start it again it works. it seems the problem occurs when i start more guest at the same time (eg. after reboot the host). and it seems there is some kind of acpi error since all of the guest hang screenshot contains some kind of acpi error.

What happens if you use "-noacpi" ?

Laurent

Signature · 9 lines
---------------- Laurent.Vivier-6ktuUTfB/[email protected]  -----------------
"Given enough eyeballs, all bugs are shallow" E. S. Raymond


-------------------------------------------------------------------------
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/

A message that is not in the archive (sent off-list or not yet received): 471874AD.4080201-6ktuUTfB/[email protected]

#8 lore raw
Quoted 66 lines · Laurent Vivier
Quoted 65 lines · Farkas Levente
Quoted 63 lines · Farkas Levente
Quoted 5 lines · Avi Kivity

kvm-47 had a host memory corruption bug when setting the guest pte dirty bit, so here's kvm-48 with a fix.

Note that guest time accounting, below, will only work with Linux 2.6.24+.

smp guests still not working with kvm-48:-( i can't image what others can do to make it work. guests hang at random stage during boot. i attached guests boot screenshot. setup:
------------------------------------------------
- host:
- Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
- Intel S3000AHV
- 8GB RAM
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-1:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 i386 32bit
- guest-2:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-3:
- Mandrake-9
- kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
- Windows XP Professional 32bit
------------------------------------------------
i try guest-1 and huest-2 with 4 vcpu others with 1 vcpu. on host the only thing i've got in dmesg:
------------------------------------------------

Call Trace:
 <IRQ>  [<ffffffff800b2c30>] softlockup_tick+0xdb/0xed
 [<ffffffff800933ec>] update_process_times+0x42/0x68
 [<ffffffff80073d61>] smp_local_timer_interrupt+0x23/0x47
 [<ffffffff80074423>] smp_apic_timer_interrupt+0x41/0x47
 [<ffffffff8005bcc2>] apic_timer_interrupt+0x66/0x6c
 <EOI>  [<ffffffff88205999>] :kvm:kvm_flush_remote_tlbs+0xfb/0x109
 [<ffffffff88205988>] :kvm:kvm_flush_remote_tlbs+0xea/0x109
 [<ffffffff88206314>] :kvm:gfn_to_page+0xa3/0xd5
 [<ffffffff88205573>] :kvm:mark_page_dirty+0x9/0x2a
 [<ffffffff8820b62c>] :kvm:kvm_mmu_pte_write+0x1fc/0x330
 [<ffffffff882065d9>] :kvm:emulator_write_emulated_onepage+0x6e/0xce
 [<ffffffff8820fcd0>] :kvm:x86_emulate_insn+0x2b98/0x4134
 [<ffffffff80008e1a>] __handle_mm_fault+0x832/0xdf2
 [<ffffffff8840a404>] :kvm_intel:vmcs_readl+0x17/0x1c
 [<ffffffff88206ac2>] :kvm:emulate_instruction+0x152/0x290
 [<ffffffff8840cb98>] :kvm_intel:handle_exception+0x170/0x250
 [<ffffffff882074f6>] :kvm:kvm_vcpu_ioctl+0x343/0xf43
 [<ffffffff80044d32>] try_to_wake_up+0x407/0x418
 [<ffffffff800850b5>] __wake_up_common+0x3e/0x68
 [<ffffffff8002dd9c>] __wake_up+0x38/0x4f
 [<ffffffff80021b8a>] __up_read+0x19/0x7f
 [<ffffffff8011735a>] avc_has_perm+0x43/0x55
 [<ffffffff80117e91>] inode_has_perm+0x56/0x63
 [<ffffffff80058bf1>] getnstimeofday+0x10/0x28
 [<ffffffff80086c37>] default_wake_function+0x0/0xe
 [<ffffffff80117f32>] file_has_perm+0x94/0xa3
 [<ffffffff8003fc5b>] do_ioctl+0x21/0x6b
 [<ffffffff8002fa61>] vfs_ioctl+0x248/0x261
 [<ffffffff8004a267>] sys_ioctl+0x59/0x78
 [<ffffffff8005b2c1>] tracesys+0xd1/0xdc
------------------------------------------------
Quoted 8 lines
Quoted 6 lines

the situation is even worse, the guests are hang during boot even with single vcpu and even with kvm-46:-( i attached another screenshot. but after i kill the guest and start it again it works. it seems the problem occurs when i start more guest at the same time (eg. after reboot the host). and it seems there is some kind of acpi error since all of the guest hang screenshot contains some kind of acpi error.

What happens if you use "-noacpi" ?

in this case single cpu guests are working with kvm-48, but 4 vcpu/guests still hang:-(

Signature · 7 lines
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
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/

A message that is not in the archive (sent off-list or not yet received): [email protected]

#10 lore raw
Quoted 72 lines · Farkas Levente
Quoted 71 lines · Laurent Vivier
Quoted 70 lines · Farkas Levente
Quoted 55 lines · Farkas Levente
Quoted 5 lines · Avi Kivity

kvm-47 had a host memory corruption bug when setting the guest pte dirty bit, so here's kvm-48 with a fix.

Note that guest time accounting, below, will only work with Linux 2.6.24+.

smp guests still not working with kvm-48:-( i can't image what others can do to make it work. guests hang at random stage during boot. i attached guests boot screenshot. setup:
------------------------------------------------
- host:
- Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
- Intel S3000AHV
- 8GB RAM
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-1:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 i386 32bit
- guest-2:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-3:
- Mandrake-9
- kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
- Windows XP Professional 32bit
------------------------------------------------
i try guest-1 and huest-2 with 4 vcpu others with 1 vcpu. on host the only thing i've got in dmesg:
------------------------------------------------

Call Trace:
 <IRQ>  [<ffffffff800b2c30>] softlockup_tick+0xdb/0xed
 [<ffffffff800933ec>] update_process_times+0x42/0x68
 [<ffffffff80073d61>] smp_local_timer_interrupt+0x23/0x47
 [<ffffffff80074423>] smp_apic_timer_interrupt+0x41/0x47
 [<ffffffff8005bcc2>] apic_timer_interrupt+0x66/0x6c
 <EOI>  [<ffffffff88205999>] :kvm:kvm_flush_remote_tlbs+0xfb/0x109
 [<ffffffff88205988>] :kvm:kvm_flush_remote_tlbs+0xea/0x109
 [<ffffffff88206314>] :kvm:gfn_to_page+0xa3/0xd5
 [<ffffffff88205573>] :kvm:mark_page_dirty+0x9/0x2a
 [<ffffffff8820b62c>] :kvm:kvm_mmu_pte_write+0x1fc/0x330
 [<ffffffff882065d9>] :kvm:emulator_write_emulated_onepage+0x6e/0xce
 [<ffffffff8820fcd0>] :kvm:x86_emulate_insn+0x2b98/0x4134
 [<ffffffff80008e1a>] __handle_mm_fault+0x832/0xdf2
 [<ffffffff8840a404>] :kvm_intel:vmcs_readl+0x17/0x1c
 [<ffffffff88206ac2>] :kvm:emulate_instruction+0x152/0x290
 [<ffffffff8840cb98>] :kvm_intel:handle_exception+0x170/0x250
 [<ffffffff882074f6>] :kvm:kvm_vcpu_ioctl+0x343/0xf43
 [<ffffffff80044d32>] try_to_wake_up+0x407/0x418
 [<ffffffff800850b5>] __wake_up_common+0x3e/0x68
 [<ffffffff8002dd9c>] __wake_up+0x38/0x4f
 [<ffffffff80021b8a>] __up_read+0x19/0x7f
 [<ffffffff8011735a>] avc_has_perm+0x43/0x55
 [<ffffffff80117e91>] inode_has_perm+0x56/0x63
Quoted 8 lines
 [<ffffffff80058bf1>] getnstimeofday+0x10/0x28
 [<ffffffff80086c37>] default_wake_function+0x0/0xe
 [<ffffffff80117f32>] file_has_perm+0x94/0xa3
 [<ffffffff8003fc5b>] do_ioctl+0x21/0x6b
 [<ffffffff8002fa61>] vfs_ioctl+0x248/0x261
 [<ffffffff8004a267>] sys_ioctl+0x59/0x78
 [<ffffffff8005b2c1>] tracesys+0xd1/0xdc
------------------------------------------------

the situation is even worse, the guests are hang during boot even with single vcpu and even with kvm-46:-( i attached another screenshot. but after i kill the guest and start it again it works. it seems the problem occurs when i start more guest at the same time (eg. after reboot the host). and it seems there is some kind of acpi error since all of the guest hang screenshot contains some kind of acpi error.

Quoted 4 lines
Quoted 1 line

What happens if you use "-noacpi" ?

in this case single cpu guests are working with kvm-48, but 4 vcpu/guests still hang:-(

one more thing which happened with single cpu guests on kvm-48 in dmesg
on the host:
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring
Fault when IDT_Vectoring

Signature · 7 lines
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
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/