From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jody Belka Subject: Re: fs-backend on -unstable Date: Thu, 26 Mar 2009 13:27:06 +0000 Message-ID: <20090326132706.GR13428@pimb.org> References: <20090325182013.GA13718@const.famille.thibault.fr> <20090325182501.GK13428@pimb.org> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <49CB570D.2000101@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: Samuel Thibault , Jeremy Fitzhardinge , Xen-devel List-Id: xen-devel@lists.xenproject.org On Thu, Mar 26, 2009 at 10:21:01AM +0000, Stefano Stabellini wrote: > Jody Belka wrote: > > > Now, the stub domain isn't actually working for me anyway, even on > > non-pvops0, but it is able to talk to the fs-backend at least. To show > > what that looks like, I've attached a couple of emails I sent off-list. > > > > There are some known issues that affect stubdoms at the moment, since > they involve some changes made on qemu upstream I am trying to find a > solution there. 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' Which is coming from within vl.c: for(i = 0;i < nb_net_clients; i++) { if (net_client_parse(net_clients[i]) < 0) exit(1); } The qemu cmdline parameters are being reported as follows: "main" "-d" "23" "-domain-name" "wintest-sd" "-videoram" "4" "-vnc" "192.168.254.135:0" "-vncunused" "-vcpus" "1" "-boot" "c" "-acpi" "-net" "nic,vlan=1,macaddr=aa:00:00:12:23:34,model=e1000" "-net" "tap,vlan=1,ifname=tap23.0,bridge=eth0" Any debugging I could add that could track down the cause of the above error, or is this something you recognize? J