Re: [Xen-devel] Failure to start xend in Xen 3.4.1 Dom0 ( 2.6.31 pvops) on top Ubuntu 9.10 Server

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Sun, Sep 13, 2009 at 10:38:04AM -0700, Boris Derzhavets wrote:
> 
> 
>     
> 
>     In meantime when loading the most recent 2.6.31 pvops kernel under Xen 
> Unstable  on top of Ubuntu 
> 9.10 Server (alpha 4, apt-get update, apt-get upgrade -> grub 1.97~beta2) i 
> get a message:
>  /proc/xen is already mounted on xenfs ( xenfs is busy)
> what causes daemon xend failure to start. Xen-bus appears not to be activated 
> during Dom0 loading. 
> As usual i added to /etc/fstab before loading Xen Host :-
>     none    /proc/xen     xenfs    defaults    0    0
> 
> as did it on 9.04. Might it be a mistake on 9.10 (or alpha bug) ?

Latest xen-unstable contains code to automatically mount xenfs from xend start.

See: http://xenbits.xen.org/xen-unstable.hg?rev/67201ec9ed79

-- Pasi

> Boris.
> 
>     
>   
> --- On Sat, 9/12/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
> 
> From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
> Subject: Re: [Xen-devel] Failure to start xend in Xen 3.4.1 Dom0 ( 2.6.31 
> pvops) on top Ubuntu 9.10 Server
> To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir 
> Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
> Date: Saturday, September 12, 2009, 12:38 PM
> 
> dmesg log for 2.6.31-rc6 is attached.
> Xen-bus activation entries are present in the log.
> 
> --- On Sat, 9/12/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
> 
> From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
> Subject: Re: [Xen-devel] Failure to start xend in Xen 3.4.1 Dom0 ( 2.6.31 
> pvops) on top Ubuntu 9.10 Server
> To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir 
> Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
> Date: Saturday, September 12, 2009, 11:55 AM
> 
> 
>  One more notice.
> 
> Jeremy's  2.6.31-rc6 kernel just several times caused xend failure to start.
> Actually, 2.6.31-rc6  hadn't  problems with supporting Dom0 on top of Ubuntu 
> 9.10 , i.e. xend started almost every time.
> 2.6.29.6 & 2.6.30.2 xenified kernels also don't have any problems with
> xend startup after loading Dom0.
> It seems to me as issue dependent on kernel supporting Dom0, first time  
> raised up for 2.6.31-rc9.
>    On the other hand 2.6.31 works fine under Xen 3.4.1 on top of Ubuntu 9.04 
> Server.
> 
> Xen port to Ubuntu is done every time via tuning Config.mk to place xen 
> folder under /usr/local/lib/phyton2.6/dist-packages.
> 
> Boris.
> 
> --- On Sat, 9/12/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
> 
> From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
> Subject: [Xen-devel] Failure to start xend in Xen 3.4.1 Dom0 ( 2.6.31 pvops) 
> on top Ubuntu 9.10 Server
> To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir 
> Fraser" <keir.fraser@xxxxxxxxxxxxx>
> Date: Saturday, September 12, 2009, 10:13 AM
> 
> Suggestion below has been used to load Dom0 via grub entry:
> 
> menuentry "Xen 3.4 / Ubuntu 9.10 kernel 2.6.31" {
> insmod ext2
> set root=(hd0,13)
> multiboot (hd0,13)/xen-3.4.gz
> module (hd0,13)/vmlinuz-2.6.31
> module (hd0,13)/initrd-2.6.31.img
> }
> 
> Dom0
>  was loaded OK.
> However, /etc/init.d/xend start generates xend.log :-
> 
> [2009-09-12 17:57:48 3372] INFO (SrvDaemon:336) Xend changeset: unavailable..
> [2009-09-12 17:57:49 3372] ERROR (SrvDaemon:349) Exception starting xend 
> ((111, 'Connection refused'))
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", 
> line 341, in run
>     servers = SrvServer.create()
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/server/SrvServer.py", 
> line 251, in create
>    
>  root.putChild('xend', SrvRoot())
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/server/SrvRoot.py", 
> line 40, in __init__
>     self.get(name)
>   File "/usr/local/lib/python2.6/dist-packages/xen/web/SrvDir.py", line 84, 
> in get
>     val = val..getobj()
>   File "/usr/local/lib/python2.6/dist-packages/xen/web/SrvDir.py", line 52, 
> in getobj
>     self.obj = klassobj()
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/server/SrvNode.py", 
> line 30, in __init__
>     self.xn = XendNode.instance()
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendNode..py", line 
> 949, in instance
>     inst.save()
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendNode.py", line 
> 484, in save
>     self.save_networks()
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendNode.py", line 
> 499, in
>  save_networks
>     for network_uuid in XendNetwork.get_all()])
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendBase.py", line 
> 102, in get_record
>     for key in keys])
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendNetwork.py", line 
> 196, in get_VIFs
>     vms = XendDomain.instance().get_all_vms()
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomain.py", line 
> 1736, in instance
>     inst.init()
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomain.py", line 
> 113, in init
>     xstransact.Mkdir(XS_VMROOT)
>   File 
> "/usr/local/lib/python2.6/dist-packages/xen/xend/xenstore/xstransact.py", 
> line 355, in Mkdir
>     complete(path, lambda t: t.mkdir(*args))
>   File 
> "/usr/local/lib/python2.6/dist-packages/xen/xend/xenstore/xstransact.py", 
> line 361, in
>  complete
>     t = xstransact(path)
>   File 
> "/usr/local/lib/python2.6/dist-packages/xen/xend/xenstore/xstransact.py", 
> line 29, in __init__
>     self.transaction = xshandle().transaction_start()
>   File "/usr/local/lib/python2.6/dist-packages/xen/xend/xenstore/xsutil.py", 
> line 18, in xshandle
>     xs_handle = xen.lowlevel.xs.xs()
> Error: (111, 'Connection refused')
> [2009-09-12 17:57:49 3371] INFO (SrvDaemon:220) Xend exited with status 1.
> 
> Boris.
> 
> 
> --- On Fri, 9/11/09, Keir Fraser <keir.fraser@xxxxxxxxxxxxxx> wrote:
> 
> From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
> Subject: Re: [Xen-devel] How to build xen.gz with static built-in command 
> line dom0_mem=1024M ?
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>,
>  "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Date: Friday, September 11, 2009, 7:30 AM
> 
> There is no supported way, as we expect to have a sane bootloader that can
> parse boot args. If youw ant to hack it in, edit the line 'cmdline =
> cmdline_cook(...' in arch/x86/setup.c to read 'cmdline = "my args go here";'
> instead.
> 
>  -- Keir
> 
> On 11/09/2009 10:00, "Boris Derzhavets" <bderzhavets@xxxxxxxxx> wrote:
> 
> > 
> > 
> > 
> > 
> >  
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
> 
> 
> 
>       
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
> 
> 
> 
>       
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel