Re: kernel BUG at arch/x86/kvm/x86.c:361! on AMD CPU

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jun 12, 2019 at 02:45:34PM -0400, George Kennedy wrote:
> The crash can still be reproduced with VM running Upstream 5.2.0-rc4 

That's clear.

> and host running Ubuntu on AMD CPU.

That's the important question: why can't I trigger it with 5.2.0-rc4+ as
the host and you can with the ubuntu kernel 4.15 or so. I.e., what changed
upstream or does the ubuntu kernel have out-of-tree stuff?

Maybe kvm folks would have a better idea. That kvm_spurious_fault thing
is for:

/*
 * Hardware virtualization extension instructions may fault if a
 * reboot turns off virtualization while processes are running.
 * Trap the fault and ignore the instruction if that happens.
 */
asmlinkage void kvm_spurious_fault(void);

but you're not rebooting...

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux