[Bug 76331] kernel BUG at drivers/iommu/intel-iommu.c:844!

2014-07-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76331 --- Comment #6 from Matt mspe...@users.sourceforge.net --- Hi Alex and David, I've been successfully using Alex's fix for more than a month now. https://lkml.org/lkml/2014/5/29/932 Would it be possible to close this bug by adding the patch to

[Bug 79041] New: External snapshot creation

2014-06-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=79041 Bug ID: 79041 Summary: External snapshot creation Product: Virtualization Version: unspecified Kernel Version: 3.2.0-23-generic Hardware: All OS: Linux Tree:

[Bug 79041] External snapshot creation

2014-06-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=79041 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25332] When a VM is rebooted, assigned devices do not get RESET ...

2014-06-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=25332 xerofo...@gmail.com changed: What|Removed |Added CC||xerofo...@gmail.com --- Comment #3

[Bug 40542] overflow/panic on KVM hipervizor

2014-06-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=40542 xerofo...@gmail.com changed: What|Removed |Added CC||xerofo...@gmail.com --- Comment #14

[Bug 42082] 3.1.0-rc2 block related lockdep report.

2014-06-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=42082 xerofo...@gmail.com changed: What|Removed |Added CC||xerofo...@gmail.com --- Comment #1

[Bug 67751] Stack trace with suspicious RCU usage, when starting ovs-switchd

2014-06-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67751 --- Comment #5 from Kashyap Chamarthy kashyap...@gmail.com --- I just saw this again when I attempt to restart OpenvSwitch with Kernel -- 3.16.0-0.rc1.git1.1.fc21.x86_64 - [ 9695.079715] [ 9695.080492]

[Bug 42980] BUG in gfn_to_pfn_prot

2014-06-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=42980 xerofo...@gmail.com changed: What|Removed |Added CC||xerofo...@gmail.com --- Comment #22

[Bug 78331] New: Qemu crash in x86

2014-06-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=78331 Bug ID: 78331 Summary: Qemu crash in x86 Product: Virtualization Version: unspecified Kernel Version: 2.6.32 Hardware: All OS: Linux Tree: Mainline

[Bug 78331] Qemu crash in x86

2014-06-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=78331 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 68051] Kernel stack trace when attempt to boot into 3.13.0-0.rc6.git0.1 results in kernel BUG at mm/page_alloc.c:2788

2014-06-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=68051 xerofo...@gmail.com changed: What|Removed |Added CC||xerofo...@gmail.com --- Comment #5

[Bug 68051] Kernel stack trace when attempt to boot into 3.13.0-0.rc6.git0.1 results in kernel BUG at mm/page_alloc.c:2788

2014-06-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=68051 Kashyap Chamarthy kashyap...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 77871] New: USB device passthrough to Virtual GUEST system from Linux

2014-06-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=77871 Bug ID: 77871 Summary: USB device passthrough to Virtual GUEST system from Linux Product: Virtualization Version: unspecified Kernel Version: 3.14.6 or 3.14.7 Hardware:

[Bug 54521] nVMX: accurately emulate VMXON region

2014-06-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=54521 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 53601] nVMX meta-bug

2014-06-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=53601 Bug 53601 depends on bug 54521, which changed state. Bug 54521 Summary: nVMX: accurately emulate VMXON region https://bugzilla.kernel.org/show_bug.cgi?id=54521 What|Removed |Added

[Bug 54521] nVMX: accurately emulate VMXON region

2014-06-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=54521 Bandan Das b...@makefile.in changed: What|Removed |Added CC||b...@makefile.in ---

[Bug 77271] New: CPUID Leaf 0x40000000 return 0 in eax

2014-06-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=77271 Bug ID: 77271 Summary: CPUID Leaf 0x4000 return 0 in eax Product: Virtualization Version: unspecified Kernel Version: 3.14 Hardware: All OS: Linux Tree:

[Bug 77271] CPUID Leaf 0x40000000 return 0 in eax

2014-06-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=77271 Alex Williamson alex.william...@redhat.com changed: What|Removed |Added CC|

[Bug 77271] CPUID Leaf 0x40000000 return 0 in eax

