[Bug 42980] BUG in gfn_to_pfn_prot
https://bugzilla.kernel.org/show_bug.cgi?id=42980 --- Comment #7 from Luke-Jr 2012-05-10 13:17:17 --- Is there anything I can do to reproduce the problem condition for the test? It seems to only occur about once every 6 months normally. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42980] BUG in gfn_to_pfn_prot
https://bugzilla.kernel.org/show_bug.cgi?id=42980 --- Comment #6 from Avi Kivity 2012-05-10 10:53:48 --- Created an attachment (id=73244) --> (https://bugzilla.kernel.org/attachment.cgi?id=73244) Fix Please test the attached patch. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 43068] Operation restricted to levels L0-2 - kerneloops when booting L3
https://bugzilla.kernel.org/show_bug.cgi?id=43068 Nadav Har'El changed: What|Removed |Added CC||n...@math.technion.ac.il --- Comment #1 from Nadav Har'El 2012-04-08 08:18:32 --- Hi, indeed, theoretically L3 should work; And also in practice - in my tests it did work (albeit very very slowly). I'll need to look into this issue, and check why this bug is happening now. You should just be aware that even if it will work, L3 will be extremely slow, likely to the point of not being useful. One of reasons is the lack of nested EPT in the upstream version. An even bigger problem is the exponential explosion of exits described in the Turtles paper, which is made much worse by one particular part of the existing implementation: Right now, on every nested entry from L1 to L2, L0 recreates all the fields of the vmcs (see prepare_vmcs02()) doing a few dozen VMWRITEs. When L0 does it, it's fine - but when we are nested yet deeper, and there is an entry from L2 into L3 and *L1* needs to do prepare_vmcs02(), now L1 calls a lot of VMWRITEs and they all cause exits, and all of this is extremely slow. There are two things we could do in the future to solve this performance problem - if people really need to use L3 (currently, even L2 isn't very popular ;-)). One is to have some sort of exit-less VMREAD/VMWRITE, with or without hardware support for this feature. The second thing is to emulate VMWRITE differently, writing to vmcs02 immediately and doing far fewer VMWRITES on nested entries (doing this correctly is harder than it might seem, as I can explain in a separate thread). Nadav Har'El -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 43068] Operation restricted to levels L0-2 - kerneloops when booting L3
https://bugzilla.kernel.org/show_bug.cgi?id=43068 josef <2...@kuarepoti-dju.net> changed: What|Removed |Added Platform|All |x86-64 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 43068] New: Operation restricted to levels L0-2 - kerneloops when booting L3
https://bugzilla.kernel.org/show_bug.cgi?id=43068 Summary: Operation restricted to levels L0-2 - kerneloops when booting L3 Product: Virtualization Version: unspecified Kernel Version: 3.2.0-2-amd64 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm AssignedTo: virtualization_...@kernel-bugs.osdl.org ReportedBy: 2...@kuarepoti-dju.net Regression: No Created an attachment (id=72845) --> (https://bugzilla.kernel.org/attachment.cgi?id=72845) Kernel oops backtrace Trying to run KVM with a high level of nesting works fine for the first two levels of virtual machines (L1 and L2) but leads to the attached oops when attempting to boot into L3. The host system has 24 Xeon X5675 cores running Ubuntu 12.04 with kernel 3.2.0-21-generic. The nested VMs are restricted to one of these core. They all run resized clones of a Debian wheezy (testing) image with kernel 3.2.0-2-amd64. In the Turtles paper, nested virtualisation has been presented to support Ln and includes L3 in the diagrams but the evaluation only went up to L2. The kernel documentation nested-vmx.txt doesn't list this as a restriction but doesn't mention L3 or higher either. Hence, it is not clear if the implementation is supposed to support L3 at all, at the moment or in the foreseeable future. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42636] PCI passthrough does not work with AMD iommu for PCI device
https://bugzilla.kernel.org/show_bug.cgi?id=42636 --- Comment #9 from Klaus Mueller 2012-04-05 08:08:58 --- I tested the same device here and got the same error as you reported. Good to know, that Xen doesn't have any problem. This really means, that it is most probably a kvm or qemu or AMD iommu bug. kvm 0.15, kernel: linux 3.1.10 (openSUSE) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42636] PCI passthrough does not work with AMD iommu for PCI device
https://bugzilla.kernel.org/show_bug.cgi?id=42636 Alexandrov Stanislav changed: What|Removed |Added CC||n...@nya.ai --- Comment #8 from Alexandrov Stanislav 2012-04-04 08:22:51 --- I have same problems with pci passthrough, while my pci-e video card hd7750 with hda(01:00.0/1) and integrated network card(05:00.0) succsessfilly assigned in guest, when i try to add usb controller, i get same error about FLR: Unable to reset PCI device :00:12.0: no FLR, PM reset or bus reset available with xen it works fine. lspci -tv -[:00]-+-00.0 Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI bridge (external gfx0 port B) +-00.2 Advanced Micro Devices [AMD] nee ATI RD990 I/O Memory Management Unit (IOMMU) +-02.0-[01]--+-00.0 Advanced Micro Devices [AMD] nee ATI Device 683f |\-00.1 Advanced Micro Devices [AMD] nee ATI Device aab0 +-09.0-[02]00.0 Etron Technology, Inc. EJ168 USB 3.0 Host Controller +-0b.0-[03]--+-00.0 nVidia Corporation GF110 [GeForce GTX 560 Ti] |\-00.1 nVidia Corporation GF110 High Definition Audio Controller +-11.0 Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] +-12.0 Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller +-12.2 Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller +-13.0 Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller +-13.2 Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller +-14.0 Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller +-14.2 Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) +-14.3 Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller +-14.4-[04]-- +-14.5 Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI2 Controller +-15.0-[05]00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller +-15.1-[06]-- +-15.2-[07]-- +-15.3-[08]-- +-16.0 Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller +-16.2 Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller +-18.0 Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration +-18.1 Advanced Micro Devices [AMD] Family 10h Processor Address Map +-18.2 Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller +-18.3 Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control \-18.4 Advanced Micro Devices [AMD] Family 10h Processor Link Control qemu-kvm-1.0, linux-3.3 motherboard is GA-990FXA-D3 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42635] PCIe passthrough broken with AMD iommu after s2disk / resume
https://bugzilla.kernel.org/show_bug.cgi?id=42635 --- Comment #3 from Klaus Mueller 2012-04-03 07:27:43 --- Meanwhile I detected, that using the boot option iommu=pt (or additional iommu=1) shows the same problem (regardless of suspend/resume). If the VM is started after the first virsh start / virsh shutdown cycle with virsh start again, the device is dead in the VM. Host must be rebooted to get it working again. If the options iommu=pt (or additional iommu=1) are not used at all, the VM can be restarted without any problem coming up. 1. Host booted w/ iommu=pt iommu=1 2. virsh start 3. virsh shutdown 4. virsh start 5. -> Passed through device in VM is dead. 1. Host booted w/o iommu=pt iommu=1 2. virsh start 3. virsh shutdown 4. virsh start 5. -> Passed through device in VM is fine. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #26 from Avi Kivity 2012-04-02 09:12:38 --- Strange, looks like the patches did not take effect at all. The opcode is 0f 6f 02, which should have been decoded as movq. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #25 from madenginee...@gmail.com 2012-04-01 23:40:21 --- Created an attachment (id=72789) --> (https://bugzilla.kernel.org/attachment.cgi?id=72789) Last 10k lines of a trace showing the fault, kernel 3.3rc5 with patches -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #24 from madenginee...@gmail.com 2012-04-01 23:39:47 --- Created an attachment (id=72788) --> (https://bugzilla.kernel.org/attachment.cgi?id=72788) Register state and code disassembly at failure point, kernel 3.3rc5 with patches -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #23 from madenginee...@gmail.com 2012-04-01 23:38:21 --- Now it dies in a different place, still with a movq instruction (movq (%edx),%mm0). I think the difference is because of a configuration change or package update since the last test, because the fault happens at the same address and same instruction under both the patched 3.3rc5 and 3.0.20. Unfortunately I've no idea what the configuration change might have been, and I didn't think to save a VM disk image from the previous tests. I also got a more recent trace-cmd built and installed, so there is usable trace output now. Still huge, so I'll post the last 10k lines as before. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #22 from Avi Kivity 2012-04-01 14:15:51 --- No guarantees of course, but this is just 3.3-rc5 with a few patches on top. It should be fine for a short test. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #21 from madenginee...@gmail.com 2012-03-31 20:10:38 --- Sorry for the delay, I've been really busy lately. Is this kernel reasonably safe to run on my main machine? I'm not worried about it crashing, but if it takes a filesystem with it... -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42636] PCI passthrough does not work with AMD iommu for PCI device
https://bugzilla.kernel.org/show_bug.cgi?id=42636 --- Comment #7 from Klaus Mueller 2012-03-30 12:16:39 --- Thanks, with the "iommu=pt iommu=1" options applied it doesn't work at all - even the "workaround" with first try to start with the bridge applied and afterwards without the bridge added isn't working then. BTW: I can pass through PCIe devices, as long as they have different PCI ids and different modules, without any problem. I'm using the option allow_unsafe_assigned_interrupts=1 already! I think there is a problem with the handling of the device behind a PCI bridge, which should be fixed (-> the Ralink device which should be passed through is a PCI device and not a PCIe device)! Take a look at the qemu-kvm crash log https://bugzilla.kernel.org/attachment.cgi?id=72753 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42636] PCI passthrough does not work with AMD iommu for PCI device
https://bugzilla.kernel.org/show_bug.cgi?id=42636 Alexandre DERUMIER changed: What|Removed |Added CC||aderum...@odiso.com --- Comment #6 from Alexandre DERUMIER 2012-03-30 11:35:49 --- Hi, for amd, pass "iommu=pt iommu=1" to kernel options you can also try to load kvm module with allow_unsafe_assigned_interrupts=1 echo "options kvm allow_unsafe_assigned_interrupts=1" > /etc/modprobe.d/kvm_iommu_map_guest.conf -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42636] PCI passthrough does not work with AMD iommu for PCI device
https://bugzilla.kernel.org/show_bug.cgi?id=42636 --- Comment #5 from Klaus Mueller 2012-03-30 11:29:50 --- More specific error message while VM is started with attached PCI bridge: Unable to reset PCI device :00:14.4: no FLR, PM reset or bus reset available I tried with kvm module for linux 3.3 and got the same crash while stopping the VM. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42636] PCI passthrough does not work with AMD iommu for PCI device
https://bugzilla.kernel.org/show_bug.cgi?id=42636 --- Comment #4 from Klaus Mueller 2012-03-30 11:07:21 --- Created an attachment (id=72753) --> (https://bugzilla.kernel.org/attachment.cgi?id=72753) log of qemu-kvm crash I tried again with only one pci card inserted (Network controller: RaLink RT2800 802.11n PCI). The tree is now like this: +-14.4-[06]07.0 RaLink RT2800 802.11n PCI I booted with intel_iommu=on (does this apply to AMD, too?). If I start the VM now, I'm getting the same error again: Failed to assign device "hostdev0" : Device or resource busy qemu-kvm: -device pci-assign,host=06:07.0,id=hostdev0,configfd=19,bus=pci.0,addr=0x5: Device 'pci-assign' could not be initialized If I'm additionally putting the bridge to the VM, I'm getting an error telling me about a missing reset function and another missing thing, too. If I remove the bridge from the VM xml-file again and start it now, the VM suddenly starts up fine :-))). But if the VM is stopped again (with halt in the VM or with virsh shutdown VM, qemu-kvm crashes and remains as zombie. The output from messages is attached as iommu-trace.log. kvm is 0.15.0 and kernel is 3.1.10 (kernel-desktop from openSUSE) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42636] PCI passthrough does not work with AMD iommu for PCI device
https://bugzilla.kernel.org/show_bug.cgi?id=42636 Daniel Mayer changed: What|Removed |Added CC||listenmitgl...@arcor.de --- Comment #3 from Daniel Mayer 2012-03-30 07:48:26 --- Hi, I feel with you - I had many, many headaches with PCI-PTrough... You said you unloaded the driver module for both devices. a) do you have the pcistub module available (kernel config)? For some PCI devices I had to enable both DMA and IRQ remapping in the kernel. The latter is disabled by default. Otherwise: sometimes, especially with older PCI cards, IRQ remapping had to be disabled... at least as module or compiled-in: Bus options (PCI etc.) --> Support for DMA Remapping Devices Bus options (PCI etc.) --> Enable DMA Remapping Devices Bus options (PCI etc.) --> PCI Stub driver [quote] Of course, I unloaded the module of this additional device before trying to passthrough it to the guest.[/qoute] b) Did you try to assign the pcistub driver as printed here: http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42980] BUG in gfn_to_pfn_prot
https://bugzilla.kernel.org/show_bug.cgi?id=42980 --- Comment #5 from Avi Kivity 2012-03-28 15:07:25 --- vcpu_enter_guest() kvm_mmu_reload() // now root_hpa is valid inject_pending_event() vmx_interrupt_allowed() nested_vmx_vmexit() load_vmcs12_host_state() kvm_mmu_reset_context() // root_hpa now invalid kvm_guest_enter() ... page fault because root_hpa is invalid, oops -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42980] BUG in gfn_to_pfn_prot
https://bugzilla.kernel.org/show_bug.cgi?id=42980 --- Comment #4 from Luke-Jr 2012-03-28 13:49:26 --- I suppose I should mention I'd been running both of these stable for at least a month now (and the GPU passthrough for nearly a full year). One factor that might (or might not) be related - the GPU fan recently died. When this crash took me down, I removed the GPU, so I won't be able to do any further testing with that setup (unless I find another similar GPU at a good price). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42980] BUG in gfn_to_pfn_prot
https://bugzilla.kernel.org/show_bug.cgi?id=42980 --- Comment #3 from Avi Kivity 2012-03-28 13:45:25 --- You're a brave one. It wasn't the nested one (at least, it wasn't running in the guest's guest at the moment of the crash), but it might be related. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42980] BUG in gfn_to_pfn_prot
https://bugzilla.kernel.org/show_bug.cgi?id=42980 --- Comment #2 from Luke-Jr 2012-03-28 13:37:53 --- IIRC, it was pretty out of the blue. I might have had one or both of two KVMs running in the background at the time: - 64-bit Gentoo with a Radeon 5850 passthrough'd (VT-d) - 32-bit Ubuntu with a nested 32-bit KVM -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42980] BUG in gfn_to_pfn_prot
https://bugzilla.kernel.org/show_bug.cgi?id=42980
Avi Kivity changed:
What|Removed |Added
CC||a...@redhat.com
--- Comment #1 from Avi Kivity 2012-03-28 13:03:25 ---
0:89 d0mov%edx,%eax
2:8d 4c ff 0c lea0xc(%rdi,%rdi,8),%ecx
6:4d 89 e0 mov%r12,%r8
9:48 d3 e8 shr%cl,%rax
c:4c 03 45 a8 add-0x58(%rbp),%r8
10:25 ff 01 00 00 and$0x1ff,%eax
15:41 39 f6 cmp%esi,%r14d
18:89 45 bc mov%eax,-0x44(%rbp)
1b:89 c0mov%eax,%eax
1d:49 8d 04 c0 lea(%r8,%rax,8),%rax
21:48 89 45 b0 mov%rax,-0x50(%rbp)
25:0f 84 e1 00 00 00je 0x10c
2b:4c 8b 00 mov(%rax),%r8
2e:41 f6 c0 01 test $0x1,%r8b
32:74 40je 0x74
34:4c 8b 0d 89 80 01 00 mov0x18089(%rip),%r9# 0x180c4
3b:4d 89 c2 mov%r8,%r10
Appears to be __direct_map()'s
if (!is_shadow_present_pte(*iterator.sptep)) {
u64 base_addr = iterator.addr;
%rax is 0x87ff. That is one less than the base of the direct map of
all physical memory. So it looks like the code
static bool shadow_walk_okay(struct kvm_shadow_walk_iterator *iterator)
{
if (iterator->level < PT_PAGE_TABLE_LEVEL)
return false;
iterator->index = SHADOW_PT_INDEX(iterator->addr, iterator->level);
iterator->sptep= ((u64 *)__va(iterator->shadow_addr)) +
iterator->index;
return true;
}
saw iterator->shadow_addr == -1ULL.
That might be INVALID_PAGE assigned to pae_root (but that is masked out in
shadow_walk_init()) or a stray -1 due to a completely unrelated bug.
Anything interesting about how this was triggered?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
--
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
[Bug 42980] New: BUG in gfn_to_pfn_prot
https://bugzilla.kernel.org/show_bug.cgi?id=42980 Summary: BUG in gfn_to_pfn_prot Product: Virtualization Version: unspecified Kernel Version: 3.2.2-gentoo Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: kvm AssignedTo: virtualization_...@kernel-bugs.osdl.org ReportedBy: luke-jr+linuxb...@utopios.org Regression: No BUG: unable to handle kernel paging request at 87ff IP: [] __direct_map.clone.86+0xa7/0x240 [kvm] PGD 0 Oops: [#1] PREEMPT SMP CPU 0 Modules linked in: tun cdc_ether usbnet cdc_acm fuse usbmon pci_stub kvm_intel kvm netconsole configfs cfq_iosched blk_cgroup snd_seq_oss snd_seq_midi_event snd_seq bridge snd_seq_device ipv6 snd_pcm_oss snd_mixer_oss stp llc coretemp hwmon usblp snd_hda_codec_hdmi snd_hda_codec_realtek usb_storage ftdi_sio usbserial usbhid hid snd_hda_intel i915 snd_hda_codec drm_kms_helper snd_hwdep drm snd_pcm firewire_ohci tpm_tis 8139too tpm firewire_core xhci_hcd i2c_algo_bit snd_timer 8250_pci 8250_pnp ehci_hcd usbcore snd e1000e 8250 tpm_bios crc_itu_t serial_core snd_page_alloc sg rtc_cmos psmouse i2c_i801 mii usb_common video evdev ata_generic pata_acpi button Pid: 9995, comm: qemu-system-x86 Not tainted 3.2.2-gentoo #1 /DQ67SW RIP: 0010:[] [] __direct_map.clone.86+0xa7/0x240 [kvm] RSP: 0018:88010bc39b08 EFLAGS: 00010293 RAX: 87ff RBX: 000ff000 RCX: 0027 RDX: 29b55000 RSI: 0004 RDI: 0003 RBP: 88010bc39bb8 R08: 87ff R09: 00113661 R10: c174f000 R11: 0800d974 R12: 8800 R13: 8803b7e6c240 R14: 0001 R15: 0001 FS: () GS:88043e20(0063) knlGS:f5ffab70 CS: 0010 DS: 002b ES: 002b CR0: 80050033 CR2: 87ff CR3: 0001027f1000 CR4: 000426e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process qemu-system-x86 (pid: 9995, threadinfo 88010bc38000, task 88000bc154f0) Stack: 8803b7e6c240 88010bc39bf0 00029b55 88010bc39b38 a031ae14 00ff88010bc39bb8 00113661 00029b55 29b55000 Call Trace: [] ? gfn_to_pfn_prot+0x14/0x20 [kvm] [] tdp_page_fault+0x1a0/0x1e0 [kvm] [] kvm_mmu_page_fault+0x32/0xb0 [kvm] [] handle_ept_violation+0x4c/0xd0 [kvm_intel] [] vmx_handle_exit+0xb4/0x6f0 [kvm_intel] [] ? sub_preempt_count+0x9d/0xd0 [] kvm_arch_vcpu_ioctl_run+0x473/0xf40 [kvm] [] ? sub_preempt_count+0x9d/0xd0 [] kvm_vcpu_ioctl+0x392/0x5e0 [kvm] [] ? kvm_vm_ioctl+0x9d/0x410 [kvm] [] ? sys_sendto+0x119/0x140 [] kvm_vcpu_compat_ioctl+0x55/0x100 [kvm] [] ? fget_light+0x8f/0xf0 [] compat_sys_ioctl+0x8e/0xff0 [] ? posix_ktime_get_ts+0xc/0x10 [] ? sys_clock_gettime+0x90/0xb0 [] ? compat_sys_clock_gettime+0x7b/0x90 [] sysenter_dispatch+0x7/0x27 Code: 89 d0 8d 4c ff 0c 4d 89 e0 48 d3 e8 4c 03 45 a8 25 ff 01 00 00 41 39 f6 89 45 bc 89 c0 49 8d 04 c0 48 89 45 b0 0f 84 e1 00 00 00 <4c> 8b 00 41 f6 c0 01 74 40 4c 8b 0d 89 80 01 00 4d 89 c2 4d 21 RIP [] __direct_map.clone.86+0xa7/0x240 [kvm] RSP CR2: 87ff ---[ end trace 4db76b33c09285f5 ]--- note: qemu-system-x86[9995] exited with preempt_count 1 usb 2-1.2: USB disconnect, device number 77 INFO: rcu_preempt detected stall on CPU 3 (t=6 jiffies) Pid: 3610, comm: kwin Tainted: G D 3.2.2-gentoo #1 Call Trace: [] __rcu_pending+0x1d9/0x420 [] ? tick_nohz_handler+0xe0/0xe0 [] rcu_check_callbacks+0x122/0x1a0 [] update_process_times+0x43/0x80 [] tick_sched_timer+0x5b/0xa0 [] __run_hrtimer.clone.30+0x63/0x140 [] hrtimer_interrupt+0xdf/0x210 [] smp_apic_timer_interrupt+0x63/0xa0 [] apic_timer_interrupt+0x6b/0x70 [] ? __pagevec_free+0x22/0x30 [] ? _raw_spin_lock+0x32/0x40 [] ? _raw_spin_lock+0x16/0x40 [] kvm_mmu_notifier_invalidate_page+0x3c/0x90 [kvm] [] __mmu_notifier_invalidate_page+0x48/0x60 [] try_to_unmap_one+0x3c5/0x3f0 [] try_to_unmap_anon+0x9d/0xe0 [] try_to_unmap+0x55/0x70 [] migrate_pages+0x2f1/0x4d0 [] ? suitable_migration_target+0x50/0x50 [] compact_zone+0x44f/0x7a0 [] try_to_compact_pages+0x197/0x1f0 [] __alloc_pages_direct_compact+0xc6/0x1c0 [] __alloc_pages_nodemask+0x3d9/0x7a0 [] ? _raw_spin_unlock+0x10/0x40 [] ? handle_pte_fault+0x3bb/0x9f0 [] do_huge_pmd_anonymous_page+0x131/0x350 [] handle_mm_fault+0x21e/0x300 [] do_page_fault+0x12d/0x430 [] ? do_mmap_pgoff+0x344/0x380 [] page_fault+0x1f/0x30 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #20 from Avi Kivity 2012-03-21 18:21:33 --- Please try git://git.kernel.org/pub/scm/virt/kvm/kvm.git emulator-movq this emulates the two movq instructions used. There may be other unemulated instructions though. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Chun-Hung Chen changed: What|Removed |Added CC||arn...@gmail.com --- Comment #19 from Chun-Hung Chen 2012-03-15 08:22:26 --- Hi, I have tested under Ubuntu 11.10 Server with Kernel 3.0.0-12 only with vhost on and it works well so far. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #18 from Jason Wang 2012-03-13 03:23:30 --- Hi all: I suspect the issue were fixed by this commit: http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;a=commitdiff;h=4b727361f0bc7ee7378298941066d8aa15023ffb;hp=e1ac50f64691de9a095ac5d73cb8ac73d3d17dba -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #17 from Kurk 2012-03-12 17:15:16 --- Steve, thank you for finding this bug. Is there a chance you could test without vhost but with the event_idx=off ? This is the xml line in case you use libvirt: That would be an effective workaround until we get a fixed qemu. Thanks for your time. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829
Steve changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution||CODE_FIX
--- Comment #16 from Steve 2012-03-07 12:40:15 ---
Thank you for information.
Today I test v3.3-rc6+ from today morning: the same version on host and guest
also latest seabios, qemu-kvm, net-tools, util-linux, kmod, udev.
Now it works correctly after few hours under huge network traffic load
both directions in paralell without any network issue.
Bellow are my arguments for tested guest running on testing host:
-
${VPS}
-nodefaults
-name ${VPS_NAME}
-chroot ${VPS_CHROOT}
-runas ${VPS_USER}
-pidfile ${VPS_PIDFILE}
-vnc ${VPS_WAN}:0
-vga std --full-screen
-smp ${VPS_CPU} -m ${VPS_MEM} -cpu host
-mem-path /hugepages -mem-prealloc
-enable-kvm -daemonize -rtc base=localtime,clock=host,driftfix=none
-balloon ${VPS_BALLOON}
-netdev tap,id=nic01,ifname=${VPS_NET_IF_NAME},
script=/etc/kvm/kvm-ifup,downscript=/etc/kvm/kvm/ifdown,
vnet_hdr=on,vhost=on,vhostforce=off
-device virtio-net-pci,netdev=nic01,mac=${VPS_MAC}
-drive aio=native,index=0,media=disk,cache=none,
if=${VPS_DRIVE_IF_TYPE},file=${VPS_IMG}
-boot order=c,menu=off &
lsmod on guest (lsmod | grep virtio):
virtio_net 12477 0
virtio_balloon 4216 0
virtio_blk 6313 3
virtio_pci 6983 0
virtio 3282 4 virtio_pci,virtio_blk,virtio_balloon,virtio_net
virtio_ring 4154 4 virtio_pci,virtio_blk,virtio_balloon,virtio_net
lspci on guest (lspci):
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 VGA compatible controller: Device 1234:
00:03.0 RAM memory: Red Hat, Inc Virtio memory balloon
00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
00:05.0 SCSI storage controller: Red Hat, Inc Virtio block device
I try to test older guest kernels with above setup.
Thank you for your time & cooperation.
Have a nice day.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
--
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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #15 from Jason Wang 2012-03-07 05:41:09 --- (In reply to comment #14) > Please could someone have a look on this issue ? > > Thank you for your time. Hello Steve: According to you bisect result, maybe the issue of the event index in qemu. Looks like you didn't use vhost according to your qemu-kvm cli, could you please try to see whether the 3.3-rc6 guest works under vhost backend (-netdev tap,vhost=on,id=XXX -device virtio-net-pci,netdev=XXX ... ). And if it works, could you please then try 3.3-rc6 guest without vhost and disable event index feature by -device virtio-net-pci,event_idx=off ? thanks -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #14 from Steve 2012-03-06 19:35:14 --- Please could someone have a look on this issue ? Thank you for your time. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #13 from Steve 2012-03-06 07:28:59 --- Hello. I start testing from latest master branch v3.3-rc6+ on both: host, guest. During all test host has the same kernel & other stuff, on guest i changed only kernel versions by git bisecting. I don't change any code, my proposal is only tip and could be wrong. I suppose that I provided sufficient information to detect bug in code. Answer to your question about containing the fixes: --- git branch --contains=a72caae21803b74e04e2afda5e035f149d4ea118 * master git branch --contains=4dbc5d9f4f791df8a5879f4a655f517adc7f56d1 * master Let me know how could I help you (when needed) to fix this issue as soon as possible. Thank you for your time. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Jason Wang changed: What|Removed |Added CC||jasow...@redhat.com --- Comment #12 from Jason Wang 2012-03-06 02:56:08 --- (In reply to comment #11) > I found bad commit. > > git bisect log: > --- > git bisect start > # bad: [550cf00dbc8ee402bef71628cb71246493dd4500] Merge tag > 'mmc-fixes-for-3.3' > of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc > git bisect bad 550cf00dbc8ee402bef71628cb71246493dd4500 > # good: [61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf] Linux 2.6.39 > git bisect good 61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf > # bad: [8a9ea3237e7eb5c25f09e429ad242ae5a3d5ea22] Merge > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next > git bisect bad 8a9ea3237e7eb5c25f09e429ad242ae5a3d5ea22 > # bad: [95a943c162d74b20d869917bdf5df11293c35b63] Merge branch 'master' of > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6 into > for-davem > git bisect bad 95a943c162d74b20d869917bdf5df11293c35b63 > # good: [98b98d316349e9a028e632629fe813d07fa5afdd] Merge branch > 'drm-core-next' > of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 > git bisect good 98b98d316349e9a028e632629fe813d07fa5afdd > # bad: [1f6e44a6dc21a5d2abb068063acbbf64f8cee548] pxa168_eth: enable transmit > time stamping. > git bisect bad 1f6e44a6dc21a5d2abb068063acbbf64f8cee548 > # good: [19de85ef574c3a2182e3ccad9581805052f14946] bitops: add #ifndef for > each > of find bitops > git bisect good 19de85ef574c3a2182e3ccad9581805052f14946 > # good: [c320afe965bf3f857249d223801d8f2fc95615c2] Blackfin: debug-mmrs: > include RSI_PID[4567] MMRs > git bisect good c320afe965bf3f857249d223801d8f2fc95615c2 > # bad: [23c79d31a3dd2602ee1a5ff31303b2d7a2d3c159] Merge > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6 > git bisect bad 23c79d31a3dd2602ee1a5ff31303b2d7a2d3c159 > # good: [cd1acdf1723d71b28175f95b04305f1cc74ce363] Merge branch 'pnfs-submit' > of git://git.open-osd.org/linux-open-osd > git bisect good cd1acdf1723d71b28175f95b04305f1cc74ce363 > # bad: [cd4ecf877a4d629c38571405fd649077c12dec50] Merge branch > 'rmobile-fixes-for-linus' of > git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6 > git bisect bad cd4ecf877a4d629c38571405fd649077c12dec50 > # bad: [5c6cce92bc8aee751aafe82c5d9caf7553226a3d] Merge branch 'for-linus' of > git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6 > git bisect bad 5c6cce92bc8aee751aafe82c5d9caf7553226a3d > # bad: [8ea8cf89e19aeb596b818ee5f2bec8a8b0586b60] vhost: support event index > git bisect bad 8ea8cf89e19aeb596b818ee5f2bec8a8b0586b60 > # good: [bc805a03c26e1e25171bc627c6264553d27f746c] lguest: fix up compilation > after move > git bisect good bc805a03c26e1e25171bc627c6264553d27f746c > # good: [bf50e69f63d21091e525185c3ae761412be0ba72] virtio balloon: kill > tell-host-first logic > git bisect good bf50e69f63d21091e525185c3ae761412be0ba72 > # good: [770b31a85e000b0194974922f238a30ade4246b6] virtio: event index > interface > git bisect good 770b31a85e000b0194974922f238a30ade4246b6 > # bad: [a5c262c5fd83ece01bd649fb08416c501d4c59d7] virtio_ring: support event > idx feature > git bisect bad a5c262c5fd83ece01bd649fb08416c501d4c59d7 > # good: [bf7035bf20563a6cadcb9e870406e7b21daf5e30] virtio ring: inline > function > to check for events > git bisect good bf7035bf20563a6cadcb9e870406e7b21daf5e30 > > > git bisect message: > === > a5c262c5fd83ece01bd649fb08416c501d4c59d7 is the first bad commit > commit a5c262c5fd83ece01bd649fb08416c501d4c59d7 > Author: Michael S. Tsirkin > Date: Fri May 20 02:10:44 2011 +0300 > > virtio_ring: support event idx feature > > Support for the new event idx feature: > 1. When enabling interrupts, publish the current avail index >value to the host to get interrupts on the next update. > 2. Use the new avail_event feature to reduce the number >of exits from the guest. > > Simple test with the simulator: > > [virtio]# time ./virtio_test > spurious wakeus: 0x7 > > real0m0.169s > user0m0.140s > sys 0m0.019s > [virtio]# time ./virtio_test --no-event-idx > spurious wakeus: 0x11 > > real0m0.649s > user0m0.295s > sys 0m0.335s > > Signed-off-by: Michael S. Tsirkin > Signed-off-by: Rusty Russell > > :04 04 933903414419858cf7402aa3fb8c3f675d6ab7cc > 0ed603da4671eef88e0702e6438e903b56688b62 M drivers > > > > I found bug in include/linux/virtio_ring.h: > === > > virtio: event index interface > authorMichael S. Tsirkin > Thu, 19 May 2011 23:10:17 + (02:10 +0300) > committerRusty Russell > Mon, 30 May 2011 01:44:14 + (10:44 +0930) > commit770b31a85e000b019497492
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Steve changed: What|Removed |Added Kernel Version|v3.0-rc1|v3.0-rc1+ Severity|high|blocking --- Comment #11 from Steve 2012-03-06 02:26:16 --- I found bad commit. git bisect log: --- git bisect start # bad: [550cf00dbc8ee402bef71628cb71246493dd4500] Merge tag 'mmc-fixes-for-3.3' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc git bisect bad 550cf00dbc8ee402bef71628cb71246493dd4500 # good: [61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf] Linux 2.6.39 git bisect good 61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf # bad: [8a9ea3237e7eb5c25f09e429ad242ae5a3d5ea22] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next git bisect bad 8a9ea3237e7eb5c25f09e429ad242ae5a3d5ea22 # bad: [95a943c162d74b20d869917bdf5df11293c35b63] Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6 into for-davem git bisect bad 95a943c162d74b20d869917bdf5df11293c35b63 # good: [98b98d316349e9a028e632629fe813d07fa5afdd] Merge branch 'drm-core-next' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 git bisect good 98b98d316349e9a028e632629fe813d07fa5afdd # bad: [1f6e44a6dc21a5d2abb068063acbbf64f8cee548] pxa168_eth: enable transmit time stamping. git bisect bad 1f6e44a6dc21a5d2abb068063acbbf64f8cee548 # good: [19de85ef574c3a2182e3ccad9581805052f14946] bitops: add #ifndef for each of find bitops git bisect good 19de85ef574c3a2182e3ccad9581805052f14946 # good: [c320afe965bf3f857249d223801d8f2fc95615c2] Blackfin: debug-mmrs: include RSI_PID[4567] MMRs git bisect good c320afe965bf3f857249d223801d8f2fc95615c2 # bad: [23c79d31a3dd2602ee1a5ff31303b2d7a2d3c159] Merge git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6 git bisect bad 23c79d31a3dd2602ee1a5ff31303b2d7a2d3c159 # good: [cd1acdf1723d71b28175f95b04305f1cc74ce363] Merge branch 'pnfs-submit' of git://git.open-osd.org/linux-open-osd git bisect good cd1acdf1723d71b28175f95b04305f1cc74ce363 # bad: [cd4ecf877a4d629c38571405fd649077c12dec50] Merge branch 'rmobile-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6 git bisect bad cd4ecf877a4d629c38571405fd649077c12dec50 # bad: [5c6cce92bc8aee751aafe82c5d9caf7553226a3d] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6 git bisect bad 5c6cce92bc8aee751aafe82c5d9caf7553226a3d # bad: [8ea8cf89e19aeb596b818ee5f2bec8a8b0586b60] vhost: support event index git bisect bad 8ea8cf89e19aeb596b818ee5f2bec8a8b0586b60 # good: [bc805a03c26e1e25171bc627c6264553d27f746c] lguest: fix up compilation after move git bisect good bc805a03c26e1e25171bc627c6264553d27f746c # good: [bf50e69f63d21091e525185c3ae761412be0ba72] virtio balloon: kill tell-host-first logic git bisect good bf50e69f63d21091e525185c3ae761412be0ba72 # good: [770b31a85e000b0194974922f238a30ade4246b6] virtio: event index interface git bisect good 770b31a85e000b0194974922f238a30ade4246b6 # bad: [a5c262c5fd83ece01bd649fb08416c501d4c59d7] virtio_ring: support event idx feature git bisect bad a5c262c5fd83ece01bd649fb08416c501d4c59d7 # good: [bf7035bf20563a6cadcb9e870406e7b21daf5e30] virtio ring: inline function to check for events git bisect good bf7035bf20563a6cadcb9e870406e7b21daf5e30 git bisect message: === a5c262c5fd83ece01bd649fb08416c501d4c59d7 is the first bad commit commit a5c262c5fd83ece01bd649fb08416c501d4c59d7 Author: Michael S. Tsirkin Date: Fri May 20 02:10:44 2011 +0300 virtio_ring: support event idx feature Support for the new event idx feature: 1. When enabling interrupts, publish the current avail index value to the host to get interrupts on the next update. 2. Use the new avail_event feature to reduce the number of exits from the guest. Simple test with the simulator: [virtio]# time ./virtio_test spurious wakeus: 0x7 real0m0.169s user0m0.140s sys 0m0.019s [virtio]# time ./virtio_test --no-event-idx spurious wakeus: 0x11 real0m0.649s user0m0.295s sys 0m0.335s Signed-off-by: Michael S. Tsirkin Signed-off-by: Rusty Russell :04 04 933903414419858cf7402aa3fb8c3f675d6ab7cc 0ed603da4671eef88e0702e6438e903b56688b62 M drivers I found bug in include/linux/virtio_ring.h: === virtio: event index interface authorMichael S. Tsirkin Thu, 19 May 2011 23:10:17 + (02:10 +0300) committerRusty Russell Mon, 30 May 2011 01:44:14 + (10:44 +0930) commit770b31a85e000b0194974922f238a30ade4246b6 treeeed81e23f3116858b49af76bcc5831c38662de96tree | snapshot parenta1b383870a28cfbd1657d4922c0fafc634a62ebdcommit | diff virtio: event index interface Define a new feature bit for th
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Steve changed: What|Removed |Added Kernel Version|v3.0-rc5|v3.0-rc1 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Steve changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|CODE_FIX| --- Comment #10 from Steve 2012-03-04 21:20:01 --- Results of longer tests: Above problem occurs after longer time, more than 10 minutes. I try to locate problem with new git bisecting. Thank you for your time. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Steve changed: What|Removed |Added Status|NEW |RESOLVED Resolution||CODE_FIX --- Comment #9 from Steve 2012-03-03 22:12:09 --- Thank you for information. Now it works fine with last kernel 3.3-rc5+ on guest machine. It seems to be: leak in virtio balloon: Probably it was bug in old commit: author: Amit Shah commiter: Rusty Russell e562966dbaf49e7804097cd991e5d3a8934fc148 and fixed by this commit: author: Amit Shah commiter: Rusty Russell 4eb05d562ea1ea34ff607aa877aefbf05b21c140 Please apply above fix commit to all older kernel versions. Thank you for your time. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #8 from Kurk 2012-03-02 11:36:43 --- Thinking again, this could also be a problem of qemu vs qemu-kvm merges in git. Have a look at these: http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/82851 http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg04047.html and all subsequent posts in this thread Git-bisecting in qemu and kvm is becoming really not straightforward now that they merge from one another, you find a lot of interleaved good and bad commits. Git bisect is for bisecting a situation in which all commits before something are good, and all commits after something are bad. It doesn't seem to be the case anymore with qemu and qemu-kvm. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #7 from Kurk 2012-03-02 11:14:10 --- Git bisect result is not network related? Highly unlikely! The "bug reproducer" technique you are using might not be reliable (sorry if that was the one I suggested). Try to make longer tests...? I suggest you retest the bisect points which you marked good, some of them might instead be bad. Thanks for your time in finding this bug: this is a very important bug! -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #6 from Steve 2012-03-02 01:05:35 --- My results: === git bisect log: --- git bisect start # good: [2c53b436a30867eb6b47dd7bab23ba638d1fb0d2] Linux 3.0-rc3 git bisect good 2c53b436a30867eb6b47dd7bab23ba638d1fb0d2 # bad: [b0af8dfdd67699e25083478c63eedef2e72ebd85] Linux 3.0-rc5 git bisect bad b0af8dfdd67699e25083478c63eedef2e72ebd85 # bad: [c01ad4081939f91ebd7277e8e731fd90ceb3e632] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input git bisect bad c01ad4081939f91ebd7277e8e731fd90ceb3e632 # bad: [f4ef084226f82ca923bf0a2658bb2876bd215ec1] Merge branch 'fbdev-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/lethal/fbdev-3.x git bisect bad f4ef084226f82ca923bf0a2658bb2876bd215ec1 # bad: [bd5dc17be87b3a3073d50b23802647db3ae3fa8e] uts: make default hostname configurable, rather than always using "(none)" git bisect bad bd5dc17be87b3a3073d50b23802647db3ae3fa8e # bad: [f39e8409955fad210a9a7169cc53c4c18daaef3a] Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 git bisect bad f39e8409955fad210a9a7169cc53c4c18daaef3a # bad: [81eb3dd8438802138ac9ce12428632f35562c060] Merge branch 'for-linus' of git://neil.brown.name/md git bisect bad 81eb3dd8438802138ac9ce12428632f35562c060 # good: [9864c0053d3da4c5731ac8a6c4835179310bd40a] md: Using poll /proc/mdstat can monitor the events of adding a spare disks git bisect good 9864c0053d3da4c5731ac8a6c4835179310bd40a # bad: [9b2dc8b665932a8e681a7ab3237f60475e75e161] md/raid5: fix raid5_set_bi_hw_segments git bisect bad 9b2dc8b665932a8e681a7ab3237f60475e75e161 # bad: [27d5ea04d08bea37bf651090e5f3c573d2390df8] md/bitmap: use proper accessor macro git bisect bad 27d5ea04d08bea37bf651090e5f3c573d2390df8 # bad: [01393f3d5836b7d62e925e6f4658a7eb22b83a11] md: check ->hot_remove_disk when removing disk git bisect bad 01393f3d5836b7d62e925e6f4658a7eb22b83a11 git bisect message: --- 01393f3d5836b7d62e925e6f4658a7eb22b83a11 is the first bad commit commit 01393f3d5836b7d62e925e6f4658a7eb22b83a11 Author: Namhyung Kim Date: Thu Jun 9 11:42:54 2011 +1000 md: check ->hot_remove_disk when removing disk Check pers->hot_remove_disk instead of pers->hot_add_disk in slot_store() during disk removal. The linear personality only has ->hot_add_disk and no ->hot_remove_disk, so that removing disk in the array resulted to following kernel bug: $ sudo mdadm --create /dev/md0 --level=linear --raid-devices=4 /dev/loop[0-3] $ echo none | sudo tee /sys/block/md0/md/dev-loop2/slot BUG: unable to handle kernel NULL pointer dereference at (null) IP: [< (null)>] (null) PGD c9f5d067 PUD 8575a067 PMD 0 Oops: 0010 [#1] SMP CPU 2 Modules linked in: linear loop bridge stp llc kvm_intel kvm asus_atk0110 sr_mod cdrom sg Pid: 10450, comm: tee Not tainted 3.0.0-rc1-leonard+ #173 System manufacturer System Product Name/P5G41TD-M PRO RIP: 0010:[<>] [< (null)>] (null) RSP: 0018:880085757df0 EFLAGS: 00010282 RAX: a00168e0 RBX: 8800d1431800 RCX: 006e RDX: 0001 RSI: 0002 RDI: 88008543c000 RBP: 880085757e48 R08: 0002 R09: 000a R10: R11: 88008543c2e0 R12: R13: 8800b4641000 R14: 0005 R15: FS: 7fe8c9e05700() GS:88011fa0() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: CR3: b4502000 CR4: 000406e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process tee (pid: 10450, threadinfo 880085756000, task 8800c9f08000) Stack: 8138496a 8800b4641000 88008543c268 8800b4641000 88008543c000 8800d1431868 81a78a90 8800b4641000 88008543c000 8800d1431800 880085757e98 Call Trace: [] ? slot_store+0xaa/0x265 [] rdev_attr_store+0x89/0xa8 [] sysfs_write_file+0x108/0x144 [] vfs_write+0xb1/0x10d [] ? trace_hardirqs_on_caller+0x111/0x135 [] sys_write+0x4d/0x77 [] system_call_fastpath+0x16/0x1b Code: Bad RIP value. RIP [< (null)>] (null) RSP CR2: ---[ end trace ba5fc64319a826fb ]--- Signed-off-by: Namhyung Kim Cc: sta...@kernel.org Signed-off-by: NeilBrown :04 04 e3d19f53113f5bb5faef422958607e4f0131d235 eab9913143e1c027df693bf1fa57475da77bd36e M drivers How could I help now ? Thank you for your time. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail bec
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Steve changed: What|Removed |Added Kernel Version|3.2-rc3 |v3.0-rc5 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #5 from Steve 2012-03-01 23:04:37 --- Results of my test: === In all test cases host configuration is the same: - kernel: latest 3.3-rc5+ compiler: gcc (4.7.0-pre 20120225 rev. 184573) glibc-2.14.1-r2 bridge-utils-1.5 iproute2-3.1.0 ethtool-3.2 other system stuff: all latest from their git repos util-linux, net-tools, kmod, udev, seabios, qemu-kvm In all test cases guest configuration except kernel is the same: compiler: gcc 4.6.2 glibc-2.14.1-r2 iproute2-3.1.0 ethtool-3.2 other system stuff: all latest from their git repos util-linux, net-tools, kmod, udev 1) guest kernel =v2.6.39 - works fine more than 5min 2) guest kernel =v3.0 - virtio network goes down in less then 1min of test 3) guest kernel latest v3.3-rc5+ - virtio network goes down in less then 1min of test I continue with tracking in kernel tags after v2.6.39: 4) guest kernel =v3.0-rc1 - works fine more than 5min 5) guest kernel =v3.0-rc5 - virtio network goes down in less then 1min of test 6) guest kernel =v3.0-rc3 - works fine more than 5min I shortly look at =v3.0-rc5, problem could be somewhere in this tag. Later I would like to locate problematic commit with git bisecting and after I report my results. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #4 from Steve 2012-03-01 15:22:53 --- Thank you for information. On host I used last updated: kernel from: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git qemu-kvm from: git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git seabios from: git://git.seabios.org/seabios.git used compiler, libs & other stuff: gcc-4.7.0 (feb 2012) glibc-2.14.1-r2 bridge-utils-1.5 iproute2-3.1.0 ethtool-3.2 On guest I can proceed this: 1) test case one - kernel before https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Kurk changed: What|Removed |Added CC||k...@shiftmail.org --- Comment #3 from Kurk 2012-03-01 14:16:36 --- Hello, I am pretty sure I read about a very similar bug report recently, dunno if that was on kvm or qemu mailing list, or in a bugzilla entry like this. The guy said that there was a reproducer: running a network test between two affected virtual machines. Maybe that was netperf, not sure. Would reproduce the bug in a short time. He said kernel 3.0 (GUEST!) was the first he tested to have this problem, while much older guest kernels did not have this problem. I suggest Steve tries this reproducer, and tell if it works in his case. If that works, debugging would be much faster. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Steve changed: What|Removed |Added Kernel Version|3.2 |3.2-rc3 --- Comment #2 from Steve 2012-03-01 10:46:09 --- Rusty, could you have a look at, please ? Thank you for your time. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42812] kvm module has bogus kernel version check
https://bugzilla.kernel.org/show_bug.cgi?id=42812 Jan Kiszka changed: What|Removed |Added CC||jan.kis...@web.de --- Comment #1 from Jan Kiszka 2012-02-28 17:29:13 --- Thanks for reporting, addressed in latest kvm-kmod.git. Jan -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 --- Comment #1 from Steve 2012-02-28 13:49:24 --- Also this sites described similar problems: https://bugzilla.redhat.com/show_bug.cgi?id=520119 http://www.mail-archive.com/scientific-linux-users@ listserv.fnal.gov/msg10661.html Let me know how could I help in solving above issue. Thank you for your time. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Steve changed: What|Removed |Added CC||ru...@rustcorp.com.au Kernel Version|3.3.0-rc5 |3.2 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42829] New: KVM Guest with virtio network driver loses network connectivity
https://bugzilla.kernel.org/show_bug.cgi?id=42829 Summary: KVM Guest with virtio network driver loses network connectivity Product: Virtualization Version: unspecified Kernel Version: 3.3.0-rc5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: kvm AssignedTo: virtualization_...@kernel-bugs.osdl.org ReportedBy: stefan.bo...@gmail.com CC: a...@redhat.com Regression: Yes Description: Running KVM guests with virtio network interfaces, the guest will (probably in some - unidentified - circumstances) stop receiving packets. A tcpdump on the bugged interface will show only ARP requests being sent by the server and unanswered. Possible workarounds: Temporarily: - restart network interface in guest Permanent: - use e1000 network driver as replacement of virtio_net driver How to reproduce: - 1) start KVM guest: qemu-kvm -nodefaults -name vps -chroot /chroot -runas kvm -pidfile /var/run/kvm/vps.pid -vnc 1.2.3.4:0 -vga std --full-screen -smp 2 -m 1g -cpu host -mem-path /hugepages -mem-prealloc -kvm-shadow-memory 1g -enable-kvm -daemonize -rtc base=localtime,clock=host,driftfix=none -balloon virtio -net nic,model=virtio,vlan=0,macaddr=52:54:00:33:22:11 -net bridge,br=br0,vlan=0 -drive aio=native,index=0,media=disk,cache=none,if=virtio,file=vps.img -boot order=c,menu=off & 2) generate huge trafic (after few minutes virtio network card crashed): from host to guest: screen ping 10.8.7.2 -s 65507 screen iperf -s -i 1 -f M from guest to host: screen ping 10.8.7.1 -s 65507 screen iperf -c 10.8.7.2 -i 1 -f M 3) restart guest network interface and repeat step 2) until network crash again Above situation occurs on (my tests): host kernel 3.3+ qemu-kvm 1.0+ any guest Linux 2.6+ - 3.3+ kernel any guest Windows 7+ Same situation described from other users on some forums: http://bugs.centos.org/view.php?id=5526 http://serverfault.com/questions/362038/ qemu-kvm-virtual-machine-virtio-network-freeze-under-load (possible, not tested old patch) Please fix above crashing of virtio_net driver. Thank you for your time. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #35 from Rosen 2012-02-26 09:53:22 --- No changes with git version of qemu-kvm Only see when work guest cpu usage is out of range, about 120% - 150% -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42812] New: kvm module has bogus kernel version check
https://bugzilla.kernel.org/show_bug.cgi?id=42812 Summary: kvm module has bogus kernel version check Product: Virtualization Version: unspecified Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm AssignedTo: virtualization_...@kernel-bugs.osdl.org ReportedBy: mcbb...@robuust.nl Regression: No In kvm-kmod-3.2, x86/external-module-compat.h, line 1102 the following check is present: #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,37) || \ (LINUX_VERSION_CODE == KERNEL_VERSION(2,6,32) && KERNEL_EXTRAVERSION < 40) The second half is bogus, since if kernel version is 2.6.32, it would have matched the < 2.6.37 anyway. Maybe the 2,6,32 should read 2,6,37 instead? (that would make more sense, but may not be right!) This check appears to be present since kvm-kmod release 3.0b, which makes it unlikely many people tried it with 2.6.27.40+ kernels and found it to be a problem... -- Maarten -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #34 from Rosen 2012-02-21 12:45:15 --- (In reply to comment #33) > Supposing it was working good with an old version of kvm: > Why don't you just do a git bisect? qemu-kvm is very quick to compile and > install. Start kvm with -snapshot so you can kill it anytime; and just by > visual inspection at boot you should be able to determine if it is fast or > slow > and proceed with next step of bisect. In a short time you would probably solve > this. not that fast compilling, it eat my memory durring compille process and going to megaswapping.. 100% CPU RAM SWAP usage when compilling kvm. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 Kurk changed: What|Removed |Added CC||k...@shiftmail.org --- Comment #33 from Kurk 2012-02-21 11:53:33 --- Supposing it was working good with an old version of kvm: Why don't you just do a git bisect? qemu-kvm is very quick to compile and install. Start kvm with -snapshot so you can kill it anytime; and just by visual inspection at boot you should be able to determine if it is fast or slow and proceed with next step of bisect. In a short time you would probably solve this. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #32 from Gleb 2012-02-21 09:10:37 --- Can you run perf without ksm? In your previous perf invocation ksm was at the top, so lets see what is it there now. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #31 from Rosen 2012-02-21 08:55:31 --- any responses ? with/without ksm no change. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #19 from madenginee...@gmail.com 2012-02-16 22:01:38 --- Doesn't seem to help. I used -cpu core2duo,-3dnow (since core2duo is the name that libvirt, my usual launcher for qemu, has been using), failed on the same movq. Also tried -cpu core2duo,-3dnow,-mmx, same results. I'll see if I can build a kernel with the Geode framebuffer driver but without setting the CPU to Geode (thus eliminating the use of MMX). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #18 from Avi Kivity 2012-02-16 17:30:47 --- As a workaround you can use -cpu blah,-3dnow. But we'll have to implement mmx movq. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #17 from Jan Kiszka 2012-02-16 17:24:34 --- (In reply to comment #15) > I set the kernel up for an AMD Geode LX800 (CONFIG_MGEODE_LX), which does > supposedly support SSE. No idea why it would have built using MMX if that is > now deprecated in favor of SSE. At least not according to the Linux configuration: MGEODE_LX only sets X86_USE_3DNOW, thus MMX. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #16 from madenginee...@gmail.com 2012-02-16 16:51:10 --- Background: I'm using KVM as a test platform for code destined for a panel PC using a Geode LX800. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #15 from madenginee...@gmail.com 2012-02-16 16:48:56 --- I set the kernel up for an AMD Geode LX800 (CONFIG_MGEODE_LX), which does supposedly support SSE. No idea why it would have built using MMX if that is now deprecated in favor of SSE. I can try disabling the framebuffer (CONFIG_FB/CONFIG_FB_GEODE/CONFIG_FB_GEODE_LX) for testing purposes; unfortunately this wouldn't work for the real thing, since we need it for the Qt-based user interface. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42782] IO_PAGE_FAULT while starting xorg
https://bugzilla.kernel.org/show_bug.cgi?id=42782 Joerg Roedel changed: What|Removed |Added CC||j...@8bytes.org --- Comment #4 from Joerg Roedel 2012-02-16 14:02:17 --- You are using the closed-source NVidia driver which apparently has a bug. The driver seems not to use the DMA-API properly and tries to DMA to an invalid handle. Please try the open source NVidia drivers or report the problem to NVidia directly. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42782] IO_PAGE_FAULT while starting xorg
https://bugzilla.kernel.org/show_bug.cgi?id=42782 --- Comment #3 from edm 2012-02-16 12:17:43 --- Created an attachment (id=72400) --> (https://bugzilla.kernel.org/attachment.cgi?id=72400) lspci -vv output -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42782] IO_PAGE_FAULT while starting xorg
https://bugzilla.kernel.org/show_bug.cgi?id=42782 --- Comment #2 from edm 2012-02-16 12:17:11 --- Created an attachment (id=72399) --> (https://bugzilla.kernel.org/attachment.cgi?id=72399) dmidecode output -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42782] IO_PAGE_FAULT while starting xorg
https://bugzilla.kernel.org/show_bug.cgi?id=42782 --- Comment #1 from edm 2012-02-16 12:14:28 --- Created an attachment (id=72398) --> (https://bugzilla.kernel.org/attachment.cgi?id=72398) dmesg output -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42782] New: IO_PAGE_FAULT while starting xorg
https://bugzilla.kernel.org/show_bug.cgi?id=42782
Summary: IO_PAGE_FAULT while starting xorg
Product: Virtualization
Version: unspecified
Kernel Version: 3.2.6
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_...@kernel-bugs.osdl.org
ReportedBy: fuffi.il.fu...@gmail.com
Regression: No
Hi,
I got this error while doing startx with 3.2.6 kernel and I can't start xorg:
[ 54.683907] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0
domain=0x0018 address=0x000220583200 flags=0x0010]
I saw the same error in this mailing list
(http://www.spinics.net/lists/kvm/msg48472.html) so I thought it was
the right ml for reporting this problem, am I wrong?
I attached the output of dmesg, lspci -vv and dmidecode.
disabling amd_iommu allow X to start but it's only a workaround.
This is the relevant part of my grub.cfg file:
# (0) Arch Linux
menuentry 'Arch Linux' {
set root='(hd0,1)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-linux' '/boot/vmlinuz-linux'
'root=/dev/disk/by-uuid/a4259127-650c-4767-af64-9c86cdc1a5e1' 'ro'
'vga=773' 'amd_iommu_dump' '3'
legacy_initrd '/boot/initramfs-linux.img' '/boot/initramfs-linux.img'
# (1) Arch Linux
}
Thanks in advance,
EDM.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
--
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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #14 from Jan Kiszka 2012-02-16 11:51:05 --- Because the selected CPU type doesn't support SSE? Didn't check the config yet, but I bet that's the reason. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 Avi Kivity changed: What|Removed |Added CC||a...@redhat.com --- Comment #13 from Avi Kivity 2012-02-16 11:40:22 --- Indeed the emulator doesn't support mmx yet. But why is the kernel using mmx instead of sse? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #12 from Gleb 2012-02-16 08:40:37 --- Can you try disabling CONFIG_FB in your guest kernel? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 Jan Kiszka changed: What|Removed |Added CC||jan.kis...@web.de --- Comment #11 from Jan Kiszka 2012-02-16 08:31:18 --- (In reply to comment #4) > Code=8e 2b 01 00 00 8b 4d f0 89 f2 8b 45 ec 0f 0d 82 40 01 00 00 <0f> 6f 02 0f > 6f 4a 08 0f 6f 52 10 0f 6f 5a 18 0f 7f 00 0f 7f 48 08 0f 7f 50 10 0f 7f 58 18 This is "movq (%rdx),%mm0". Possibly still unsupported by the emulator. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #10 from Gleb 2012-02-16 08:04:22 --- (In reply to comment #8) > Not sure what you mean by installing trace-cmd before capturing the trace--I > did do that, otherwise I wouldn't have had a trace-cmd to run. The package I meant that if you compile it by yourself you need to run "make install" instead of running it from where it was compiled. Otherwise it does not find plugins. If you install it from package manager this is not relevant of course. > version is trace-cmd 1.0.3-0ubuntu1 if that helps. I tried running it again > against qemu 1.0 (the last one was for qemu 0.14), still contained a bunch of > [FAILED TO PARSE] messages. > Something wrong with ubuntu trace-cmd then. Either it does not have kvm plugin or it is too old. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #9 from madenginee...@gmail.com 2012-02-16 07:57:35 --- Created an attachment (id=72397) --> (https://bugzilla.kernel.org/attachment.cgi?id=72397) Register state and code disassembly at failure point with qemu 1.0 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #8 from madenginee...@gmail.com 2012-02-16 07:56:03 --- Not sure what you mean by installing trace-cmd before capturing the trace--I did do that, otherwise I wouldn't have had a trace-cmd to run. The package version is trace-cmd 1.0.3-0ubuntu1 if that helps. I tried running it again against qemu 1.0 (the last one was for qemu 0.14), still contained a bunch of [FAILED TO PARSE] messages. Attaching the output you requested separately. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #7 from Gleb 2012-02-16 07:43:11 --- Have you installed trace-cmd before capturing the trace? It failed to parse kvm events. qemu haven't paused the guest after emulation error (looks like a bug), so 'x/30i $eip' output is not useful either. Can you do 'x/30i 0xXXX' where XXX is the address in EIP from register dump you see after instruction emulation failure message (c1228905 in your output from comment #4)? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #6 from madenginee...@gmail.com 2012-02-16 07:22:41 --- Created an attachment (id=72395) --> (https://bugzilla.kernel.org/attachment.cgi?id=72395) Last 10k lines of a trace showing the fault Per Gleb's request -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 Gleb changed: What|Removed |Added CC||g...@redhat.com --- Comment #5 from Gleb 2012-02-16 07:15:49 --- (In reply to comment #3) > Couldn't attach the trace I recorded of the fault occurring since it's 3 MB > compressed with xz, bigger still with other formats. I can email it if it will > be useful. Can you do "tail -1" on it and attach it here? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #4 from madenginee...@gmail.com 2012-02-16 06:32:48 --- Same problem occurs with qemu-kvm 1.0 from https://launchpad.net/~bderzhavets/+archive/lib-usbredir39: $ sudo kvm -M pc-1.0 -enable-kvm -m 1024 -drive file=/var/lib/libvirt/images/eve.img,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=21,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:b5:f4:00,bus=pci.0,addr=0x3 -chardev vc,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vga cirrus kvm: -netdev tap,fd=21,id=hostnet0: TUNGETIFF ioctl() failed: Bad file descriptor TUNSETOFFLOAD ioctl() failed: Bad file descriptor kvm: -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:b5:f4:00,bus=pci.0,addr=0x3: pci_add_option_rom: failed to find romfile "pxe-e1000.rom" KVM internal error. Suberror: 1 emulation failure EAX=f681 EBX=003e ECX=003e EDX=c00b8000 ESI=c00b8000 EDI=c15b EBP=c15b1f74 ESP=c15b1f58 EIP=c1228905 EFL=00010206 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =007b 00c0f300 DPL=3 DS [-WA] CS =0060 00c09b00 DPL=0 CS32 [-RA] SS =0068 00c09300 DPL=0 DS [-WA] DS =007b 00c0f300 DPL=3 DS [-WA] FS = GS = LDT= TR =0080 c15b6300 206b 8b00 DPL=0 TSS32-busy GDT= c15b3000 00ff IDT= c15b2000 07ff CR0=80050033 CR2=ffee4000 CR3=01663000 CR4=0690 DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=8e 2b 01 00 00 8b 4d f0 89 f2 8b 45 ec 0f 0d 82 40 01 00 00 <0f> 6f 02 0f 6f 4a 08 0f 6f 52 10 0f 6f 5a 18 0f 7f 00 0f 7f 48 08 0f 7f 50 10 0f 7f 58 18 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #3 from madenginee...@gmail.com 2012-02-16 05:57:25 --- Couldn't attach the trace I recorded of the fault occurring since it's 3 MB compressed with xz, bigger still with other formats. I can email it if it will be useful. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 madenginee...@gmail.com changed: What|Removed |Added Attachment #72394|application/octet-stream|text/plain mime type|| -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 madenginee...@gmail.com changed: What|Removed |Added Attachment #72393|application/octet-stream|text/plain mime type|| -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #2 from madenginee...@gmail.com 2012-02-16 05:47:18 --- Created an attachment (id=72394) --> (https://bugzilla.kernel.org/attachment.cgi?id=72394) Result of 'registers info' and 'x/30i $eip' after fault -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 --- Comment #1 from madenginee...@gmail.com 2012-02-16 05:46:07 --- Created an attachment (id=72393) --> (https://bugzilla.kernel.org/attachment.cgi?id=72393) Configuration of the guest kernel -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42779] New: KVM domain hangs after loading initrd with Xenomai kernel
https://bugzilla.kernel.org/show_bug.cgi?id=42779 Summary: KVM domain hangs after loading initrd with Xenomai kernel Product: Virtualization Version: unspecified Kernel Version: 3.0.0-15 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm AssignedTo: virtualization_...@kernel-bugs.osdl.org ReportedBy: madenginee...@gmail.com Regression: No Attempting to boot a 32 bit Debian guest with a Xenomai kernel inside KVM causes it to hang and spin (using 1 full CPU core) after loading the initrd, as determined by serial console output. The only error message is "KVM internal error. Suberror: 1"/"emulation failure". Booting a regular Debian kernel succeeds, as does running the Xenomai kernel with software emulation (-no-kvm). Info: CPU: Intel Core i7-2670QM Emulator: qemu-kvm 0.14.1 Host kernel: 3.0.0-15 (Ubuntu build), x86_64 Guest OS: Debian Squeeze, kernel.org 2.6.37 kernel with Xenomai 2.6.0 (config attached) Qemu command: kvm -M pc-0.14 -enable-kvm -m 1024 -drive file=/var/lib/libvirt/images/eve.img,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=21,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:b5:f4:00,bus=pci.0,addr=0x3 -chardev stdio,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vga cirrus Effects of flags: Adding one or both of --no-kvm-irqchip or --no-kvm-pit has no apparent effect. Adding --no-kvm appears to correct the problem, at the cost of performance due to using the software emulator. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #30 from Avi Kivity 2012-02-15 09:28:12 --- Disable ksm, and build with debug information so we get useful information instead of hex addresses. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #29 from Rosen 2012-02-15 07:49:35 --- (In reply to comment #28) > (In reply to comment #27) > > and there soon will be video capture with 'perf top' > > > > http://vbox7.com/play:199e9ede30 > > Run it while the guest is also running. Good Morning! There will be video http://vbox7.com/play:7128f03f1f after some momments. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #28 from Avi Kivity 2012-02-14 14:47:38 --- (In reply to comment #27) > and there soon will be video capture with 'perf top' > > http://vbox7.com/play:199e9ede30 Run it while the guest is also running. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #27 from Rosen 2012-02-13 14:37:36 --- and there soon will be video capture with 'perf top' http://vbox7.com/play:199e9ede30 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #26 from Rosen 2012-02-13 14:24:36 --- Created an attachment (id=72365) --> (https://bugzilla.kernel.org/attachment.cgi?id=72365) info pci -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #25 from Rosen 2012-02-13 14:14:17 --- (In reply to comment #23) > What guest did during this trace? Can you provide "info pci" monitor output > pls? can't see full output from this command -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 Avi Kivity changed: What|Removed |Added CC||a...@redhat.com --- Comment #24 from Avi Kivity 2012-02-13 13:43:35 --- Please run 'perf top' in the host and report the output (while tracing is disabled). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #23 from Gleb 2012-02-13 13:30:01 --- What guest did during this trace? Can you provide "info pci" monitor output pls? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #22 from Rosen 2012-02-13 13:19:29 --- Created an attachment (id=72363) --> (https://bugzilla.kernel.org/attachment.cgi?id=72363) trace-cmd report -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #21 from Gleb 2012-02-13 08:53:28 --- Can you please compile trace-cmd from its git [1] (do "make all_cmd install_cmd"; install part is important) and try getting trace with it? If this will not work I will guide you how to take a trace using debugfs directly. [1] git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #20 from Rosen 2012-02-12 16:14:21 --- i compilled it from AUR, maybe package is broken -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #19 from Gleb 2012-02-12 15:09:04 --- (In reply to comment #17) > hello again! > > roko__@ArchXFCE64(16:47:28-12-02-12)( /mnt/home/roko__-backup/kvm pts/6 )# > trace-cmd report > version = 6 > cound not load plugin '/usr/local/share/trace-cmd/plugins/plugin_python.so' > /usr/local/share/trace-cmd/plugins/plugin_python.so: undefined symbol: > PyString_FromString > > File possibly truncated. Need at least 1654784, but file size is 1654292. > trace-cmd: Invalid argument > failed to init data > > And the trace.dat file is in attachments. It is corrupted for me too. Have you compiled trace-cmd by yourself? If yes have you ran "make install" before using it? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #18 from Rosen 2012-02-12 14:55:25 --- Created an attachment (id=72360) --> (https://bugzilla.kernel.org/attachment.cgi?id=72360) sudo trace-cmd record -b 2 -e kvm trace.dat from roko__@ArchXFCE64(16:46:25-12-02-12)( /mnt/home/roko__-backup/kvm pts/6 )# sudo trace-cmd record -b 2 -e kvm /sys/kernel/debug/tracing/events/kvm/filter /sys/kernel/debug/tracing/events/*/kvm/filter Hit Ctrl^C to stop recording ^CKernel buffer statistics: Note: "entries" are the entries left in the kernel ring buffer and are not recorded in the trace data. They should all be zero. CPU: 0 entries: 0 overrun: 0 commit overrun: 0 bytes: 0 oldest event ts: 18446612134.805802 now ts: 3383.418379 CPU: 1 entries: 0 overrun: 0 commit overrun: 0 bytes: 0 oldest event ts: 142390.782329 now ts: 3383.418586 CPU0 data recorded at offset=0x194000 0 bytes in size CPU1 data recorded at offset=0x194000 0 bytes in size roko__@ArchXFCE64(16:47:23-12-02-12)( /mnt/home/roko__-backup/kvm pts/6 )# -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #17 from Rosen 2012-02-12 14:49:41 --- hello again! roko__@ArchXFCE64(16:47:28-12-02-12)( /mnt/home/roko__-backup/kvm pts/6 )# trace-cmd report version = 6 cound not load plugin '/usr/local/share/trace-cmd/plugins/plugin_python.so' /usr/local/share/trace-cmd/plugins/plugin_python.so: undefined symbol: PyString_FromString File possibly truncated. Need at least 1654784, but file size is 1654292. trace-cmd: Invalid argument failed to init data And the trace.dat file is in attachments. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #16 from Gleb 2012-02-12 10:49:04 --- (In reply to comment #15) > > zgrep TRACING /proc/config.gz > CONFIG_TRACING_SUPPORT=y > You need CONFIG_TRACING/CONFIG_FTRACE and others. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #15 from Rosen 2012-02-12 10:41:31 --- (In reply to comment #14) > (In reply to comment #13) > > (In reply to comment #12) > > > Allready mounted. Bu this directory doesn't exist, i have those dirs: > > > > > > /sys/kernel/debug > > > acpi bdi dri hid ieee80211 kvm mce suspend_stats usb > > > virtio-ports > > > wakeup_sources x86 > > > > Is this ancient kernel? Or have you disabled tracing during kernel compile? > > If > > later you will have to rebuild the kernel with tracing enabled. This is the > > only way to see what is happening. > > Its my kernel not default ARCH kernel. > > zgrep TRACE /proc/config.gz > CONFIG_STACKTRACE_SUPPORT=y > # CONFIG_RCU_TRACE is not set > # CONFIG_TREE_RCU_TRACE is not set > CONFIG_HAVE_ARCH_TRACEHOOK=y > # CONFIG_TRACE_SINK is not set > CONFIG_TRACE_IRQFLAGS_SUPPORT=y > CONFIG_USER_STACKTRACE_SUPPORT=y > CONFIG_HAVE_FUNCTION_TRACER=y > CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y > CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y > CONFIG_HAVE_DYNAMIC_FTRACE=y > CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y > CONFIG_HAVE_SYSCALL_TRACEPOINTS=y > # CONFIG_FTRACE is not set > CONFIG_HAVE_MMIOTRACE_SUPPORT=y > zgrep TRACING /proc/config.gz CONFIG_TRACING_SUPPORT=y > i'm not sure which option need to be enabled?! -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
[Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
https://bugzilla.kernel.org/show_bug.cgi?id=42755 --- Comment #14 from Rosen 2012-02-12 10:40:56 --- (In reply to comment #13) > (In reply to comment #12) > > Allready mounted. Bu this directory doesn't exist, i have those dirs: > > > > /sys/kernel/debug > > acpi bdi dri hid ieee80211 kvm mce suspend_stats usb virtio-ports > > wakeup_sources x86 > > Is this ancient kernel? Or have you disabled tracing during kernel compile? If > later you will have to rebuild the kernel with tracing enabled. This is the > only way to see what is happening. Its my kernel not default ARCH kernel. zgrep TRACE /proc/config.gz CONFIG_STACKTRACE_SUPPORT=y # CONFIG_RCU_TRACE is not set # CONFIG_TREE_RCU_TRACE is not set CONFIG_HAVE_ARCH_TRACEHOOK=y # CONFIG_TRACE_SINK is not set CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_SYSCALL_TRACEPOINTS=y # CONFIG_FTRACE is not set CONFIG_HAVE_MMIOTRACE_SUPPORT=y i'm not sure which option need to be enabled?! -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- 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
