xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Stodden <daniel.stodden@citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	"David P. Quigley" <dpquigl@tycho.nsa.gov>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] pv-grub: fix boot crash when no fb is available
Date: Tue, 6 Apr 2010 15:28:38 -0700	[thread overview]
Message-ID: <1270592918.29145.267.camel@agari.van.xensource.com> (raw)
In-Reply-To: <4BBB88E3.4080309@goop.org>

On Tue, 2010-04-06 at 15:17 -0400, Jeremy Fitzhardinge wrote:
> On 04/06/2010 11:22 AM, David P. Quigley wrote:
> > I'm under the impression that if you just do tap:aio it instantiates a
> > blktap device not a blktap2 device. There are definitely different
> > blktap controller classes in xend which handle entries using tapdisk and
> > ones just using tap.
> >    
> 
> The pvops dom0 doesn't have blktap support, only blktap2 (unless blktap2 
> does a back-compat thing?).  

No blktap1, and no compat layer. It's all blkback instances sitting on a
blktap2 node, which provides a block device node.

The disk I'm running for development purposes is set up as follows:

disk = [ "tap:tapdisk:aio:/var/tmp/lenny.ext,xvda,w" ]

Took me a while to figure the syntax out, not sure if different ones
like yours work too.

> Or maybe it falls back to plain blkback?

Could be... What major number do you see in the physical-device XS node?

That config thing is clearly a nightmare.

Daniel

  reply	other threads:[~2010-04-06 22:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 17:18 [PATCH] pv-grub: fix boot crash when no fb is available Samuel Thibault
2010-04-05 13:40 ` David P. Quigley
2010-04-05 15:16   ` Samuel Thibault
2010-04-05 15:17     ` David P. Quigley
2010-04-05 21:57       ` Samuel Thibault
2010-04-06 15:42         ` David P. Quigley
2010-04-06 18:16           ` Jeremy Fitzhardinge
2010-04-06 18:22             ` David P. Quigley
2010-04-06 19:17               ` Jeremy Fitzhardinge
2010-04-06 22:28                 ` Daniel Stodden [this message]
2010-04-06 21:47           ` Samuel Thibault
2010-04-13 14:55             ` David P. Quigley
2010-04-13 15:12               ` Keir Fraser
2010-04-13 17:16               ` Jeremy Fitzhardinge
2011-04-28 10:56               ` Samuel Thibault

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=1270592918.29145.267.camel@agari.van.xensource.com \
    --to=daniel.stodden@citrix.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=dpquigl@tycho.nsa.gov \
    --cc=jeremy@goop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).