2014-06-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=77271 --- Comment #2 from Jidong Xiao jidong.x...@gmail.com --- Oh, thanks Alex. I think you are right here, it's not a bug. But do you think that, does it make sense to submit a patch to qemu, so as to make them consistent between userspace qemu and

[Bug 77271] CPUID Leaf 0x40000000 return 0 in eax

2014-06-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=77271 --- Comment #3 from Alex Williamson alex.william...@redhat.com --- The best way to find out is to submit a patch. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line

[Bug 77271] CPUID Leaf 0x40000000 return 0 in eax

2014-06-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=77271 Jidong Xiao jidong.x...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 76331] kernel BUG at drivers/iommu/intel-iommu.c:844!

2014-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76331 --- Comment #5 from Matt mspe...@users.sourceforge.net --- Hi Alex, Great news ! Yesterday I had the opportunity to recompile my kernel with your suggested fix in intel-iommu driver : dmar_domain-gaw = min(dmar_domain-gaw, addr_width); After

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #31 from Jidong Xiao jidong.x...@gmail.com --- Hi, Paolo, I added a sti instruction in kvm-unit-tests:x86/debug.c, like this: asm volatile( pushf\n\t pop %%rax\n\t sti\n\t

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #32 from Jatin Kumar jatin.iitde...@gmail.com --- (In reply to Jidong Xiao from comment #29) Okay, I will try the sti instruction. Jatin, since your title says that there is something wrong with the sti instruction, but looking at

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #33 from Jidong Xiao jidong.x...@gmail.com --- Jatin, thanks for the clarification. Are you using kgdb to perform single step kernel code? I am still wondering how did you do the single step execution for kernel level code. -- You

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #34 from Jatin Kumar jatin.iitde...@gmail.com --- (In reply to Jidong Xiao from comment #33) Jatin, thanks for the clarification. Are you using kgdb to perform single step kernel code? I am still wondering how did you do the single

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #25 from Jidong Xiao jidong.x...@gmail.com --- (In reply to Jatin Kumar from comment #24) linux:~/code/cvedr # ./accessmsr Segmentation fault You got a seg fault because it is privileged instruction and I run it in kernel mode

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #26 from Jatin Kumar jatin.iitde...@gmail.com --- In arch/x86/kvm/vmx.c file, there is a complete list of kvm_vmx_exit_handlers, you can find there appropriate handlers for each of the exit reasons. There is a handle_io() handler. Can

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #27 from Jidong Xiao jidong.x...@gmail.com --- Jatin, after I have added printk in handle_io, it looks like the printk will be called very frequently, I don't need to run any own program in the guest OS, the printk message in

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #28 from Paolo Bonzini bonz...@gnu.org --- As Jatin said, most of the time the emulator is not invoked for instructions that require intervention of the hypervisor. Instead, the processor provides enough pre-decoded information about

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #29 from Jidong Xiao jidong.x...@gmail.com --- Okay, I will try the sti instruction. Jatin, since your title says that there is something wrong with the sti instruction, but looking at your sample code, it does not include a sti

[Bug 76331] kernel BUG at drivers/iommu/intel-iommu.c:844!

2014-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76331 Alex Williamson alex.william...@redhat.com changed: What|Removed |Added CC|

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #18 from Jidong Xiao jidong.x...@gmail.com --- Hi, Paolo, I am still reading the source code so as to understand the root cause of this problem. In particular, I added some printk statements in x86_emulate_insn(). For example, I added

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #19 from Jatin Kumar jatin.iitde...@gmail.com --- I am not sure if I am correct but `add` doesn't look like any privileged or special instruction so if running with KVM it should run directly on the hardware and without needing

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #20 from Jidong Xiao jidong.x...@gmail.com --- Thanks Jatin, I actually tried some other instructions, like accessing cr register. I use the following program: linux:~/code/cvedr # cat getcr.c #include stdio.h main(){ asm

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #21 from Jatin Kumar jatin.iitde...@gmail.com --- The way I would approach this problem is to first check if there is a VM_EXIT while executing this instruction. You should be able to find that in vmx_vcpu_run() function (I guess in

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #22 from Jidong Xiao jidong.x...@gmail.com --- Alright, I added a printk statement in the wrmsr case, like this: case 0x30: printk(KERN_ERR DEBUG: Passed %s %d \n,__FUNCTION__,__LINE__); /*

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #23 from Jidong Xiao jidong.x...@gmail.com --- Jatin, do you mean that if one instruction triggers a VM_EXIT, then it won't trigger the emulate code? So why the emulate code tries to emulate those privileged instructions, like wrmsr,

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #24 from Jatin Kumar jatin.iitde...@gmail.com --- linux:~/code/cvedr # ./accessmsr Segmentation fault You got a seg fault because it is privileged instruction and I run it in kernel mode not user mode. But you are likely to be

