search for: tarral

From: Mathieu Tarral <mathieu.tarral at protonmail.com> This function is used by KVMI (KVM introspection sub-system) to ungracefully shutdown the guest when an introspection tool requests it. A security application will use it as a last resort in stopping the spread of a malware from a guest Signed-off-by: Mat...

From: Mathieu Tarral <mathieu.tarral at protonmail.com> This function is used by VM introspection code to ungracefully shutdown a guest at the request of the introspection tool. A security application will use this as the last resort to stop the spread of a malware from a guest. Signed-off-by: Mathieu Tarral &...

...alization failed So there are 2 things here: - why libvirt is unable to configure Libxl ? where should i look for any clues ? - "Initialization of LIBXL state driver failed: no error" it looks like a bug in Libvirt, if it fails, an error message should be reported Thank you. -- Mathieu Tarral Sent with ProtonMail Secure Email.

Le lundi 28 septembre 2020 19:04, Jim Fehlig <jfehlig@suse.com> a écrit : > On 9/28/20 5:21 AM, Mathieu Tarral wrote: > > > Hi, > > I'm facing an issue with libvirt and the LIBXL driver, failing when searching for DMI data in /sys. > > info : libvirt version: 5.0.0, package: 4+deb10u1 (Guido Günther agx@sigxcpu.org Thu, 05 Dec 2019 00:22:14 +0100) > > error : udevGetDMIData:17...

...4e54 in iw_add_doc (iw=0x1dfaa00, doc=0x99f5e0) at index.c:5968 #11 0xfdf34990 in frt_iw_add_doc (self=27175152, rdoc=27184872) at r_index.c:1541 Kinda wonder if this is a 64-bit issue though I haven''t made any attempt to compile these in 64-bit mode... -- -Robert Tarrall.- Unix System/Network Admin E.Central/Neighborhood Link

Hi, I'm facing an issue with libvirt and the LIBXL driver, failing when searching for DMI data in /sys. info : libvirt version: 5.0.0, package: 4+deb10u1 (Guido Günther <agx@sigxcpu.org> Thu, 05 Dec 2019 00:22:14 +0100) error : udevGetDMIData:1719 : internal error: Failed to get udev device for syspath '/sys/devices/virtual/dmi/id' or '/sys/class/dmi/id' error :

...ice name. For Dev_or_Path parameters much the same, except we can also use the is_device_parameter function elsewhere in the daemon to distinguish if we were called with a device or path parameter. Previously we used a simple test if the path begins with "/dev/...". Reported by Mathieu Tarral. --- daemon/daemon.h | 1 + daemon/dd.c | 8 +++--- daemon/ext2.c | 4 +-- daemon/file.ml | 2 +- daemon/mount.c | 2 +- daemon/stubs-macros.h | 11 ++------ daemon/upload.c | 6 ++-- daemon/utils-c.c | 7 +++++ daemon/utils.c | 78 +++...

...ROL_CLEANUP KVM: introspection: add KVMI_VCPU_GET_XCR KVM: introspection: add KVMI_VCPU_SET_XSAVE KVM: introspection: extend KVMI_GET_VERSION with struct kvmi_features KVM: introspection: add KVMI_VCPU_TRANSLATE_GVA Marian Rotariu (1): KVM: introspection: add KVMI_VCPU_GET_CPUID Mathieu Tarral (1): signal: export kill_pid_info() Mihai Don?u (35): KVM: x86: add kvm_arch_vcpu_get_regs() and kvm_arch_vcpu_get_sregs() KVM: x86: avoid injecting #PF when emulate the VMCALL instruction KVM: x86: add .control_msr_intercept() KVM: x86: vmx: use a symbolic constant when checking the exi...

...pected vCPU KVM: introspection: add KVMI_VCPU_PAUSE KVM: introspection: add KVMI_EVENT_PAUSE_VCPU KVM: introspection: extend KVMI_GET_VERSION with struct kvmi_features KVM: introspection: add KVMI_VCPU_TRANSLATE_GVA Marian Rotariu (1): KVM: introspection: add KVMI_VCPU_GET_CPUID Mathieu Tarral (1): export kill_pid_info() Mihai Don?u (34): KVM: x86: add kvm_arch_vcpu_get_regs() and kvm_arch_vcpu_get_sregs() KVM: x86: avoid injecting #PF when emulate the VMCALL instruction KVM: x86: add .control_msr_intercept() KVM: x86: vmx: use a symbolic constant when checking the exit qu...

https://bugzilla.redhat.com/show_bug.cgi?id=1477623 The first two patches are cleanups. The third patch changes the way that we handle Device and Dev_or_Path parameters so that a parameter marked as such can really only contain a block device name (and not, for instance, a chardev). Using a chardev here caused hangs in the API. The next two patches fix API usage to conform to this new stricter

...for minimum overhead. This patch series is based on 5.0-rc7, commit de3ccd26fafc ("KVM: MMU: record maximum physical address width in kvm_mmu_extended_role"). The previous RFC (v5) can be read here: https://www.spinics.net/lists/kvm/msg179441.html Thanks to Samuel Laur?n and Mathieu Tarral, the previous version has been integrated and tested with libVMI. KVM-VMI: https://github.com/KVM-VMI/kvm-vmi Kernel: https://github.com/KVM-VMI/kvm/tree/kvmi QEMU: https://github.com/KVM-VMI/qemu/tree/kvmi (not all patches, but enough to work) libVMI: https://github.com/KVM-VMI...

...for minimum overhead. This patch series is based on 5.0-rc7, commit de3ccd26fafc ("KVM: MMU: record maximum physical address width in kvm_mmu_extended_role"). The previous RFC (v5) can be read here: https://www.spinics.net/lists/kvm/msg179441.html Thanks to Samuel Laur?n and Mathieu Tarral, the previous version has been integrated and tested with libVMI. KVM-VMI: https://github.com/KVM-VMI/kvm-vmi Kernel: https://github.com/KVM-VMI/kvm/tree/kvmi QEMU: https://github.com/KVM-VMI/qemu/tree/kvmi (not all patches, but enough to work) libVMI: https://github.com/KVM-VMI...