From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Unstableness in grant table block drivers
Date: Wed, 13 Apr 2005 20:43:32 -0500 [thread overview]
Message-ID: <425DCAC4.6030407@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3B51@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>OK, that's news to us - we haven't seen any problems.
>
>It's been tested with dd's and kernel builds, and wasn't expected to be
>a particularly dangerous change.
>
>How you confirmed that disabling the option fixes your problems? Can you
>give a simple recipe to provoke problems?
>
We've had three different systems lose the ability to start domUs.
Disabling VBD grant tables fixed the problem. The best reproducable
example we have is default config on a domU from today's xen-unstable
snapshot. /dev/console is not accessible and no valid root is found.
In my own case, it was working fairly well and then it just stopped
working. It would die mid-way through boot. Again, disabling VBD
grant-tables fixed the problem. I'm going to look into the problem this
evening and see if I can get you guys a more reproducable scenario.
>It doesn't seem to be destablizing, at least for us. Possibly there's
>been some feature interaction with later checkins.
>
>
Possibly.
>Anyone using the unstable tree should be reading the changelog
>closely...
>
>
I agree. I do, but I don't think a lot of people do. I'm not trying to
give you guys more work to do :-) Just a quick note to xen-devel would
suffice (if you've got an extra second).
Thanks Ian,
Regards,
Anthony Liguori
>Ian
>
>
>
next prev parent reply other threads:[~2005-04-14 1:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 1:16 Unstableness in grant table block drivers Ian Pratt
2005-04-14 1:43 ` Anthony Liguori [this message]
2005-04-14 2:04 ` Christopher Clark
2005-04-14 2:17 ` Kip Macy
2005-04-14 2:25 ` Anthony Liguori
2005-04-14 15:00 ` Ryan Harper
2005-04-14 16:34 ` Christopher Clark
2005-04-14 17:28 ` Ryan Harper
2005-04-15 18:45 ` Christopher Clark
2005-04-15 21:14 ` Ryan Harper
2005-04-15 21:32 ` Kip Macy
2005-04-15 21:41 ` Ryan Harper
2005-04-15 21:46 ` Kip Macy
2005-04-15 21:50 ` Ryan Harper
2005-04-15 21:52 ` Ryan Harper
2005-04-15 22:07 ` Christopher Clark
2005-04-15 22:08 ` Ryan Harper
[not found] <aliguori@us.ibm.com>
2005-04-14 1:18 ` Anthony Liguori
2005-04-14 1:20 ` Steven Hand
2005-04-14 1:46 ` Anthony Liguori
2005-04-14 1:53 ` Kip Macy
2005-04-14 2:27 ` Anthony Liguori
2005-04-14 2:55 ` Kip Macy
[not found] <E1DLu58-0005lx-KR@host-192-168-0-1-bcn-london>
2005-04-14 10:17 ` Ge van Geldorp
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 10:24 Ian Pratt
2005-04-14 10:34 ` Ge van Geldorp
2005-04-15 22:30 Ian Pratt
2005-04-16 1:18 ` Christopher Clark
2005-04-16 1:32 ` Christopher Clark
2005-04-16 3:03 ` David Hopwood
2005-04-16 1:32 Ian Pratt
2005-04-16 15:39 ` Ryan Harper
2005-04-18 16:38 ` Christopher Clark
2005-04-18 16:45 ` Ryan Harper
2005-04-18 20:51 ` Ryan Harper
2005-04-20 18:52 ` Christopher Clark
2005-04-20 19:37 ` Ryan Harper
2005-04-22 18:57 ` Ryan Harper
2005-04-22 19:06 ` Anthony Liguori
2005-05-12 1:50 ` Xiaofeng Ling
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=425DCAC4.6030407@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.