Xen devel - Sep 2013 - xl list shows dom0 name as (null) in Xen 4.2.3

Hello,

Fedora 19 running Xen 4.2.3 rpms, "xl list" after dom0 reboot:

[root@localhost ~]# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
(null)                                       0  1024     8     r-----      16.3


Why is dom0''s name "(null)" ? 
It seems also xenstore is quite empty:

[root@localhost ~]# xenstore-ls
tool = ""
 xenstored = ""

If i start xend, and then run "xl list" again the name is correct:

[root@localhost ~]# systemctl start xend.service
[root@localhost ~]# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  1024     8     r-----      18.2


So xend seems to fix it.. someone else seeing the same behaviour? 
Also xenstore gets a lot of stuff after xend is started.

Am I missing some daemon/script that should be executed at boot time when using
only xl?


[root@localhost ~]# xl info
host                   : localhost.localdomain
release                : 3.11.1-200.fc19.x86_64
version                : #1 SMP Sat Sep 14 15:04:51 UTC 2013
machine                : x86_64
nr_cpus                : 8
max_cpu_id             : 7
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 3392
hw_caps                :
bfebfbff:28100800:00000000:00007f40:77bae3ff:00000000:00000001:00000281
virt_caps              : hvm hvm_directio
total_memory           : 16201
free_memory            : 14958
sharing_freed_memory   : 0
sharing_used_memory    : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 2
xen_extra              : .3
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : placeholder dom0_mem=1024M,max:1024M loglvl=all
guest_loglvl=all
cc_compiler            : gcc (GCC) 4.8.1 20130603 (Red Hat 4.8.1-1)
cc_compile_by          : mockbuild
cc_compile_domain      : phx2.fedoraproject.org
cc_compile_date        : Mon Sep  9 19:18:40 UTC 2013
xend_config_format     : 4



-- Pasi

Friday, September 27, 2013, 8:13:25 PM, you wrote:
> Hello,
> Fedora 19 running Xen 4.2.3 rpms, "xl list" after dom0 reboot:
> [root@localhost ~]# xl list
> Name                                        ID   Mem VCPUs      State  
Time(s)
> (null)                                       0  1024     8     r-----     
16.3
> Why is dom0''s name "(null)" ? 
> It seems also xenstore is quite empty:
> [root@localhost ~]# xenstore-ls
> tool = ""
>  xenstored = ""
> If i start xend, and then run "xl list" again the name is
correct:
> [root@localhost ~]# systemctl start xend.service
> [root@localhost ~]# xl list
> Name                                        ID   Mem VCPUs      State  
Time(s)
> Domain-0                                     0  1024     8     r-----     
18.2
> So xend seems to fix it.. someone else seeing the same behaviour?
Not exactly the same, but sometimes guests end up stuck on shutdown in .. i
thought -d---p- state and name (null).
I haven''t exactly spotted when and why (although it always seem to be
with passthrough domains in my case)

Problem with a domain in the list with name "(null)" that is .. that
the xendomains script  bails out on shutdown before shutting down any guest (i
seems to interpret it literally).
So it would be quite preferable that domain names do not get reset to
"(null)" in any case ..

--
Sander
> Also xenstore gets a lot of stuff after xend is started.
> Am I missing some daemon/script that should be executed at boot time when
using only xl?
> [root@localhost ~]# xl info
> host                   : localhost.localdomain
> release                : 3.11.1-200.fc19.x86_64
> version                : #1 SMP Sat Sep 14 15:04:51 UTC 2013
> machine                : x86_64
> nr_cpus                : 8
> max_cpu_id             : 7
> nr_nodes               : 1
> cores_per_socket       : 4
> threads_per_core       : 2
> cpu_mhz                : 3392
> hw_caps                :
bfebfbff:28100800:00000000:00007f40:77bae3ff:00000000:00000001:00000281
> virt_caps              : hvm hvm_directio
> total_memory           : 16201
> free_memory            : 14958
> sharing_freed_memory   : 0
> sharing_used_memory    : 0
> free_cpus              : 0
> xen_major              : 4
> xen_minor              : 2
> xen_extra              : .3
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler          : credit
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : unavailable
> xen_commandline        : placeholder dom0_mem=1024M,max:1024M loglvl=all
guest_loglvl=all
> cc_compiler            : gcc (GCC) 4.8.1 20130603 (Red Hat 4.8.1-1)
> cc_compile_by          : mockbuild
> cc_compile_domain      : phx2.fedoraproject.org
> cc_compile_date        : Mon Sep  9 19:18:40 UTC 2013
> xend_config_format     : 4

> -- Pasi

On Fri, 2013-09-27 at 21:13 +0300, Pasi Kärkkäinen
wrote:
> 
> Am I missing some daemon/script that should be executed at boot time
> when using only xl? 
xencommons is supposed to start xenstored and initialise it which
includes writing the dom0 name field, regardless of which toolstack you
are using. This has been the case since around 4.1 I think.

Ian.