Re: [Xen-devel] Error during domain creation on xen 4.8

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Jun 13, 2017 at 11:27:27AM -0700, Sarah Newman wrote:
> On 06/13/2017 10:28 AM, Sarah Newman wrote:
> > On 06/13/2017 10:08 AM, Wei Liu wrote:
> >> On Tue, Jun 13, 2017 at 05:56:26PM +0100, Wei Liu wrote:
> >>> On Tue, Jun 13, 2017 at 09:29:22AM -0700, Sarah Newman wrote:
> >>>> Hi,
> >>>>
> >>>> With xen 4.8.1, I got the error message:
> >>>>
> >>>> libxl: error: libxl_dom.c:60:libxl__domain_cpupool: got info for 
> >>>> dom2098, wanted dom2097
> >>>> : No such file or directory
> >>>>
> >>>> This was while creating an HVM domain with a stub domain, probably 
> >>>> concurrent to creating a PV domain. The domains were created as 2098 + 
> >>>> 2099 I
> >>>> believe. I was also using oxenstored.
> >>>
> >>> The xc_domain_getinfolist function is a bit awful to work with.
> >>
> >> To give you a bit more information: that function searches for N domains
> >> starting from the one you specify.
> >>
> >> That the parameter was 2097 but there wasn't dom2097 in Xen, so Xen
> >> returned 2098. The toolstack (correctly) bailed out.
> >>
> >> I'm still a bit baffled at this point. Maybe 2097 crashed?
> >>
> > 
> > It was probably a domain shut down on purpose. Rerunning with -vvv.
> > 
> > --Sarah
> > 
> 
> Could this be happening from the block script? There's a function that uses 
> xenstore (I'm using oxenstored) and checks whether a given block device is
> in use by the dom0 or another guest.
> 
> libxl: debug: libxl_device.c:1157:device_hotplug: calling hotplug script: 
> /etc/xen/scripts/block add
> libxl: debug: libxl_device.c:1158:device_hotplug: extra args:
> libxl: debug: libxl_device.c:1166:device_hotplug: env:
> libxl: debug: libxl_device.c:1173:device_hotplug:       script: 
> /etc/xen/scripts/block
> libxl: debug: libxl_device.c:1173:device_hotplug:       XENBUS_TYPE: vbd
> libxl: debug: libxl_device.c:1173:device_hotplug:       XENBUS_PATH: 
> backend/vbd/2853/268441856
> libxl: debug: libxl_device.c:1173:device_hotplug:       XENBUS_BASE_PATH: 
> backend
> libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to 
> execute: /etc/xen/scripts/block add
> libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch 
> w=0x1ad98f0: deregister unregistered
> libxl: debug: libxl_linux.c:200:libxl__get_hotplug_script_info: num_exec 1, 
> not running hotplug scripts
> libxl: debug: libxl_device.c:1143:device_hotplug: No hotplug script to execute
> libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch 
> w=0x1ad98f0: deregister unregistered
> libxl: error: libxl_dom.c:60:libxl__domain_cpupool: got info for dom2852, 
> wanted dom2851
> : No such file or directory
> libxl: debug: libxl_numa.c:502:libxl__get_numa_candidate: New best NUMA 
> placement candidate found: nr_nodes=1, nr_cpus=20, nr_vcpus=184, 
> free_memkb=151897
> libxl: debug: libxl_numa.c:502:libxl__get_numa_candidate: New best NUMA 
> placement candidate found: nr_nodes=1, nr_cpus=20, nr_vcpus=183, 
> free_memkb=157905
> 

No likely from the block script. The code in question is trying to get
cpupool / NUMA information. Block does neither of those.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel