qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Binun <binun@cs.bgu.ac.il>,
	Stefan Hajnoczi <stefanha@gmail.com>
Cc: kahilm@post.bgu.ac.il, boaz.menuhin@gmail.com,
	markbl@post.bgu.ac.il, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kill /destroy a VM - help
Date: Thu, 06 Mar 2014 12:28:34 +0100	[thread overview]
Message-ID: <53185BE2.4080101@redhat.com> (raw)
In-Reply-To: <201403061031.s26AVWJL012337@indigo.cs.bgu.ac.il>

Il 06/03/2014 11:31, Alexander Binun ha scritto:
> Then - more questions :
>    1. How can I access the Qemu process (relevant to a given VM) from within in the kernel context (being in a kernel module) ?

The struct pid for the VCPU is in the "pid" field of struct kvm_vcpu.

 From there if needed you can get the task (with pid_task) and the 
task's thread group leader (the task's group_leader), and send a signal 
to it.

>    2. Should I uninitialize some internal structures for the VM being killed ?

No, it will happen automatically.  When QEMU is terminated, the VM's 
file descriptor is closed and this frees all internal structures.

>    3. My module detects malicious activities at a VCPU. How can one get the VM owning this VCPU ?

Field "kvm" in struct kvm_vcpu points to the struct kvm for the VM.

Paolo

  reply	other threads:[~2014-03-06 11:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 14:47 [Qemu-devel] sniffing traffic between VMs Alexander Binun
2013-10-10  9:02 ` Stefan Hajnoczi
2013-10-10 11:00   ` [Qemu-devel] kvm binary is deprecated Alexander Binun
2013-10-11  9:05     ` Stefan Hajnoczi
2013-10-12 14:45       ` Alexander Binun
2013-10-14  9:12         ` Stefan Hajnoczi
2013-10-14 10:36           ` Alexander Binun
2013-10-14 14:16             ` Stefan Hajnoczi
2013-10-24  9:23               ` [Qemu-devel] kvm binary is deprecated - solved! Alexander Binun
2013-10-24  9:49                 ` Stefan Hajnoczi
2013-10-24  9:54                   ` [Qemu-devel] observing VM actions Alexander Binun
2013-12-18 11:53           ` [Qemu-devel] sniffing traffic between virtual machines Alexander Binun
2013-12-19  9:05             ` Stefan Hajnoczi
2014-03-05 16:35               ` [Qemu-devel] kill /destroy a VM - help Alexander Binun
2014-03-06 10:22                 ` Stefan Hajnoczi
2014-03-06 10:31                   ` Alexander Binun
2014-03-06 11:28                     ` Paolo Bonzini [this message]
2014-03-06 15:54                       ` [Qemu-devel] kill /destroy a VM - still hangs! Alexander Binun
2014-03-09 15:40                       ` [Qemu-devel] trying to kill a VM Alexander Binun
2014-03-13 12:59                       ` [Qemu-devel] different IDTs of the same VCPU Alexander Binun
2014-03-13 15:15                         ` Paolo Bonzini
2014-03-17 11:54                           ` Alexander Binun
2014-03-17 12:20                             ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53185BE2.4080101@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=binun@cs.bgu.ac.il \
    --cc=boaz.menuhin@gmail.com \
    --cc=kahilm@post.bgu.ac.il \
    --cc=markbl@post.bgu.ac.il \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).