From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Is that possible to virtualize a kernel module? Date: Tue, 27 Dec 2011 12:02:39 +0200 Message-ID: <4EF997BF.9030601@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org To: =?UTF-8?B?5ZC06ZSQ?= <19890121wr@gmail.com> Return-path: Received: from mx1.redhat.com ([209.132.183.28]:6186 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752550Ab1L0KCm (ORCPT ); Tue, 27 Dec 2011 05:02:42 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 12/27/2011 11:58 AM, =E5=90=B4=E9=94=90 wrote: > Hi, > > I am currently do a project to detect malicious module. And I want to > use KVM, namely, using virtualization to achieve this? > Is that possible to virtualize a kernel module without a virtualized = Linux? > For example, if I only want to virtualize a network device, the > network device still runs inside the kernel memory address space > without changing anything else. > The only difference is that the network device will run on VMX > non-root mode, while the kernel still run on VMX root mode. > What would be the point? the "virtualized" module can corrupt the non-virtualized kernel's memory. It may be technically possible (using vmx, but not kvm), but it's a lot of work. --=20 error compiling committee.c: too many arguments to function