|
xen-devel
[Xen-devel] Re: fs-backend on -unstable
On Wed, Mar 25, 2009 at 05:05:13PM -0700, Jeremy Fitzhardinge wrote:
> Jody Belka wrote:
> >Ok, had to sort out creating a linux domain, as had nothing I could
> >actually
> >try pv-grub with on the test-box in question :)
> >
> >Anyway, having done so, pv-grub is working fine under pvops0
>
> Hm. If pv-grub starts then that's most of the way to stubdom. Are
> there any other log messages?
>
> Are you trying to start an hvm domain? That's known-problematic. Are
> you having any success at all? Does it work without a stub domain?
Not hvm, no. I try it every so often to see if it's been sorted out, but
here I'm just trying a stub domain.
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.
J
--- Begin Message ---
On Wed, Mar 25, 2009 at 06:25:01PM +0000, Jody Belka wrote:
> On Wed, Mar 25, 2009 at 07:20:13PM +0100, Samuel Thibault wrote:
> > Jody Belka, le Wed 25 Mar 2009 18:14:12 +0000, a écrit :
> > > Yep, although nothing has been displayed by it since it was started:
> > >
> > > jmb@peri:~$ sudo fs-backend
> > > [sudo] password for jmb:
> > > Connection to the xenbus deamon opened successfully.
> > > XS transaction is 132
> > > xenbus_printf (backend/vfs/exports/0/name) <= default.
> >
> > That's a problem. Could you see with Stefano Stabellini? He's the one
> > working on fs-backend at the moment.
>
> Yep, sure thing.
Apologies; it seems that there's some bug somewhere that means fs-backend
doesn't work with a pvops-dom0. I thought I'd tried otherwise, but seems not.
Booting with a non-pvops dom0 gets a bit further, but not much I don't think.
This is the fs-backend output now:
Connection to the xenbus deamon opened successfully.
XS transaction is 3
xenbus_printf (backend/vfs/exports/0/name) <= default.
Path changed backend/vfs/exports/requests
Awaiting next connection.
Path changed backend/vfs/exports/requests/2/0/frontend
Handling connection from dom=2, for export=0
Frontend found at: /local/domain/2/device/vfs/0 (gref=1789, evtchn=5)
Our own dom_id=0
Awaiting next connection.
Awaiting next connection.
Backend consumed: 0 requests
Pushed responces and notify=0
Path changed backend/vfs/exports/requests/2/0/frontend
Awaiting next connection.
And this is the stubdom output:
(XEN) HVM1: HVM Loader
(XEN) HVM1: Detected Xen v3.4-unstable
(XEN) HVM1: CPU speed is 2100 MHz
Bootstrapping...
Xen Minimal OS!
start_info: 0x552000(VA)
nr_pages: 0x2000
shared_inf: 0xcfaf1000(MA)
pt_base: 0x555000(VA)
nr_pt_frames: 0x7
mfn_list: 0x542000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: -d 1
stack: 0x500f40-0x520f40
MM: Init
_text: 0x0(VA)
_etext: 0xfa105(VA)
_erodata: 0x147000(VA)
_edata: 0x14fa48(VA)
stack start: 0x500f40(VA)
_end: 0x541850(VA)
start_pfn: 55f
max_pfn: 2000
Mapping memory range 0x800000 - 0x2000000
setting 0x0-0x147000 readonly
skipped 0x1000
MM: Initialise page allocator for 56b000(56b000)-2000000(2000000)
MM: done
Demand map pfns at 2001000-2002001000.
Heap resides at 2002002000-4002002000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x2001000.
Initialising scheduler
Thread "Idle": pointer: 0x2002002010, stack: 0x590000
Initialising xenbus
Thread "xenstore": pointer: 0x20020027c0, stack: 0x5a0000
Dummy main: start_info=0x521040
Thread "main": pointer: 0x2002002f70, stack: 0x5b0000
[main] Waiting for network.
************************ NETFRONT for device/vif/0 **********
net TX ring size 256
net RX ring size 256
backend at /local/domain/0/backend/vif/2/0
mac is 00:16:3e:0d:4c:f9
**************************
[main] IP c0a8fe87 netmask ffffff00 gateway 0.
[main] TCP/IP bringup begins.
Thread "tcpip_thread": pointer: 0x2002005cb0, stack: 0x6c0000
[tcpip_thread] TCP/IP bringup ends.
[main] Network is ready.
Initing FS fronend(s).
FS export [dom=0, id=0] found
Initialising FS fortend to backend dom 0
Allocating request array for import 0, nr_entries = 128.
Our own id is 2
Backend found at /local/domain/0/backend/vfs/0
Backend ready.
dom vm is at /vm/abc1914e-d0fc-4fec-0e92-f109d204d019
close(0)
close(1)
close(2)
main returned 1
close network: backend at /local/domain/0/backend/vif/2/0
port 5 still bound!
Do_exit called!
base is 0x5bf158 caller is 0xc994a
base is 0x5bf178 caller is 0xcb3af
base is 0x5bf1b8 caller is 0xe69eb
base is 0x5bf1d8 caller is 0x74d4
base is 0x5bfe48 caller is 0xcb327
base is 0x5bffe8 caller is 0x33da
--- End Message ---
--- Begin Message ---
On Wed, Mar 25, 2009 at 10:38:33PM +0100, Samuel Thibault wrote:
> Jody Belka, le Wed 25 Mar 2009 19:17:30 +0000, a écrit :
> > Apologies; it seems that there's some bug somewhere that means fs-backend
> > doesn't work with a pvops-dom0.
>
> It'd be good to report that on xen-unstable.
>
> > Backend found at /local/domain/0/backend/vfs/0
> > Backend ready.
>
> That's better.
>
> > dom vm is at /vm/abc1914e-d0fc-4fec-0e92-f109d204d019
> > close(0)
> > close(1)
> > close(2)
> > main returned 1
>
> That means qemu-dm exited. You should now have a look at qemu's log in
> /var/log/xen
I stopped xend, cleared out /var/log/xen, restarted xend, and then ran the
xm create. Nothing stands out to me immediately, but they're all attached.
J
logs.tgz
Description: GNU Unix tar archive
--- End Message ---
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home