public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
	Wenhao Xu <xuwenhao2008@gmail.com>,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [questions] savevm|loadvm
Date: Thu, 1 Apr 2010 12:20:09 +0000	[thread overview]
Message-ID: <201004011320.10119.paul@codesourcery.com> (raw)
In-Reply-To: <m3k4ss682t.fsf@trasno.mitica>

> Wenhao Xu <xuwenhao2008@gmail.com> wrote:
> > Hi, Juan,
> >    I am fresh to both QEMU and KVM. But so far, I notice that QEMU
> > uses "KVM_SET_USER_MEMORY_REGION" to set memory region that KVM can
> > use and uses cpu_register_physical_memory_offset to register the same
> > memory to QEMU emulator, which means QEMU and KVM use the same host
> > virtual memory. And therefore the memory KVM modified could be
> > directly reflected to QEMU. I don't quite understand the different
> > memory layout problem between the two. So I don't know exactly what
> > you mean to "fix" it?
> 
> 1st. qemu-kvm.git and qemu.git memory layouts are different, indeed with
> qemu.git kvm mode. (yes it is complex and weird).
> 
> kvm vs qemu initialization is different.  Expecting to stop kvm, and run
> tcg from there is not going to work.  I guess it would need a lot of
> changes, but I haven't looked at it myself.

FWIW I think this really *should* work, and any failure to do so is definitely 
a bug.

Paul

      parent reply	other threads:[~2010-04-01 12:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30  5:59 [questions] savevm|loadvm Wenhao Xu
2010-03-30  8:22 ` Juan Quintela
2010-03-30 17:03   ` Wenhao Xu
2010-03-31 11:31     ` Juan Quintela
2010-04-01  8:42       ` Avi Kivity
2010-04-01 19:35         ` Wenhao Xu
2010-04-07  5:56           ` Avi Kivity
2010-04-01 12:20       ` Paul Brook [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=201004011320.10119.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=xuwenhao2008@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