All of lore.kernel.org
 help / color / mirror / Atom feed
From: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Anthony Liguori <aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Alexander Graf <agraf-r27SGEef+tmzQB+pC5nmwQ@public.gmane.org>,
	Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: kvm -kernel option (x86_64)
Date: Wed, 14 Nov 2007 18:19:35 +0200	[thread overview]
Message-ID: <1195057175.3165.2.camel@localhost.localdomain> (raw)
In-Reply-To: <473B1E05.4050808-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>


On Wed, 2007-11-14 at 10:10 -0600, Anthony Liguori wrote:
> Avi Kivity wrote:
> > Alexander Graf wrote:
> >   
> >> Hi,
> >>
> >> I just tried to run a kernel directly using the -kernel option on VMX.  
> >> This worked with the kvm modules in the vanilla 2.6.24 kernel but  
> >> breaks on the recent git. I have not tried any version in between.
> >> This really looks like the x86 emulator is broken.
> >>
> >>   
> >>     
> >
> > May also be userspace guest memory, which changes how memory is allocated.
> >
> >   
> 
> It looks like it broke somewhere between 
> 0fcf487831bbc48e720210c164ca9747b6e99af7 and kvm-52.  It's definitely a 
> qemu issue as I'm currently using that git rev of kvm-userspace and 
> kvm-52 kernel modules and it works just fine.
> 

it is probably the new mappings that we did in qemu,
i will check this.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

      parent reply	other threads:[~2007-11-14 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14 14:55 kvm -kernel option (x86_64) Alexander Graf
     [not found] ` <76F10B2B-18F0-49E7-973C-8C17100ED191-r27SGEef+tmzQB+pC5nmwQ@public.gmane.org>
2007-11-14 15:27   ` Avi Kivity
     [not found]     ` <473B13D0.4010509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-14 16:10       ` Anthony Liguori
     [not found]         ` <473B1E05.4050808-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-11-14 16:19           ` Izik Eidus [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=1195057175.3165.2.camel@localhost.localdomain \
    --to=izike-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=agraf-r27SGEef+tmzQB+pC5nmwQ@public.gmane.org \
    --cc=aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@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.