[Bug 76621] Bridged networking stopped working after yum update

2014-05-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 --- Comment #2 from Henrik hne.jwe...@eit.se --- It works with kernel version 3.11.10-301.fc20.x86_64. It does not work with kernel version 3.14.4-200.fc20 -- You are receiving this mail because: You are watching the assignee of the bug. -- To

[Bug 76621] Bridged networking stopped working after yum update

2014-05-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 Henrik hne.jwe...@eit.se changed: What|Removed |Added Kernel Version|Very latest with Fedora 20 |3.14.4-200.fc20 (Very

[Bug 76621] Bridged networking stopped working after yum update

2014-05-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 --- Comment #3 from Henrik hne.jwe...@eit.se --- I have updated header with kernel version. Will see if I can report it to Fedora then. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this

[Bug 76621] Bridged networking stopped working after yum update

2014-05-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 Henrik hne.jwe...@eit.se changed: What|Removed |Added Kernel Version|3.14.4-200.fc20 (Very |3.14.4-200.fc20

[Bug 76621] Bridged networking stopped working after yum update

2014-05-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 Henrik hne.jwe...@eit.se changed: What|Removed |Added Regression|No |Yes -- You are receiving this

[Bug 76621] Bridged networking stopped working after yum update

2014-05-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 --- Comment #4 from Henrik hne.jwe...@eit.se --- I have nw reported this at fedora insted. https://bugzilla.redhat.com/show_bug.cgi?id=1100228 -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe

[Bug 76621] Bridged networking stopped working after yum update

2014-05-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 --- Comment #5 from Henrik hne.jwe...@eit.se --- It still works with 3.14.3-200.fc20.x86_64 if that was of any interest. Will now close this report. -- You are receiving this mail because: You are watching the assignee of the bug. -- To

[Bug 76621] Bridged networking stopped working after yum update

2014-05-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 Henrik hne.jwe...@eit.se changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 76331] kernel BUG at drivers/iommu/intel-iommu.c:844!

2014-05-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76331 --- Comment #3 from Matt mspe...@users.sourceforge.net --- Hi Alex, Any news ? Do you need additional info ? I keep receiving the bug each time I power off the VM (VM is working perfectly fine before the shutdown with both sound and gpu

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #7 from Paolo Bonzini bonz...@gnu.org --- Hi Jidong, no this is not fixed yet. Basically OUT instructions are emulated by KVM, and support for single-stepping and breakpoints in the emulator is quite minimal. 3.12 added some support

[Bug 76621] New: Bridged networking stopped working after yum update

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 Bug ID: 76621 Summary: Bridged networking stopped working after yum update Product: Virtualization Version: unspecified Kernel Version: Very latest with Fedora 20 yum update 2014-05-21

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #8 from Jidong Xiao jidong.x...@gmail.com --- Hi, Jatin, from inside the OS means from within the Guest OS right? (In reply to Jatin Kumar from comment #5) -- You are receiving this mail because: You are watching the assignee of the

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #9 from Jidong Xiao jidong.x...@gmail.com --- Hi, Paolo, It seems that Gleb's patch commit 03617c188f41eeeb4223c919ee7e66e5a114f2c6 KVM: VMX: mark unusable segment as nonpresent fixed a similar problem like this, look at this:

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #10 from Paolo Bonzini bonz...@gnu.org --- No, hardware error 0x8021 includes pretty much everything that could go wrong in vmx.c. :) -- You are receiving this mail because: You are watching the assignee of the bug. -- To

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #11 from Jidong Xiao jidong.x...@gmail.com --- Hi, Paolo, thanks for your explanation. I am interested in fixing this. So what's the technical challenge here? When you say support for single-stepping and breakpoints in the emulator is

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #12 from Paolo Bonzini bonz...@gnu.org --- Hi, Paolo, thanks for your explanation. I am interested in fixing this. So what's the technical challenge here? The first step is to reproduce the failure. To do this you can make a patch

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #13 from Jidong Xiao jidong.x...@gmail.com --- Great, I will try. Yes I have the inter manual and I have studied it for a while, so basically I know the data structure of VMCS. To reproduce the failure, so, if I use gdb in a guest OS,

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #14 from Jatin Kumar jatin.iitde...@gmail.com --- (In reply to Jidong Xiao from comment #8) Hi, Jatin, from inside the OS means from within the Guest OS right? (In reply to Jatin Kumar from comment #5) Hello Jidong, Yes it means

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #15 from Paolo Bonzini bonz...@gnu.org --- if I use gdb in a guest OS, like to debug a program inside the Guest OS, and run the single step command in gdb, that should trigger this bug right Yes. For kvm-unit-tests you would

[Bug 76621] Bridged networking stopped working after yum update

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76621 Michael Tokarev m...@tls.msk.ru changed: What|Removed |Added CC||m...@tls.msk.ru ---

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #16 from Jidong Xiao jidong.x...@gmail.com --- Alright, thank you Paolo, I will try and let you know once I am done.(In reply to Paolo Bonzini from comment #15) -- You are receiving this mail because: You are watching the assignee of

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #17 from Jidong Xiao jidong.x...@gmail.com --- Hi,Paolo, I am not familiar with kvm-unit-tests, and I cannot find any documents describe it. So I use gdb to debug. And yes I can reproduce the problem. I just use Jatin's sample code

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #2 from Jatin Kumar jatin.iitde...@gmail.com --- Hello Jidong, thanks for the info. I will try and let you know. While you are at this, can you please help me another single stepping issue and the issue is: 1. While single stepping,

[Bug 45931] Nested Virt: VMX can't be initialized in L1 Xen (Xen on KVM)

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=45931 Zhou, Chao chao.z...@intel.com changed: What|Removed |Added CC||chao.z...@intel.com ---

[Bug 75981] [Nested kvm on kvm]L2 guest reboot continuously when create a rhel6u5(64bit) as L2 guest.

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75981 --- Comment #4 from Zhou, Chao chao.z...@intel.com --- kvm.git + qemu.git: d9f89b88_e5bfd640 host kernel:3.15.0_rc1 test on Romley_EP, create a 64bit rhel6u5 guest as L2 guest, the L2 guest boots up fine. -- You are receiving this mail because:

[Bug 75981] [Nested kvm on kvm]L2 guest reboot continuously when create a rhel6u5(64bit) as L2 guest.

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75981 Zhou, Chao chao.z...@intel.com changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 75981] [Nested kvm on kvm]L2 guest reboot continuously when create a rhel6u5(64bit) as L2 guest.

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75981 --- Comment #5 from Zhou, Chao chao.z...@intel.com --- this commit fixed the bug: commit d9f89b88f5102ce235b75a5907838e3c7ed84b97 Author: Jan Kiszka jan.kis...@siemens.com Date: Sat May 10 09:24:34 2014 +0200 KVM: x86: Fix CR3 reserved bits

