From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: fs-backend on -unstable Date: Thu, 26 Mar 2009 15:03:23 -0700 Message-ID: <49CBFBAB.8010605@goop.org> References: <20090325191730.GM13428@pimb.org> <20090325213833.GC13718@const.famille.thibault.fr> <20090325224157.GO13428@pimb.org> <49CAB50A.8040205@goop.org> <20090326000237.GP13428@pimb.org> <49CAC6B9.3020200@goop.org> <20090326001608.GQ13428@pimb.org> <49CB570D.2000101@eu.citrix.com> <20090326132706.GR13428@pimb.org> <49CBD001.8060109@goop.org> <20090326211824.GS13428@pimb.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090326211824.GS13428@pimb.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jody Belka Cc: Samuel Thibault , Xen-devel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org Jody Belka wrote: > 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. Oops, sorry. Too much pattern matching. J