All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jed Smith <jsmith@linode.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen devel <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Re: [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update
Date: Fri, 21 Aug 2009 10:57:17 -0400	[thread overview]
Message-ID: <4A8EB5CD.6070706@linode.com> (raw)
In-Reply-To: <4A8DEC9C.50207@goop.org>

Jeremy Fitzhardinge wrote:
> But it also sounds like it could be on the Xen side.  Would it be
> possible to try and narrow down where Xen stops breaking?

We can narrow it down to between Xen 3.2.1-rc5 and 3.3.0.  Are you able
to reproduce on Xen 3.2.1-rc5 or earlier?

I have a Linode under 3.2.1-rc5, and you're more than welcome to use it
(I've been reproducing with pv-grub under that hypervisor).  Do you want
credentials to give it a whirl?

-Jed

  reply	other threads:[~2009-08-21 14:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18  0:26 [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update Christopher S. Aker
2009-08-18  4:30 ` Jeremy Fitzhardinge
2009-08-18 14:16   ` Christopher S. Aker
2009-08-18 20:15     ` Jeremy Fitzhardinge
2009-08-18 20:56       ` Jeremy Fitzhardinge
2009-08-20 19:11       ` Jed Smith
2009-08-20 23:31         ` Jeremy Fitzhardinge
2009-08-21  0:13           ` Jed Smith
2009-08-21  0:38             ` Jeremy Fitzhardinge
2009-08-21 14:57               ` Jed Smith [this message]
2009-08-21 16:20                 ` Jeremy Fitzhardinge
2009-08-21 16:30                   ` Jed Smith
2009-08-21 16:16         ` Jeremy Fitzhardinge
2009-08-21 17:02           ` Jed Smith
2009-08-21 17:44             ` Jeremy Fitzhardinge
2009-08-21 16:16     ` Jeremy Fitzhardinge

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=4A8EB5CD.6070706@linode.com \
    --to=jsmith@linode.com \
    --cc=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.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 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.