From: Gleb Natapov <gleb@redhat.com>
To: Jim MacArthur <jim@mode7.co.uk>
Cc: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Subject: Re: Starting a VM using /dev/kvm
Date: Fri, 22 Nov 2013 08:56:49 +0200 [thread overview]
Message-ID: <20131122065649.GA13898@redhat.com> (raw)
In-Reply-To: <CAMGYSmH72-9bJhTLqtUfEuqCD2kCVoyb0T+ioZ-MVUmqMn9Wvw@mail.gmail.com>
On Thu, Nov 21, 2013 at 11:57:46PM +0000, Jim MacArthur wrote:
> On 21 November 2013 07:27, Gleb Natapov <gleb@redhat.com> wrote:
> > On Thu, Nov 21, 2013 at 12:39:49AM +0000, Jim MacArthur wrote:
> >> After reading this I added a call to KVM_GET_SREGS. Everything you say
> >> here matches my experience except that CS.base=0xf0000.
> >> So I adjusted my memory to cover physical address 0xFFFF0, and now
> >> it's happily running instructions (NOPs, at least.)
> >> I'm a bit puzzled that it didn't start with CS.base=0xffff0000, but it
> >> doesn't matter, I've done what I wanted to do for now.
> >>
> > What is your kernel version?
>
> This is on a Mac mini: Linux version 3.2.0-56-generic
> (buildd@roseapple) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) )
> #86-Ubuntu SMP Wed Oct 23 09:20:45 UTC 2013
>
> I get the same results from 3.2.0-4-amd64 on my thinkpad.
>
> The code I'm running is at http://pastebin.com/Z1SR5Vid.
>
> It's likely to be because I'm doing something wrong, and I've got what
> I wanted working anyway. Thanks again for your help.
No, this is because old kernels started in incorrect state, on recent
kernels KVM_GET_SREGS will return correct one.
--
Gleb.
prev parent reply other threads:[~2013-11-22 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 23:56 Starting a VM using /dev/kvm Jim MacArthur
2013-11-20 17:28 ` Paolo Bonzini
2013-11-21 0:39 ` Jim MacArthur
2013-11-21 7:27 ` Gleb Natapov
2013-11-21 23:57 ` Jim MacArthur
2013-11-22 6:56 ` Gleb Natapov [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=20131122065649.GA13898@redhat.com \
--to=gleb@redhat.com \
--cc=jim@mode7.co.uk \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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 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.