[Bug 75981] [Nested kvm on kvm]L2 guest reboot continuously when create a rhel6u5(64bit) as L2 guest.

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75981 Zhou, Chao chao.z...@intel.com changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are

[Bug 53601] nVMX meta-bug

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=53601 Bug 53601 depends on bug 45931, which changed state. Bug 45931 Summary: Nested Virt: VMX can't be initialized in L1 Xen (Xen on KVM) https://bugzilla.kernel.org/show_bug.cgi?id=45931 What|Removed |Added

[Bug 45931] Nested Virt: VMX can't be initialized in L1 Xen (Xen on KVM)

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=45931 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added CC||bonz...@gnu.org ---

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #4 from Jidong Xiao jidong.x...@gmail.com --- Jatin, are you using gdb to do the single step?(In reply to Jatin Kumar from comment #2) -- You are receiving this mail because: You are watching the assignee of the bug. -- To

[Bug 30402] Debian 4 fails to boot in KVM

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=30402 Jidong Xiao jidong.x...@gmail.com changed: What|Removed |Added CC||jidong.x...@gmail.com

[Bug 30402] Debian 4 fails to boot in KVM

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=30402 --- Comment #3 from Joerg Roedel j...@8bytes.org --- (In reply to Jidong Xiao from comment #2) Joerg, how do you know this? Some investigation showed that this kernel uses MMX instructions to access MMIO regions. These instructions are not

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #5 from Jatin Kumar jatin.iitde...@gmail.com --- @Paolo: Thanks for the info. That makes sense to me. (In reply to Jidong Xiao from comment #4) Jatin, are you using gdb to do the single step?(In reply to Jatin Kumar from comment #2)

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 --- Comment #6 from Jatin Kumar jatin.iitde...@gmail.com --- (In reply to Jatin Kumar from comment #5) whenever I hit an out instruction, the very next instruction is not skipped Sorry I meant 'is skipped'. -- You are receiving this mail

