Re: Kernel oops in host caused by mmaping RAM

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

 



On Wed, Apr 13, 2011 at 12:09 AM, Jan Kiszka <jan.kiszka@xxxxxx> wrote:
> On 2011-04-12 21:41, Sasha Levin wrote:
>> Hello,
>>
>> I've tried using mmap to map the RAM of a guest instead of
>> posix_memalign which is used both in the kvm tool and qemu.
>>
>> Doing so caused a kernel Oops, which happens every time I run the code
>> and was confirmed both on 2.6.38 and the latest git build of 2.6.39.
>>
>
> Can you share the test case that triggers it? That's easier than
> guessing what you did precisely.

It's the native Linux kvm tool patched to use mmap() instead of
posix_memalign(). Sasha, maybe you should post your patch so other
people can try to reproduce the problem?
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[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