From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH 2 of 2] Remove Remus kernel extensions (now distributed with pvops kernel)
Date: Tue, 7 Sep 2010 20:03:42 +0300 [thread overview]
Message-ID: <20100907170342.GX2804@reaktio.net> (raw)
In-Reply-To: <20100907170155.GA26457@kremvax.cs.ubc.ca>
On Tue, Sep 07, 2010 at 10:01:55AM -0700, Brendan Cully wrote:
> On Saturday, 04 September 2010 at 12:45, Pasi Kärkkäinen wrote:
> > On Fri, Sep 03, 2010 at 02:29:48PM -0700, Brendan Cully wrote:
> > > # HG changeset patch
> > > # User Brendan Cully <brendan@cs.ubc.ca>
> > > # Date 1283549073 25200
> > > # Node ID 3da9f0de715657ae1d1fa622802564ac845d0be3
> > > # Parent 28b1cd50c43d408c43f89c177b720984168ee196
> > > Remove Remus kernel extensions (now distributed with pvops kernel)
> > >
> > > Note that 2.6.18 doesn't have these extensions, so as of this patch
> > > Remus no longer supports 2.6.18 dom0 (2.6.18 is still the preferred
> > > kernel for domU, since it contains the suspend event channel).
> > >
> >
> > Hmm.. so pvops kernel *does* work for domU?
> > But it's *preferred* to use linux-2.6.18-xen ?
>
> Er, no, not as of the last time I checked. pvops *should* work but it
> has a bug handling suspend_cancel that prevents it from resuming
> correctly after the first checkpoint. So, you're right, 2.6.18 or HVM
> is the only currently working domU configuration.
>
Ok, thanks for the confirmation.
-- Pasi
prev parent reply other threads:[~2010-09-07 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 21:29 [PATCH 0 of 2] Remus: Use kmods in pvops tree instead of building standalone versions Brendan Cully
2010-09-03 21:29 ` [PATCH 1 of 2] Remus: use plug qdisc for network buffering instead of queue Brendan Cully
2010-09-03 21:29 ` [PATCH 2 of 2] Remove Remus kernel extensions (now distributed with pvops kernel) Brendan Cully
2010-09-04 9:45 ` Pasi Kärkkäinen
2010-09-07 17:01 ` Brendan Cully
2010-09-07 17:03 ` Pasi Kärkkäinen [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=20100907170342.GX2804@reaktio.net \
--to=pasik@iki.fi \
--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.