[Bug 53191] hardware error 0x80000021 on a KVM virtual machine with kernel 3.7

2014-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=53191 Jidong Xiao jidong.x...@gmail.com changed: What|Removed |Added CC||jidong.x...@gmail.com

[Bug 65561] KVM:Entry failed on Single stepping sti instruction

2014-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65561 Jidong Xiao jidong.x...@gmail.com changed: What|Removed |Added CC||jidong.x...@gmail.com

[Bug 76331] New: kernel BUG at drivers/iommu/intel-iommu.c:844!

2014-05-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76331 Bug ID: 76331 Summary: kernel BUG at drivers/iommu/intel-iommu.c:844! Product: Virtualization Version: unspecified Kernel Version: 3.14.4 Hardware: x86-64 OS: Linux

[Bug 76331] kernel BUG at drivers/iommu/intel-iommu.c:844!

2014-05-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76331 Alex Williamson alex.william...@redhat.com changed: What|Removed |Added CC|

[Bug 76331] kernel BUG at drivers/iommu/intel-iommu.c:844!

2014-05-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76331 --- Comment #2 from Matt mspe...@users.sourceforge.net --- Hi Alex, # dmesg | grep ecap [0.057396] dmar: IOMMU 0: reg_base_addr fbfff000 ver 1:0 cap c9008010e60262 ecap f020fa [0.057403] dmar: IOMMU 1: reg_base_addr fbffe000 ver 1:0 cap

[Bug 76191] vt-d intel IOMMU - jump label: negative count!

2014-05-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76191 Julian d...@psyrium.com.au changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 76141] New: kvm intel nested virtualization get PANIC: double fault, error_code: 0x0

2014-05-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76141 Bug ID: 76141 Summary: kvm intel nested virtualization get PANIC: double fault, error_code: 0x0 Product: Virtualization Version: unspecified Kernel Version: 3.12.18

[Bug 76141] kvm intel nested virtualization get PANIC: double fault, error_code: 0x0

2014-05-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76141 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added CC||bonz...@gnu.org ---

[Bug 76191] New: vt-d intel IOMMU - jump label: negative count!

2014-05-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=76191 Bug ID: 76191 Summary: vt-d intel IOMMU - jump label: negative count! Product: Virtualization Version: unspecified Kernel Version: Linux venus 3.12-1-amd64 #1 SMP Debian 3.12.9-1

[Bug 75981] [Nested kvm on kvm]L2 guest reboot continuously when create a rhel6u5(64bit) as L2 guest.

2014-05-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75981 Jan Kiszka jan.kis...@web.de changed: What|Removed |Added CC||jan.kis...@web.de ---

[Bug 75981] [Nested kvm on kvm]L2 guest reboot continuously when create a rhel6u5(64bit) as L2 guest.

2014-05-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75981 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added CC||bonz...@gnu.org ---

[Bug 75981] New: [Nested kvm on kvm]L2 guest reboot continuously when create a rhel6u5(64bit) as L2 guest.

