All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Travis <corasian@gmail.com>
Cc: xen@lists.fedoraproject.org, xen-devel@lists.xensource.com
Subject: Re: [Fedora-xen] [Xen-devel] Xen4.1.0 and Fedora15 Block device bug?
Date: Thu, 30 Jun 2011 18:05:54 -0400	[thread overview]
Message-ID: <20110630220554.GD18218@dumpdata.com> (raw)
In-Reply-To: <BANLkTi=g+u_DCZxk7HVY7Q9ricpz752pjg@mail.gmail.com>

On Thu, Jun 30, 2011 at 02:45:42PM -0400, Travis wrote:
> Hi guys,
> 
> I'm an administrator for a small cluster running ganeti2.3.1/xen4.1.0/drbd83
> on centos5.6, with predominantly fedora14 instances. We've been running the
> fedora 14 images pretty well, not many issues. However, I've noticed that in
> an attempt to install fedora 15, the virtualized block devices are
> unrecognized by anaconda. has anyone else seen this or is this a known

Uh, I hadn't tried to install it. How did you install Fedora Core 14 in the past?

  reply	other threads:[~2011-06-30 22:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 18:45 [Fedora-xen] Xen4.1.0 and Fedora15 Block device bug? Travis
2011-06-30 22:05 ` Konrad Rzeszutek Wilk [this message]
2011-07-01  5:29   ` [Fedora-xen] [Xen-devel] " Travis
2011-07-01  6:15     ` Fajar A. Nugraha
2011-07-02  3:50       ` Travis
2011-07-02  4:15         ` Fajar A. Nugraha
2011-07-02  5:32           ` [Fedora-xen] [Xen-devel] " Travis
2011-07-02  6:02           ` Ian Campbell
2011-07-02  6:07             ` [Fedora-xen] [Xen-devel] " Travis
2011-07-02  7:05               ` Travis
2011-07-05 13:52                 ` Konrad Rzeszutek Wilk
2011-07-05 17:54                   ` [Fedora-xen] [Xen-devel] " Travis
2011-07-06 13:32                     ` Konrad Rzeszutek Wilk
2011-07-07 20:58                       ` Konrad Rzeszutek Wilk
2011-07-08  8:25                         ` Fajar A. Nugraha

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=20110630220554.GD18218@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=corasian@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen@lists.fedoraproject.org \
    /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.