All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: cwc22@cam.ac.uk
Cc: xen-devel@lists.xensource.com
Subject: Re: Unstableness in grant table block drivers
Date: Thu, 14 Apr 2005 10:00:52 -0500	[thread overview]
Message-ID: <20050414150052.GE27571@us.ibm.com> (raw)
In-Reply-To: <eab087540504131904433d4910@mail.gmail.com>

* Christopher Clark <christopher.w.clark@gmail.com> [2005-04-13 21:04]:
Hi,

> The machines you can't get to start domUs, and symptom of not finding
> the root filesystem is exactly what you'd see if your dom0 and domU
> configs don't match; either both or neither need to be using grant
> tables for transport. Your other issues will need more investigation,

I build xen-unstable nightly and install it completely to my test box.
My configs between dom0 and domU are always identicle except for
priviledged domain.

> and a reproducable scenario would be extremely helpful indeed.

My scenario is building the default configs either as UP or with adding
in CONFIG_SMP.  The resule is always, dom0 will boot, domU will not.
domU fails with not finding /dev/console and no root device.

I use loopback device mounts exported as /dev/sda1.

As soon as I turn off CONFIG_XEN_BLKDEV_GRANT in dom0/U configs,
the domU boots properly.

I build with debug=y and I can generate any sort of dump or information
you need to track this down.  Let me know what you need.

--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

  parent reply	other threads:[~2005-04-14 15:00 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
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 [this message]
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=20050414150052.GE27571@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=cwc22@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.