similar to: Kvm Libvirt dirty page log facility

The host needs to zap its shadow entries before performing an inflate operation to avoid the guest from using stale ones. So add an ioctl to interface with kvm_mmu_zap_all(). Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> Index: kvm.quilt/arch/x86/kvm/x86.c =================================================================== --- kvm.quilt.orig/arch/x86/kvm/x86.c +++

This patch introduces a hypercall implemented for X86 that can assist against subset of kernel rootkits, it works by place readonly protection in shadow PTE. The end result protection is also kept in a bitmap for each kvm_memory_slot and is used as reference when updating SPTEs. The whole goal is to protect the guest kernel static data from modification if attacker is running from guest ring 0,

This patch introduces a hypercall implemented for X86 that can assist against subset of kernel rootkits, it works by place readonly protection in shadow PTE. The end result protection is also kept in a bitmap for each kvm_memory_slot and is used as reference when updating SPTEs. The whole goal is to protect the guest kernel static data from modification if attacker is running from guest ring 0,

From: Carsten Otte <cotte at de.ibm.com> This patch adds Documentation/s390/kvm.txt, which describes specifics of kvm's user interface that are unique to s390 architecture. Signed-off-by: Carsten Otte <cotte at de.ibm.com> --- Documentation/s390/kvm.txt | 125 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 125 insertions(+) Index: kvm/Documentation/s390/kvm.txt

From: Carsten Otte <cotte at de.ibm.com> This patch adds Documentation/s390/kvm.txt, which describes specifics of kvm's user interface that are unique to s390 architecture. Signed-off-by: Carsten Otte <cotte at de.ibm.com> --- Documentation/s390/kvm.txt | 125 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 125 insertions(+) Index: kvm/Documentation/s390/kvm.txt

From: ?tefan ?icleru <ssicleru at bitdefender.com> This function is needed for the KVMI_VM_GET_MAX_GFN command. Signed-off-by: ?tefan ?icleru <ssicleru at bitdefender.com> Signed-off-by: Adalbert Laz?r <alazar at bitdefender.com> --- include/linux/kvm_host.h | 1 + virt/kvm/kvm_main.c | 24 ++++++++++++++++++++++++ 2 files changed, 25 insertions(+) diff --git

Here is change log from V3 To V4: - Fixing spelling/grammar mistakes suggested by Randy Dunlap - Changing the hypercall interface to be able to process multiple pages per one hypercall also suggested by Randy Dunlap. It turns out that this will save lots of vmexist/memory slot flushes when protecting many pages. [PATCH RFC V4 1/3] KVM: X86: Memory ROE documentation [PATCH RFC V4 2/3] KVM:

Kashyap Chamarthy <kchamart@redhat.com> schreef op 19 januari 2015 19:00:23 CET: >[Dropping libvir list and adding libvir-users list.] > >On Mon, Jan 19, 2015 at 04:12:46PM +0100, liedekef@telenet.be wrote: >> Hi all, >> >> I had libvirt 1.2.10 running without issues together with the qemu >package >> qemu-kvm-0.12.1.2-2.415.el6_5.14.x86_64.rpm >

On 2018/12/13 ??10:31, Michael S. Tsirkin wrote: >> Just to make sure I understand this. It looks to me we should: >> >> - allow passing GIOVA->GPA through UAPI >> >> - cache GIOVA->GPA somewhere but still use GIOVA->HVA in device IOTLB for >> performance >> >> Is this what you suggest? >> >> Thanks > Not really. We already

On 2018/12/14 ??9:20, Michael S. Tsirkin wrote: > On Fri, Dec 14, 2018 at 10:43:03AM +0800, Jason Wang wrote: >> On 2018/12/13 ??10:31, Michael S. Tsirkin wrote: >>>> Just to make sure I understand this. It looks to me we should: >>>> >>>> - allow passing GIOVA->GPA through UAPI >>>> >>>> - cache GIOVA->GPA somewhere but

On Mon, May 06, 2019 at 10:23:29PM -0400, Jason Wang wrote: > Note: there're archs (few non popular ones) that don't implement > futex helper, we can't log dirty pages. We can fix them on top or > simply disable LOG_ALL features of vhost. That means vhost now has to depend on HAVE_FUTEX_CMPXCHG to make sure we have a working implementation. > #include

On 2019/5/10 ??10:59, Jason Wang wrote: >>> >>> ? ????? r = get_user_pages_fast(log, 1, 1, &page); >> OK so the trick is that page is pinned so you don't expect >> arch_futex_atomic_op_inuser below to fail.? get_user_pages_fast >> guarantees page is not going away but does it guarantee PTE won't be >> invaidated or write protected? > >

From: Jason Wang <jasowang at redhat.com> Date: Mon, 13 May 2019 01:27:45 -0400 > Vhost log dirty pages directly to a userspace bitmap through GUP and > kmap_atomic() since kernel doesn't have a set_bit_to_user() > helper. This will cause issues for the arch that has virtually tagged > caches. The way to fix is to keep using userspace virtual > address. Fortunately, futex

On 2018/12/25 ??1:41, Michael S. Tsirkin wrote: > On Mon, Dec 24, 2018 at 11:43:31AM +0800, Jason Wang wrote: >> On 2018/12/14 ??9:20, Michael S. Tsirkin wrote: >>> On Fri, Dec 14, 2018 at 10:43:03AM +0800, Jason Wang wrote: >>>> On 2018/12/13 ??10:31, Michael S. Tsirkin wrote: >>>>>> Just to make sure I understand this. It looks to me we should:

Hi All, I have several questions about log dirty mode during live migration. For my understanding, each time after XEN_DOMCTL_SHADOW_OP_CLEAN or XEN_DOMCTL_SHADOW_OP_PEEK operation, all the pages are set as read only. The following memory accesses to the memory pages will cause page fault (permission conflict) then using page_mark_dirty function to set the dirty bitmap. However, after I read

Hi, I currently have a couple of Debian KVM servers with all a different version of kvm or qemu-kvm. I can live migrate a guest OS from one server to the other just fine, as long as the version of qemu-kvm is the same. However, when I try to migrate a guest to a server running a newer (or older) version of qemu-kvm, I run into problems. I think this is because the xml configuration differs

On Mon, May 06, 2019 at 10:23:29PM -0400, Jason Wang wrote: > Vhost log dirty pages directly to a userspace bitmap through GUP and > kmap_atomic() since kernel doesn't have a set_bit_to_user() > helper. This will cause issues for the arch that has virtually tagged > caches. The way to fix is to keep using userspace virtual address. > > Fortunately, futex has a cmpxchg to

On Mon, May 13, 2019 at 01:27:45AM -0400, Jason Wang wrote: > Vhost log dirty pages directly to a userspace bitmap through GUP and > kmap_atomic() since kernel doesn't have a set_bit_to_user() > helper. This will cause issues for the arch that has virtually tagged > caches. The way to fix is to keep using userspace virtual > address. Fortunately, futex has

On Thu, May 09, 2019 at 08:58:00AM -0400, Jason Wang wrote: > Vhost log dirty pages directly to a userspace bitmap through GUP and > kmap_atomic() since kernel doesn't have a set_bit_to_user() > helper. This will cause issues for the arch that has virtually tagged > caches. The way to fix is to keep using userspace virtual > address. Fortunately, futex has

List, http://www.redhat.com/archives/libvirt-users/2010-January/msg00012.html As in the above post, I wondered why the Qemu Monitor is not available when using kvm with libvirt. With the amount of features that are already exposed in Qemu, it might be easier to run qemu-kvm commands manually/script and forget libvirt in order to not lose this ability. -- Mark