All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jody Belka <lists-xen@pimb.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: fs-backend on -unstable
Date: Thu, 26 Mar 2009 21:18:24 +0000	[thread overview]
Message-ID: <20090326211824.GS13428@pimb.org> (raw)
In-Reply-To: <49CBD001.8060109@goop.org>

On Thu, Mar 26, 2009 at 11:57:05AM -0700, Jeremy Fitzhardinge wrote:
> Jody Belka wrote:
> >Ok, by changing from a pvfb vnc inside the stubdom config, to vnc in the
> >master config, I now get output into my qemu-dm log file, and so can see
> >the debug printf's I added in. It also means a msg from qemu is appearing:
> >
> >Could not initialize device 'tap'
> >  
> 
> pvops dom0 doesn't support blktap yet, so you need to use normal blkback 
> for disks for now.

That line's not referring to a block device, it's referring to a qemu -net
parameter.


J

  reply	other threads:[~2009-03-26 21:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090325165439.GH13428@pimb.org>
     [not found] ` <20090325171822.GY5737@const.bordeaux.inria.fr>
     [not found]   ` <20090325175037.GI13428@pimb.org>
     [not found]     ` <20090325180655.GA8031@const.famille.thibault.fr>
     [not found]       ` <20090325181412.GJ13428@pimb.org>
     [not found]         ` <20090325182013.GA13718@const.famille.thibault.fr>
     [not found]           ` <20090325182501.GK13428@pimb.org>
     [not found]             ` <20090325191730.GM13428@pimb.org>
     [not found]               ` <20090325213833.GC13718@const.famille.thibault.fr>
2009-03-25 22:41                 ` fs-backend on -unstable Jody Belka
2009-03-25 22:49                   ` Jeremy Fitzhardinge
2009-03-26  0:02                     ` Jody Belka
2009-03-26  0:05                       ` Jeremy Fitzhardinge
2009-03-26  0:16                         ` Jody Belka
2009-03-26 10:21                           ` Stefano Stabellini
2009-03-26 12:18                             ` Boris Derzhavets
2009-03-26 13:27                             ` Jody Belka
2009-03-26 18:57                               ` Jeremy Fitzhardinge
2009-03-26 21:18                                 ` Jody Belka [this message]
2009-03-26 22:03                                   ` Jeremy Fitzhardinge
2009-03-26 22:41                               ` Jody Belka
2009-03-26  8:32                         ` Boris Derzhavets
2009-03-26 18:39                           ` Jeremy Fitzhardinge
2009-03-27 10:28                             ` Boris Derzhavets
2009-03-26 14:54                         ` Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) Boris Derzhavets
2009-03-26 16:14                           ` Boris Derzhavets
2009-03-27 23:21                             ` Jeremy Fitzhardinge
2009-03-28  8:41                               ` Boris Derzhavets
2009-03-28 10:18                                 ` Boris Derzhavets
2009-03-28 11:45                                   ` Boris Derzhavets
2009-03-28 18:25                                     ` Boris Derzhavets

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=20090326211824.GS13428@pimb.org \
    --to=lists-xen@pimb.org \
    --cc=jeremy@goop.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --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.