All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jun Koi <junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Map VM's memory?
Date: Tue, 28 Nov 2006 16:07:09 +0200	[thread overview]
Message-ID: <456C428D.3030408@qumranet.com> (raw)
In-Reply-To: <fdaac4d50611280553x3a0dfcadyd32d17898ad561b4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Jun Koi wrote:
> Hi,
>
> Could anybody tell me how to map memory of VMs in KVM (mapping done
> from hypervisor)?
> I am reading the source, but still cannot figure it out.
>
>   

In the kernel, see struct kvm->memslots[x].phys_mem[y].  You need to 
kmap()/kunmap() it before use.

In userspace, just mmap() /dev/kvm, the file offset is the physical 
memory address.


> Another question: can KVM provide strong isolation between VMs? That
> means if there is a security bug in a VM kernel, can it affect other
> VMs? (It seems not to me, could anybody confirm this?)
>
>   

Barring any bugs, kvm fully isolates guests.  Guest kernel activity 
(malicious or erronous) should not affect other guests except through 
defined interfaces (e.g. networking).

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      parent reply	other threads:[~2006-11-28 14:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 13:53 Map VM's memory? Jun Koi
     [not found] ` <fdaac4d50611280553x3a0dfcadyd32d17898ad561b4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-11-28 14:07   ` Avi Kivity [this message]

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=456C428D.3030408@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.