2014-05-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75981 Bug ID: 75981 Summary: [Nested kvm on kvm]L2 guest reboot continuously when create a rhel6u5(64bit) as L2 guest. Product: Virtualization Version: unspecified Kernel Version:

[Bug 75981] [Nested kvm on kvm]L2 guest reboot continuously when create a rhel6u5(64bit) as L2 guest.

2014-05-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75981 --- Comment #1 from Zhou, Chao chao.z...@intel.com --- the first bad commit is: commit 346874c9507a2582d0c00021f848de6e115f276c Author: Nadav Amit na...@cs.technion.ac.il Date: Fri Apr 18 03:35:09 2014 +0300 KVM: x86: Fix CR3 reserved bits

[Bug 73721] KVM hv-time

2014-05-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=73721 --- Comment #4 from Marcus Schmidt anickn...@gmail.com --- Thanks, now everything works good. -- 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

[Bug 73721] KVM hv-time

2014-05-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=73721 Paolo Bonzini bonz...@gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 75331] soft lockup CPU#0 stuck for 23s regression on 32bit 3.13.0+ kernels.

2014-05-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75331 --- Comment #1 from Ivan Kalvachev i...@yahoo.com --- I tried to isolate the difference in .o object files when compiling the kernel with and without the above commit. Unfortunately there were no differences (only in version, boot and init code).

[Bug 75331] New: soft lockup CPU#0 stuck for 23s regression on 32bit 3.13.0+ kernels.

2014-05-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75331 Bug ID: 75331 Summary: soft lockup CPU#0 stuck for 23s regression on 32bit 3.13.0+ kernels. Product: Virtualization Version: unspecified Kernel Version: 3.13.0+

[Bug 75331] soft lockup CPU#0 stuck for 23s regression on 32bit 3.13.0+ kernels.

2014-05-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=75331 Ivan Kalvachev i...@yahoo.com changed: What|Removed |Added CC||i...@yahoo.com

[Bug 74251] Assign I350 NIC VF and Intel 82599 NIC VF to win7/win8 32bit guest, the interface cannot get IP

2014-04-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=74251 robert...@intel.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 65081] Starting a second guest with -smp 2 makes the first guest very slow and the second one hang (or also very slow)

2014-04-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65081 --- Comment #2 from Daniel Haid d.h...@gogi.tv --- The problem persists with linux 3.14.1 and qemu 1.7.1. Any suggestions on which further information you need is very welcome. -- You are receiving this mail because: You are watching the

[Bug 65081] Starting a second guest with -smp 2 makes the first guest very slow and the second one hang (or also very slow)

2014-04-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65081 --- Comment #3 from Daniel Haid d.h...@gogi.tv --- I removed all unnecessary arguments. The following command line is actually sufficient to produce hanging guests: qemu-system-x86_64 -enable-kvm -kernel vmlinuz-linux -initrd initramfs-linux.img

[Bug 65081] Starting a second guest with -smp 2 makes the first guest very slow and the second one hang (or also very slow)

2014-04-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=65081 Daniel Haid d.h...@gogi.tv changed: What|Removed |Added Kernel Version|3.12|3.14 --- Comment #4 from

[Bug 74251] New: Assign I350 NIC VF and Intel 82599 NIC VF to win7/win8 32bit guest, the interface cannot get IP

2014-04-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=74251 Bug ID: 74251 Summary: Assign I350 NIC VF and Intel 82599 NIC VF to win7/win8 32bit guest, the interface cannot get IP Product: Virtualization Version: unspecified Kernel

[Bug 73331] Nested Virtualization, L2 cannot boot up on Ivybridge and Haswell

2014-04-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=73331 Shesha shes...@gmail.com changed: What|Removed |Added CC||shes...@gmail.com --- Comment

[Bug 73721] KVM hv-time

2014-04-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=73721 --- Comment #1 from flyse...@gmx.de --- I can confirm the problem. It happens on my gentoo system as well. Let me know, if you want me to create debug logs or similar. -- You are receiving this mail because: You are watching the assignee of the

<    1   2   3   4   5   6   7   8   9   10   >