Re: [kvm-devel] Oops on 2.6.23.11 with KVM 57
On Thu, Dec 27, 2007 at 12:34:58PM +0200, Avi Kivity wrote: Looks like memory corruption; this was a call through a function pointer that pointed into userspace. Please try kvm-58, that has a fix for preemption notifiers on AMD; this may solve the problem. kvm-58 doesn't show this problem, thanks! The host runs stable now. I'm still seeing network stalls on large transfers in the guest though. Ifup/ifdown'ing the interface in the guest gets things going again until it stops again. There's nothing in dmesg of either host or guest. I still have to check with different guest kernels and qemu network adapter emulations though (current one is ne2k using a bridge on the host). The problem has at least been around since kvm-52. Cheers, -- Guido - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Oops on 2.6.23.11 with KVM 57
Guido Guenther wrote: On Thu, Dec 27, 2007 at 12:34:58PM +0200, Avi Kivity wrote: Looks like memory corruption; this was a call through a function pointer that pointed into userspace. Please try kvm-58, that has a fix for preemption notifiers on AMD; this may solve the problem. kvm-58 doesn't show this problem, thanks! The host runs stable now. I'm still seeing network stalls on large transfers in the guest though. Ifup/ifdown'ing the interface in the guest gets things going again until it stops again. There's nothing in dmesg of either host or guest. I still have to check with different guest kernels and qemu network adapter emulations though (current one is ne2k using a bridge on the host). The there are known problems with ne2k, please rtl8139 and report if it work - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Oops on 2.6.23.11 with KVM 57
Guido Guenther wrote: On Sat, Dec 22, 2007 at 09:59:43PM +0200, Avi Kivity wrote: Guido Guenther wrote: Hi, I got the Oops below on an Dual CPU Dual-Core AMD Opteron(tm) Processor 2220 running a 32bit kernel. Kernel is 2.6.23.11, kvm version 57. Doesn't happen all the time but usually right at VM startup. Seems to be easier to trigger when starting up several VMs in row. What guest are you running? smp or uni? Uniprocessor Linux, standard etch 2.6.18 kernel. kvm commandline was: -M pc -m 512 -smp 1 -monitor pty -boot c -hda /dev/mapper/foo -hdb /dev/mapper/bar -net nic,macaddr=54:52:00:1b:9b:10,vlan=0 -net tap,fd=11,script=,vlan=0 -usb -usbdevice tablet -vnc 127.0.0.1:0 Looks like memory corruption; this was a call through a function pointer that pointed into userspace. Please try kvm-58, that has a fix for preemption notifiers on AMD; this may solve the problem. -- error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] Oops on 2.6.23.11 with KVM 57
Hi, I got the Oops below on an Dual CPU Dual-Core AMD Opteron(tm) Processor 2220 running a 32bit kernel. Kernel is 2.6.23.11, kvm version 57. Doesn't happen all the time but usually right at VM startup. Seems to be easier to trigger when starting up several VMs in row. Does it help to post more of these as they show up? Cheers, -- Guido BUG: unable to handle kernel paging request1BUG: unable to handle kernel paging request at virtual address 52004605 printing eip: 52004605 *pdpt = 2f35d001 *pde = Oops: 0010 [#1] SMP Modules linked in: tun bitrev nfs nfsd exportfs lockd sunrpc ac lock_nolock lock_dlm gfs2 dlm configfs bridge llc kvm_amd kvm bonding ipmi_si ipmi_msghandler i2c_piix4 container dm_mirror dm_snapshot raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod dm_round_robin dm_emc dm_multipath dm_mod sd_mod qla2xxx firmware_class scsi_transport_fc scsi_mod bnx2 crc32 serverworks usbhid thermal processor fan BUG: unable to handle kernel paging request at virtual address 3131ce82 printing eip: 3131ce82 *pdpt = 2fcfa001 *pde = CPU:3 EIP:0060:[52004605]Not tainted VLI EFLAGS: 00010046 (2.6.23.11-aa-smp-64gb #1) EIP is at 0x52004605 eax: 45811b60 ebx: c0f602c1 ecx: 0003 edx: esi: c0f602c1 edi: ede2 ebp: esp: f08e9d70 ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Process kvm (pid: 10396, ti=f08e8000 task=ef53d000 task.ti=efaea000) Stack: f8d498d8 0090 f8d49f8e ef64a000 eff3c020 f8cb5be6 eff3c020 f8d4121e 0097 10002800 f5611140 eff3c020 ae80 f8d3da32 0002 c01759cd f655d7d0 dfc213c0 df803a80 Call Trace: [f8d498d8] pic_update_irq+0x68/0x80 [kvm] [f8d49f8e] kvm_pic_read_irq+0x6e/0xe0 [kvm] [f8cb5be6] svm_intr_assist+0x66/0x100 [kvm_amd] [f8d4121e] kvm_arch_vcpu_ioctl_run+0x8e/0x470 [kvm] [f8d3da32] kvm_vcpu_ioctl+0x2a2/0x2f0 [kvm] [c01759cd] flush_old_exec+0x43d/0x890 [c011e5dc] kmap_atomic+0x1c/0x30 [c012b523] current_fs_time+0x13/0x20 [c0184dc7] touch_atime+0x87/0x130 [c01514f5] do_generic_mapping_read+0x3c5/0x490 [c0152d90] generic_file_aio_read+0xd0/0x1e0 [c0150a00] file_read_actor+0x0/0x100 [c0170ed7] do_sync_read+0xc7/0x110 [c013a180] autoremove_wake_function+0x0/0x50 [c015bfba] kmap_high+0x1a/0x1b0 [c015be5b] page_address+0xcb/0xd0 [f8d3d790] kvm_vcpu_ioctl+0x0/0x2f0 [kvm] [c017c9fb] do_ioctl+0x2b/0x90 [c017cabc] vfs_ioctl+0x5c/0x290 [c0170e10] do_sync_read+0x0/0x110 [c017cd2d] sys_ioctl+0x3d/0x70 [c010416e] sysenter_past_esp+0x5f/0x85 === Code: Bad EIP value. EIP: [52004605] 0x52004605 SS:ESP 0068:f08e9d70 kernel tried to execute NX-protected page - exploit attempt? (uid: 65534) BUG: unable to handle kernel paging request at virtual address f08e9b00 printing eip: f08e9b00 *pdpt = 4001 *pde = 8000308001e3 *pte = BUG: unable to handle kernel paging request at virtual address 01f56124 printing eip: c0172142 *pdpt = 0044e001 *pde = - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
