From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Marcial Rion <marcial.rion@swissonline.ch>,
xen-devel@lists.xensource.com,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: xen/next Linux 2.6.32 pv_ops dom0 kernel
Date: Mon, 22 Feb 2010 15:34:28 -0800 [thread overview]
Message-ID: <4B831484.8030909@goop.org> (raw)
In-Reply-To: <20100222232325.GM2761@reaktio.net>
On 02/22/2010 03:23 PM, Pasi Kärkkäinen wrote:
> On Mon, Feb 22, 2010 at 12:27:55PM -0800, Jeremy Fitzhardinge wrote:
>
>> On 02/20/2010 07:29 AM, Pasi Kärkkäinen wrote:
>>
>>> I just tried the latest xen/next 2.6.32 64bit dom0 kernel with Xen 4.0.0-rc4 hypervisor.
>>> It seems to build, boot and work for me.
>>>
>>> I'm able to run PV guests without problems!
>>>
>>>
>> That's great news.
>>
>> What's your config? Are you using pvgrub? What are your block and net
>> devices?
>>
>>
> .config here:
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32-pvops-dom0-xen-next-x86_64
>
I meant your Xen config file.
> I was using pygrub, not pvgrub..
Can you get pvgrub working?
> also I was using phy: backed LVM volumes,
>
Try blktap; tap:aio should work.
>> At the very least pvgrub/minios fails in very obscure ways and needs to
>> give better diagnostics. But there may also be some outright bugs in
>> there which are triggering non-deterministically...
>>
>>
> Ok.. I can try pvgrub after a couple of days when I'm back from travelling
> and have access to my testing equipment.
>
Thanks,
J
prev parent reply other threads:[~2010-02-22 23:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 15:39 Issue with pv_ops Kernel 2.6.31.6 and Xen [yinghai@kernel.org: [PATCH 01/35] x86: fix sci on ioapic 1] Konrad Rzeszutek Wilk
2010-02-13 23:12 ` Marcial Rion
2010-02-16 18:10 ` SOLVED: " Konrad Rzeszutek Wilk
2010-02-16 21:51 ` Jeremy Fitzhardinge
2010-02-17 8:33 ` Pasi Kärkkäinen
2010-02-17 11:56 ` M A Young
2010-02-17 18:53 ` Jeremy Fitzhardinge
2010-02-17 22:35 ` M A Young
2010-02-17 22:56 ` Jeremy Fitzhardinge
2010-02-17 23:24 ` M A Young
2010-02-17 18:52 ` Jeremy Fitzhardinge
2010-02-17 19:07 ` Michael D Labriola
2010-02-17 19:20 ` Pasi Kärkkäinen
2010-02-17 19:36 ` Jeremy Fitzhardinge
2010-02-17 19:41 ` Pasi Kärkkäinen
2010-02-17 19:47 ` Michael D Labriola
2010-02-17 19:55 ` Pasi Kärkkäinen
2010-02-17 19:34 ` Jeremy Fitzhardinge
2010-02-20 15:29 ` xen/next Linux 2.6.32 pv_ops dom0 kernel Pasi Kärkkäinen
2010-02-20 19:55 ` Stefan Kuhne
2010-02-20 20:50 ` Boris Derzhavets
2010-02-20 21:01 ` Boris Derzhavets
2010-02-21 2:02 ` Pasi Kärkkäinen
2010-02-23 18:41 ` Martinx
2010-02-23 19:07 ` Boris Derzhavets
2010-02-22 20:27 ` Jeremy Fitzhardinge
2010-02-22 23:23 ` Pasi Kärkkäinen
2010-02-22 23:34 ` Jeremy Fitzhardinge [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=4B831484.8030909@goop.org \
--to=jeremy@goop.org \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=marcial.rion@swissonline.ch \
--cc=pasik@iki.fi \
--cc=samuel.thibault@ens-lyon.org \
--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.