From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Nitin A Kamble <nitin.a.kamble@intel.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: paravirtops kernel and HVM guests
Date: Thu, 02 Apr 2009 20:37:35 -0700 [thread overview]
Message-ID: <49D5847F.304@goop.org> (raw)
In-Reply-To: <1238726501.6208.6.camel@mukti.sc.intel.com>
Nitin A Kamble wrote:
> Jeremy,
> I was trying the latest bits from your paravirtops tree with
> xen-unstable. Dom0 is booting fine in Fedora 10 environment. I am seeing
> page fault handing error while trying to create an HVM guest.
> Is anybody working on the HVM support on top of paravirtops kernel?
>
Yes, that's how it fails at the moment; that debug message is from the
last time I tried to track down what's going wrong, but I haven't
managed to make any progress beyond that. Getting it working is a
fairly high priority; I'll probably have another look at it next week.
J
next prev parent reply other threads:[~2009-04-03 3:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 19:17 Question about x86/mm/gup.c's use of disabled interrupts Jeremy Fitzhardinge
2009-03-18 21:13 ` Avi Kivity
2009-03-18 21:23 ` Jeremy Fitzhardinge
2009-03-18 21:40 ` Avi Kivity
2009-03-18 22:14 ` Jeremy Fitzhardinge
2009-03-18 22:41 ` Avi Kivity
2009-03-18 22:55 ` Jeremy Fitzhardinge
2009-03-18 23:05 ` Avi Kivity
2009-03-18 23:32 ` Jeremy Fitzhardinge
2009-03-19 9:46 ` Avi Kivity
2009-03-19 17:16 ` Jeremy Fitzhardinge
2009-03-19 17:33 ` Avi Kivity
2009-04-03 2:41 ` paravirtops kernel and HVM guests Nitin A Kamble
2009-04-03 3:37 ` Jeremy Fitzhardinge [this message]
[not found] ` <70513aa50903181617r418ec23s744544dccfd812e8@mail.gmail.com>
2009-03-18 23:37 ` Question about x86/mm/gup.c's use of disabled interrupts Jeremy Fitzhardinge
2009-03-19 1:32 ` Nick Piggin
2009-03-19 17:31 ` Jeremy Fitzhardinge
2009-03-20 4:40 ` Paul E. McKenney
2009-03-20 15:38 ` Jeremy Fitzhardinge
2009-03-20 15:57 ` Paul E. McKenney
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=49D5847F.304@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nitin.a.kamble@intel.com \
--cc=xen-devel@lists.xensource.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